What databases and task types are supported by DTS - Data Transmission Service

DTS supports data transmission between RDBMS, NoSQL, and OLAP data sources, including data migration, data synchronization, and change tracking.

Note

For more information about terms such as migration types, synchronization types, and change tracking data types, see Terms.
Cross-region tasks are supported for all data links except when the destination is Function Compute (FC).
For data links where the source or destination is an RDS for MySQL database, Serverless ApsaraDB RDS for MySQL instances are supported. For data links where the source or destination is an RDS for PostgreSQL database, Serverless ApsaraDB RDS for PostgreSQL instances are supported only as a destination. Serverless ApsaraMQ for Kafka instances are not supported.
Cross-account task support depends on the database type and connection type. If supported, the Replicate Data Across Alibaba Cloud Accounts option appears when you configure the source or destination instance. Set it to Yes to create a cross-account task. Configure a task across Alibaba Cloud accounts.
DTS can access ApsaraDB for MyBase instances. Set the Access Method to Alibaba Cloud Instance, then follow the relevant instructions in the tables below.

Data synchronization

Data synchronization replicates data between sources in real time. Typical use cases include active geo-redundancy, geo-disaster recovery, on-premises data disaster recovery, cross-border synchronization, query and report offloading, cloud business intelligence (BI), and real-time data warehousing.

The following tables and the Overview of data synchronization solutions list supported databases, versions, and synchronization types.

Note

If your source database type is not available in the Database Type list for the DTS data synchronization feature, you can use the data shipping feature. For more information, see Data shipping.

Self-managed MySQL or RDS for MySQL

Important

Databases in PolarDB-X 1.0 must be created based on an ApsaraDB RDS for MySQL instance. DTS does not support databases that are created based on PolarDB for MySQL.
If the destination is a PolarDB-X 1.0 instance, schema synchronization and schema initialization are not supported. If the destination is a PolarDB-X 2.0 instance, both are supported.
We recommend using PolarDB-X 2.0 version 5.4.11 or later. For more information, see View and upgrade the engine version of a PolarDB for Xscale instance.

Source database	Destination database	Synchronization type	Synchronization topology	References
self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4 ApsaraDB RDS for MySQL All versions	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4 ApsaraDB RDS for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	Synchronize data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance One-way synchronization between ApsaraDB RDS for MySQL instances Two-way synchronization between MySQL databases Synchronize ApsaraDB RDS for MySQL instances across different Alibaba Cloud accounts
	PolarDB for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	Synchronize ApsaraDB RDS for MySQL to PolarDB for MySQL Two-way synchronization between a MySQL database and a PolarDB for MySQL database
	Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, or 19c	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to a self-managed Oracle database
	PolarDB-X 1.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to PolarDB-X 1.0
	PolarDB-X 2.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to PolarDB-X 2.0
	AnalyticDB for MySQL Versions 2.0 or 3.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to AnalyticDB for MySQL 3.0 Synchronize data from ApsaraDB RDS for MySQL to AnalyticDB for MySQL
	self-managed PostgreSQL Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, or 18.x ApsaraDB RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, or 18	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to ApsaraDB RDS for PostgreSQL
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, or 7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to AnalyticDB for PostgreSQL
	ApsaraMQ for Kafka Versions 0.10.1.0 to 2.x self-managed Kafka Versions 0.10.1.0 to 2.7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to ApsaraMQ for Kafka
	ApsaraDB for ClickHouse Version 20.8 or later	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for MySQL to ApsaraDB for ClickHouse
	DataHub	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to DataHub
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, or 8.x	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to Elasticsearch
	MaxCompute	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to MaxCompute
	Tair Versions 4.0, 5.0, 6.0, or 7.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for MySQL to Tair
	Tablestore	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to Tablestore
	Function Compute Version 2.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to Function Compute
	ApsaraDB for SelectDB	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to ApsaraDB for SelectDB
	ApsaraDB for Lindorm	full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to ApsaraDB for Lindorm
	Doris Version 1.2 or later	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for MySQL to a self-managed Doris database
	ApsaraMQ for RocketMQ 4.x and 5.x series	full data synchronization incremental data synchronization	one-way synchronization	Synchronize ApsaraDB RDS for MySQL to ApsaraMQ for RocketMQ

Source: PolarDB for MySQL

Important

Databases in PolarDB-X 1.0 must be created based on an ApsaraDB RDS for MySQL instance. DTS does not support databases that are created based on PolarDB for MySQL.
If the destination is a PolarDB-X 1.0 instance, schema synchronization and schema initialization are not supported. If the destination is a PolarDB-X 2.0 instance, both are supported.
We recommend using PolarDB-X 2.0 version 5.4.11 or later. For more information, see View and upgrade the engine version of a PolarDB for Xscale instance.

Source database	Destination database	Type	Topology	Documentation
PolarDB for MySQL All versions	PolarDB for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	One-way synchronization between PolarDB for MySQL instances Two-way synchronization between PolarDB for MySQL instances
	self-managed MySQL Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4 ApsaraDB RDS for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	Synchronize data from PolarDB for MySQL to ApsaraDB RDS for MySQL
	PolarDB-X 1.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to PolarDB-X 1.0
	PolarDB-X 2.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to PolarDB-X 2.0
	AnalyticDB for MySQL Version 2.0 or 3.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to AnalyticDB for MySQL 3.0 Synchronize data from PolarDB for MySQL to AnalyticDB for MySQL
	AnalyticDB for PostgreSQL Version 4.3, 6.0, or 7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to AnalyticDB for PostgreSQL
	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 synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to Message Queue for Apache Kafka
	DataHub	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to DataHub
	ApsaraDB for ClickHouse Version 20.8 or later	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to ApsaraDB for ClickHouse
	Elasticsearch Version 5.5, 5.6, 6.x, 7.x, or 8.x	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to Elasticsearch
	MaxCompute	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to MaxCompute
	Oracle (RAC or non-RAC) Version 9i, 10g, 11g, 12c, 18c, or 19c	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to a self-managed Oracle
	ApsaraDB for SelectDB	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to ApsaraDB for SelectDB
	Doris Version 1.2 or later	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to a self-managed Doris
	ApsaraDB for Lindorm	full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from PolarDB for MySQL to ApsaraDB for Lindorm

