You can use Data Transmission Service (DTS) to migrate data between homogeneous and heterogeneous data sources. Typical scenarios include data migration to Alibaba Cloud, data migration between instances within Alibaba Cloud, and database splitting and scale-out. This topic describes the database types, database versions, and migration types that are supported by the data migration feature.

For more information about data migration in various scenarios, see Overview of data migration scenarios.

Note The data migration feature can achieve data synchronization in specific scenarios. However, data migration and data synchronization differ in scenarios, supported databases, features, and billing. For more information, see What are the differences between data migration and data synchronization?

Migration types

Migration type Description
Schema migration

DTS migrates the schemas of the required objects from the source database to the destination database. Tables, views, triggers, and stored procedures can be migrated.

For schema migration between heterogeneous databases, DTS converts the schema syntax based on the syntax of the source and destination databases. For example, it converts the NUMBER data type in Oracle databases into the DECIMAL data type in MySQL databases.

Full data migration DTS migrates historical data of the required objects from the source database to the destination database. If you select only schema migration and full data migration, DTS does not migrate incremental data that was generated in the source database.
Note To ensure data consistency, do not write data to the source database during full data migration. To ensure service continuity, you must select Schema Migration, Full Data Migration, and Incremental Data Migration when you configure a data migration task.
Incremental data migration DTS retrieves static snapshots that are used for full data migration from the source database, and migrates the snapshot data to the destination database. Then, DTS synchronizes incremental data that was generated in the source database to the destination database.
Note During incremental data migration, data is synchronized between the source and destination databases in real time. The migration task does not automatically stop. You must manually stop the migration task.

Supported databases and migration types

A self-managed MySQL, SQL Server, or Oracle database can be one of the following types:

  • Self-managed database with a public IP address
  • Self-managed database that has no public IP address or port number (connected over Database Gateway)
  • Self-managed database that is connected over Cloud Enterprise Network (CEN)
  • Self-managed database that is hosted on Elastic Compute Service (ECS)
  • Self-managed database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway
Source database Destination database Migration types
  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL

    All versions

Self-managed MySQL database

Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB 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

DRDS

All versions

Note The databases in the DRDS instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not support DRDS databases that are created based on PolarDB for MySQL clusters.
  • Full data migration
  • Incremental data migration

HybridDB for MySQL (Previous name: PetaData)

All versions

  • Full data migration
  • Incremental data migration

AnalyticDB for MySQL

Version 2.0 or 3.0

  • Schema migration
  • Full data migration
  • Incremental data migration

Self-managed PostgreSQL database

Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, or 12

  • Full data migration
  • Incremental data migration

Self-managed Oracle database (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

  • Schema migration
  • Full data migration
  • Incremental data migration

Message Queue for Apache Kafka

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MariaDB TX

Version 10.3

ApsaraDB RDS for MariaDB TX

Version 10.3

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MySQL

All versions

  • Schema migration
  • Full data migration
  • Full data migration

Self-managed MySQL database

Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration
ApsaraDB RDS for PPAS

All versions

PolarDB-O

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

PolarDB for MySQL

All versions

PolarDB for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

Self-managed MySQL database

Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

PolarDB-O

All versions

PolarDB-O

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

Self-managed Oracle database (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

  • Schema migration
  • Full data migration
  • Incremental data migration

Message Queue for Apache Kafka

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

  • Schema migration
  • Full data migration
  • Incremental data migration

PolarDB for PostgreSQL

Version 11

Self-managed Oracle database (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

  • Full data migration
  • Incremental data migration

MaxCompute

All versions

  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL

    All versions

All
  • Schema migration
  • Full data migration
  • Self-managed SQL Server database

    Version 2005, 2008, 2008 R2, 2012, 2014, 2016, or 2017

    Note
    • DTS does not support SQL Server clusters or SQL Server Always On availability groups (AOAGs).
    • If the version of the source database is 2005, incremental data migration is not supported.
  • ApsaraDB RDS for SQL Server

    Version 2008, 2008 R2, 2012, 2014, 2016, or 2017

    Note If the version of the source database is 2008 or 2008 R2, incremental data migration is not supported.

Self-managed SQL Server database

Version 2005, 2008, 2008 R2, 2012, 2014, 2016, or 2017

Note DTS does not support SQL Server clusters or SQL Server Always On availability groups (AOAGs).
  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for SQL Server

Version 2008, 2008 R2, 2012, 2014, 2016, or 2017

  • Schema migration
  • Full data migration
  • Incremental data migration

Self-managed Oracle database (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

Self-managed Oracle database (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

  • Schema migration
  • Full data migration
  • Incremental data migration

PolarDB-O

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for PPAS

Version 9.3 or 10

  • Schema migration
  • Full data migration
  • Incremental data migration

Self-managed MySQL database

Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB 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

DRDS

All versions

Note The databases in the DRDS instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not support DRDS databases that are created based on PolarDB for MySQL clusters.
  • Full data migration
  • Incremental data migration

AnalyticDB for MySQL

Version 2.0 or 3.0

  • Schema migration
  • Full data migration
  • Incremental data migration

AnalyticDB for PostgreSQL

Version 4.3 or 6.0

  • Schema migration
  • Full data migration
  • Incremental data migration

Message Queue for Apache Kafka

Version 0.10.1.0 to 2.x

Self-managed Kafka cluster

Version 0.10.1.0 to 2.7.0

  • Schema migration
  • Full data migration
  • Incremental data migration

PolarDB for PostgreSQL

Version 11

  • Schema migration
  • Full data migration
  • Incremental data migration
  • Self-managed PostgreSQL database

    Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, or 12

  • ApsaraDB RDS for PostgreSQL

    Version 9.4, 10, 11, or 12

  • Schema migration
  • Full data migration
  • Incremental data migration
  • Self-managed PostgreSQL database

    Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, or 12

  • ApsaraDB RDS for PostgreSQL

    Version 9.4, 10, 11, or 12

  • Self-managed PostgreSQL database

    Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, or 12

  • ApsaraDB RDS for PostgreSQL

    Version 9.4, 10, 11, or 12

  • Schema migration
  • Full data migration
  • Incremental data migration
  • Self-managed MongoDB database (standalone, replica set, or sharded cluster architecture)

    Version 3.0, 3.2, 3.4, 3.6, or 4.0

  • ApsaraDB for MongoDB instance (standalone or replica set architecture)

    Version 3.4, 4.0, or 4.2

  • Self-managed MongoDB database (standalone, replica set, or sharded cluster architecture)

    Version 3.0, 3.2, 3.4, 3.6, or 4.0

  • ApsaraDB for MongoDB instance (standalone, replica set, or sharded cluster architecture)

    Version 3.4, 4.0, or 4.2

  • Full data migration
  • Incremental data migration
Note MongoDB is a NoSQL database that does not require schema migration.

Self-managed Redis database (standalone architecture)

Version 2.8, 3.0, 3.2, 4.0, or 5.0

Self-managed Redis database (standalone or cluster architecture)

Version 2.8, 3.0, 3.2, 4.0, or 5.0

  • Full data migration
  • Incremental data migration
Note Redis is a NoSQL database that does not require schema migration.

ApsaraDB for Redis instance (standalone or cluster architecture)

Community Edition 4.0 or 5.0

  • Full data migration
  • Incremental data migration
Self-managed TiDB database

Self-managed MySQL database

Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB 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
  • Self-managed Db2 database

    Version 9.7 to 11.5

  • Self-managed Db2 for i database

    Version 7.3 or 7.4

Self-managed MySQL database

Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration