Databases supported by the data migration feature - Data Transmission Service

The data migration feature lets you migrate data between homogeneous or disparate data sources. You can use this feature to migrate data to the cloud, move data between Alibaba Cloud instances, or scale out your database. This topic describes the supported databases, versions, and migration types, and provides links to the relevant configuration documents.

Background information

Migration types

Migration type	Description
Schema migration	DTS migrates the schema definitions of objects from the source database to the destination database. These objects include tables, views, triggers, stored procedures, and indexes. For schema migration between heterogeneous databases, DTS converts the syntax of schema definitions based on the source and destination databases. For example, DTS converts the NUMBER data type in Oracle to the DECIMAL data type in MySQL.
Full data migration	DTS migrates all historical data of the objects from the source database to the destination database. If you select only schema migration and full data migration when you configure a data migration task, new data in the source database is not migrated to the destination database. Important To ensure data consistency, do not write new data to the source database during the migration. For a zero-downtime migration, select Schema Migration, Full Data Migration, and Incremental Data Migration when you configure the data migration task.
Incremental data migration	DTS obtains the incremental data change statements for the migration objects from the source database. For example, DTS obtains incremental change statements from the binary logs of a MySQL database. DTS then converts the statements based on the destination database type and executes the statements in the destination database. This process implements real-time migration of incremental data. Note Incremental data migration runs in real time, and the migration task does not automatically stop. You must manually stop or release the migration task. For more information, see Stop a DTS instance and Release a DTS instance.

Differences between data synchronization and data migration

Although data migration can perform some data synchronization tasks, the data synchronization feature offers greater network stability and a wider range of features. For more information, see Differences between data migration and data synchronization.

Important

To configure a migration task between different regions (cross-border or cross-region), the source and destination databases must meet the following conditions:

If the Access Method parameter is set to Alibaba Cloud Instance for the source database, the source database must have a public endpoint.
If the Access Method parameter is not set to Alibaba Cloud Instance for the source database, the destination database must have a public endpoint.

Cross-account data migration

Whether you can perform cross-Alibaba Cloud account migration tasks by setting Replicate Data Across Alibaba Cloud Accounts to Yes for the source or destination instance depends on the database type and connection type. For more information, see Configure a cross-account task.

Source database limitations

The network bandwidth limits and service requirements for the source database are listed in the following table. For more information about other limitations, see the relevant configuration document.

Limitation	Description
Network bandwidth	Supports a network bandwidth of at least 100 MB/s. If the migration instance includes an incremental migration task, make sure that the round-trip time (RT) between the source database and the DTS service, and between the DTS service and the destination database, is less than 2 ms. Otherwise, the performance of the migration instance is affected. For example, if the physical distance between the source database and the DTS service is long, the RT may be much higher than 2 ms. This can cause latency for the migration instance. An example is a database deployed in the Singapore region that connects to DTS through a VPN Gateway in the Hong Kong (China) region.
Service requirements	The total size of logs must be less than 1 TB. The average size of logs per hour must be less than 50 GB. The peak traffic must be less than 15 MB/s. Important By default, DTS pulls the logs of the entire database instance. If the objects that are not synchronized or migrated contain a large number of data changes, the DTS task is also delayed. When you update a large amount of data or modify large fields such as those of the CLOB, BLOB, and LONG types, the DTS task may be delayed. We recommend that you perform such operations in batches or do not perform such operations. Do not frequently delete or modify tables without primary keys. Otherwise, the DTS task may be delayed. Do not frequently perform DDL operations. We recommend that you execute at most 10 DDL statements per second. Otherwise, the DTS task may be delayed. Do not run large transactions, such as a transaction whose total size of logs exceeds 100 GB. Otherwise, the DTS task may fail.

FAQ

