Migrating schemas v1.4.1 (LTS)

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): As long as the EDB Postgres AI agent is connected to your source database, 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.

Oracle sources

For Oracle sources, schema migration is more complex due to the differences between Oracle and Postgres. Both approaches start the same way: in Migration Portal, where you resolve compatibility issues and convert the schema to be compatible with EDB Postgres Advanced Server.

• Simplified: After resolving incompatibilities in Migration Portal, HM imports the converted schema automatically as part of the migration, applying constraints in the correct order.
• Manual: After resolving incompatibilities in Migration Portal, import the schema into the destination database yourself and manage constraint ordering.

Oracle schema migration

Postgres source databases

Migrating a schema from a Postgres source (PostgreSQL, EDB Postgres Advanced Server, or EDB Postgres Extended Server on-premises or cloud distributions) is more straightforward. Since both the source and the HM-managed destination are based on the same technology, their schemas are already compatible, eliminating the need for conversion.

• Simplified: No manual preparation is required. HM imports the schema automatically as part of the migration.
• Manual: Use standard PostgreSQL tools, such as Migration Toolkit (MTK) or pg_dump, to export your schema from the source database and import it into your HM-managed destination cluster yourself.

Postgres schema migration