Data Transmission Service (DTS) migrates data between homogeneous or heterogeneous data sources. Its use cases include migrating data to Alibaba Cloud, migrating between Alibaba Cloud instances, and sharding and scaling databases. This topic describes the supported database types, versions, and migration types, with links to their respective configuration guides.
Background
Migration types
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 schema definition syntax based on the syntax of the source and destination databases. For example, DTS converts the NUMBER data type in an Oracle database to the DECIMAL data type in a MySQL database. |
Full data migration | DTS migrates all existing 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, new data written to the source database is not migrated to the destination database. Important To ensure data consistency, do not write new data to the source database during full data migration. For a zero-downtime migration, you must select Schema Migration, Full Data Migration, and Incremental Data Migration when you configure the task. |
Incremental data migration | DTS captures incremental change statements for the objects to be migrated from the source database, such as from the binary log of a MySQL database. DTS then converts and applies these statements to the destination database to replicate data in real time. Note Incremental data migration runs continuously in real time and does not stop automatically. You must manually terminate or release the migration task. For more information, see Terminate a DTS instance and Release DTS instances. |
Data synchronization vs. data migration
Although data migration can be used for data synchronization in certain scenarios, we recommend using data synchronization for its superior network stability and richer feature set. For more information, see What's the difference between data migration and data synchronization?.
To configure a migration instance with the source and destination databases in different regions (cross-border or cross-region), they must meet the following requirements:
-
If Access Method is set to Alibaba Cloud Instance for the source database, the source database must have a public endpoint.
-
If Access Method 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 or cross-region operations, ensure that your task bandwidth does not exceed 100 Mbit/s. For higher bandwidth requirements, you must configure cross-region network bandwidth by using Cloud Enterprise Network (CEN) before you configure the DTS task.
NoteA cross-region or cross-border task is one where the source and destination databases are in different regions, for example, a source RDS instance in the Singapore region and a destination RDS instance in the China (Hangzhou) region.
Cross-account data migration
Support for cross-account data migration depends on the database type and access method. If supported, the Replicate Data Across Alibaba Cloud Accounts parameter appears when you configure the task. To perform a cross-account data migration, set this parameter to Yes. For more information, see Configure a cross-account DTS task.
Source database limitations
The following table describes the network bandwidth and business requirements for the source database. For more limitations, see the relevant configuration documentation.
Limitation | Description |
Network bandwidth |
|
Business requirements |
|
FAQ
Does DTS support ApsaraDB RDS for MySQL serverless instances?
Yes.
Does DTS support PolarDB for MySQL serverless clusters?
Yes.
Does DTS support ApsaraDB RDS for PostgreSQL serverless instances?
Currently, an ApsaraDB RDS for PostgreSQL serverless instance can be used only as a destination database, not as a source database.
Does DTS support instances in ApsaraDB for MyBase?
Yes. DTS can access database instances in ApsaraDB for MyBase if you set the Access Method to Alibaba Cloud Instance. To configure the task, refer to the documentation for your specific database migration scenario.
NoteFor example, to migrate data from a self-managed MySQL database to a MySQL instance in ApsaraDB for MyBase, you can follow the instructions in Migrate from a self-managed MySQL database to ApsaraDB RDS for MySQL.
What is a self-managed database?
A self-managed database is any database instance with an Access Method other than Alibaba Cloud Instance in the DTS configuration. Self-managed databases include databases from third-party cloud providers, on-premises databases, and databases on ECS instances.
Why do the estimated total and completed counts differ during the full migration phase?
The estimated total and completed counts may differ during the full migration phase. The estimate is based on the database's statistical information. This information can sometimes be inaccurate. To ensure data accuracy, rely on the data from the full verification phase.
Migration plans
In the On this page section on the right, click a source database migration plan to view the supported versions, migration types, and configuration procedures.
Migration from self-managed or RDS for MySQL
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 |
|
| 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 | ||
PolarDB-X 2.0 | schema migration full data migration incremental data migration | ||
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 | |
| schema migration full data migration incremental data migration | Migrate ApsaraDB RDS for MySQL to ApsaraDB RDS for PostgreSQL | |
| 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 | ||
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 | ||
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 | ||
Tablestore | schema migration full data migration incremental data migration | ||
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 | ||
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 |
|
| schema migration full data migration incremental data migration | |
RDS for MySQL | schema migration full data migration incremental data migration | ||
RDS for PostgreSQL Versions 9.4 and 10–18 | schema migration full data migration incremental data migration |
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
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 | |
| 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 | |
| Schema migration Full data migration Incremental data migration | ||
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 | |
| 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
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 | |
AnalyticDB for MySQL Version 3.0 | schema migration full data migration incremental data migration | ||
AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0 | schema migration full data migration incremental data migration | ||
DataHub | schema migration incremental data migration | ||
Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x | schema migration full data migration incremental data migration | ||
| schema migration full data migration incremental data migration | Migrate from PolarDB-X 1.0 to Message Queue for Apache Kafka | |
| schema migration full data migration incremental data migration | ||
PolarDB-X 2.0 | PolarDB-X 2.0 | schema migration full data migration incremental data migration | |
| schema migration full data migration incremental data migration | ||
PolarDB for MySQL All versions | schema migration full data migration incremental data migration | ||
AnalyticDB for MySQL Version 3.0 | schema migration full data migration incremental data migration | ||
AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0 | schema migration full data migration incremental data migration | ||
MaxCompute | schema migration full data migration incremental data migration | ||
| 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 | ||
Elasticsearch Versions 5.5, 5.6, 6.x, 7.x, and 8.x | schema migration full data migration incremental data migration | ||
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 | ||
PolarDB-X 1.0 | full data migration incremental data migration | ||
ApsaraDB for SelectDB | schema migration full data migration incremental data migration |
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 | |
| 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 |
| Schema migration Full data migration |
Migration from OceanBase (MySQL mode)
Source database | Destination database | Migration type | Documentation |
|
| 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 | ||
Lindorm | full data migration incremental data migration |
Oracle source migration scenarios
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 | |
self-managed Oracle (RAC or non-RAC architecture) Versions 9i, 10g, 11g, 12c, 18c, and 19c | schema migration full data migration incremental data migration | ||
| schema migration full data migration incremental data migration | ||
PolarDB for MySQL All versions | schema migration full data migration incremental data migration | ||
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 | ||
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 | |
| schema migration full data migration incremental data migration | ||
| 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 |
Migration from PostgreSQL sources
ApsaraDB RDS for PostgreSQL Serverless is supported only as a destination database, not as a source database.
Source | Destination | Type | References |
|
| schema migration full data migration incremental data migration | |
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 | |
| 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
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 |
|
| schema migration full data migration incremental data migration | |
| schema migration full data migration incremental data migration | ||
PolarDB for MySQL All versions | schema migration full data migration incremental data migration | ||
AnalyticDB for MySQL Version 3.0 | schema migration full data migration incremental data migration | ||
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 |
Migration from self-managed or ApsaraDB for MongoDB
Source database | Destination database | Migration type | Configuration document |
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 | Full data migration Incremental data migration | |
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 | |
| 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 | ||
| 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
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 |
|
| Full data migration Incremental data migration |
TiDB as a migration source
Source database | Destination database | Migration type | References |
TiDB |
| 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 | ||
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
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 |
| schema migration full data migration incremental data migration | |
PolarDB-X 2.0 | full data migration incremental data migration | ||
AnalyticDB for PostgreSQL Versions 4.3, 6.0, and 7.0 | schema migration full data migration incremental data migration | ||
| schema migration full data migration incremental data migration | ||
PolarDB for MySQL All versions | schema migration full data migration incremental data migration |
Db2 for i (AS/400) migration
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 |
| 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
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 |
Migrating from self-managed HBase
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
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 |
Migration from AnalyticDB for PostgreSQL
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 |
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. | ||
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 |
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 |
PolarDB for MySQL | schema migration full data migration incremental data migration | ||
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 | |
Cross-account migration between instances
Source database | Destination database | Migration type | Documentation |
Source RDS instance | Destination RDS instance | Schema migration Full data migration Incremental data migration | Migrate data between ApsaraDB RDS instances across Alibaba Cloud accounts |