Does DTS support Serverless ApsaraDB RDS for MySQL instances?
This is supported.
Does DTS support PolarDB for MySQL serverless clusters?
This is supported.
Does DTS support RDS for PostgreSQL serverless instances?
Currently, they are supported only as destination databases, not as source databases.
Does DTS support instances in ApsaraDB for MyBase?
Yes. DTS can read database instances created in ApsaraDB for MyBase if you set the Access Method to Alibaba Cloud Instance. For configuration details, see the relevant database link document in the tables below.
Note
For example, to migrate data from a self-managed MySQL database to a MySQL instance in ApsaraDB for MyBase, see Migrate data from a self-managed MySQL database to an RDS for MySQL instance.
What is a self-managed database?
A self-managed database is a database instance where the Access Method is not set to Alibaba Cloud Instance when you configure a DTS instance. Self-managed databases include databases from third-party cloud providers, on-premises databases, and databases deployed on ECS instances.
Why is the estimated total number of objects different from the completed number during the full migration phase?
The estimation is based on database statistics, which can be inaccurate. Therefore, the estimated number of objects may differ from the actual number of migrated objects. For an accurate count, refer to the results of the full data verification phase.

Migration solutions

To find the right solution, click the source database in the On This Page section on the right. You can then view the supported versions, migration types, and configuration steps.

Migration solutions for a self-managed MySQL or RDS for MySQL source

Important

Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
Schema migration is not supported when the destination is PolarDB-X 1.0. It is supported when the destination is PolarDB-X 2.0.
Use PolarDB-X 2.0 instances of version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the version of an instance.
Migration solutions with AnalyticDB for MySQL 2.0 as the destination are not available in the new console. You can configure these solutions only in the classic console.

Source database	Destination database	Migration type	Configuration document
Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed MySQL database to an RDS for MySQL instance Migrate data between RDS for MySQL instances
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed MySQL database to a PolarDB for MySQL instance Migrate data from an RDS for MySQL instance to a PolarDB for MySQL instance
	PolarDB-X 1.0	Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a PolarDB-X 1.0 instance
	PolarDB-X 2.0	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a PolarDB-X 2.0 instance
	AnalyticDB for MySQL Versions 2.0 and 3.0	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an AnalyticDB for MySQL 3.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an AnalyticDB for PostgreSQL instance
	Self-managed PostgreSQL Versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, and 17.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an RDS for PostgreSQL instance
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a Message Queue for Apache Kafka instance
	ApsaraDB for ClickHouse cluster Version 20.8 and later	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an ApsaraDB for ClickHouse cluster
	DataHub All versions	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a DataHub instance
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an Elasticsearch instance
	MaxCompute	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a MaxCompute project
	Self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a self-managed Oracle database
	Tair instance (cluster, standard, or read/write splitting architecture) Versions 4.0, 5.0, 6.0, and 7.0	Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a Tair or Redis instance
	Tablestore	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a Tablestore instance
	ApsaraDB for SelectDB	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an ApsaraDB for SelectDB instance
	Lindorm	Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a Lindorm instance
	Doris Version 1.2 and later	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to a self-managed Doris instance
	ApsaraMQ for RocketMQ 4.x and 5.x series	Full data migration Incremental data migration	Migrate data from an RDS for MySQL instance to an ApsaraMQ for RocketMQ instance

Migration solutions for a MariaDB source

Source database	Destination database	Migration type	Configuration document
RDS for MariaDB Self-managed MariaDB	RDS for MariaDB Self-managed MariaDB	Schema migration Full data migration Incremental data migration	Migrate data between RDS for MariaDB instances Migrate data from a self-managed MariaDB database to an RDS for MariaDB instance
	RDS for MySQL	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MariaDB instance to an RDS for MySQL instance
	RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for MariaDB instance to an RDS for PostgreSQL instance

Migration solutions for an RDS PPAS source

Source database

Destination database

Migration type

Configuration document

RDS PPAS

All versions

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

Schema migration

Full data migration

Incremental data migration

Migrate data from an RDS PPAS instance to a PolarDB for PostgreSQL (Compatible with Oracle) cluster

Migration solutions for a PolarDB for MySQL source

Important

Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
Schema migration is not supported when the destination is PolarDB-X 1.0. It is supported when the destination is PolarDB-X 2.0.
Use PolarDB-X 2.0 instances of version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the version of an instance.

