Migrate your self-managed Postgres database to an HM-managed database v1.4.1 (LTS)

These are the tasks involved in an end-to-end migration from a self-managed Postgres database to a database cluster managed by Hybrid Manager (HM). The process uses two agents: the EDB Postgres AI agent (beacon-agent) to register your Postgres database with HM and ingest schema for assessment, and the EDB DMS agent (cdcagent) to perform the actual data migration.

  1. Configure your auxiliary machine — Configure the machine that hosts both migration agents. This machine acts as the bridge between your Postgres source and HM.

  2. Prepare your source Postgres database — Create the required users and configure your Postgres database for schema ingestion with the EDB Postgres AI agent and data migration with the DMS agent.

  3. Configure the EDB Postgres AI agent — Connect the agent to your source database and to HM to enable schema ingestion and migration assessment.

  4. Prepare a destination database — Create or identify the HM-managed database cluster that will receive the migrated schema and data.

  5. Migrate your schema — Choose between the simplified path, where HM handles schema migration and constraint ordering automatically, or the manual path, where you export, prepare, and import the schema yourself.

  6. Configure the EDB DMS agent — Create migration credentials, configure the DMS agent in reader mode to read changes from your Postgres source, and verify the source appears in HM.

  7. Migrate your data — Create and run the data migration in the HM console, monitor its progress, finalize streaming, and apply post-migration constraints.