Migrate your self-managed Postgres database to a different self-managed Postgres database v1.3.4

These are all the steps you need to perform a migration from a self-managed Postgres database to a different self-managed Postgres database using the data migration service (DMS) of Hybrid Manager (HM).

Prepare your source database

Prepare your source database for data migration. This involves creating a dedicated user for the migration and altering the database configuration to enable replication features.

1. Prepare the source Postgres database.

Assess the database (optional)

Install and configure the HM agent with your database to obtain observability and monitoring data for your Postgres database. This optional step also provides high-level migration metrics, like schema count and names, table count, and object count.

1. Configure the HM agent to assess your database.

Prepare your destination database

Create a server to host the destination database. Then, alter the destination database's configuration to to enable replication features.

1. Create a destination database in your server.

2. Prepare the destination Postgres database.

Migrate your schema

Handle incompatibilities and transfer your schemas.

1. Handling constraints for schema migration.

2. Migrating schemas.

Migrate your data

Execute the data transfer and complete the final cleanup steps.

1. Create project credentials for the data migration.

2. Configure a DMS agent in reader mode for a data migration.

3. Verify your source database appears in the HM console.

4. Configure a DMS Agent in writer mode for a data migration to a self-managed Postgres database.

5. Verify your destination appears in the HM console.

6. Create and perform the data migration.

7. Finalize the migration (for streaming migrations only).

8. Apply excluded constraints.