Use the collaborative project-scoped workspace of Migration Portal in Hybrid Manager (HM) to prepare and migrate schemas in the context of a database migration. HM provides an integration that lets you use the HM console to create a Migration Portal project. In this project, you can add source database schemas preloaded by the EDB Postgres AI agent while performing a database migration.
HM creates a Migration Portal project automatically for every registered source database — Oracle or Postgres, including PostgreSQL, Enterprise Postgres (PGE), and Enterprise Postgres Oracle compatible (EPAS). Alternatively, you can manually create or delete a Migration Portal project. Oracle schemas additionally require compatibility assessment and conversion before migration — see Migrating Oracle schemas for that workflow. Postgres schemas are assumed to be compatible with the destination, so HM passes them through automatically with no manual assessment or conversion step — for Postgres sources, this page is mainly useful for viewing a project or recreating one, for example after a manual deletion or a change to the source schema. See Migrating Postgres schemas for how Postgres schema migration itself works.
To upload and assess externally provided DDL schema files, use the user's workspace.
Prerequisites
Register a source database with HM: Oracle or Postgres. A Migration Portal project is created automatically once the EDB Postgres AI agent finishes loading the schema.
Optional, Oracle sources: To facilitate resolving schema incompatibilities in Migration Portal, the HM administrator must enable and configure the AI Copilot with the AI/LLM of your organization.
Accessing Migration Portal
Use the Migration Portal integration to view, create, or manage a project for either source type:
In the Estate page, select the Migrations tab.
To open the detailed view of the database, select the name of the database you want to migrate.
If you already created a schema migration project for one, several, or all schemas, the HM console displays a link with the name of the project in the Migration Portal Project column. Select the link to open a Migration Portal workspace that contains all the schemas in that project.
If you haven't created a project for your schema migrations yet, select either the global New Migration Portal Project button or the schema-scoped + sign. This selection starts a new workflow to create a Migration Portal project.
Creating a Migration Portal project
If you registered a source database with Hybrid Manager via the EDB Postgres AI agent, a Migration Portal project is created automatically for all the database schemas and dependencies, regardless of whether the source is Oracle or Postgres. It creates a project per registered database (per resource_id established in the beacon-agent.yaml). Take into account that any schemas added post-registration aren't reflected in the Migration Portal project.
If the Migration Portal didn't automatically create projects for your registered databases, create projects manually. This can be the case when:
- The size of the ingested DDL exceeds the default limit of 300 MB.
- The size of the ingested DDL exceeds the limit customized by yourself.
- You disabled the automatic creation of Migration Portal projects.
Creating a Migration Portal project manually
Create Migration Portal projects manually when the automatic project creation is disabled or failed.
In the Estate page, select the Migrations tab.
To open the detailed view of the database, select the name of the database you want to migrate.
In the detailed view of the database, select the Schemas tab.
Select New Migration Portal Project or the the plus sign next to one of the schemas you want to migrate.
In the pop-up window, enter the project details:
- Project name
- Application interface — JDBC, ODBC, .NET, or Other. Oracle sources offer two additional options: OCI and Pro*C.
- Target database version — for Oracle sources, the target EDB Postgres Advanced Server (EPAS) version, 16 to 18; for Postgres sources, the target PostgreSQL version, 16 to 18.
- Description (optional)
- Oracle sources only: Additional settings for the conversion — adding a suffix to make object names unique, using Oracle's default case for schema migration, and assessing the DEFAULT profile.
Select Continue.
Select all the schemas you want to add to this Migration Portal project. You can select only schemas that the EDB Postgres AI agent has ingested successfully and schemas that aren't already part of a different Migration Portal project. You can't add schemas to an existing project later — to migrate additional schemas to the same destination database, create a different project instead.
Tip
Oracle sources: The Dependencies column shows the other schemas the current schema relies on. We recommend grouping a schema with all its dependencies in a single Migration Portal project to ensure that all referenced objects exist in the destination database.
Postgres sources: The schema picker doesn't show the complexity, assessment, or dependency columns, since compatibility assessment doesn't apply.
Select Create New Project.
In the background, this creates a Migration Portal project and loads the source schemas into it for analysis.
After HM finishes loading the schemas and creating a project in Migration Portal, a link is added with the name of the project. Select the link to open Migration Portal.
Deleting a Migration Portal project
When using the project-scoped workspace of Migration Portal, you can delete projects only through the HM console, not through the Migration Portal itself.
From the Estate page, select the Migrations tab.
Select the name of the database you were migrating.
In the database's detailed view, select the Schemas tab. You see a list of schemas and the assigned Migration Portal projects.
Locate the schema assigned to the Migration Portal project you want to delete, and select the + (plus) sign in the same line.
Note
If you're using a project to assess several schemas, deleting the project from any of the assigned schemas deletes the project for all schemas.
In the expanded view, under Actions, select the trash can icon.
Type delete project and select Confirm Delete to permanently delete the project.
Switching to user's workspace
While you're working on schemas in Migration Portal, you can switch to the user's workspace for manual DDL upload.
To do so, select Switch to user's workspace.
However, this workspace doesn't display the schemas you selected during project creation. It serves only as a way to quickly switch between tasks. See Managing external schemas for external DDL for more information.
Related topics
Perform an online or offline migration of the converted schemas to a destination database.
Migration Portal documentation for recommendations and guidelines on how to use the portal.
Control Migration Portal project creation by customizing the maximum size of projects or disabling automatic project creation.