All Products
Search
Document Center

ApsaraDB RDS:RDS for MySQL console operations (data migration)

Last Updated:Mar 30, 2026

The RDS console includes a built-in data migration feature powered by Data Transmission Service (DTS). Use it to migrate data into or out of your ApsaraDB RDS for MySQL instance without leaving the console.

Prerequisites

Before you begin, ensure that you have:

Billing

This feature is provided by DTS and shares the same billable items as DTS. See Billable items.

Create a data migration task

Step 1: Open the data migration page

  1. Go to the Instances page.

  2. In the top navigation bar, select the region where your RDS instance resides. Find the instance and click its instance ID.

  3. In the left-side navigation pane, click Data Migration and Synchronization.

  4. Click the Data Migration tab, then click Create Data Migration Task.

Step 2: Configure source and destination databases

If the current RDS instance is the source or destination, the Instance Region and RDS Instance ID parameters are automatically filled in and cannot be modified.

Configure the source database:

  1. Set the Database Account and Database Password parameters.

  2. Set the Encryption parameter.

Configure the destination database:

  1. Set the Database Type and Access Method parameters.

  2. Set the Instance Region and RDS Instance ID parameters.

  3. Set the Encryption parameter.

Click Test Connectivity and Proceed to verify the connection before moving on.

Step 3: Configure objects

This step follows the same configuration as the original DTS console. The new DTS console has an optimized experience. See [Notice] DTS console fully upgraded.
  1. Set Migration Types. Choose based on whether your source database can go offline during migration: To migrate with minimal downtime: select both Full Data Migration and Incremental Data Migration. The task performs a full load first, then continuously applies changes until you cut over.

    Migration type What it does When to use
    Schema Migration Migrates database schemas (tables, indexes, constraints) without data Run first if you need to create the target schema before migrating data
    Full Data Migration Copies all existing data from the source to the destination at a point in time Use when your source database can go offline during migration, or for an initial bulk load
    Incremental Data Migration Captures and applies ongoing changes (inserts, updates, deletes) from the source after the full data migration completes Use when your source database cannot go offline, or when you need near-zero downtime migration
  2. Set Processing Mode of Conflicting Tables:

    • Precheck and Report Errors: DTS checks for table conflicts before starting. If conflicts are found, the task stops and reports the errors. Use this mode when data integrity is critical and you want to resolve conflicts before migration begins.

    • Ignore Errors and Proceed: DTS skips conflicting tables and continues migrating the rest. Use this mode when you accept partial conflicts and prefer the task to continue without interruption.

  3. Set Capitalization of Object Names in Destination Instance to control whether database names, table names, and column names are capitalized in the destination. By default, DTS default policy is selected. To make capitalization match your source or destination database, select another option. See Specify the capitalization of object names in the destination instance.

  4. In the Source Objects section, select the objects to migrate and move them to the Selected Objects section.

  5. To rename objects in the destination instance, click the object name inline. To rename multiple objects at once, click Batch Edit in the upper-right corner.

  6. (Optional) Click Advanced Settings (Optional) to configure advanced parameters: Use the following references for parameter details based on your source and destination: For cross-account migrations, see Migrate data between ApsaraDB RDS instances of different Alibaba Cloud accounts.

    • In Data Verification Settings, set Data Verification Mode. The available options depend on the migration types selected in step 1.

    • In Advanced Settings, configure any remaining parameters based on your requirements. These settings and subsequent steps match the DTS console experience.

    From ApsaraDB RDS for MySQL:

    Destination Reference
    Self-managed MySQL instance Migrate data between ApsaraDB RDS for MySQL instances
    PolarDB for MySQL cluster Migrate data from an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster
    AnalyticDB for MySQL V3.0 cluster Migrate data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL V3.0 cluster
    Tair/ApsaraDB for Redis instance Migrate data from an ApsaraDB RDS for MySQL instance to a Tair or ApsaraDB for Redis instance
    ApsaraDB RDS for PostgreSQL instance Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB RDS for PostgreSQL instance
    ApsaraMQ for Kafka instance Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraMQ for Kafka instance
    AnalyticDB for PostgreSQL instance Migrate data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance
    Self-managed Oracle database Migrate data from an ApsaraDB RDS for MySQL instance to a self-managed Oracle database
    PolarDB-X 1.0 instance Migrate data from an ApsaraDB RDS for MySQL instance to a PolarDB-X 1.0 instance
    PolarDB-X 2.0 instance Migrate data from an ApsaraDB RDS for MySQL instance to a PolarDB-X 2.0 instance
    ApsaraDB for ClickHouse cluster Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for ClickHouse cluster
    DataHub project Migrate data from an ApsaraDB RDS for MySQL instance to a DataHub project
    Elasticsearch cluster Migrate data from an ApsaraDB RDS for MySQL instance to an Elasticsearch cluster
    MaxCompute project Migrate data from an ApsaraDB RDS for MySQL instance to a MaxCompute project
    ApsaraDB for SelectDB instance Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for SelectDB instance
    Tablestore instance Migrate data from an ApsaraDB RDS for MySQL instance to a Tablestore instance

    To ApsaraDB RDS for MySQL:

    Source Reference
    Self-managed MySQL instance Migrate self-managed MySQL to RDS MySQL
    PolarDB for MySQL cluster Migrate data from a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance
    ApsaraDB RDS for SQL Server instance Migrate data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance
    ApsaraDB RDS for PostgreSQL instance Migrate data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance
    Self-managed Oracle database Migrate data from a self-managed Oracle database to an ApsaraDB RDS for MySQL instance
    PolarDB-X 1.0 instance Migrate data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance
    PolarDB-X 2.0 instance Migrate data from a PolarDB-X 2.0 instance to an ApsaraDB RDS for MySQL instance
    Db2 for LUW instance Migrate data from a Db2 for LUW instance to an ApsaraDB RDS for MySQL instance
    ApsaraDB RDS for MariaDB instance Migrate data from an ApsaraDB RDS for MariaDB instance to an ApsaraDB RDS for MySQL instance
    MaxCompute project Migrate data from a MaxCompute project to an ApsaraDB RDS for MySQL instance
    OceanBase database in MySQL mode Migrate data from an OceanBase database in MySQL mode to an ApsaraDB RDS for MySQL instance
    Self-managed TiDB database Migrate incremental data from a self-managed TiDB database to an ApsaraDB RDS for MySQL instance

FAQ

**What do I do if the DTS-RETRY-ERR-0069: Datasource rejected establishment of connection (.*)? Too many connections error appears?**

The source or destination database has reached its maximum connection limit. Increase the maximum number of connections on the affected database, then restart the migration task.

For other DTS errors, see Common errors and troubleshooting.