Source database	Destination database	Migration type	Configuration document
PolarDB for MySQL All versions	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data between PolarDB for MySQL instances
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to an RDS for MySQL instance
	PolarDB-X 1.0	Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a PolarDB-X 1.0 instance
	PolarDB-X 2.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a PolarDB-X 2.0 instance
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to an AnalyticDB for MySQL 3.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to an AnalyticDB for PostgreSQL instance
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a Kafka instance
	DataHub All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a DataHub instance
	ApsaraDB for ClickHouse cluster Version 20.8 and later	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to an ApsaraDB for ClickHouse cluster
	Self-managed Oracle (RAC, PDB, or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a self-managed Oracle database
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to an Elasticsearch instance
	MaxCompute	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a MaxCompute project
	ApsaraDB for SelectDB	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to an ApsaraDB for SelectDB instance
	Doris Version 1.2 and later	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a self-managed Doris instance
	Lindorm	Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL instance to a Lindorm instance

Migration solutions for a PolarDB for PostgreSQL (Compatible with Oracle) source

Source database	Destination database	Migration type	Configuration document
PolarDB for PostgreSQL (Compatible with Oracle) All versions	PolarDB for PostgreSQL (Compatible with Oracle) All versions	Schema migration Full data migration Incremental data migration	Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) instances
	Self-managed Oracle (RAC, PDB, or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) instance to a self-managed Oracle database
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) instance to a Message Queue for Apache Kafka instance
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) instance to an AnalyticDB for MySQL 3.0 instance

Migration solutions for a PolarDB-X source

Important

You can configure these solutions only in the new console.
Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
Use PolarDB-X 2.0 instances of version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the version of an instance.

Source database	Destination database	Migration type	Configuration document
PolarDB-X 1.0	PolarDB-X 2.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for MySQL 3.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance
	DataHub	Schema migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to a DataHub instance
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to an Elasticsearch instance
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to a Message Queue for Apache Kafka instance
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 1.0 instance to an RDS for MySQL instance
PolarDB-X 2.0	PolarDB-X 2.0	Schema migration Full data migration Incremental data migration	Migrate data between PolarDB-X 2.0 instances
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to an RDS for MySQL instance
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a PolarDB for MySQL instance
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL 3.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance
	MaxCompute	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a MaxCompute project
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a Message Queue for Apache Kafka instance
	DataHub All versions	Schema migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a DataHub instance
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to an Elasticsearch instance
	Self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a self-managed Oracle database
	Tablestore	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a Tablestore instance
	PolarDB-X 1.0	Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to a PolarDB-X 1.0 instance
	ApsaraDB for SelectDB	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB-X 2.0 instance to an ApsaraDB for SelectDB instance

Migration solutions for a PolarDB for PostgreSQL source

Source database	Destination database	Migration type	Configuration document
PolarDB for PostgreSQL Versions 11, 14, 15, 16, and 17	PolarDB for PostgreSQL Versions 11, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data between PolarDB for PostgreSQL instances
	Self-managed PostgreSQL Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, and 17.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL instance to an RDS for PostgreSQL instance
	Self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL instance to a self-managed Oracle database
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL instance to an AnalyticDB for PostgreSQL instance
	ApsaraDB for SelectDB	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for PostgreSQL instance to an ApsaraDB for SelectDB instance

Migration solutions for a MaxCompute source

Source database

Destination database

Migration type

Configuration document

MaxCompute

All versions

Self-managed MySQL
Versions 5.1, 5.5, 5.6, 5.7, and 8.0
RDS for MySQL
All versions

Schema migration

Full data migration

Migrate data from a MaxCompute project to an RDS for MySQL instance

Migration solutions for an OceanBase (MySQL) source

Source database	Destination database	Migration type	Configuration document
ApsaraDB for OceanBase Cluster instances and tenant instances (MySQL) OceanBase (MySQL) Community Edition	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from an OceanBase database (MySQL mode) to an RDS for MySQL instance
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from an OceanBase database (MySQL mode) to a PolarDB for MySQL instance
	Lindorm	Full data migration Incremental data migration	Migrate data from an OceanBase database (MySQL mode) to a Lindorm instance

Migration solutions for an Oracle source

Important

Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
Schema migration is not supported when the destination is PolarDB-X 1.0. It is supported when the destination is PolarDB-X 2.0.
Use PolarDB-X 2.0 instances of version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the version of an instance.

