These are the tasks involved in an end-to-end migration from a self-managed Postgres database to a different self-managed Postgres database using the Data Migration Service (DMS) of Hybrid Manager (HM). Because the destination isn't HM-managed, this migration requires two DMS agent instances: a reader to stream changes from the source, and a writer to apply them to the destination.
Configure your auxiliary machine — Configure the machine that hosts both migration agents. This machine acts as the bridge between your Postgres source and HM.
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 reader agent.
Configure the EDB Postgres AI agent — Connect the agent to your source database and to HM to enable schema ingestion and migration assessment.
Prepare a destination database — Create a self-managed Postgres database and configure it with SSL and a CDC migration role to receive the migrated data.
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.
Configure the EDB DMS agent — Create migration credentials, configure the reader agent for your source and the writer agent for your destination, and verify both appear in HM.
Migrate your data — Create and run the data migration in the HM console, monitor its progress, finalize streaming, and apply post-migration constraints.