When you select a database from the Migrations tab of the Estate page in Hybrid Manager (HM), a detailed view opens. Use this view to plan and execute migrations from external databases. The Schemas and Assessment tabs display different information depending on whether your source database is Postgres or Oracle.
Status
At the top of the database details page, a status selector appears next to the database name. Use it to update the current state of a database migration and track your migration workflow, providing clarity for you and your team members.
You can select from the following statuses:
- Assessing (default)
- Planning
- Decided Not To Migrate
- In Progress
- Done
Schemas
The Schemas tab offers an overview of the schemas found in your connected database. It displays summary metrics for the database, along with a list of schemas where you granted SELECT access on at least one table. Only schemas containing at least one table are displayed.
This information can help you scope your migration effort and effectively plan the migration of your schemas.
Important
The EDB Postgres AI agent detects schema changes to tables and columns while running. However, changes to views or procedures aren't detected until you restart the EDB Postgres AI agent.
Summary cards
- Total schemas for the selected database.
- Total tables for the selected database.
- Total objects for the selected database.
Schema table
- Name: Name of the schema.
- # of Tables: Number of tables in the schema.
- # of Objects: Number of objects in the schema.
- MP Project: Link to the Migration Portal project associated with this schema. Migration Portal projects for Postgres databases are created automatically by the EDB Postgres AI agent.
Selecting a row expands it to show the following:
Schema Compatibility Summary: Shows the compatibility status of schema objects as reported by the Migration Portal, including the count of failed, system-repaired, user-repaired, and passed objects, along with the total object count and passed percentage.
Migration Portal project table: Lists the Migration Portal project associated with the schema, including the project name, target EDB Postgres Advanced Server (EPAS) version, creation date, and available actions.
Summary cards
- Total schemas for the selected database.
- Total tables for the selected database.
- Total objects for the selected database.
- Complexity overview for all schemas, color-coded by complexity (Very Easy, Easy, Medium, Hard, Very Hard).
- Migration level of effort, color-coded by day ranges (0–5, 6–15, 16–25, 26–40, 40+ days), defined by 8-hour working days.
Schema table
- Name: Name of the schema.
- Latest Assessment: Status of the latest assessment. Possible values are Not Started, In Progress, Complete, and Error.
- Last Assessed: Timestamp of the last assessment. The assessment is regenerated or updated if the EDB Postgres AI agent discovers a new schema or an update to an existing one.
- # of Tables: Number of tables in the schema.
- # of Objects: Number of objects in the schema.
- Complexity: Indicates how challenging it will be to convert the schema to EDB Postgres Advanced Server, based on a detailed, object-level analysis. Possible values are Very Easy, Easy, Medium, Hard, and Very Hard. A single schema's complexity may be higher than the overall database complexity, as schema-level analysis is more granular.
- Migration LoE: Indicates how many days it will take to migrate the schema, in 8-hour working days, based on a detailed, object-level analysis.
- Dependencies: The names of any schemas the current schema depends on. Migrate schemas with their dependencies in the same batch (using the same Migration Portal project) to ensure that all referenced objects exist in the destination database.
- MP Project: Link to the Migration Portal project associated with this schema. To create a new project, select + New MP Project above the table and provide the required details. HM creates the project in the background using the Migration Portal project-scoped workspace. You can access it later from the Migration tab.
Selecting a row expands it to show the following:
Schema Compatibility Summary: Shows the compatibility status of schema objects as reported by the Migration Portal, including the count of failed, system-repaired, user-repaired, and passed objects, along with the total object count and passed percentage.
Migration Portal project table: Lists the Migration Portal project associated with the schema, including the project name, target EDB Postgres Advanced Server (EPAS) version, creation date, and available actions. You can delete a project from the Actions column.
Assessment
The Assessment tab provides a migration assessment of your connected database, offering insights to help you scope the effort and plan the migration of your database objects. This section contains a summary of the assessment, including key metrics and detailed breakdowns of the factors that contribute to the generated analysis.
To export the assessment results in .json formatting, select Download Report.
Assessment Details: Shows a high-level migration assessment summary of the database and the key information used in the assessment. For Postgres databases, this includes database name, engine, version, size, object count, table count, and schema count. For Oracle databases, it also includes migration complexity, Oracle database features used, Oracle PL/SQL features used, database migration LoE, number of CPUs, number of schemas assessed, assessment type, and last assessment timestamp.
Extensions Installed: Lists the extensions, including foreign database wrappers, that are installed in the selected database. Check the EDB Postgres extensions documentation to determine which extensions are supported for each EDB supported database prior to migrating your database.
Foreign Servers: Lists the foreign servers created in the selected database and the corresponding Foreign Data Wrapper (FDW) used to configure them. Before migrating, verify that each FDW is compatible with your destination database and that the destination can reach the foreign server.
Foreign Tables: Lists the count of foreign tables in schemas included in the assessment for the selected database, grouped by schema and foreign server.
Tablespaces: Lists the tablespaces in the selected database, including tablespace name, owner, and location.
Tablespace Schema Usage Summary: Lists the non-built-in Postgres tablespaces (excluding pg_default and pg_global) in the selected database, with the count of table, index, or materialized view objects created in those tablespaces per schema included in the assessment.
Schemas Without Full Replica Identity: Lists the count of tables in each schema included in the assessment that don't have a primary key, a unique key, or replica identity set to FULL. This condition impacts the ability to perform change data capture (CDC) streaming data migration.
Installed Procedural Languages: Lists the procedural languages installed in the selected database. If these languages are needed to support application requirements, check the EDB Postgres extensions documentation to determine which languages are supported for use in EDB supported databases prior to migrating your database. Also, if any of the installed languages are untrusted languages, determine if their use complies with security policies and is supported.
Compatibility Summary: Shows a high-level compatibility summary of database features and schema objects, along with other factors that contribute to the overall migration complexity and level of effort assessment. Metrics include total schemas, total assessed PL/SQL objects, compatible objects, incompatible objects and occurrences with known workarounds, incompatible objects and occurrences that need further analysis, Oracle database features used, database size, PL/SQL lines, large objects usage, partition types used, aggregate queries, and SQL count.
Oracle PL/SQL Features Used: Lists all PL/SQL objects that contain Oracle built-in features. For each feature, the table shows the object count, occurrence count, whether it's EPAS compatible (Yes/No), and migration complexity.
Oracle Database Features Used: Lists all Oracle database features in use in the database, including their migration complexity and migration level of effort (LoE) in days.
Incompatible PL/SQL Features in Objects: Lists all incompatible PL/SQL features found in database objects. For each entry, the table shows the schema name, object type (function, package, and so on), object name, the incompatible PL/SQL feature, number of occurrences, and migration complexity.
Migration
The Migration tab helps you perform migration-related tasks for the selected database.
Migration Workflows
Create a Destination: Opens the cluster creation workflow, where you can set up a new database cluster to serve as the destination for your migration. See Creating a database cluster for more guidance.
Migrate Schema(s): Defines a migration that moves both your database schemas and data to your target cluster. Select Migrate Schema(s) to start.
Migrate Data: Transfers your complete data set to a new cluster while maintaining data integrity and minimizing downtime. Select Migrate Data to start. See Choose your migration for end-to-end examples.
Active Migrations
Lists the migrations associated with the selected database. Select View All Migrations to see all migrations across your estate.
The table includes the following columns:
- Name: Name of the migration, linked to the migration details page.
- Source: The external source database being migrated.
- Destination: The target database and cluster.
- Snapshot Type: The type of snapshot used. Possible values are Snapshot and Snapshot + Streaming.
- Scope: The scope of the migration. Possible values are Schema Only, Data Only, and Schema + Data.
- Migration Progress: Shows three metrics for the migration: total tables, snapshot tables completed, and migrated rows. Not shown for schema-only migrations.
- Status: Current status of the migration.