All Products
Search
Document Center

PolarDB:Migration evaluation

Last Updated:May 07, 2026

To ensure a smooth migration, PolarDB offers a migration evaluation feature. Before migrating, use this feature to check prerequisites like instance status, task dependencies, and source instance properties. Identifying and resolving issues in advance reduces the cost and effort of the actual migration.

If you encounter issues during the migration evaluation, see the FAQ for solutions.

Supported regions

The migration evaluation feature is available in the following regions:

China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Chengdu), China (Hong Kong), Singapore, Indonesia (Jakarta), US (Silicon Valley), and US (Virginia).

Impact

A migration evaluation does not affect your services.

Create a migration evaluation task

  1. Log on to the PolarDB console. On the Clusters page, click Migration/Upgrade Evaluation.

  2. Create a migration evaluation task. PolarDB provides three ways to create a migration evaluation task:

    • From the Clusters page: In the upper-left corner of the Clusters page, click Migrate/Upgrade Evaluation.

      image

    • From the Migration/Upgrade page: In the upper-left corner of the Migration/Upgrade page, click Create Migration/Upgrade Evaluation.

      image

    • On the PolarDB buy page for a one-click upgrade: Select Migrate from RDS, the Source RDS Version, the target Database Engine, and the target Database Edition. Then, click Migration Evaluation.

      image

  3. Configure the parameters for the migration evaluation task.

    Parameter

    Description

    Creation method

    Select Migrate from RDS.

    If you create a migration evaluation task from the PolarDB buy page, you do not need to specify this parameter. The system automatically selects Migrate from RDS.

    Source RDS version

    Select the engine version of the source RDS instance.

    Source RDS instance

    From the drop-down list, select the source RDS instance.

    Target database engine

    Select the database engine version of the destination PolarDB for MySQL cluster.

    Database edition

    Select the database edition of the destination PolarDB for MySQL cluster.

    Then, click Next.

  4. PolarDB prechecks and evaluates your source RDS instance and migration plan based on four categories: Basic information verification, Migration task dependency verification, Key information verification, and Other verification. Resolve any issues found based on the evaluation results.

    PolarDB has compiled a list of common issues that you may encounter during a migration evaluation and their solutions. For more information, see Common issues and solutions.

    image

    Note

    DTS cannot synchronize events during migration or upgrade tasks. If the event check result is Existing, you must manually synchronize the events to the destination PolarDB cluster.

  5. Click Continue to Buy or Buy to go to the PolarDB buy page and complete the subsequent steps. For more information, see Upgrade procedure.

Manage migration evaluation tasks

To view the details of an existing evaluation task, go to the Migration/Evaluation page. After an evaluation is complete, you can re-evaluate or proceed to purchase.

Note

Migration evaluation tasks are automatically deleted after seven days. If a task has expired, you can create a new one.

image

FAQ

Category

Check item

Solution

Notice

Event check

The source RDS instance has events, but DTS does not support event synchronization. You must manually synchronize the events to the destination PolarDB cluster.

Source instance basic information check

Source instance running status

The source RDS instance must be in the Running state.

Source instance read/write status

The source RDS instance must be in the Running state and be readable and writable.

Source instance account mode

If the source RDS instance is in high-security mode (database proxy mode), you must create a privileged account (see (Deprecated and redirected to Step 1) Create a database account) or switch to high-performance mode (see Switch to high-performance mode) to perform a one-click upgrade.

PolarDB service-linked role

You must create a service-linked role for PolarDB for your account.

You can follow the instructions in Check whether a service-linked role for PolarDB is created or create one by using OpenAPI.

Migration task dependency check

DTS service permissions

You must grant DTS permissions to access cloud resources.

For instructions, see Grant DTS the permissions to access cloud resources.

Check whether the source instance is empty

The source RDS instance has no databases. You must create a database in the instance before you can start the migration.

Source instance table engine check

Only source RDS instances with tables that use the InnoDB or X-Engine storage engine support the one-click upgrade feature.

Source instance trigger check

If the source RDS instance has triggers, you must delete them first to prevent the migration from being interrupted.

Note

You can run the following statements to delete triggers from the source RDS instance based on your business requirements.

-- View the triggers.
SHOW TRIGGERS;
-- Select and run the statement to delete a trigger.
DROP TRIGGER  trigger_name;

After the migration is complete, you can manually create the triggers in the destination PolarDB cluster.

Source instance tables without primary keys check

If the source RDS instance contains tables without primary keys, duplicate data may occur in the destination database after synchronization.

Connect to the database on the source RDS instance by using a privileged account and run the following SQL statement to find tables without primary keys:

SELECT t1.table_schema, t1.table_name 
FROM information_schema.TABLES t1 LEFT OUTER 
	JOIN information_schema.TABLE_CONSTRAINTS t2 
  ON t1.table_schema = t2.TABLE_SCHEMA AND t1.table_name = t2.TABLE_NAME AND t2.CONSTRAINT_NAME 
  IN ("PRIMARY") 
WHERE t2.table_name IS NULL AND t1.table_type = "BASE TABLE" AND t1.TABLE_SCHEMA NOT IN ("information_schema", "performance_schema", "mysql", "sys");

You can add primary keys to the tables returned by the query.

If you determine that duplicate records are acceptable, you can ignore this check. When prompted during the one-click upgrade process, select Continue Upgrade.

Source instance key information check

Source instance root account check

To ensure compatibility between the account systems of RDS MySQL and PolarDB and prevent system accounts of the destination PolarDB cluster from being overwritten after migration, the source RDS instance cannot have both the root and aliyun_root accounts. For more information, see Delete redundant system accounts from the source RDS instance.