Source database	Destination database	Migration type	Configuration document
Self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	PolarDB for PostgreSQL (Compatible with Oracle) All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a PolarDB for PostgreSQL (Compatible with Oracle) instance Migrate data from an Amazon RDS for Oracle instance to a PolarDB for PostgreSQL (Compatible with Oracle) instance
	Self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	Schema migration Full data migration Incremental data migration	Migrate data between self-managed Oracle databases
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to an RDS for MySQL instance
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a PolarDB for MySQL instance
	PolarDB for PostgreSQL Versions 11, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a PolarDB for PostgreSQL instance
	PolarDB-X 1.0 and 2.0	Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a PolarDB-X 2.0 instance
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to an AnalyticDB for MySQL 3.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance
	Self-managed PostgreSQL Versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, and 17.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a self-managed PostgreSQL database Migrate data from a self-managed Oracle database to an RDS for PostgreSQL instance
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a Message Queue for Apache Kafka instance
	DataHub All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed Oracle database to a DataHub instance

Migration solutions for a self-managed PostgreSQL or RDS for PostgreSQL source

Important

RDS for PostgreSQL serverless instances are not supported as source databases but are supported as destination databases.

Source database	Destination database	Migration type	Configuration document
Self-managed PostgreSQL Versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, and 17.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Self-managed PostgreSQL Versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, and 17.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data between RDS for PostgreSQL instances Migrate data from a self-managed PostgreSQL database to an RDS for PostgreSQL instance
	PolarDB for PostgreSQL Versions 11, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL instance
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for PostgreSQL instance to an RDS for MySQL instance
	PolarDB for PostgreSQL (Compatible with Oracle) All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL (Compatible with Oracle) instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed PostgreSQL database to an AnalyticDB for PostgreSQL instance
	ApsaraDB for SelectDB	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for PostgreSQL instance to an ApsaraDB for SelectDB instance

Migration solutions for a self-managed SQL Server or RDS for SQL Server source

Important

The source self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.
The destination self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.
If the source is a self-managed SQL Server 2005 instance or an RDS for SQL Server 2008 or 2008 R2 instance, incremental data migration is not supported.
When Azure SQL Database is the source database, you must set SQL Server Incremental Synchronization Mode to Polling and querying CDC instances for incremental synchronization.
SQL Server Cluster and SQL Server Always On availability groups are supported.
In hybrid log parsing mode, when SQL Server Incremental Synchronization Mode is set to Parse Logs For Incremental Synchronization For Non-Heap Tables And Use CDC For Incremental Synchronization For Heap Tables, the following source databases are supported:
- Enterprise or Enterprise Evaluation edition: Versions 2012, 2014, 2016, 2019, or 2022.
- Standard edition: Versions 2016, 2019, or 2022.
When the source database is the Web edition of SQL Server, SQL Server Incremental Synchronization Mode only supports Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

Source database	Destination database	Migration type	Configuration document
Self-managed SQL Server Versions 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022 RDS for SQL Server Versions 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022	Self-managed SQL Server Versions 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022 RDS for SQL Server Versions 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022	Schema migration Full data migration Incremental data migration	Migrate data between RDS for SQL Server instances Migrate data from a self-managed SQL Server database to an RDS for SQL Server instance Migrate a self-managed SQL Server database to the cloud over a physical connection Migrate data from a SQL Server instance on Azure to an RDS for SQL Server instance Migrate data from a SQL Server instance on AWS to an RDS for SQL Server instance
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for SQL Server instance to an RDS for MySQL instance
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for SQL Server instance to a PolarDB for MySQL instance
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from an RDS for SQL Server instance to an AnalyticDB for MySQL 3.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed SQL Server database to an AnalyticDB for PostgreSQL instance
	RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed SQL Server database to an RDS for PostgreSQL instance
	DataHub	Schema migration Incremental data migration	Migrate data from an RDS for SQL Server instance to a DataHub instance

Migration solutions for a self-managed MongoDB or ApsaraDB for MongoDB source

Source database

Destination database

Migration type

Configuration document

Standalone architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4 and 4.0

Standalone, replica set, or sharded cluster architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Schema migration

Full data migration

Migrate data from a standalone ApsaraDB for MongoDB instance to an ApsaraDB for MongoDB instance of any architecture

Replica set architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Replica set or sharded cluster architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Schema migration

Full data migration

