Migrating schemas Innovation Release

Schema migration is an essential step in database migrations — your schema must be present on the destination database before data migration begins. Hybrid Manager (HM) supports two approaches, regardless of your source database type:

• Simplified (recommended): Once your source database is registered with HM through the EDB Postgres AI agent, HM manages schema migration and constraint ordering for you automatically as part of the data migration. Select Schema and data as the migration scope when creating the migration.

• Manual: Export and import the schema yourself, and handle constraint ordering based on the key structure of each source table.

The tools involved in each approach — and the amount of manual work required — still depend on your source database, since Oracle schemas require conversion and Postgres schemas don't. Every registered database also gets a Migration Portal project automatically, used to track the schema and, for Oracle, convert it — see Migration Portal in HM below for managing that project.

Migrating by source database

• Migrating Oracle schemas — resolve compatibility issues in Migration Portal, then choose the Simplified or Manual import path.

• Migrating Postgres schemas — no conversion needed; choose the Simplified or Manual import path. Postgres refers to all distributions supported by HM: PostgreSQL, Enterprise Postgres (PGE), and Enterprise Postgres Oracle compatible (EPAS).

Migration Portal in HM

Use these topics to manage the Migration Portal project created for your database, regardless of source type:

• Accessing Migration Portal — the difference between the project-scoped and user's workspaces.
• Managing Migration Portal projects — create, view, or delete a Migration Portal project.
• Managing Migration Portal projects for external schemas — assess externally provided DDL files outside the EDB Postgres AI agent workflow.
• Controlling Migration Portal project creation — customize or disable automatic project creation.