Status of migration scenarios supported by Azure Database Migration Service
Azure Database Migration Service is designed to support different migration scenarios (source/target pairs) for both offline (one-time) and online (continuous sync) migrations. The scenario coverage provided by Azure Database Migration Service is being extended over time. New scenarios are being added on a regular basis. This article identifies migration scenarios currently supported by Azure Database Migration Service and the status (private preview, public preview, or general availability) for each scenario.
Offline versus online migrations
With Azure Database Migration Service, you can do an offline or an online migration. With offline migrations, application downtime begins at the same time that the migration starts. To limit downtime to the time required to cut over to the new environment when the migration completes, use an online migration. It's recommended to test an offline migration to determine whether the downtime is acceptable; if not, do an online migration.
Migration scenario status
The status of migration scenarios supported by Azure Database Migration Service varies with time. Generally, scenarios are first released in private preview. After private preview, the scenario status changes to public preview. Azure Database Migration Service users can try out migration scenarios in public preview directly from the user interface. No sign-up is required. However, migration scenarios in public preview may not be available in all regions and may undergo additional changes before final release. After public preview, the scenario status changes to generally availability. General availability (GA) is the final release status, and the functionality is complete and accessible to all users.
Migration scenario support
The following tables show which migration scenarios are supported when using Azure Database Migration Service.
Note
If a scenario listed as supported below does not appear within the user interface, please contact the Ask Azure Database Migrations alias for additional information.
Offline (one-time) migration support
The following table shows Azure Database Migration Service support for offline migrations.
| Target | Source | Support | Status |
|---|---|---|---|
| Azure SQL DB | SQL Server | ✔ | GA |
| RDS SQL | ✔ | GA | |
| Oracle | X | ||
| Azure SQL DB MI | SQL Server | ✔ | GA |
| RDS SQL | ✔ | GA | |
| Oracle | X | ||
| Azure SQL VM | SQL Server | ✔ | GA |
| Oracle | X | ||
| Azure Cosmos DB | MongoDB | ✔ | GA |
| Azure DB for MySQL - Single Server | MySQL | ✔ | GA |
| RDS MySQL | ✔ | GA | |
| Azure DB for MySQL* | ✔ | GA | |
| Azure DB for MySQL - Flexible Server | MySQL | ✔ | GA |
| RDS MySQL | ✔ | GA | |
| Azure DB for MySQL* | ✔ | GA | |
| Azure DB for PostgreSQL - Single server | PostgreSQL | X | |
| RDS PostgreSQL | X | ||
| Azure DB for PostgreSQL - Flexible server | PostgreSQL | X | |
| RDS PostgreSQL | X | ||
| Azure DB for PostgreSQL - Hyperscale (Citus) | PostgreSQL | X | |
| RDS PostgreSQL | X |
Online (continuous sync) migration support
The following table shows Azure Database Migration Service support for online migrations.
| Target | Source | Support | Status |
|---|---|---|---|
| Azure SQL DB | SQL Server | X | |
| RDS SQL | X | ||
| Oracle | X | ||
| Azure SQL DB MI | SQL Server | ✔ | GA |
| RDS SQL | ✔ | GA | |
| Oracle | X | ||
| Azure SQL VM | SQL Server | X | |
| Oracle | X | ||
| Azure Cosmos DB | MongoDB | ✔ | GA |
| Azure DB for MySQL | MySQL | X | |
| RDS MySQL | X | ||
| Azure DB for PostgreSQL - Single server | PostgreSQL | ✔ | GA |
| Azure DB for PostgreSQL - Single server* | ✔ | GA | |
| RDS PostgreSQL | ✔ | GA | |
| Azure DB for PostgreSQL - Flexible server | PostgreSQL | ✔ | GA |
| Azure DB for PostgreSQL - Single server* | ✔ | GA | |
| RDS PostgreSQL | ✔ | GA | |
| Azure DB for PostgreSQL - Hyperscale (Citus) | PostgreSQL | ✔ | GA |
| RDS PostgreSQL | ✔ | GA |
Note
If your source database is already in Azure PaaS (EG: Azure DB for MySQL or Azure DB for PostgreSQL), choose the corresponding engine when creating your migration activity. For example, if you are migrating from Azure DB for MySQL - Single Server to Azure DB for MySQL - Flexible Server, choose MySQL as the source engine during scenario creation. If you are migrating from Azure DB for PostgreSQL - Single Server to Azure DB for PostgreSQL - Flexible Server, choose PostgreSQL as the source engine during scenario creation.
Next steps
For an overview of Azure Database Migration Service and regional availability, see the article What is the Azure Database Migration Service.
Feedback
Submit and view feedback for