Database Migration Service provides flexible continuous migration flows for your homogeneous PostgreSQL to AlloyDB for PostgreSQL migrations. Depending on your database architecture, networking configuration, downtime tolerance, and resource management practices, you can choose from different workflows designed to meet your migration goals. Detailed networking and configuration prerequisites are described in each migration guide.
The following table provides an overview of each migration workflow:
| Migration workflow | Best suited for | Description |
|---|---|---|
| Migrate to a new destination cluster | Standard migrations where you want Database Migration Service to create a clean target cluster tailored for the migration workload. | Database Migration Service automatically creates a new destination AlloyDB for PostgreSQL cluster and primary instance using configuration options that you select, and continuously replicates source schemas and data. |
| Migrate to an existing destination cluster | Scenarios where destination cluster parameters must be pre-configured, custom private IP or VPC configurations are required, or clusters are provisioned through Terraform or infrastructure-as-code (IaC). | Migrate data into an AlloyDB for PostgreSQL cluster that you have already created and configured. The destination cluster must be in a RUNNABLE state and must contain only default system databases (postgres, template0, template1) with no user tables. |
| Use quick-start migrations (Preview) | Rapid setup and streamlined migrations with pgnative replication
and Private Service Connect network attachments to simplify network
configuration.
|
Perform an automated continuous migration using predefined configurations and private connectivity to migrate your PostgreSQL databases to AlloyDB for PostgreSQL. Learn more in About quick-start migrations. |