Source: PolarDB for PostgreSQL

Source	Destination	Synchronization type	Topology	Documentation
PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	self-managed PostgreSQL database Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x ApsaraDB RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	Synchronizing PolarDB for PostgreSQL to ApsaraDB RDS for PostgreSQL Two-way synchronization between PolarDB for PostgreSQL and ApsaraDB RDS for PostgreSQL
	PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	One-way synchronization between PolarDB for PostgreSQL instances Two-way synchronization between PolarDB for PostgreSQL instances
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronizing PolarDB for PostgreSQL to AnalyticDB for PostgreSQL
	Alibaba Cloud SelectDB	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronizing PolarDB for PostgreSQL to Alibaba Cloud SelectDB

PolarDB-X as the source

Important

Databases in PolarDB-X 1.0 must be created based on an ApsaraDB RDS for MySQL instance. DTS does not support databases that are created based on PolarDB for MySQL.
If the destination is a PolarDB-X 1.0 instance, schema synchronization and schema initialization are not supported. If the destination is a PolarDB-X 2.0 instance, both are supported.
We recommend using PolarDB-X 2.0 version 5.4.11 or later. For more information, see View and upgrade the engine version of a PolarDB for Xscale instance.

Source database	Destination database	Synchronization type	Synchronization topology	References
PolarDB-X 1.0	PolarDB-X 1.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize data between PolarDB-X 1.0 instances
	self-managed MySQL Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4 RDS for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to an RDS for MySQL instance
	PolarDB for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to a PolarDB for MySQL cluster
	AnalyticDB for MySQL Version 3.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to AnalyticDB for MySQL 3.0
	DataHub	schema synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to a DataHub project
	AnalyticDB for PostgreSQL Version 4.3, 6.0, or 7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 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 synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to Message Queue for Apache Kafka
	Elasticsearch Version 5.5, 5.6, 6.x, 7.x, or 8.x	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to an Elasticsearch cluster
	PolarDB-X 2.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance
