All Products
Search

This Product

    Data Transmission Service:Overview of migration solutions

    Document Center

    Data Transmission Service:Overview of migration solutions

    Last Updated:Nov 11, 2025

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

    Background information

    Migration type descriptions

    Migration type

    Description

    Schema migration

    DTS migrates the schema definitions of objects from the source database to the destination database. These objects can include tables, views, triggers, stored procedures, and indexes.

    For schema migration between heterogeneous databases, DTS converts the syntax of the 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 during the migration.

    Important

    To ensure data consistency, do not write new data to the source database during the migration. To achieve a zero-downtime migration, you need to select Schema Migration, Full Data Migration, and Incremental Data Migration when you configure the data migration task.

    Incremental data migration

    DTS obtains the incremental change statements for the objects from the source database. For example, it gets incremental change statements from the binary logging of a MySQL database. DTS then converts the statements based on the destination database type and executes them in the destination database. This process migrates incremental data to the destination database in real time.

    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 in certain scenarios, the data synchronization feature provides better network stability and more features. We recommend using the data synchronization feature to take advantage of these benefits. For more information about the differences, see What are the differences between data migration and data synchronization?.

    Important

    • If you configure a migration instance where the source and destination databases are in 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.

    • If your synchronization or migration task involves cross-border and cross-region operations, ensure that the task bandwidth does not exceed 100 Mbit/s. If your bandwidth exceeds 100 Mbit/s, use a CEN configuration to configure cross-region network bandwidth, and then configure the DTS task.

      Note

      A cross-region or cross-border task is one where the source and destination databases are in different regions. For example, you can configure a task in the DTS console where the source database is an RDS instance in the Singapore region and the destination database is an RDS instance in the China (Hangzhou) region.

    Cross-account data migration

    The ability to create a cross-Alibaba Cloud account migration task (a task where the source or destination database instance has the Replicate Data Across Alibaba Cloud Accounts configuration item and Yes is selected) is determined by the database type and connection type. For more information, see Configure a cross-Alibaba Cloud account task.

    Source database limits

    The following table lists the network bandwidth limits and other requirements for the source database. For a complete list of limitations, see the relevant configuration document.

    Limit

    Description

    Network bandwidth

    • Supports a network bandwidth of at least 100 MB/s.

    • If the migration instance includes an incremental migration task, ensure that the round-trip time (RTT) 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 RTT can be much higher than 2 ms. This can cause latency in the migration instance. An example is a database deployed in the Singapore region that connects to DTS through a VPN deployed in the Hong Kong (China) region.

    Business 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?

      Yes, it does.

    • Does DTS support PolarDB for MySQL serverless clusters?

      This is supported.

    • Does DTS support RDS for PostgreSQL serverless instances?

      Support is currently available for destination databases, but not for source databases.

    • Does DTS support instances in ApsaraDB for MyBase dedicated clusters?

      Yes, DTS can read database instances from ApsaraDB for MyBase if you select Alibaba Cloud Instance as the Access Method. For configuration instructions, see the corresponding database link documents in the table below.

      Note

      For example, to migrate data from a user-created MySQL database to a MySQL instance in ApsaraDB for MyBase, see Migrate a user-created MySQL database to RDS MySQL.

    • What is a self-managed database?

      When you configure a DTS instance, a database instance is considered self-managed if its Access Method is not Alibaba Cloud Instance. Self-managed databases include database instances from third-party clouds, 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 estimated total number of objects and the completed number may differ during the full migration phase. This is because the estimate is based on database performance statistics, which can be inaccurate. To ensure data accuracy, rely on the results from the full verification phase.

    Overview of migration solutions

    To find the supported versions, migration types, and configuration steps for your scenario, click the relevant migration solution for your source database in the In this topic section on the right.

    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. Schema migration is supported when the destination is PolarDB-X 2.0.

    • Use PolarDB-X 2.0 instances of version 5.4.11 or later. To upgrade an instance, see View and upgrade the instance version.

    • 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 old console.

    Source database

    Destination database

    Migration types

    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

    PolarDB for MySQL

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    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 cluster

    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

      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

      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

      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 or later

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to an ApsaraDB for ClickHouse cluster

    DataHub

    DataHub: All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to DataHub

    Elasticsearch

    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 cluster

    MaxCompute

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to MaxCompute

    Self-managed Oracle with RAC or non-RAC architectures

    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

    An ApsaraDB for Tair (compatible with Redis) instance that uses a 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

    SelectDB

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to a SelectDB instance

    Lindorm

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to Lindorm

    Doris

    Version 1.2 or later

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to a self-managed Doris database

    ApsaraMQ for RocketMQ

    Versions 4.x and 5.x

    Full data migration

    Incremental data migration

    Migrate data from an RDS for MySQL instance to ApsaraMQ for RocketMQ

    Migration solutions for a MariaDB source

    Source database

    Destination database

    Migration types

    Configuration document

    • RDS for MariaDB

    • Self-managed MariaDB

    • RDS for MariaDB

    • Self-managed MariaDB

    Schema migration

    Full data migration

    Incremental data migration

    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 types

    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. Schema migration is supported when the destination is PolarDB-X 2.0.

    • Use PolarDB-X 2.0 instances of version 5.4.11 or later. To upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Migration types

    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 clusters

    • 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 cluster to an RDS for MySQL instance

    PolarDB-X 1.0

    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

    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

    Version 3.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL 3.0 cluster

    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 cluster to an AnalyticDB for PostgreSQL instance

    • Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • Self-managed Kafka

      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 cluster to a Kafka instance

    DataHub

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for MySQL cluster to DataHub

    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 (RAC, PDB, or non-RAC)

    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

    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 cluster to an Elasticsearch cluster

    MaxCompute

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for MySQL cluster to MaxCompute

    SelectDB

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for MySQL cluster to a SelectDB instance

    Doris

    Doris: Version 1.2 and later

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for MySQL cluster to a self-managed Doris database

    Lindorm

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for MySQL cluster to Lindorm

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

    Source database

    Destination database

    Migration types

    Configuration document

    PolarDB for PostgreSQL (Compatible with Oracle): All versions

    All versions

    PolarDB for PostgreSQL (Compatible with Oracle): All versions

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) clusters

    Self-managed Oracle (RAC, PDB, or non-RAC)

    9i, 10g, 11g, 12c, 18c, and 19c

    Full data migration

    Incremental data migration

    Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to a self-managed Oracle database

    • Message Queue for Apache Kafka

      Message Queue for Apache Kafka: Versions 0.10.1.0 to 2.x

    • Self-managed Kafka

      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) cluster 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) cluster to an AnalyticDB for MySQL 3.0 cluster

    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. To upgrade an instance, see View and upgrade the instance version.

    Source database

    Destination database

    Migration types

    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 cluster

    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

    Elasticsearch: Versions 5.5, 5.6, 6.x, 7.x, and 8.x

    Database and table schema migration

    Full data migration

    Incremental data migration

    Migrate from PolarDB-X 1.0 to Elasticsearch

    • Alibaba Cloud Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • Self-managed Kafka

      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

    Migration between PolarDB-X 2.0 instances

    • Self-managed MySQL

      Self-managed MySQL: Versions 5.1, 5.5, 5.6, 5.7, and 8.0

    • RDS MySQL

      All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migration from PolarDB-X 2.0 to RDS for MySQL

    PolarDB for MySQL: All versions

    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 is a cloud-native data warehouse.

    Versions 4.3, 6.0, and 7.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate 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

    • Alibaba Cloud Message Queue for Apache Kafka

      Versions 0.10.1.0 through 2.x

    • Self-managed Kafka

      Self-managed Kafka: Versions 0.10.1.0 to 2.7.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate 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

    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)

    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 PolarDB-X 2.0 to self-managed Oracle

    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

    SelectDB

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from PolarDB-X 2.0 to SelectDB

    Migration solutions for PolarDB for PostgreSQL sources

    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

    Migration between PolarDB for PostgreSQL instances

    • Self-managed PostgreSQL

      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

      RDS for PostgreSQL: Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from PolarDB for PostgreSQL to RDS for PostgreSQL

    Self-managed Oracle databases (RAC or non-RAC)

    Versions 9i, 10g, 11g, 12c, 18c, and 19c

    Full data migration

    Incremental data migration

    Migrate from PolarDB for PostgreSQL to self-managed Oracle

    AnalyticDB for PostgreSQL, a cloud-native data warehouse

    Versions 4.3, 6.0, and 7.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from PolarDB for PostgreSQL to AnalyticDB for PostgreSQL

    ApsaraDB for SelectDB

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from PolarDB for PostgreSQL to ApsaraDB for SelectDB

    Migration from MaxCompute

    Source database

    Destination database

    Migration type

    Configuration document

    MaxCompute

    All versions

    • Self-hosted MySQL

      Versions 5.1, 5.5, 5.6, 5.7, and 8.0

    • RDS MySQL

      All versions

    Schema migration

    Full data migration

    Migrate from MaxCompute to RDS MySQL

    Migration solutions for OceanBase (MySQL) sources

    Source database

    Destination database

    Migration type

    Configuration document

    • ApsaraDB for OceanBase

      Cluster 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 from OceanBase (MySQL mode) to RDS for MySQL

    PolarDB for MySQL

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from OceanBase (MySQL mode) to PolarDB for MySQL

    Lindorm

    Full data migration

    Incremental data migration

    Migrate from OceanBase (MySQL mode) to Lindorm

    Migration from Oracle

    Important

    • Databases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not currently support databases that are created based on PolarDB for MySQL.

    • Schema migration is not supported for PolarDB-X 1.0 destinations. Schema migration is supported for PolarDB-X 2.0 destinations.

    • Use PolarDB-X 2.0 instances of version 5.4.11 or later. For more information about how to upgrade, see View and upgrade instance versions.

    Source database

    Destination database

    Migration types

    Configuration documents

    Self-managed Oracle databases (single-instance or RAC)

    Versions 9i, 10g, 11g, 12c, 18c, and 19c

    PolarDB for PostgreSQL (Compatible with Oracle)

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Self-managed Oracle (RAC or non-RAC)

    Versions 9i, 10g, 11g, 12c, 18c, and 19c

    Schema migration

    Full data migration

    Incremental data migration

    Migrate 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 from self-managed Oracle to RDS for MySQL

    PolarDB for MySQL

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed Oracle to PolarDB for MySQL

    PolarDB for PostgreSQL

    Versions 11 and 14-17

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed Oracle to PolarDB for PostgreSQL

    PolarDB-X 1.0 and 2.0

    Full data migration

    Incremental data migration

    Migrate from self-managed Oracle to PolarDB-X 2.0

    AnalyticDB for MySQL

    Version 3.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed Oracle 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 self-managed Oracle to AnalyticDB for PostgreSQL

    • Self-managed PostgreSQL

      Self-managed PostgreSQL: Versions 9.4.8 or 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

      RDS for PostgreSQL: Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17

    Schema migration

    Full data migration

    Incremental data migration

    • Message Queue for Apache Kafka

      Versions 0.10.1.0 to 2.x

    • Self-managed Kafka

      Self-managed Kafka: Versions 0.10.1.0 to 2.7.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed Oracle to Message Queue for Apache Kafka

    DataHub

    DataHub: All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed Oracle to DataHub

    Migration solutions for self-managed PostgreSQL or RDS PostgreSQL

    Important

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

    Source database

    Destination database

    Migration type

    Configuration document

    • Self-managed 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, and 17.x

    • RDS for PostgreSQL

      RDS for PostgreSQL: Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17

    • Self-hosted 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, and 17.x

    • RDS for PostgreSQL

      RDS for PostgreSQL: Versions 9.4, 10, 11, 12, 13, 14, 15, 16, and 17

    Schema migration

    Full data migration

    Incremental data migration

    PolarDB for PostgreSQL

    Versions 11 and 14 through 17

    Schema migration

    Full data migration

    Incremental data migration

    Migrate a self-managed PostgreSQL database to PolarDB for PostgreSQL

    • Self-managed MySQL

      Versions 5.1, 5.5, 5.6, 5.7, and 8.0

    • RDS MySQL

      RDS for MySQL: All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from RDS PostgreSQL to RDS for MySQL

    PolarDB for PostgreSQL (Compatible with Oracle): All versions

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from a self-managed PostgreSQL database to PolarDB for PostgreSQL (Compatible with Oracle)

    AnalyticDB for PostgreSQL

    Versions 4.3, 6.0, and 7.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from a self-managed PostgreSQL database to AnalyticDB for PostgreSQL

    ApsaraDB for SelectDB

    Schema migration

    Full data migration

    Incremental data migration

    Migration from RDS PostgreSQL to SelectDB

    Migration solutions for self-managed SQL Server or RDS SQL Server sources

    Important

    • The supported editions for self-managed SQL Server sources are Enterprise, Developer, Enterprise Evaluation, Standard, and Web.

    • The supported editions for self-managed SQL Server destinations are Enterprise, Developer, Enterprise Evaluation, Standard, and Web.

    • Incremental data migration is not supported if the source is a self-managed SQL Server 2005 instance or an RDS SQL Server 2008 or 2008 R2 instance.

    • If the source database is Azure SQL Database, set SQL Server Incremental Synchronization Mode to Polling and querying CDC instances for incremental synchronization.

    • SQL Server clusters and SQL Server Always On availability groups are supported.

    • The following source database versions are supported when you use the hybrid log parsing mode. To use this mode, set SQL Server Incremental Synchronization Mode to Use Log Parsing For Incremental Synchronization Of Non-Heap Tables And CDC For Incremental Synchronization Of Heap Tables. This mode is supported for RDS SQL Server and self-managed SQL Server sources:

      • Enterprise or Enterprise Evaluation edition: 2012, 2014, 2016, 2019, or 2022.

      • Standard edition: 2016, 2019, or 2022.

    • If the source is a Web edition of SQL Server, SQL Server Incremental Synchronization Mode supports only 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

      Self-managed SQL Server: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    • RDS SQL Server

      RDS SQL Server: 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    • Self-Managed SQL Server

      Self-managed SQL Server: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    • RDS SQL Server

      RDS SQL Server: 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022

    Schema migration

    Full data migration

    Incremental data migration

    • 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 SQL Server instance to an RDS for MySQL instance

    PolarDB for MySQL: All versions

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS SQL Server instance to a PolarDB for MySQL cluster

    AnalyticDB for MySQL

    Version 3.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from an RDS SQL Server instance 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 data from a self-managed SQL Server database to AnalyticDB for PostgreSQL

    RDS for PostgreSQL

    Versions 9.4 and 10 through 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 SQL Server instance to DataHub

    Migration solutions for self-managed or ApsaraDB for MongoDB sources

    Source database

    Destination database

    Migration type

    Configuration document

    Single-node architecture

    • Self-managed MongoDB

      Versions 3.0 to 7.0

    • ApsaraDB for MongoDB

      ApsaraDB for MongoDB: Versions 3.4 and 4.0

    Single-node, ReplicaSet, or sharded cluster architecture

    • Self-hosted MongoDB

      Versions 3.0 to 7.0

    • ApsaraDB for MongoDB

      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 single-node ApsaraDB for MongoDB instance to an ApsaraDB for MongoDB instance of any architecture

    ReplicaSet 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

    ReplicaSet or sharded cluster architecture

    • Self-managed MongoDB

      Versions 3.0 to 7.0

    • ApsaraDB for MongoDB

      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 an ApsaraDB for MongoDB ReplicaSet instance to an ApsaraDB for MongoDB ReplicaSet or sharded cluster 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

    ReplicaSet or sharded cluster architecture

    • Self-hosted MongoDB

      Versions 3.0 to 7.0

    • ApsaraDB for MongoDB

      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 self-managed MongoDB sharded cluster instance to an ApsaraDB for MongoDB ReplicaSet or sharded cluster instance

    ReplicaSet or sharded cluster architecture

    • Self-managed MongoDB

      Versions 3.0 to 7.0

    • ApsaraDB for MongoDB

      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

    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

    • A MySQL database created by a user

      Supported 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 ApsaraDB for MongoDB to RDS for MySQL

    PolarDB for MySQL: All versions

    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

      Self-managed Kafka: 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

    Migration scenarios from self-hosted Redis or ApsaraDB Tair (Redis-compatible)

    Important

    • Redis is a NoSQL database. Schema migration is not required.

    • For self-managed Redis or ApsaraDB for Tair (Redis-compatible) sources, full and incremental data migration are supported. These migration types are combined and displayed as Incremental Data Migration in the console.

    • DTS supports RDB versions up to 11, which corresponds to Redis 7.2.

    Source database

    Destination database

    Migration type

    Configuration document

    • Self-managed Redis instances (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) instances (cluster, standard, or read/write splitting architecture)

      Versions: 4.0, 5.0, 6.0, and 7.0

    • Self-managed Redis instances (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) instances (cluster, standard, or read/write splitting architecture)

      Versions: 4.0, 5.0, 6.0, and 7.0

    Full data migration

    Incremental data migration

    Migration from 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 from self-managed TiDB to RDS for MySQL

    PolarDB for MySQL

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed TiDB to PolarDB for MySQL

    PolarDB-X 2.0

    Schema migration

    Full data migration

    Incremental data migration

    Document coming soon

    AnalyticDB for MySQL

    Version 3.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from self-managed TiDB to AnalyticDB for MySQL 3.0

    Migration solution for a Db2 for LUW source

    Important

    Source database

    Destination database

    Migration type

    Configuration document

    Db2 for LUW

    Db2 for LUW: Versions 9.5, 9.7, 10.1, 10.5, 11.1, and 11.5

    • Self-hosted 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 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 Apache Kafka

      Versions 0.10.1.0 to 2.x

    • Self-managed Kafka

      Self-managed Kafka: Versions 0.10.1.0 to 2.7.0

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from Db2 for LUW to Message Queue for Apache Kafka

    PolarDB for MySQL: All versions

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Migrate data from Db2 for LUW to PolarDB for MySQL

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

    Important

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

    Source database

    Destination database

    Migration type

    Configuration document

    Db2 for i

    Versions 7.3 and 7.4

    • Self-hosted 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

    Document is being prepared

    PolarDB for MySQL

    All versions

    Schema migration

    Full data migration

    Incremental data migration

    Document is being prepared

    Migration from Teradata

    Important

    You can configure this solution only in the new console. The DTS instance must be in the China (Shanghai), China (Qingdao), or China (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 from Teradata to AnalyticDB for PostgreSQL

    Migration solution for a self-managed HBase source

    Important

    You can configure this solution only in the new console.

    Source database

    Destination database

    Migration type

    Configuration document

    Self-managed HBase

    Version 1.x

    AnalyticDB for MySQL

    Version 3.0

    Schema migration

    Full data migration

    Migrate from self-managed HBase to AnalyticDB for MySQL 3.0

    Migration solutions from an AnalyticDB MySQL 3.0 source

    Note

    To migrate incremental data, the kernel version of the source AnalyticDB for MySQL 3.0 cluster must be 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

    Migration between AnalyticDB for MySQL V3.0 instances

    Migration solution for an AnalyticDB for MySQL 3.0 source

    Note

    To migrate incremental data, the source AnalyticDB for PostgreSQL instance must be 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

    Migration between AnalyticDB for PostgreSQL instances

    Migration from third-party clouds

    DTS lets you migrate data from third-party cloud databases, such as Amazon RDS for MySQL and Amazon RDS for Oracle, to Alibaba Cloud database products, such as RDS for MySQL.

    Source database

    Destination database

    Migration types

    Configuration document

    Databases on the Azure platform

    Refer to the console.

    Migrate data from Azure to Alibaba Cloud RDS over a VPN Gateway

    Amazon RDS for MySQL

    RDS for MySQL

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from Amazon RDS for MySQL to Alibaba Cloud RDS for MySQL

    Amazon RDS for Oracle

    RDS for MySQL

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from Amazon RDS for Oracle to Alibaba Cloud RDS for MySQL

    Amazon RDS for PostgreSQL

    RDS for PostgreSQL

    Schema migration

    Full data migration

    Incremental data migration

    Incrementally migrate from Amazon RDS for PostgreSQL to Alibaba Cloud

    Schema migration

    Full data migration

    Fully migrate from Amazon RDS for PostgreSQL to Alibaba Cloud

    Amazon RDS for SQL Server

    RDS for SQL Server

    Schema migration

    Full data migration

    Fully migrate from Amazon RDS for SQL Server to Alibaba Cloud

    Amazon Aurora MySQL

    RDS for MySQL

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from Amazon Aurora MySQL to Alibaba Cloud

    PolarDB for MySQL

    Schema migration

    Full data migration

    Incremental data migration

    Migrate from Amazon Aurora MySQL to PolarDB for MySQL

    Amazon Aurora PostgreSQL

    RDS for PostgreSQL

    Schema migration

    Full data migration

    Migrate from Amazon Aurora PostgreSQL to Alibaba Cloud

    MongoDB Atlas

    ApsaraDB for MongoDB

    Full data migration

    Incremental data migration

    Use DTS to migrate a MongoDB Atlas database to Alibaba Cloud

    Migration scenarios for instances across Alibaba Cloud accounts

    Source database

    Destination database

    Migration types

    Documentation

    Source RDS instance

    Destination RDS instance

    Schema migration

    Full data migration

    Incremental data migration

    Migrate RDS instances across Alibaba Cloud accounts