Incremental data migration

Migrate data from a replica set ApsaraDB for MongoDB instance to a replica set or sharded cluster ApsaraDB for MongoDB instance

Sharded cluster architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Replica set or sharded cluster architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Schema migration

Full data migration

Incremental data migration

Migrate data from a sharded cluster self-managed MongoDB database to a replica set or sharded cluster ApsaraDB for MongoDB instance

Replica set or sharded cluster architecture

Self-managed MongoDB
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Lindorm

Full data migration

Incremental data migration

Migrate data from an ApsaraDB for MongoDB instance to a Lindorm instance

AnalyticDB for PostgreSQL

4.3, 6.0, and 7.0

Full data migration

Incremental data migration

Migrate data from an ApsaraDB for MongoDB instance to an AnalyticDB for PostgreSQL instance

AnalyticDB for MySQL 3.0

Full data migration

Incremental data migration

Migrate data from an ApsaraDB for MongoDB instance to an AnalyticDB for MySQL 3.0 instance

Self-managed MySQL
Versions 5.1, 5.5, 5.6, 5.7, and 8.0
RDS for MySQL
All versions

Full data migration

Incremental data migration

Migrate data from an ApsaraDB for MongoDB instance to an RDS for MySQL instance

PolarDB for MySQL

All versions

Full data migration

Incremental data migration

Migrate data from an ApsaraDB for MongoDB instance to a PolarDB for MySQL instance

Message Queue for Apache Kafka
Versions 0.10.1.0 to 2.x
Self-managed Kafka
Versions 0.10.1.0 to 2.7.0

Full data migration

Incremental data migration

Synchronize data from an ApsaraDB for MongoDB instance to a Message Queue for Apache Kafka instance

Migration solutions for a self-managed Redis or Tair (Redis-compatible) source

Important

Redis is a NoSQL database and does not require schema migration.
If the source is a self-managed Redis or Tair instance, both full data migration and incremental data migration are supported. These are combined into a single migration type called Incremental Data Migration.
DTS supports RDB versions up to 11, which corresponds to Redis 7.2.

Source database

Destination database

Migration type

Configuration document

Self-managed Redis (standalone or cluster architecture)
Versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2
Tair instance (cluster, standard, or read/write splitting architecture)
Versions 4.0, 5.0, 6.0, and 7.0

Self-managed Redis (standalone or cluster architecture)
Versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2
Tair instance (cluster, standard, or read/write splitting architecture)
Versions 4.0, 5.0, 6.0, and 7.0

Full data migration

Incremental data migration

Migration solutions for a TiDB source

Source database	Destination database	Migration type	Configuration document
TiDB	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed TiDB database to an RDS for MySQL instance
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed TiDB database to a PolarDB for MySQL instance
	PolarDB-X 2.0	Schema migration Full data migration Incremental data migration	Documentation is being prepared.
	AnalyticDB for MySQL Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a self-managed TiDB database to an AnalyticDB for MySQL 3.0 instance

Migration solutions for a Db2 for LUW source

Important

Db2 for LUW appears as DB2 LUW in the console.
Use PolarDB-X 2.0 destination instances of version 5.4.11 or later. For information about how to upgrade an instance, see View and upgrade the version of an instance.

Source database	Destination database	Migration type	Configuration document
Db2 for LUW Versions 9.5, 9.7, 10.1, 10.5, 11.1, and 11.5	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, and 8.0 RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a Db2 for LUW database to an RDS for MySQL instance
	PolarDB-X 2.0	Full data migration Incremental data migration	Migrate data from a Db2 for LUW database to a PolarDB-X 2.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x Self-managed Kafka Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a Db2 for LUW database to a Message Queue for Apache Kafka instance
	PolarDB for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a Db2 for LUW database to a PolarDB for MySQL instance

Migration solutions for a Db2 for i (AS/400) source

Important

Db2 for i appears as DB2 iSeries(AS/400) in the console.

Source database

Destination database

Migration type

Configuration document

Db2 for i

Versions 7.3 and 7.4

Self-managed MySQL
Versions 5.1, 5.5, 5.6, 5.7, and 8.0
RDS for MySQL
All versions

Schema migration

Full data migration

Incremental data migration