PolarDB-X 2.0	PolarDB-X 2.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	One-way synchronization between PolarDB-X 2.0 instances Two-way synchronization between PolarDB-X 2.0 instances
	self-managed MySQL Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4 RDS for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to an RDS for MySQL instance
	PolarDB for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster
	AnalyticDB for MySQL Version 3.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to AnalyticDB for MySQL 3.0
	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 synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to Message Queue for Apache Kafka
	DataHub	schema synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to a DataHub project
	MaxCompute	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to a MaxCompute project
	AnalyticDB for PostgreSQL Version 4.3, 6.0, or 7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance
	Elasticsearch Version 5.5, 5.6, 6.x, 7.x, or 8.x	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to an Elasticsearch cluster
	Oracle (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to a self-managed Oracle database
	Tablestore	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to a Tablestore instance
	PolarDB-X 1.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to a PolarDB-X 1.0 instance
	Alibaba Cloud SelectDB	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB-X 2.0 instance to an Alibaba Cloud SelectDB instance

PolarDB for PostgreSQL (Compatible with Oracle) as a source

Source database	Destination database	Synchronization type	Synchronization topology	Documentation
PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions	PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization two-way synchronization	One-way synchronization between PolarDB for PostgreSQL (Compatible with Oracle) clusters Two-way synchronization between PolarDB for PostgreSQL (Compatible with Oracle) clusters
	Message Queue for Kafka Versions 0.10.1.0–2.x self-managed Kafka cluster Versions 0.10.1.0–2.7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to Message Queue for Kafka
	AnalyticDB for MySQL cluster Version 3.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to AnalyticDB for MySQL 3.0

Source: Oracle

Important

You can configure this scenario only in the new console.
Use version 5.4.11 or later for the destination PolarDB-X 2.0 instance. To upgrade the instance, see View and update the engine version of a PolarDB for Xscale instance.

Source database	Destination database	Synchronization type	Synchronization topology	References
Self-managed Oracle database (RAC or non-RAC) Version 9i, 10g, 11g, 12c, 18c, or 19c	AnalyticDB for PostgreSQL Version 4.3, 6.0, or 7.0	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to AnalyticDB for PostgreSQL
	DataHub	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to DataHub
	PolarDB-X 2.0	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to PolarDB-X 2.0
	PolarDB for MySQL All versions	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to PolarDB for MySQL
	MaxCompute	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to MaxCompute
	PolarDB for PostgreSQL (Compatible with Oracle) All versions	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to PolarDB for PostgreSQL (Compatible with Oracle)
	ApsaraMQ for Kafka Versions 0.10.1.0 to 2.x	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize a self-managed Oracle database to ApsaraMQ for Kafka

Source: self-managed PostgreSQL or RDS for PostgreSQL

Important

A serverless RDS for PostgreSQL instance can be used as a destination database, but not as a source database.

Source database	Destination database	Synchronization type	Synchronization topology	References
self-managed PostgreSQL Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	self-managed PostgreSQL Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization Two-way synchronization	Two-way synchronization between PostgreSQL databases One-way synchronization between RDS for PostgreSQL instances Synchronize self-managed PostgreSQL to RDS for PostgreSQL
	PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization Two-way synchronization	Synchronize RDS for PostgreSQL to PolarDB for PostgreSQL Configure two-way synchronization between RDS for PostgreSQL and PolarDB for PostgreSQL
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize RDS for PostgreSQL to AnalyticDB for PostgreSQL
	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 RDS for MySQL All versions	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize RDS for PostgreSQL to RDS for MySQL
	PolarDB for PostgreSQL (Compatible with Oracle) All versions	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize self-managed PostgreSQL to PolarDB for PostgreSQL (Compatible with Oracle)
	SelectDB	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize RDS for PostgreSQL to SelectDB

Source: Self-managed or ApsaraDB RDS for SQL Server

Important

The source self-managed SQL Server must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.
The destination self-managed SQL Server must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.
SQL Server clusters and SQL Server Always On availability groups are supported.
If the source database is Azure SQL Database, set the SQL Server Incremental Synchronization Mode parameter to Polling and querying CDC instances for incremental synchronization.
The following are not supported as source databases: self-managed SQL Server version 2005 and ApsaraDB RDS for SQL Server versions 2008 or 2008 R2.
In hybrid log parsing mode, where the SQL Server Incremental Synchronization Mode is set to Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables (Hybrid Log-based Parsing), the following source databases are supported:
- Enterprise or Enterprise Evaluation edition: 2012, 2014, 2016, 2019, 2022, or 2025.
- Standard edition: 2016, 2019, 2022, or 2025.
If the source database is the Web edition of SQL Server, the SQL Server Incremental Synchronization Mode can only be set to Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

Source	Destination	Sync type	Topology	Guide
Self-managed SQL Server Versions 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025 ApsaraDB RDS for SQL Server Versions 2012, 2014, 2016, 2017, 2019, 2022, or 2025	Self-managed SQL Server Versions 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025 ApsaraDB RDS for SQL Server Versions 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data between ApsaraDB RDS for SQL Server instances
	Self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for SQL Server to ApsaraDB RDS for MySQL
	PolarDB for MySQL All versions	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a self-managed SQL Server to PolarDB for MySQL
	AnalyticDB for MySQL Version 3.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for SQL Server to AnalyticDB for MySQL 3.0
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a self-managed SQL Server to AnalyticDB for PostgreSQL Synchronize data from ApsaraDB RDS for SQL Server to AnalyticDB for PostgreSQL
	ApsaraDB RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from a self-managed SQL Server to ApsaraDB RDS for PostgreSQL
	DataHub	schema synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for SQL Server to DataHub

Source: MariaDB

Source	Destination	Sync type	Topology	Documentation
ApsaraDB RDS for MariaDB 10.x A self-managed MariaDB database 10.x, 11.0 to 11.4	ApsaraDB RDS for MariaDB A self-managed MariaDB database	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data between ApsaraDB RDS for MariaDB instances Synchronize data from a self-managed MariaDB database to ApsaraDB RDS for MariaDB
	ApsaraDB RDS for MySQL	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for MariaDB to ApsaraDB RDS for MySQL
	ApsaraDB RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, and 16	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize data from ApsaraDB RDS for MariaDB to ApsaraDB RDS for PostgreSQL

Source: Self-managed or Alibaba Cloud MongoDB

Source	Destination	Sync type	Topology	Guide
Replica set architecture self-managed MongoDB Versions 3.0 to 8.0 Alibaba Cloud MongoDB Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	Replica set or sharded cluster architecture self-managed MongoDB Versions 3.0 to 8.0 Alibaba Cloud MongoDB Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize a replica set to a replica set or sharded cluster
Sharded cluster architecture self-managed MongoDB Versions 3.0 to 8.0 Alibaba Cloud MongoDB Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	Replica set or sharded cluster architecture self-managed MongoDB Versions 3.0 to 8.0 Alibaba Cloud MongoDB Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	schema synchronization full data synchronization incremental data synchronization	one-way synchronization	Synchronize a sharded cluster to a replica set or sharded cluster
Alibaba Cloud MongoDB (sharded cluster architecture) Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	Alibaba Cloud MongoDB (sharded cluster architecture) Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	schema synchronization full data synchronization incremental data synchronization	two-way synchronization	Two-way synchronization between Alibaba Cloud MongoDB sharded clusters
Alibaba Cloud MongoDB (replica set architecture) Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	Alibaba Cloud MongoDB (replica set architecture) Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	schema synchronization full data synchronization incremental data synchronization	two-way synchronization	Two-way synchronization between Alibaba Cloud MongoDB replica sets
Replica set or sharded cluster architecture self-managed MongoDB Versions 3.0 to 8.0 Alibaba Cloud MongoDB Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0	Function Compute Version 2.0	incremental data synchronization	one-way synchronization	Synchronize a MongoDB replica set to Function Compute Synchronize a MongoDB sharded cluster to Function Compute
	Lindorm	full data synchronization incremental data synchronization	one-way synchronization	Synchronize MongoDB to Lindorm
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize MongoDB to AnalyticDB for PostgreSQL
	AnalyticDB for MySQL 3.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize MongoDB to AnalyticDB for MySQL 3.0
	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 Alibaba Cloud RDS for MySQL All versions	full data synchronization incremental data synchronization	one-way synchronization	Synchronize MongoDB to Alibaba Cloud RDS for MySQL
	PolarDB for MySQL All versions	full data synchronization incremental data synchronization	one-way synchronization	Synchronize MongoDB to PolarDB for MySQL
	ApsaraMQ for Kafka Versions 0.10.1.0 to 2.x self-managed Kafka Versions 0.10.1.0 to 2.7.0	full data synchronization incremental data synchronization	one-way synchronization	Synchronize MongoDB to Message Queue for Apache Kafka

Source: Self-managed Redis or Tair (Redis OSS-Compatible)

Important

Redis is a NoSQL database and does not require schema synchronization.
Only two-way synchronization between Tair (Enterprise Edition) instances is supported.
When the source database is a self-managed Redis or a Tair (Redis OSS-Compatible) instance, full data synchronization and incremental data synchronization are supported and collectively displayed as Incremental Data Synchronization.
It supports RDB versions up to 11, corresponding to Redis 7.2.

Source database

Destination database

Type

Topology

References

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 (Redis OSS-Compatible) 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 (Redis OSS-Compatible) instance (cluster, standard, or read/write splitting architecture)

Versions 4.0, 5.0, 6.0, and 7.0

Full data synchronization

Incremental data synchronization

One-way synchronization

Tair (Redis OSS-Compatible) Enterprise Edition instance (cluster, standard, or read/write splitting architecture)

Full data synchronization

Incremental data synchronization

Two-way synchronization

Source: TiDB

Source database

Destination database

Synchronization type

Synchronization topology

Documentation

TiDB

AnalyticDB for MySQL cluster

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize a self-managed TiDB database to an AnalyticDB for MySQL V3.0 cluster

PolarDB-X 2.0 instance

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Coming soon

Source: Db2 for LUW

Important

Db2 for LUW is displayed as DB2 for LUW in the console.
The destination PolarDB-X 2.0 instance should be version 5.4.11 or later. For upgrade instructions, see View and upgrade instance version.

Source database	Destination database	Synchronization type	Synchronization topology	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, 8.0, and 8.4 RDS for MySQL	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize data from Db2 for LUW to an RDS for MySQL instance
	PolarDB for MySQL All versions	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize data from Db2 for LUW to a PolarDB for MySQL cluster
	PolarDB-X 2.0	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize data from Db2 for LUW to a PolarDB-X 2.0 instance
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize data from Db2 for LUW 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 synchronization Full data synchronization Incremental data synchronization	One-way synchronization	Synchronize data from Db2 for LUW to a self-managed Kafka cluster

Source: Db2 for i (AS/400)

Important

The console displays Db2 for i as DB2 for iSeries (AS/400).

Source database

Destination database

Synchronization type

Synchronization topology

Documentation

Db2 for i

Versions 7.3 and 7.4

self-managed MySQL

Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4
ApsaraDB RDS for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Available soon

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Available soon

Source: AnalyticDB for MySQL 3.0

Important

The source AnalyticDB for MySQL 3.0 cluster must run kernel version 3.2.1.0 or later.

Source database

Destination database

Synchronization type

Synchronization topology

Configuration guide

AnalyticDB for MySQL

Version 3.0

AnalyticDB for MySQL

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from AnalyticDB for MySQL 3.0 to AnalyticDB for MySQL 3.0

Source: AnalyticDB for PostgreSQL

Important

The source AnalyticDB for PostgreSQL instance requires kernel version 7.2.1.4 or later.

Source

Destination

Type

Topology

Document

AnalyticDB for PostgreSQL

Version 7.0

AnalyticDB for PostgreSQL

Version 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Data Synchronization Between AnalyticDB for PostgreSQL Instances

AnalyticDB for PostgreSQL

Version 7.0

Message Queue for Apache Kafka

Versions 0.10.1.0 to 2.x

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize Data from an AnalyticDB for PostgreSQL Instance to a Message Queue for Apache Kafka Instance

DMS logical database as a source

Important

A DMS logical database must be created from shards of multiple PolarDB for MySQL clusters.

Source database

Destination database

Synchronization type

Synchronization topology

Configuration document

DMS logical database

AnalyticDB for MySQL

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a DMS logical database to AnalyticDB for MySQL 3.0

Source: AWS database

Source database	Destination database	Synchronization type	Synchronization topology	Configuration document
AWS database	See the console for the latest information.			Use DTS to synchronize data between ApsaraDB RDS and Amazon EC2 over a VPN gateway

Data migration

Data migration moves data between homogeneous or heterogeneous sources. Typical use cases include cloud migration, cross-instance migration, and database sharding and scale-out.

For information about the supported databases, versions, migration types, and configuration documents, see the following tables or Migration scenarios.

Migration from self-managed or RDS for MySQL

Important

A database in a PolarDB-X 1.0 instance must be built on ApsaraDB RDS for MySQL. DTS does not support databases that are built on PolarDB for MySQL.
DTS supports schema migration to PolarDB-X 2.0 instances, but not to PolarDB-X 1.0 instances.
We recommend using PolarDB-X 2.0 version 5.4.11 or later. For instructions on how to upgrade the instance, see View and update the engine version of a PolarDB for Xscale instance.
The new console does not support migrations to AnalyticDB for MySQL 2.0. Use the previous console for this task.

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

Migration scenarios for MariaDB sources

Source database	Destination database	Migration type	Configuration document
RDS for MariaDB 10.x self-managed MariaDB 10.x, 11.0–11.4	RDS for MariaDB self-managed MariaDB	schema migration full data migration incremental data migration	Migrate data between RDS for MariaDB instances Migrate a self-managed MariaDB database to RDS for MariaDB
	RDS for MySQL	schema migration full data migration incremental data migration	Migrate from RDS for MariaDB to RDS for MySQL
	RDS for PostgreSQL Versions 9.4 and 10–18	schema migration full data migration incremental data migration	Migrate from RDS for MariaDB to RDS for PostgreSQL

Migration from ApsaraDB RDS for PPAS

Source database

Destination database

Migration type

Documentation

ApsaraDB RDS for PPAS

All versions

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

Schema migration

Full data migration

Incremental data migration

Migrate data from ApsaraDB RDS for PPAS to PolarDB for PostgreSQL (Compatible with Oracle)

Migration from PolarDB for MySQL

Important

A database in a PolarDB-X 1.0 instance must be based on ApsaraDB RDS for MySQL. DTS does not support this type of instance if its database is based on PolarDB for MySQL.
Schema migration is not supported for PolarDB-X 1.0 instances but is supported for PolarDB-X 2.0 instances.
Use PolarDB-X 2.0 version 5.4.11 or later. For upgrade instructions, see View and update the engine version of a PolarDB for Xscale instance.

Source	Destination	Migration type	Documentation
PolarDB for MySQL cluster All versions	PolarDB for MySQL cluster All versions	Schema migration Full data migration Incremental data migration	Migrate between PolarDB for MySQL clusters
	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance
	PolarDB-X 1.0 instance	Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 1.0 instance
	PolarDB-X 2.0 instance	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 2.0 instance
	AnalyticDB for MySQL cluster Version 3.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL V3.0 cluster
	AnalyticDB for PostgreSQL instance Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance
	ApsaraMQ for Kafka instance Versions 0.10.1.0 to 2.x self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to Kafka
	DataHub project All versions	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to a DataHub project
	ApsaraDB for ClickHouse cluster Version 20.8 or later	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for ClickHouse cluster
	self-managed Oracle database (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 cluster to a self-managed Oracle database
	Elasticsearch cluster 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 cluster to an Elasticsearch cluster
	MaxCompute project	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to a MaxCompute project
	ApsaraDB for SelectDB instance	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for SelectDB instance
	Doris database Version 1.2 or later	Schema migration Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to a self-managed Doris database
	Lindorm instance	Full data migration Incremental data migration	Migrate data from a PolarDB for MySQL cluster to a Lindorm instance

Migration from PolarDB for PostgreSQL (Compatible with Oracle)

Source	Destination	Type	Documentation
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 database (RAC, PDB, or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, or 19c	full data migration incremental data migration	Migrate data from PolarDB for PostgreSQL (Compatible with Oracle) to a self-managed Oracle database
	Message Queue for Apache Kafka Versions 0.10.1.0 to 2.x self-managed Kafka cluster Versions 0.10.1.0 to 2.7.0	schema migration full data migration incremental data migration	Migrate data from PolarDB for PostgreSQL (Compatible with Oracle) to Message Queue for Apache Kafka
	AnalyticDB for MySQL version 3.0	schema migration full data migration incremental data migration	Migrate data from PolarDB for PostgreSQL (Compatible with Oracle) to AnalyticDB for MySQL

Migration from PolarDB-X

Important

You can configure these migration scenarios only in the new DTS console.
Databases in a PolarDB-X 1.0 instance must be created on ApsaraDB RDS for MySQL. DTS does not support databases that are created based on PolarDB for MySQL.
We recommend using PolarDB-X 2.0 version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.

Source	Destination	Migration type	Documentation
PolarDB-X 1.0	PolarDB-X 2.0	schema migration full data migration incremental data migration	Migrate from PolarDB-X 1.0 to PolarDB-X 2.0
	AnalyticDB for MySQL Version 3.0	schema migration full data migration incremental data migration	Migrate from PolarDB-X 1.0 to AnalyticDB for MySQL 3.0
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema migration full data migration incremental data migration	Migrate from PolarDB-X 1.0 to AnalyticDB for PostgreSQL
	DataHub	schema migration incremental data migration	Migrate from PolarDB-X 1.0 to DataHub
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x	schema migration full data migration incremental data migration	Migrate from PolarDB-X 1.0 to Elasticsearch
	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 from PolarDB-X 1.0 to Message Queue for Apache Kafka
	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate from PolarDB-X 1.0 to ApsaraDB RDS for MySQL
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, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to ApsaraDB RDS for MySQL
	PolarDB for MySQL All versions	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to PolarDB for MySQL
	AnalyticDB for MySQL Version 3.0	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to AnalyticDB for MySQL 3.0
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to AnalyticDB for PostgreSQL
	MaxCompute	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to MaxCompute
	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 from PolarDB-X 2.0 to Message Queue for Apache Kafka
	DataHub All versions	schema migration incremental data migration	Migrate from PolarDB-X 2.0 to DataHub
	Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to Elasticsearch
	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 from PolarDB-X 2.0 to a self-managed Oracle database
	Tablestore	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to Tablestore
	PolarDB-X 1.0	full data migration incremental data migration	Migrate from PolarDB-X 2.0 to PolarDB-X 1.0
	ApsaraDB for SelectDB	schema migration full data migration incremental data migration	Migrate from PolarDB-X 2.0 to ApsaraDB for SelectDB

Migration from PolarDB for PostgreSQL

Source database	Destination database	Migration type	Documentation
PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	Schema migration Full data migration Incremental data migration	Migrate data between PolarDB for PostgreSQL clusters
	Self-managed PostgreSQL Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x ApsaraDB RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	Schema migration Full data migration Incremental data migration	Migrate data from PolarDB for PostgreSQL to ApsaraDB RDS for PostgreSQL
	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 PolarDB for PostgreSQL to self-managed Oracle
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	Schema migration Full data migration Incremental data migration	Migrate data from PolarDB for PostgreSQL to AnalyticDB for PostgreSQL
	ApsaraDB for SelectDB	Schema migration Full data migration Incremental data migration	Migrate data from PolarDB for PostgreSQL to ApsaraDB for SelectDB

Migration scenarios from MaxCompute

Source

Destination

Type

Documentation

MaxCompute

All versions

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

Schema migration

Full data migration

Migrate data from MaxCompute to ApsaraDB RDS for MySQL

Migration from OceanBase (MySQL mode)

Source database	Destination database	Migration type	Documentation
ApsaraDB for OceanBase cluster and tenant instances (MySQL mode) OceanBase (MySQL mode) Community Edition	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrating from OceanBase (MySQL mode) to ApsaraDB RDS for MySQL
	PolarDB for MySQL All versions	schema migration full data migration incremental data migration	Migrating from OceanBase (MySQL mode) to PolarDB for MySQL
	Lindorm	full data migration incremental data migration	Migrating from OceanBase (MySQL mode) to Lindorm

Oracle source migration scenarios

Important

A database in a PolarDB-X 1.0 instance must be based on an RDS for MySQL instance. DTS does not support databases based on a PolarDB for MySQL cluster.
Schema migration is not supported for a PolarDB-X 1.0 instance, but is supported for PolarDB-X 2.0 instances.
Your PolarDB-X 2.0 instance should be version 5.4.11 or later. For upgrade instructions, see View and upgrade the engine version of a PolarDB for Xscale instance.

Source	Destination	Migration type	References
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 a self-managed Oracle database to PolarDB for PostgreSQL (Compatible with Oracle) Migrate an Amazon RDS for Oracle database to PolarDB for PostgreSQL (Compatible with Oracle)
	self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c	schema migration full data migration incremental data migration	Migration between self-managed Oracle databases
	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to RDS for MySQL
	PolarDB for MySQL All versions	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to PolarDB for MySQL
	PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to PolarDB for PostgreSQL
	PolarDB-X 1.0 and 2.0	full data migration incremental data migration	Migrate a self-managed Oracle database to PolarDB-X 2.0
	AnalyticDB for MySQL Version 3.0	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to AnalyticDB for MySQL 3.0
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to AnalyticDB for PostgreSQL
	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, 17.x, and 18.x RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to a self-managed PostgreSQL database Migrate a self-managed Oracle database to RDS for PostgreSQL
	Alibaba Cloud 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 a self-managed Oracle database to Alibaba Cloud Message Queue for Apache Kafka
	DataHub All versions	schema migration full data migration incremental data migration	Migrate a self-managed Oracle database to DataHub

Migration from PostgreSQL sources

Important

ApsaraDB RDS for PostgreSQL Serverless is supported only as a destination database, not as a source database.

Source	Destination	Type	References
self-managed PostgreSQL database Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, or 18.x ApsaraDB RDS for PostgreSQL Version 9.4, 10, 11, 12, 13, 14, 15, 16, 17, or 18	self-managed PostgreSQL database Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, or 18.x ApsaraDB RDS for PostgreSQL Version 9.4, 10, 11, 12, 13, 14, 15, 16, 17, or 18	schema migration full data migration incremental data migration	Data migration between ApsaraDB RDS for PostgreSQL instances Migrate data from a self-managed PostgreSQL database to ApsaraDB RDS for PostgreSQL
	PolarDB for PostgreSQL Version 11, 14, 15, 16, 17, or 18	schema migration full data migration incremental data migration	Migrate a self-managed PostgreSQL database to a PolarDB for PostgreSQL cluster
	self-managed MySQL database Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate ApsaraDB RDS for PostgreSQL to ApsaraDB RDS for MySQL
	PolarDB for PostgreSQL (Compatible with Oracle) All versions	schema migration full data migration incremental data migration	Migrate a self-managed PostgreSQL database to PolarDB for PostgreSQL (Compatible with Oracle)
	AnalyticDB for PostgreSQL Version 4.3, 6.0, or 7.0	schema migration full data migration incremental data migration	Migrate a self-managed PostgreSQL database to AnalyticDB for PostgreSQL
	ApsaraDB for SelectDB	schema migration full data migration incremental data migration	Migrate ApsaraDB RDS for PostgreSQL to ApsaraDB for SelectDB

Migration from self-managed or RDS SQL Server

Important

The source self-managed SQL Server must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.
The destination self-managed SQL Server must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, Standard, or Web.
Incremental data migration is not supported if the source self-managed SQL Server is version 2005, or if the source RDS for SQL Server is version 2008 or 2008 R2.
If the source database is Azure SQL Database, set the SQL Server Incremental Synchronization Mode parameter to Polling and querying CDC instances for incremental synchronization.
SQL Server Cluster and SQL Server Always On availability groups are supported.
In hybrid log-based parsing mode (when the SQL Server Incremental Synchronization Mode parameter is set to log-based parsing for non-heap tables and CDC-based incremental synchronization for heap tables), this mode supports the following source databases (including RDS for SQL Server and self-managed SQL Server):
- Enterprise or Enterprise Evaluation: 2012, 2014, 2016, 2019, 2022, or 2025.
- Standard: 2016, 2019, 2022, or 2025.
If the source database is the Web edition of SQL Server, the SQL Server Incremental Synchronization Mode parameter supports only Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

Source	Destination	Migration type	Documentation
self-managed SQL Server Versions 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025 RDS for SQL Server Versions 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025	self-managed SQL Server Versions 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025 RDS for SQL Server Versions 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025	schema migration full data migration incremental data migration	Migrate data between RDS for SQL Server instances Migrate from a self-managed SQL Server to RDS for SQL Server Migrate a self-managed SQL Server to the cloud using a physical gateway Migrate from SQL Server on Azure to RDS for SQL Server Migrate from SQL Server on AWS to RDS for SQL Server
	self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate from RDS for SQL Server to RDS for MySQL
	PolarDB for MySQL All versions	schema migration full data migration incremental data migration	Migrate from RDS for SQL Server to PolarDB for MySQL
	AnalyticDB for MySQL Version 3.0	schema migration full data migration incremental data migration	Migrate from RDS for SQL Server to AnalyticDB for MySQL 3.0
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema migration full data migration incremental data migration	Migrate from a self-managed SQL Server to AnalyticDB for PostgreSQL
	RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18	schema migration full data migration incremental data migration	Migrate from a self-managed SQL Server to RDS for PostgreSQL
	DataHub	schema migration incremental data migration	Migrate from RDS for SQL Server to DataHub

Migration from self-managed or ApsaraDB for MongoDB

Source database

Destination database

Migration type

Configuration document

Standalone architecture

Self-managed MongoDB database
Versions 3.0 to 7.0
ApsaraDB for MongoDB
Version 3.4 or 4.0

Standalone, replica set, or sharded cluster architecture

Self-managed MongoDB database
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 a standalone ApsaraDB for MongoDB instance to an ApsaraDB for MongoDB instance of any architecture

Replica set architecture

Self-managed MongoDB database
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 database
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 a replica set ApsaraDB for MongoDB instance to a replica set or sharded cluster ApsaraDB for MongoDB instance

Sharded cluster architecture

Self-managed MongoDB database
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 database
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 a self-managed sharded cluster MongoDB database to a replica set or sharded cluster ApsaraDB for MongoDB instance

Replica set or sharded cluster architecture

Self-managed MongoDB database
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 ApsaraDB for MongoDB to Lindorm

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to AnalyticDB for PostgreSQL

AnalyticDB for MySQL 3.0

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to AnalyticDB for MySQL 3.0

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

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to ApsaraDB RDS for MySQL

PolarDB for MySQL

All versions

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to PolarDB for MySQL

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

Full data migration

Incremental data migration

Synchronize data from ApsaraDB for MongoDB to Message Queue for Apache Kafka

Migrate from Redis or ApsaraDB for Tair

Important

Redis is a NoSQL database and does not require schema migration.
If the source database is a self-managed Redis instance or an ApsaraDB for Tair (Redis-compatible) instance, both full data migration and incremental data migration are supported. These migration types are presented as Incremental Data Migration.
It supports RDB versions up to 11, corresponding to Redis 7.2.

Source database

Destination database

Migration type

Guide

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
ApsaraDB for Tair (Redis-compatible) 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
ApsaraDB for Tair (Redis-compatible) instance (cluster, standard, or read/write splitting architecture)
Versions 4.0, 5.0, 6.0, and 7.0

Full data migration

Incremental data migration

TiDB as a migration source

Source database	Destination database	Migration type	References
TiDB	self-managed MySQL 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate data from self-managed TiDB to ApsaraDB RDS for MySQL
	PolarDB for MySQL All versions	schema migration full data migration incremental data migration	Migrate data from self-managed TiDB to PolarDB for MySQL
	PolarDB-X 2.0	schema migration full data migration incremental data migration	Documentation coming soon.
	AnalyticDB for MySQL Version 3.0	schema migration full data migration incremental data migration	Migrate data from self-managed TiDB to AnalyticDB for MySQL 3.0

Migration from Db2 for LUW

Important

In the console, Db2 for LUW is displayed as DB2 LUW.
We recommend that the destination PolarDB-X 2.0 instance be version 5.4.11 or later. For upgrade instructions, see View and update the engine version of a PolarDB for Xscale instance.

Source database	Destination database	Migration type	References
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, 8.0, and 8.4 RDS for MySQL All versions	schema migration full data migration incremental data migration	Migrate from Db2 for LUW to RDS for MySQL
	PolarDB-X 2.0	full data migration incremental data migration	Migrate from Db2 for LUW to PolarDB-X 2.0
	AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0	schema migration full data migration incremental data migration	Migrate from Db2 for LUW to AnalyticDB for PostgreSQL
	Message Queue for 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 from Db2 for LUW to Message Queue for Kafka
	PolarDB for MySQL All versions	schema migration full data migration incremental data migration	Migrate from Db2 for LUW to PolarDB for MySQL

Db2 for i (AS/400) migration

Important

In the console, Db2 for i is displayed as DB2 iSeries(AS/400).

Source database

Destination database

Migration type

Documentation

Db2 for i

Versions 7.3 and 7.4

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

Schema migration

Full data migration

Incremental data migration

Available soon

PolarDB for MySQL

All versions

Schema migration

Full data migration

Incremental data migration

Available soon

Migration from Teradata

Important

This task can only be configured on the new console. The data migration instance must be in the China (Shanghai), China (Qingdao), or China (Zhangjiakou) region.

Source database

Destination database

Migration type

Configuration document

Teradata

Version 17 or earlier

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

Schema migration

Full data migration

Migrate data from Teradata to AnalyticDB for PostgreSQL

Migrating from self-managed HBase

Important

This migration can be configured only in the new console.

Source

Destination

Type

Documentation

self-managed HBase

Version 1.x

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

Migrate data from a self-managed HBase instance to AnalyticDB for MySQL V3.0

Migration from AnalyticDB for MySQL V3.0

Note

Incremental data migration requires the source AnalyticDB for MySQL V3.0 cluster to have a kernel version of 3.2.1.0 or later.

Source

Target

Type

Documentation

AnalyticDB for MySQL

V3.0

AnalyticDB for MySQL

V3.0

schema migration

full data migration

incremental data migration

Migrate data between AnalyticDB for MySQL V3.0 clusters

Migration from AnalyticDB for PostgreSQL

Note

For an incremental data migration, the source AnalyticDB for PostgreSQL instance must have kernel version 7.2.1.4 or later.

Source database

Target database

Migration type

References

AnalyticDB for PostgreSQL

Version 7.0

AnalyticDB for PostgreSQL

Version 7.0

schema migration

full data migration

incremental data migration

Migrating data between AnalyticDB for PostgreSQL instances

Migration from third-party clouds

Data Transmission Service (DTS) migrates data from third-party clouds, such as Amazon RDS for MySQL and Amazon RDS for Oracle, to Alibaba Cloud products like ApsaraDB RDS for MySQL.

Source database	Destination database	Type	References
Databases on Microsoft Azure	See the console.		Connect an Azure VNet to an Alibaba Cloud VPC
Amazon RDS for MySQL	ApsaraDB RDS for MySQL	schema migration full data migration incremental data migration	Migrate data from Amazon RDS for MySQL to ApsaraDB RDS for MySQL
Amazon RDS for Oracle	ApsaraDB RDS for MySQL	schema migration full data migration incremental data migration	Migrate data from Amazon RDS for Oracle to ApsaraDB RDS for MySQL
Amazon RDS for PostgreSQL	ApsaraDB RDS for PostgreSQL	schema migration full data migration incremental data migration	Incrementally migrate data from Amazon RDS for PostgreSQL to ApsaraDB RDS for PostgreSQL
Amazon RDS for PostgreSQL	ApsaraDB RDS for PostgreSQL	schema migration full data migration	Fully migrate data from Amazon RDS for PostgreSQL to ApsaraDB RDS for PostgreSQL
Amazon RDS for SQL Server	ApsaraDB RDS for SQL Server	schema migration full data migration	Fully migrate data from Amazon RDS for SQL Server to ApsaraDB RDS for SQL Server
Amazon Aurora MySQL	ApsaraDB RDS for MySQL	schema migration full data migration incremental data migration	Migrate data from Amazon Aurora MySQL to ApsaraDB RDS for MySQL
Amazon Aurora MySQL	PolarDB for MySQL	schema migration full data migration incremental data migration	Migrate data from Amazon Aurora MySQL to PolarDB for MySQL
Amazon Aurora PostgreSQL	ApsaraDB RDS for PostgreSQL	schema migration full data migration	Migrate data from Amazon Aurora PostgreSQL to ApsaraDB RDS for PostgreSQL
MongoDB Atlas	ApsaraDB for MongoDB	full data migration incremental data migration	Migrate data from MongoDB Atlas to ApsaraDB for MongoDB

Note

Data migration can substitute for data synchronization in some scenarios, but they differ in terms of scenarios, supported databases, features, and billing. What are the differences between data migration and data synchronization?
For long-term incremental data migration, use data synchronization, which provides better network stability and more features.

Change tracking

Change tracking retrieves real-time incremental data from databases such as self-managed MySQL and RDS for MySQL. Use cases include cache updates, asynchronous decoupling, cross-source synchronization, and complex ETL processes. You can consume tracked data through SDK, Flink, or other clients. For information about the supported change tracking solutions and configuration documents, see the following table or Change tracking plans.

Source database	Supported types	Documentation
self-managed MySQL Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4 ApsaraDB RDS for MySQL All versions	data update schema update	Track data changes from an ApsaraDB RDS for MySQL instance
PolarDB for MySQL All versions	data update schema update	Create a PolarDB for MySQL change tracking task
PolarDB-X 1.0 Important The underlying databases for PolarDB-X must be based on ApsaraDB RDS for MySQL. DTS does not support databases created on PolarDB for MySQL.	data update schema update	Create a PolarDB-X 1.0 change tracking task
PolarDB-X 2.0 Important The underlying databases for PolarDB-X must be based on ApsaraDB RDS for MySQL. DTS does not support databases created on PolarDB for MySQL.	data update schema update	Create a PolarDB-X 2.0 change tracking task
PolarDB for PostgreSQL (Compatible with Oracle) All versions	data update	Create a change tracking task for PolarDB for PostgreSQL (Compatible with Oracle)
self-managed Oracle (non-RAC architecture) Versions 9i, 10g, and 11g	data update schema update	Create an Oracle change tracking task
ApsaraDB RDS for PostgreSQL Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18 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, 17.x, and 18.x	data update	Create an RDS PostgreSQL change tracking task
Data Management (DMS) logical database Important The logical database must consist of database shards from multiple PolarDB for MySQL instances.	data update	Create a DMS logical database change tracking task
PolarDB for PostgreSQL Versions 11, 14, 15, 16, 17, and 18	data update schema update	Create a change tracking task for PolarDB for PostgreSQL