All Products
Search

This Product

    Data Transmission Service:Migrate RDS for MySQL to PolarDB for MySQL

    Document Center

    Data Transmission Service:Migrate RDS for MySQL to PolarDB for MySQL

    Last Updated:Jul 17, 2026

    Use Data Transmission Service (DTS) to migrate data from a MySQL database to a PolarDB for MySQL cluster.

    Supported source databases

    The source MySQL database can be one of the following types. This topic uses an ApsaraDB RDS for MySQL instance as an example. The configuration process for other types of source databases is similar.

    • ApsaraDB RDS for MySQL instances.

    • Self-managed databases:

      • Self-managed database with a public IP address
      • 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
      • Self-managed database that is connected over Database Gateway

    Prerequisites

    Limits

    Note

    Type

    Description

    Source database limits

    • Bandwidth requirement: The server that hosts the source database must have sufficient outbound bandwidth. Otherwise, the data migration rate is affected.

    • Tables to migrate must have a primary key or a unique constraint whose column values are unique. Otherwise, duplicate data may be generated in the destination database.

    • If the migration objects are at the table level and you need to edit them (for example, to map column names), a single migration task supports at most 1,000 tables. If the number exceeds the limit, an error is returned when you submit the task. In this case, split the tables to migrate and configure the migration in multiple tasks, or configure a database-level migration task.

    • If you perform incremental migration, binary logs must meet these requirements:

      • Binary logging must be enabled, with binlog_format set to row and binlog_row_image set to full. Otherwise, the precheck reports an error and the data migration task cannot start.

        Important

        If the self-managed MySQL source instance is a dual-primary cluster (the two servers are both primary and replica of each other), enable the log_slave_updates parameter to ensure that DTS captures all binary logs.

      • ApsaraDB RDS for MySQL instances must retain local binary logs for at least three days (seven days is recommended). Self-managed MySQL databases must retain local binary logs for at least seven days. Otherwise, DTS may fail to fetch binary logs and the task may fail. In extreme cases, data inconsistency or data loss may occur. Issues caused by setting a binary log retention time shorter than the DTS requirement are not covered by the DTS SLA.

        Note

        For how to configure the local binary log retention period on an ApsaraDB RDS for MySQL instance, see Configure automatic deletion (local log retention policy).

    • Restrictions on source database operations:

      • During the schema migration and full data migration phases, do not perform DDL operations that change database or table schemas. Otherwise, the data migration task fails.

        Note

        During the full data migration phase, DTS queries the source database, which generates metadata locks that may block DDL operations on the source database.

      • If you perform only full data migration, do not write new data to the source instance. Otherwise, data inconsistency between the source and destination occurs. To keep data consistent in real time, we recommend that you select Schema migration, Full data migration, and Incremental data migration.

    • While the migration instance is running, data generated by operations that are not written to the binary log (such as data restored by physical backup or generated by cascade operations) is not migrated to the destination database.

      Note

      If this occurs and your business allows, re-run a full data migration.

    • If the source database is MySQL 8.0.23 or later and the data to migrate contains invisible columns, data loss may occur because DTS cannot fetch data from those columns.

      Note

      You can use the ALTER TABLE <table_name> ALTER COLUMN <column_name> SET VISIBLE; statement to make an invisible column visible. For more information, see Invisible Columns.

    • MySQL compatibility: When DTS migrates data from a MySQL-family source database, it relies on the standard MySQL protocol and binary log format. Behaviors that are not compatible with standard MySQL are not supported. If your source database claims to be MySQL-compatible but behaves differently from MySQL (for example, when OceanBase acts as a MySQL-compatible source database, the timestamp of the rotate event at the end of the binary log is 0, which is inconsistent with MySQL), the DTS migration task may fail unexpectedly.

    Other limits

    • We recommend that the source and destination databases use the same MySQL version for compatibility.

    • If your source database uses temporary-table-mode online DDL operations—including multi-table merge scenarios—or adds function-based indexes to unique key columns, data loss or task failure may occur on the destination database.

    • Parsers defined by using comment syntax cannot be migrated.

    • If a primary key or unique key conflict occurs during migration:

      • If the table schemas are consistent and a record in the destination database has the same primary key value as a record in the source database:

        • During full migration, DTS keeps the record in the destination database. The record from the source database is not migrated.

        • During incremental migration, DTS does not keep the record in the destination database. The record from the source database overwrites the record in the destination database.

      • If the table schemas are inconsistent, only some columns of data may be migrated, or the migration may fail. Proceed with caution.

    • Before migration, evaluate the performance of the source and destination databases. We recommend that you migrate data during off-peak hours, as DTS consumes read and write resources on both databases during full data migration, which may increase the database load.

    • Because full data migration runs concurrent INSERT operations, table fragmentation occurs in the destination database. After full data migration, the storage space of tables in the destination database is larger than that of the source instance.

    • If the data to migrate contains content that requires four-byte storage (such as rare characters or emoji), the destination database and tables that receive the data must use the utf8mb4 character set.

      Note

      If you use DTS to migrate the schema, set the instance-level parameter character_set_server to utf8mb4 on the destination database.

    • Verify whether the migration precision that DTS applies to FLOAT and DOUBLE columns meets your business requirements. DTS reads the values of these columns by calling ROUND(COLUMN,PRECISION). If the precision is not explicitly defined, DTS migrates FLOAT with 38-digit precision and DOUBLE with 308-digit precision.

    • DTS attempts to resume failed migration tasks within seven days. Therefore, before switching your business to the destination instance, complete or release the task, or run the revoke command to revoke the write permissions of the account that DTS uses to access the destination instance. This prevents the task from resuming automatically and overwriting data in the destination instance with data from the source.

    • DTS does not support converting datetime data to varchar.

    • If a DDL statement fails to write to the destination database, the DTS task keeps running. You must view the failed DDL statement in the task log. For how to view the task log, see View task logs.

    • If Fully Encrypted Database (EncDB) is enabled on an RDS MySQL instance, full data migration is not supported.

      Note

      RDS MySQL instances that have Transparent Data Encryption (TDE) enabled support schema migration, full data migration, and incremental data migration.

    • To migrate accounts from the source database, you must meet the applicable prerequisites and understand the related considerations. For more information, see Migrate database accounts.

    • If a task fails, DTS support staff will attempt to restore it within eight hours. During restoration, they may restart the task or adjust its parameters.

      Note

      Only DTS task parameters are modified—not database parameters. Parameters that may be adjusted include those listed in Modify instance parameters.

    Special cases

    • When the source database is a self-managed MySQL database:

      • If the source database performs a primary/secondary switchover during migration, the migration task fails.

      • The migration latency reported by DTS is the difference between the timestamp of the latest data migrated to the destination database and the current timestamp. If the source database has not performed DML operations for a long time, the reported latency may be inaccurate. If the displayed latency seems too high, run a DML operation on the source database to update the latency.

        Note

        If you migrate an entire database, you can also create a heartbeat table that is updated or written to at regular intervals (for example, every second).

      • DTS periodically runs the CREATE DATABASE IF NOT EXISTS `test` statement on the source database to advance the binary log position.

      • If the source database is Amazon Aurora MySQL or another MySQL cluster mode, make sure that the domain name or IP address configured for the task—and its DNS resolution—always resolves to a read/write (RW) node. Otherwise, the migration task may not run properly.

    • When the source database is RDS MySQL:

      • To migrate incremental data, RDS MySQL instances that do not record transaction logs (such as read-only instances of RDS MySQL 5.6) cannot be used as source databases.

      • DTS periodically runs the CREATE DATABASE IF NOT EXISTS `test` statement on the source database to advance the binary log position.

    • When the destination database is PolarDB MySQL Edition:

      • DTS automatically creates a database in PolarDB for MySQL. If the name of the database to be migrated does not meet the naming conventions of PolarDB for MySQL, you must create the database in PolarDB for MySQL before you configure the migration task. For related operations, see Manage databases.

      • You cannot adjust the full migration rate.

    Billing

    Migration type

    Instance configuration fee

    Internet traffic fee

    Schema migration and full data migration

    Free of charge.

    You are charged Internet traffic fees when the Access Method of the destination database is set to Public IP Address. For more information, see Billing overview.

    Incremental data migration

    Charged. For more information, see Billing overview.

    Migration types

    • Schema migration

      DTS migrates the schema definitions of the selected objects from the source database to the destination database.

      • DTS supports schema migration for tables, views, triggers, stored procedures, and functions.

        Note

        The routine_body of stored procedures, the routine_body of functions, and the select_statement of views are not modified.

      • During schema migration, DTS changes the `DEFINER` to `INVOKER` for the views, stored procedures, and functions to be migrated. This action changes the value of `SQL SECURITY` to `INVOKER`. DTS also sets the `DEFINER` to the destination database account that is used for the migration task.

        Note

        The security authentication method and definer of the source database are not modified.

      • Because DTS does not migrate user information, you must grant read and write permissions to the invoker to call views, stored procedures, and functions in the destination database.

    • Full migration

      DTS migrates all historical data of the selected objects from the source database to the destination database.

    • Incremental migration

      After full migration completes, DTS migrates incremental data changes from the source to the destination database, allowing you to migrate data without interrupting your self-managed applications.

    SQL operations for incremental migration

    Operation type

    SQL statement

    DML

    INSERT, UPDATE, DELETE

    DDL

    • ALTER TABLE, ALTER VIEW

    • CREATE FUNCTION, CREATE INDEX, CREATE PROCEDURE, CREATE TABLE, CREATE VIEW

    • DROP INDEX, DROP TABLE

    • RENAME TABLE

      Important

      A RENAME TABLE operation may cause data inconsistency. For example, if you select only one table as the migration object and rename the table in the source instance during migration, the data of this table is not migrated to the destination database. To prevent this issue, select the entire database to which the table belongs as the migration object when you configure the data migration task. Make sure that the databases to which the table belongs before and after the RENAME TABLE operation are both included in the migration objects.

    • TRUNCATE TABLE

    Required permissions for database accounts

    Database

    Schema migration

    Full data migration

    Incremental data migration

    ApsaraDB RDS for MySQL instance

    SELECT permission

    SELECT permission

    REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions

    PolarDB for MySQL cluster

    Read and write permissions

    For instructions on creating database accounts and granting permissions, see:

    Procedure

    1. Navigate to the migration task list page for the destination region using one of the following methods.

      From the DTS console

      1. Log on to the Data Transmission Service (DTS) console.

      2. In the navigation pane on the left, click Data Migration.

      3. In the upper-left corner of the page, select the region where the migration instance is located.

      From the DMS console

      Note

      The actual operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode console and Customize the layout and style of the DMS console.

      1. Log on to the Data Management (DMS) console.

      2. In the top menu bar, choose Data + AI > Data Transmission (DTS) > Data Migration.

      3. To the right of Data Migration Tasks, select the region where the migration instance is located.

    2. Click Create Task to navigate to the task configuration page.

    3. Optional: In the upper-right corner of the page, click New Configuration Page.

      Note

      • If you are already on the new configuration page (the button in the upper-right corner is Back to Previous Version), you can skip this step.

      • The parameters on the new and old configuration pages are different. We recommend that you use the new configuration page.

    4. Configure the source and destination databases.

      Warning

      After you select the source and destination instances, read the Limits at the top of the page to ensure that the migration task can be created and run successfully.

      Section

      Parameter

      Description

      N/A

      Task Name

      DTS generates a task name automatically. Specify a descriptive name for easy identification. The name does not need to be unique.

      Source Database

      Select a DMS database instance.

      Select an existing instance as needed.

      • If you use an existing instance, the database information is automatically filled in. You do not need to enter it again.

      • If you do not use an existing instance, configure the following database information.

      Note

      Database Type

      Select MySQL.

      Connection Type

      Select Alibaba Cloud Instance.

      Instance Region

      Select the region of the source ApsaraDB RDS for MySQL instance.

      Cross-account

      This example migrates data within the same Alibaba Cloud account. Select No.

      RDS Instance ID

      Select the ID of the source ApsaraDB RDS for MySQL instance.

      Database Account

      Enter the database account of the source ApsaraDB RDS for MySQL instance. For information about the required permissions, see Required permissions for database accounts.

      Database Password

      Enter the password for the database account.

      Connection Method

      Select Non-encrypted or SSL-encrypted based on your database requirements. If you set this parameter to SSL-encrypted, you must enable SSL encryption for the RDS for MySQL instance beforehand. For more information, see Quickly enable SSL encryption using a cloud certificate.

      Destination Database

      Select a DMS database instance.

      Select an existing instance as needed.

      • If you use an existing instance, the database information is automatically filled in. You do not need to enter it again.

      • If you do not use an existing instance, configure the following database information.

      Note

      Database Type

      Select PolarDB for MySQL.

      Connection Type

      Select Alibaba Cloud Instance.

      Instance Region

      Select the region of the destination PolarDB for MySQL cluster.

      PolarDB Cluster ID

      Select the ID of the destination PolarDB for MySQL cluster.

      Database Account

      Enter the database account for the destination PolarDB for MySQL cluster. For information about the required permissions, see Required permissions for database accounts.

      Database Password

      Enter the password for the database account.

      Encryption

      Select a connection type as needed. For more information about the SSL encryption feature, see Enable SSL encryption.

    5. After you complete the configuration, click Test Connectivity and Proceed at the bottom of the page.

      If the source or destination database is an Alibaba Cloud database instance, such as an RDS for MySQL or ApsaraDB for MongoDB instance, DTS automatically adds the CIDR blocks of DTS servers to the IP address whitelist of the instance. If the source or destination database is a self-managed database hosted on an ECS instance, DTS automatically adds the CIDR blocks of DTS servers to the security group rules of the ECS instance. You must also ensure that the database is accessible from the ECS instance. If the self-managed database is hosted on multiple ECS instances, you must manually add the CIDR blocks of DTS servers to the security group rules of each ECS instance. If the source or destination database is a self-managed database that is deployed in an on-premises data center or provided by a third-party cloud service provider, you must manually add the CIDR blocks of DTS servers to the IP address whitelist of the database to allow access from DTS servers. For more information about the IP addresses of DTS servers, see CIDR blocks of DTS servers.

      Warning

      Adding the public IP address blocks of DTS servers, whether automatically or manually, may introduce security risks. Using this product, you acknowledge and accept these potential risks. You must implement basic security measures, such as using strong passwords, limiting open ports for each CIDR block, using authentication for internal API calls, and regularly checking and restricting unnecessary CIDR blocks. You can also connect using an internal network, such as a leased line, VPN Gateway, or Smart Access Gateway.

    6. Configure the task objects.

      1. On the Configure Objects page, configure the objects that you want to migrate.

        Parameter

        Description

        Migration Types

        • If you only need to perform a full migration, select both Schema Migration and Full Data Migration.

        • To perform a migration with no downtime, select Schema Migration, Full Data Migration, and Incremental Data Migration.

        Note

        • If you do not select Schema Migration, you must ensure that a database and tables to receive the data exist in the destination database. You can also use the object name mapping feature in the Selected Objects box as needed.

        • If you do not select Incremental Data Migration, do not write new data to the source instance during data migration to ensure data consistency.

        Method to Migrate Triggers in Source Database

        Select a method for migrating triggers based on your business requirements. If the objects to be migrated do not involve triggers, you can skip this setting. For more information, see Configure how to synchronize or migrate triggers.

        Note

        This setting is available only when both Migration Types and Schema Migration are selected for Incremental Data Migration.

        Processing Mode of Conflicting Tables

        • Precheck and Report Errors: Checks whether tables with the same names exist in the destination database. If no tables with the same names exist, the precheck is passed. If tables with the same names exist, an error is reported during the precheck, and the data migration task does not start.

          Note

          If a table in the destination database has the same name but cannot be easily deleted or renamed, you can change the name of the table in the destination database. For more information, see Object name mapping.

        • Ignore Errors and Proceed: Skips the check for tables with the same names.

          Warning

          Selecting Ignore Errors and Proceed may cause data inconsistency and business risks. For example:

          • If the table schemas are consistent and a record in the destination database has the same primary key value as a record in the source database:

            • During full migration, DTS keeps the record in the destination database. The record from the source database is not migrated.

            • During incremental migration, DTS does not keep the record in the destination database. The record from the source database overwrites the record in the destination database.

          • If the table schemas are inconsistent, only some columns of data may be migrated, or the migration may fail. Proceed with caution.

        Whether to migrate Event

        Select whether to migrate source database events. If you select Yes, additional steps are required. Synchronize or migrate events.

        Capitalization of Object Names in Destination Instance

        You can configure the case sensitivity policy for the names of migrated objects, such as databases, tables, and columns, in the destination instance. By default, DTS default policy is selected. You can also choose to keep the case sensitivity consistent with the default policy of the source or destination database. For more information, see Case sensitivity of object names in the destination database.

        Source Objects

        Select one or more objects from the Source Objects section. Click the Rightwards arrow icon and add the objects to the Selected Objects section.

        Note

        The granularity for selecting migration objects is schema, table, and column. If you select only tables or columns as migration objects, other objects such as views, triggers, and stored procedures are not migrated to the destination database.

        Selected Objects
        Note

        • If you use the object name mapping feature, the migration of other objects that depend on the renamed object might fail.

        • To filter data by using a WHERE clause, right-click the table to be migrated in the Selected Objects box and specify the filter condition in the dialog box that appears. For instructions, see Set filter conditions.

        • To select SQL operations to migrate at the database or table level, right-click the object in the Selected Objects box and select the desired SQL operations in the dialog box that appears. For a list of supported operations, see Supported SQL operations for incremental migration.

      2. Click Next: Advanced Settings to configure advanced parameters.

        Parameter

        Description

        Dedicated Cluster for Task Scheduling

        By default, DTS schedules tasks on a shared cluster, and no selection is needed. You can purchase a dedicated cluster with specific specifications to run DTS migration tasks. For more information, see What is a DTS dedicated cluster?.

        Select the engine type of the destination database

        Select the engine type for the destination database based on your business requirements.

        • InnoDB: The default storage engine.

        • X-Engine: An online transaction processing (OLTP) database storage engine.

        Copy the temporary table of the Online DDL tool that is generated in the source table to the destination database.

        If you use Data Management (DMS) or gh-ost to perform online DDL changes in the source database, you can choose whether to migrate the data from the temporary tables generated by the online DDL changes.

        Important

        • DTS tasks do not support using tools such as pt-online-schema-change to perform online DDL changes. Otherwise, the DTS task fails.

        • The processing methods for each phase are as follows: The Schema Migration and Full Data Migration phases do not allow DDL operations that change the database or table structure. Therefore, they are not controlled by the online DDL policy.

          • Schema Migration: Not controlled by the online DDL policy. Related temporary tables are created.

          • Full Data Migration: Not controlled by the online DDL policy. The migration of temporary tables is not included in the full migration objects. All tables whose names match the regular expression (^_(.+)_(?:gho|new)$ or ^_(.+)_(?:ghc|del|old)$) are filtered out.

          • Incremental Data Migration: Controlled by the online DDL policy.

            • Yes: Migrates data changes from temporary tables (for example, _table_name_gho) generated by online DDL operations.

            • No, Adapt to DMS Online DDL and No, Adapt to gh-ost: Filters out data changes from temporary tables (for example, _table_name_gho) generated by tools such as gh-ost based on regular expression rules.

        • Yes: Migrates the data from the temporary tables generated by online DDL changes.

          Note

          If online DDL changes generate a large amount of data in temporary tables, it may cause task latency.

        • No, Adapt to DMS Online DDL: Does not migrate the data from the temporary tables generated by online DDL changes. It only migrates the original DDL statements executed using Data Management (DMS).

          Note

          This option causes tables in the destination database to be locked.

        • No, Adapt to gh-ost: Does not migrate the data from the temporary tables generated by online DDL changes. It supports custom filtering rules. DTS filters out data changes from temporary tables (for example, _table_name_gho) generated by tools such as gh-ost based on regular expression rules. You can modify the default regular expressions used to match shadow and useless tables as needed:

          • Shadow table: ^_(.+)_(?:gho|new)$

          • Useless table: ^_(.+)_(?:ghc|del|old)$

          Note

          This option causes tables in the destination database to be locked.

        Whether to Migrate Accounts

        Choose whether to migrate account information from the source database. If you select Yes, you also need to select the accounts to be migrated and confirm their permissions. For more information, including authorization methods, see Migrate database accounts.

        Retry Time for Failed Connections

        After the migration task starts, if the connection to the source or destination database fails, DTS reports an error and immediately begins to retry the connection. The default retry duration is 720 minutes. You can customize the retry time to a value from 10 to 1440 minutes. We recommend that you set the duration to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified duration, the migration task automatically resumes. Otherwise, the task fails.

        Note

        • For multiple DTS instances that share the same source or destination, the network retry time is determined by the setting of the last created task.

        • Because you are charged for the task during the connection retry period, we recommend that you customize the retry time based on your business needs, or release the DTS instance as soon as possible after the source and destination database instances are released.

        Retry Time for Other Issues

        After the migration task starts, if a non-connectivity issue, such as a DDL or DML execution exception, occurs in the source or destination database, DTS reports an error and immediately begins to retry the operation. The default retry duration is 10 minutes. You can customize the retry time to a value from 1 to 1440 minutes. We recommend that you set the duration to more than 10 minutes. If the related operations succeed within the specified retry duration, the migration task automatically resumes. Otherwise, the task fails.

        Important

        The value of Retry Time for Other Issues must be less than the value of Retry Time for Failed Connections.

        Enable Throttling for Full Data Migration

        During full migration, DTS consumes read and write resources on the source and destination databases, which may increase the database load. If required, you can enable throttling for the full migration task. You can set Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) to reduce the load on the destination database.

        Note

        • This configuration item is available only if you select Full Data Migration for Migration Types.

        • You can also adjust the full migration speed after the migration instance is running.

        Enable Throttling for Incremental Data Migration

        If required, you can also choose to set speed limits for the incremental migration task. You can set RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) to reduce the load on the destination database.

        Note

        • This configuration item is available only if you select Incremental Data Migration for Migration Types.

        • You can also adjust the incremental migration speed after the migration instance is running.

        Environment Tag

        Select an environment tag to identify the instance based on your business requirements. No selection is needed for this example.

        Whether to delete SQL operations on heartbeat tables of forward and reverse tasks

        Choose whether to write heartbeat SQL information to the source database when the DTS instance is running.

        • Yes: Heartbeat SQL information is not written to the source database. This may cause the DTS instance to report a delay.

        • No: Writes heartbeat SQL information to the source database. This may interfere with features such as physical backup and cloning of the source database.

        Configure ETL

        Choose whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values:

        Monitoring and Alerting

        Select whether to set alerts and receive alert notifications based on your business needs.

        • No: Does not set an alert.

        • Yes: Configure alerts by setting an alert threshold and an alert notifications. If a migration fails or the latency exceeds the threshold, the system sends an alert notification.

      3. Click Next: Data Validation to configure a data validation task.

        If you want to use the data validation feature, see Configure data validation for configuration instructions.

    7. Save the task and run a precheck.

      • To view the parameters for configuring this instance when you call the API operation, move the pointer over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the bubble that appears.

      • If you do not need to view or have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.

      Note

      • Before the migration task starts, DTS performs a precheck. The task starts only after it passes the precheck.

      • If the precheck fails, click View Details next to the failed check item, fix the issue based on the prompt, and then run the precheck again.

      • If a warning is reported during the precheck:

        • For check items that cannot be ignored, click View Details next to the failed item, fix the issue based on the prompt, and then run the precheck again.

        • For check items that can be ignored, you can click Confirm Alert Details, Ignore, OK, and Precheck Again to skip the alert item and run the precheck again. If you choose to ignore a warning, it may cause issues such as data inconsistency and pose risks to your business.

    8. When the Success Rate is 100%, click Next: Purchase Instance.

    9. Purchase the instance.

      1. On the Purchase page, select the link specification for the data migration instance. For more information, see the following table.

        Category

        Parameter

        Description

        New Instance Class

        Resource Group Settings

        Select the resource group to which the instance belongs. The default value is default resource group. For more information, see What is Resource Management?

        Instance Class

        DTS provides migration specifications with different performance levels. The link specification affects the migration speed. You can select a specification based on your business scenario. For more information, see Data migration link specifications.

      2. After the configuration is complete, read and select Data Transmission Service (Pay-as-you-go) Service Terms.

      3. Click Buy and Start. In the OK dialog box that appears, click OK.

        You can view the progress of the migration task on the Data Migration Tasks list page.

        Note

        • If the migration task does not include incremental migration, it stops automatically after the full migration is complete. After the task stops, its Status changes to Completed.

        • If the migration task includes incremental migration, it does not stop automatically. The incremental migration task continues to run. While the incremental migration task is running, the Status of the task is Running.