Documentation is being prepared.

PolarDB for MySQL

All versions

Schema migration

Full data migration

Incremental data migration

Documentation is being prepared.

Migration solutions for a Teradata source

Important

You can configure these solutions only in the new console. The migration instance must be in the Shanghai, Qingdao, or Zhangjiakou region.

Source database

Destination database

Migration type

Configuration document

Teradata

Version 17 and earlier

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

Schema migration

Full data migration

Migrate data from a Teradata database to an AnalyticDB for PostgreSQL instance

Migration solutions for a self-managed HBase source

Important

You can configure these solutions only in the new console.

Source database

Destination database

Migration type

Configuration document

Self-managed HBase

1.x versions

AnalyticDB for MySQL

Version 3.0

Schema migration

Full data migration

Migrate data from a self-managed HBase database to an AnalyticDB for MySQL 3.0 instance

Migration solutions for an AnalyticDB for MySQL 3.0 source

Note

To migrate incremental data, the source AnalyticDB for MySQL 3.0 cluster must be of kernel version 3.2.1.0 or later.

Source database

Destination database

Migration type

Configuration document

AnalyticDB for MySQL

Version 3.0

AnalyticDB for MySQL

Version 3.0

Schema migration

Full data migration

Incremental data migration

Migrate data between AnalyticDB for MySQL 3.0 instances

Migration solutions for an AnalyticDB for MySQL 3.0 source

Note

To migrate incremental data, the source AnalyticDB for PostgreSQL instance must be of kernel version 7.2.1.4 or later.

Source database

Destination database

Migration type

Configuration document

AnalyticDB for PostgreSQL

Version 7.0

AnalyticDB for PostgreSQL

Version 7.0

Schema migration

Full data migration

Incremental data migration

Migrate data between AnalyticDB for PostgreSQL instances

Migration solutions for third-party cloud sources

DTS supports migrating data from third-party clouds, such as Amazon RDS for MySQL and Amazon RDS for Oracle, to Alibaba Cloud products, such as RDS for MySQL.

Source database	Destination database	Migration type	Configuration document
Database on Azure	Subject to the console		Use DTS to migrate data from Azure to Alibaba Cloud RDS over a VPN Gateway connection
Amazon RDS for MySQL	RDS for MySQL	Schema migration Full data migration Incremental data migration	Migrate data from an Amazon RDS for MySQL instance to an Alibaba Cloud RDS for MySQL instance
Amazon RDS for Oracle	RDS for MySQL	Schema migration Full data migration Incremental data migration	Migrate data from an Amazon RDS for Oracle instance to an Alibaba Cloud RDS for MySQL instance
Amazon RDS for PostgreSQL	RDS for PostgreSQL	Schema migration Full data migration Incremental data migration	Incrementally migrate data from an Amazon RDS for PostgreSQL instance to Alibaba Cloud
Amazon RDS for PostgreSQL	RDS for PostgreSQL	Schema migration Full data migration	Perform a full data migration from an Amazon RDS for PostgreSQL instance to Alibaba Cloud
Amazon RDS for SQL Server	RDS for SQL Server	Schema migration Full data migration	Perform a full data migration from an Amazon RDS for SQL Server instance to Alibaba Cloud
Amazon Aurora MySQL	RDS for MySQL	Schema migration Full data migration Incremental data migration	Migrate data from an Amazon Aurora MySQL instance to Alibaba Cloud
Amazon Aurora MySQL	PolarDB for MySQL	Schema migration Full data migration Incremental data migration	Migrate data from an Amazon Aurora MySQL instance to a PolarDB for MySQL instance
Amazon Aurora PostgreSQL	RDS for PostgreSQL	Schema migration Full data migration	Migrate data from an Amazon Aurora PostgreSQL instance to Alibaba Cloud
Atlas MongoDB	ApsaraDB for MongoDB	Full data migration Incremental data migration	Use DTS to migrate data from a MongoDB Atlas database to Alibaba Cloud

Migration solutions for instances under different Alibaba Cloud accounts

Source database

Destination database

Migration type

Configuration document

Source RDS instance

Destination RDS instance

Schema migration

Full data migration

Incremental data migration

Migrate data between RDS instances that belong to different Alibaba Cloud accounts