Data Transmission Service (DTS) allows you to migrate data between homogeneous data sources or between heterogeneous data sources. Typical scenarios include data migration to Alibaba Cloud, data migration between instances within Alibaba Cloud, and database sharding and scaling. This topic describes the database types, database versions, and migration types that are supported by the data migration feature. This topic also provides links to the relevant references.
In some scenarios, data migration can implement part of data synchronization features. However, data synchronization provides better network stability and additional features. We recommend that you use data synchronization instead of data migration. For more information about the differences between data migration and data synchronization, see the What are the differences between data migration and data synchronization? section of the "FAQ" topic.
Cross-region data migration is supported for all data migration tasks.
Whether cross-account data migration is supported depends on the type and access method of a database. If cross-account data migration is supported, the Replicate Data Across Alibaba Cloud Accounts parameter is displayed when you configure the source and destination databases. If you want to migrate data across Alibaba Cloud accounts, set this parameter to Yes. For more information, see the Supported databases section of the "Configure a DTS task across Alibaba Cloud accounts" topic.
A serverless ApsaraDB RDS for MySQL instance can serve as the source or destination database. A serverless ApsaraDB RDS for PostgreSQL instance can serve only as the destination database instead of the source database.
When you create a task to migrate data to or from a database instance that is created in ApsaraDB MyBase, you can set the Access Method parameter to Alibaba Cloud Instance. This way, DTS can access the database instance as expected. You can configure the data migration task by referring to the topics listed in the following tables. For example, you can migrate data from a self-managed MySQL database to an ApsaraDB MyBase for MySQL instance by referring to the Migrate data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance topic.
Migration types
Migration type | Description |
Schema migration | DTS migrates the schemas of selected objects, such as tables, views, triggers, and stored procedures, from the source database to the destination database. For schema migration between heterogeneous databases, DTS converts the schema syntax based on the syntax of the source and destination databases. For example, DTS converts the NUMBER data type in Oracle databases into the DECIMAL data type in MySQL databases. |
Full data migration | DTS migrates the historical data of the selected 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, DTS does not migrate incremental data that are generated in the source database. Important 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, migrates the snapshot data to the destination database, and then synchronizes incremental data 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 data migration task does not automatically stop. You must manually stop the data migration task. |
Data migration scenarios
DTS supports the following data migration scenarios. You can select one of the following scenarios based on your business requirements to view the supported database versions, migration types, and configuration procedures.
Migrate data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Migrate data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
Migrate data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
Migrate data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Migrate data from a self-managed Redis database, a Tair instance, or an ApsaraDB for Redis instance
Migrate data between instances of different Alibaba Cloud accounts
When you create a task to migrate data from or to a self-managed database that is described in the following tables, such as a MySQL, SQL Server, or Oracle database, you can set the Access Method parameter to one of the following values for the database:
Public IP Address
Self-managed Database on ECS
Express Connect, VPN Gateway, or Smart Access Gateway
Database Gateway (for a self-managed database without a public IP address or port number)
Data migration tasks that involve this type of database may be unstable due to factors such as poor quality of Internet connections. We recommend that you use Express Connect or Smart Access Gateway to connect the data center to a virtual private cloud (VPC). This way, DTS can access the self-managed database over Express Connect, VPN Gateway, or Smart Access Gateway. For more information, see Connect a data center to a VPC.
Cloud Enterprise Network (CEN)
Migrate data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data migration task whose destination database is a PolarDB-X 1.0 instance, schema migration is not supported. Schema migration is supported for a data migration task whose destination database is a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Data migration to an AnalyticDB for MySQL 2.0 cluster is not supported in the new DTS console. You can configure a data migration task for this scenario only in the old DTS console.
Source database | Destination database | Migration type | References |
|
| Schema migration Full data migration Incremental data migration | |
PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | ||
PolarDB-X 1.0 or PolarDB-X 2.0 instance | Full data migration Incremental data migration | ||
AnalyticDB for MySQL cluster Version 2.0 or 3.0 | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL V3.0 cluster | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance | |
| Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB RDS for PostgreSQL instance | |
| Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraMQ for Kafka instance | |
ApsaraDB for ClickHouse cluster Version 20.8 or later | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for ClickHouse cluster | |
DataHub project All versions | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to a DataHub project | |
Elasticsearch cluster Version 5.5, 5.6, 6.x, or 7.x | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to an Elasticsearch cluster | |
MaxCompute project | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to a MaxCompute project | |
| Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to a Db2 for LUW database | |
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 | Migrate data from an ApsaraDB RDS for MySQL instance to a self-managed Oracle database | |
| Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to a Tair or ApsaraDB for Redis instance | |
Tablestore instance | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MySQL instance to a Tablestore instance |
Migrate data from a MariaDB database
Source database | Destination database | Migration type | References |
|
| Schema migration Full data migration Incremental data migration | |
ApsaraDB RDS for MySQL instance | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MariaDB instance to an ApsaraDB RDS for MySQL instance | |
ApsaraDB RDS for PostgreSQL instance | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for MariaDB instance to an ApsaraDB RDS for PostgreSQL instance |
Migrate data from an ApsaraDB RDS for PPAS instance
You can configure a data migration task for this scenario only in the old DTS console.
Source database | Destination database | Migration type | References |
ApsaraDB RDS for PPAS instance All versions | PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB for Oracle cluster |
Migrate data from a PolarDB for MySQL cluster
A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data migration task whose destination database is a PolarDB-X 1.0 instance, schema migration is not supported. Schema migration is supported for a data migration task whose destination database is a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database | Destination database | Migration type | References |
PolarDB for MySQL cluster All versions | PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | |
| 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 or PolarDB-X 2.0 instance | 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 Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance | |
| Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB for MySQL cluster to a Kafka cluster | |
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) Version 9i, 10g, 11g, 12c, 18c, or 19c | Schema migration Full data migration Incremental data migration | Available soon | |
Elasticsearch cluster Version 5.5, 5.6, 6.x, or 7.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 | Available soon |
Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Source database | Destination database | Migration type | References |
PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions | PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions | Schema migration Full data migration Incremental data migration | Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) clusters |
Self-managed Oracle database (RAC, PDB, or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c | Full data migration Incremental data migration | ||
| Incremental data migration | Available soon | |
AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration Incremental data migration |
Migrate data from a PolarDB-X instance
You can configure a data migration task for this scenario only in the new DTS console.
A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database | Destination database | Migration type | References |
PolarDB-X 1.0 instance | PolarDB-X 2.0 instance | 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 cluster 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 V3.0 cluster | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance | |
DataHub project | Schema migration Incremental data migration | Migrate data from a PolarDB-X 1.0 instance to a DataHub project | |
Elasticsearch cluster Version 5.5, 5.6, 6.x, or 7.x | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 1.0 instance to an Elasticsearch cluster | |
| Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 1.0 instance to an ApsaraMQ for Kafka instance | |
| Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance | |
PolarDB-X 2.0 instance | PolarDB-X 2.0 instance | Schema migration Full data migration Incremental data migration | |
| Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance | |
MaxCompute project | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to a MaxCompute project | |
| Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to a Message Queue for Apache Kafka instance | |
DataHub project All versions | Schema migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to a DataHub project | |
Elasticsearch cluster Version 5.5, 5.6, 6.x, or 7.x | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to an Elasticsearch cluster | |
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 | Migrate data from a PolarDB-X 2.0 instance to a self-managed Oracle database | |
Tablestore instance | Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB-X 2.0 instance to a Tablestore instance |
Migrate data from a PolarDB for PostgreSQL cluster
Source database | Destination database | Migration type | References |
PolarDB for PostgreSQL cluster Version 11 or 14 | PolarDB for PostgreSQL cluster Version 11 or 14 | Schema migration Full data migration Incremental data migration | Available soon |
| Schema migration Full data migration Incremental data migration | Migrate data from a PolarDB for PostgreSQL cluster to an ApsaraDB RDS for PostgreSQL instance | |
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c | Full data migration Incremental data migration | Migrate data from a PolarDB for PostgreSQL cluster to a self-managed Oracle database | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Available soon |
Migrate data from a MaxCompute project
Source database | Destination database | Migration type | References |
MaxCompute project All versions |
| Schema migration Full data migration | Migrate data from a MaxCompute project to an ApsaraDB RDS for MySQL instance |
Migrate data from an OceanBase database in MySQL mode
Source database | Destination database | Migration type | References |
OceanBase database in MySQL mode Community Edition |
| Schema migration Full data migration Incremental data migration | Migrate data from an OceanBase database in MySQL mode to an ApsaraDB RDS for MySQL instance |
PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | Migrate data from a MySQL-compatible OceanBase database to a PolarDB for MySQL cluster |
Migrate data from an Oracle database
A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data migration task whose destination database is a PolarDB-X 1.0 instance, schema migration is not supported. Schema migration is supported for a data migration task whose destination database is a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database | Destination database | Migration type | References |
Self-managed Oracle database (RAC or non-RAC architecture) Version 9i, 10g, 11g, 12c, 18c, or 19c | PolarDB for PostgreSQL (Compatible with Oracle) cluster 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 | ||
| Schema migration Full data migration Incremental data migration | Migrate data from a self-managed Oracle database to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | Migrate data from a self-managed Oracle database to a PolarDB for MySQL cluster | |
PolarDB for PostgreSQL cluster Version 11 or 14 | Schema migration Full data migration Incremental data migration | Available soon | |
PolarDB-X 1.0 or PolarDB-X 2.0 instance | Full data migration Incremental data migration | Migrate data from a self-managed Oracle database to a PolarDB-X 1.0 instance | |
AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration Incremental data migration | Migrate data from a self-managed Oracle database to an AnalyticDB for MySQL V3.0 cluster | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance | |
| Schema migration Full data migration Incremental data migration | ||
| Schema migration Full data migration Incremental data migration | Migrate data from a self-managed Oracle database to an ApsaraMQ for Kafka instance | |
DataHub project All versions | Schema migration Full data migration Incremental data migration | Available soon |
Migrate data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
A serverless ApsaraDB RDS for PostgreSQL instance can serve only as the destination database instead of the source database.
Source database | Destination database | Migration type | References |
|
| Schema migration Full data migration Incremental data migration | |
PolarDB for PostgreSQL cluster Version 11 or 14 | Schema migration Full data migration Incremental data migration | Migrate data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL cluster | |
| Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for PostgreSQL (Compatible with Oracle) cluster All versions | Full data migration Incremental data migration | ||
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a self-managed PostgreSQL database to an AnalyticDB for PostgreSQL instance |
Migrate data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
The source self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
The destination self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
If the version of the self-managed SQL Server database is 2005 or the version of the ApsaraDB RDS for SQL Server instance is 2008 or 2008 R2, incremental data migration is not supported for this scenario.
DTS supports SQL Server clusters and SQL Server Always On availability groups (AOAGs).
If 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, data is migrated in the hybrid log-based parsing mode and the following versions of source databases are supported:
Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Enterprise or Enterprise Evaluation edition: version 2012, 2014, 2016, 2019, or 2022.
Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Standard edition: version 2016, 2019, or 2022.
Source database | Destination database | Migration type | References |
|
| Schema migration Full data migration Incremental data migration | |
| Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance | |
PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for SQL Server instance to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration Incremental data migration | Migrate data from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for MySQL V3.0 cluster | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a self-managed SQL Server database to an AnalyticDB for PostgreSQL instance | |
DataHub project | Schema migration Incremental data migration | Migrate data from an ApsaraDB RDS for SQL Server instance to a DataHub project |
Migrate data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Source database | Destination database | Migration type | References |
Standalone architecture
| Standalone, replica set, or sharded cluster architecture
| Schema migration Full data migration | |
Replica set architecture
| Replica set or sharded cluster architecture
| Schema migration Full data migration Incremental data migration | |
Sharded cluster architecture
| Replica set or sharded cluster architecture
| Schema migration Full data migration Incremental data migration | |
Replica set or sharded cluster architecture
| Lindorm instance | Full data migration Incremental data migration | Migrate data from an ApsaraDB for MongoDB instance to a Lindorm instance |
Migrate data from a self-managed Redis database, a Tair instance, or an ApsaraDB for Redis instance
A Redis database is a NoSQL database and does not require schema migration.
If the source database is a self-managed Redis database or an ApsaraDB for Redis Community Edition instance, full data migration and incremental data migration are supported and collectively displayed as Incremental Data Migration.
Source database | Destination database | Migration type | References |
|
| Full data migration Incremental data migration |
Migrate data from a TiDB database
You can configure a data migration task for this scenario only in the old DTS console.
Source database | Destination database | Migration type | References |
TiDB database |
| Schema migration Full data migration Incremental data migration | |
PolarDB for MySQL cluster All versions | Schema migration Full data migration Incremental data migration | Available soon | |
AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration Incremental data migration | Available soon |
Migrate data from a self-managed Db2 for LUW database
The Db2 for LUW database is displayed as DB2 for LUW in the DTS console.
A destination database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database | Destination database | Migration type | References |
Db2 for LUW database Version 9.5, 9.7, 10.1, 10.5, 11.1, or 11.5 |
| Schema migration Full data migration Incremental data migration | Migrate data from a self-managed Db2 database to an ApsaraDB RDS for MySQL instance |
PolarDB-X 2.0 instance | Full data migration Incremental data migration | Migrate data from a Db2 for LUW database to a PolarDB-X 2.0 instance | |
AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration Incremental data migration | Migrate data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance | |
| Schema migration Full data migration Incremental data migration | Migrate data from a Db2 for LUW database to an ApsaraMQ for Kafka instance | |
PolarDB for MySQL cluster | Schema migration Full data migration Incremental data migration | Migrate data from a Db2 for LUW database to a PolarDB for MySQL cluster | |
AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration Incremental data migration | Available soon |
Migrate data from a Db2 for iSeries (AS/400) database
The Db2 for iSeries (AS/400) database is displayed as DB2 for iSeries (AS/400) in the DTS console.
Source database | Destination database | Migration type | References |
Db2 for iSeries (AS/400) database Version 7.3 or 7.4 |
| Schema migration Full data migration Incremental data migration | Available soon |
PolarDB for MySQL cluster | Schema migration Full data migration Incremental data migration | Available soon |
Migrate data from a Teradata database
You can configure a data migration task for this scenario only in the new DTS console, and the data migration instance must reside in the China (Shanghai), China (Qingdao), or China (Zhangjiakou) region.
Source database | Destination database | Migration type | References |
Teradata database Version 17 or earlier | AnalyticDB for PostgreSQL instance Version 4.3, 6.0, or 7.0 | Schema migration Full data migration | Migrate data from a Teradata database to an AnalyticDB for PostgreSQL instance |
Migrate data from a self-managed HBase database
You can configure a data migration task for this scenario only in the new DTS console.
Source database | Destination database | Migration type | References |
Self-managed HBase database Version 1.x | AnalyticDB for MySQL cluster Version 3.0 | Schema migration Full data migration | Migrate data from a self-managed HBase database to an AnalyticDB for MySQL V3.0 cluster |
Migrate data from a database hosted on a third-party cloud
You can use DTS to migrate data from a database hosted on a third-party cloud such as Amazon RDS for MySQL and Amazon RDS for Oracle to an Alibaba Cloud database, such as ApsaraDB RDS for MySQL.
Source database | Destination database | Migration type | References |
Amazon RDS for MySQL instance | ApsaraDB RDS for MySQL instance | Schema migration Full data migration Incremental data migration | Migrate data from an Amazon RDS for MySQL instance to an ApsaraDB RDS for MySQL instance |
Amazon RDS for Oracle instance | ApsaraDB RDS for MySQL instance | Schema migration Full data migration Incremental data migration | Migrate data from an Amazon RDS for Oracle instance to an ApsaraDB RDS for MySQL instance |
Amazon RDS for PostgreSQL instance | ApsaraDB RDS for PostgreSQL instance | Schema migration Full data migration Incremental data migration | |
Schema migration Full data migration | |||
Amazon RDS for SQL Server instance | ApsaraDB RDS for SQL Server instance | Schema migration Full data migration | |
Amazon Aurora MySQL cluster | ApsaraDB RDS for MySQL instance | Schema migration Full data migration Incremental data migration | Migrate data from an Amazon Aurora MySQL cluster to an ApsaraDB RDS for MySQL instance |
PolarDB for MySQL cluster | Schema migration Full data migration Incremental data migration | ||
Amazon Aurora PostgreSQL instance | ApsaraDB RDS for PostgreSQL instance | Schema migration Full data migration | Migrate data from Amazon Aurora PostgreSQL to an ApsaraDB RDS for PostgreSQL instance |
MongoDB Atlas database | ApsaraDB for MongoDB instance | Full data migration Incremental data migration | Migrate data from a MongoDB Atlas database to ApsaraDB for MongoDB by using DTS |
Migrate data between instances of different Alibaba Cloud accounts
Source database | Destination database | Migration type | References |
Source ApsaraDB RDS instance | Destination ApsaraDB RDS instance | Schema migration Full data migration Incremental data migration | Migrate data between ApsaraDB RDS instances of different Alibaba Cloud accounts |