Accessing Migration Portal v1.3.2

Migration Portal in Hybrid Manager (HM) offers two different workspaces that you access differently depending on how you want to use it.

Project-scoped workspace vs. user's workspace

Deploying HM includes a built-in instance of Migration Portal that has two types of workspaces:

• The project-scoped workspace in the Migration Portal is where you manage Migration Portal projects created with the HM console for schemas loaded by the HM agent.

  This shared portal environment aligns your Migration Portal projects directly with your HM projects. In this shared portal, you can see all Migration Portal projects created by you and other users who are part of the same HM project. You can't, however, see Migration Portal projects from migrations performed in other HM projects.

• The user's workspace in the Migration Portal is where you create and manage migration projects for external schemas that you manually upload for analysis, conversion, and migration.

  This isn't a shared environment. Only you have access to the Migration Portal projects created in this workspace.

This separation allows Migration Portal to cater to different types and scales of migration efforts:

• Organized, large-scale, enterprise-driven projects (project-scoped)
• More flexible, smaller-scale, or individual-driven migrations (user's workspace)

Accessing

A Migration Portal has two type of workspaces for different purposes:

• To create and manage projects for schemas loaded into HM by the HM agent, see Assessing schemas for HM projects. This uses the project-scoped access to Migration Portal.

• To manually upload externally provided DDL files and assess schemas with the Migration Portal, see Assessing schemas for external projects. This uses the user's workspace access to Migration Portal.