All Products
Search

This Product

    Server Migration Center:Migrate ECS instances between different accounts in the console

    Document Center

    Server Migration Center:Migrate ECS instances between different accounts in the console

    Last Updated:Aug 20, 2025

    Server Migration Center (SMC) lets you migrate ECS instances across zones and regions. You can migrate instances from other Alibaba Cloud accounts and create them as ECS instances or custom images in your current account. The source instance can remain running during the migration, and SMC supports incremental data migration.

    Prerequisites

    Preparations

    • If you use a RAM user to import the migration source, you must grant the `AliyunSTSAssumeRoleAccess` permission to that RAM user in the destination Alibaba Cloud account. This permission allows the user to call the Security Token Service (STS).

      1. Log on to the RAM console using the destination Alibaba Cloud account.

      2. In the navigation pane on the left, choose Users and then click the logon name of the target user.

      3. Choose Permission Management > Add Permissions.

      4. On the Add Permissions page, enter `AliyunSTSAssumeRoleAccess`, select the policy, and then click OK.image

    • Record the Alibaba Cloud account IDs for the source and destination accounts.

      1. Log on to the Alibaba Cloud Management Console using the source and destination accounts.

      2. Hover over the profile icon in the upper-right corner to view the Alibaba Cloud account ID.image

    Step 1: Grant permissions in the source account

    Log on to the RAM console using the source account that owns the ECS instance. This account must have permissions to manage RAM. Then, create a role and grant permissions to it.

    1. Create an access policy.

      1. In the navigation pane on the left, choose Permission Management > Policies. Click Create Policy.image

      2. Click the Script tab. Replace the existing script with the following policy and then click OK. 

        {
    "Version": "1",
    "Statement": [
        {
            "Action": [
                "ecs:DescribeZones",
                "ecs:DescribeInstances",
                "ecs:DescribeSecurityGroupAttribute",
                "ecs:DescribeSecurityGroups",
                "ecs:DescribeSnapshots",
                "ecs:DescribeImages",
                "ecs:DescribeDisks",
                "ecs:DescribeCloudAssistantStatus",
                "ecs:RunCommand",
                "ecs:DescribeInvocations"
            ],
            "Resource": "*",
            "Effect": "Allow"
        }
    ]
}

      3. In the Create Policy dialog box, enter `policy-smc` as the policy name and then click OK.image

    2. Create a role.

      1. In the navigation pane on the left, choose Identity > Roles. Click Create Role.image

      2. For Select Trusted Entity, select Alibaba Cloud Account. In the text box, enter the Alibaba Cloud account ID of the destination account.image

      3. Click OK. In the Create Role dialog box, enter a custom role name. For example, `ram-role-smc`.image

    3. Grant permissions to the role.

      1. On the Roles page, click the name of the role that you created to open the role details page.image

      2. Click the Permissions tab and then click Grant Permission.image

      3. On the Grant Permission page, select Custom Policy. Enter `policy-smc`, which is the access policy that you created in Step 1, and then click OK.image

    Step 2: Import the migration source in the destination account

    1. Log on to the SMC console using the destination account. In the navigation pane on the left, choose Cross-account/Intra-account Migration.

    2. On the Server Migration page, click Import Migration source.

    3. Configure the parameters as prompted and copy the activation code command. The following table describes the parameters.

      Parameter

      Description

      Migration Source Type

      Alibaba Cloud ECS Server.

      Import Method

      Select Console Import.

      SMC remotely connects to the source server from the console to automatically import the migration source. The import process automatically invokes Cloud Assistant. Do not interrupt or exit this process.

      Cross-account Migration

      Cross-account.

      Alibaba Cloud Account Of Source Server

      Enter the Alibaba Cloud account ID of the server that you want to migrate. This is the source Alibaba Cloud account ID.

      Role Of The Source Server's Account

      Enter the role that you created and authorized in Step 1. For example, `ram-role-smc`.

      Region

      From the drop-down list, select the region where the server that you want to migrate is located.

      Instance

      Search for and select the ECS instances that you want to migrate in the specified region. You can search by instance ID, instance name, or IP address. You can select multiple instances to perform a batch import.

    4. After you configure the parameters, click Import.

      SMC automatically starts the Cloud Assistant Agent to perform the import. The import process takes about 3 to 10 minutes. Please wait.

    5. On the Cross-account/Intra-account Migration page of the SMC console, view the status of the migration source in the Real-time Migration Status column.

      • If the status is Online, the import is successful.

        Note

        During a cross-account ECS instance migration, the public IP address of the source instance may not be displayed, the operating system may not be fully identified, or the instance status may not be recognized. This is expected behavior and does not affect the migration task.

      • If any other status is displayed, the import failed. Troubleshoot the issue using the following solutions and then re-import the source.

        • You can troubleshoot the issue based on the error message in the console or by viewing the SMC client log file. The default installation directories of the SMC client are:

          • For a Windows server: C:\smc.

          • For a Linux server: /smc.

        • For information about common issues and solutions, see SMC FAQ and Troubleshoot errors.

    Step 3: Configure the migration in the destination account

    1. Find the migration source that you want to manage and click Start Migration in the Actions column.

    2. Configure the parameters and click Start Migration.

      1. Configure the basic parameters described in the following table.

        Parameter

        Description

        Example

        Migration Job Name

        The name of the migration job.

        Server migration

        Job Description

        The description of the migration job.

        test

        Destination Type

        Required. The type of the destination. Select a destination type based on the actual migration scenario.

        ECS Image

        Migrate the source server to an ECS custom image and then use the custom image to create an ECS instance.

        If you set the Destination Type parameter to ECS Image, the following parameters are displayed:

        • Destination Region: the Alibaba Cloud region to which you want to migrate the source server. This parameter is required. For more information about regions, see Regions and zones.

        • Image Name: the name of the destination custom image generated by SMC for the source server.

        ECS Instance

        Migrate the source server to an existing ECS instance whose configurations such as storage and operating system match those of the source server.

        Important

        During the migration, the operating system of the destination ECS instance is replaced, and automatic snapshots of the system disk are released and cannot be recovered. If you want to retain automatic snapshots for future needs or for data security considerations, you can manually cancel the release of automatic snapshots together with the disk before the migration. For more information, see Delete automatic snapshots while releasing a disk.

        If you set the Destination Type parameter to ECS Instance, the following parameters are displayed:

        • Destination Region: the Alibaba Cloud region to which you want to migrate the source server. This parameter is required. For more information about regions, see Regions and zones.

        • Destination Instance: the ECS instance that is used as the destination instance.

        ECS Image

        Migration Test

        Specifies whether to enable the migration test feature. This feature helps you understand the feasibility and risks of a migration job before the migration job starts and provides solutions to identified issues. You can also obtain information such as the amount of data to be migrated, migration speed, and total duration of the migration. This helps reduce the issues and losses that may occur during the actual migration. During the test, you are charged for pay-as-you-go resources. By default, Migration Test is turned on.

        Warning

        If you set the Destination Type parameter to ECS Instance, snapshots are created for all disks of the destination ECS instance. If the migration test is abnormal or the Execution Method parameter is set to Test Only, the disk snapshots are automatically rolled back. During the migration test, the destination ECS instance is unavailable and all data is lost. Make sure that the destination ECS instance does not have important data.

        For more information, see Configure a migration test.

        Keep the default setting

        Execution Method

        The mode in which the migration job is run. Select an execution method based on whether Migration Test is turned on.

        When Migration Test is turned on

        • Test Only: The system performs only the migration test. After the migration test is complete, you must manually start the server migration job.

        • Test and Migrate: The system performs the migration test. After the migration test is complete, if no test items are in the Critical state, the system automatically starts the server migration job. This is the default value.

        When Migration Test is turned off

        • Migrate Now: The migration job starts immediately after it is created. This is the default value.

        • Migrate Later: The migration job automatically starts at the specified time after it is created.

          Note

          The earliest time that you can specify to run a migration job is 10 minutes after the job is created.

        • Create Only: After the migration job is created, you must click Start Migration Job in the Actions column to manually start the migration job.

        Keep the default setting

        Automatic Incremental Synchronization

        Specifies whether SMC automatically synchronizes incremental data of the migration source to Alibaba Cloud. By default, this feature is disabled.

        • If you enable this feature, you must configure the following parameters:

          • Synchronization Interval: the interval at which SMC automatically synchronizes incremental data to Alibaba Cloud.

          • Maximum Reserved Images: the maximum number of images that can be retained during incremental data synchronization.

          SMC automatically synchronizes incremental data to Alibaba Cloud at the specified interval. For more information about the best practices for incremental data synchronization, see Migrate incremental data from a server.

        • If you disable this feature, incremental data is not synchronized.

        Keep the default setting

        Enable Migration Template

        If you set the Destination Type parameter to ECS Image, this parameter is available.

        The migration template is used to preset parameters for a migration task, and the template parameters are automatically filled in when the migration starts. For more information about setting up a migration template, see Configure the migration template.

        Keep the default setting

      2. Adjust the disk partition structure as needed. The following table describes the parameters.

        Parameter

        Description

        Example

        Modify Disk Partition

        Determine whether to enable Modify Disk Partition based on your needs. This feature is only supported in SMC client 2.8.0 or above. For more information, see Use the SMC client.

        • Not enabled: By default, the disk partition structure of the destination system are the same as those of the migration source.

        • Enabled: You can adjust the destination disk partition structure, including partition size and order, transfer method, whether to enable LVM, and other configurations.

          The parameter descriptions for the disk partition structure are as follows.

          Configure disks

          • System Disk: the size of the system disk of the destination instance. Unit: GiB. Valid values: 20 to 2048,

            The size of the destination system disk must be larger than the amount of data on the source system disk. For example, if the total size of the source system disk is 400 GiB but the size of data stored on this disk is only 100 GiB, you must set this parameter to a value greater than 100.

            Note

            The default value of this parameter is the size of the source system disk. We recommend that you retain the default value or specify a greater value.

          • Data Disk <N>: the size of the data disk of the destination instance. Unit: GiB. Valid values: 1 to 32768.

            • The variable <N> indicates the serial number of the data disk. If the disk is migrated to the destination instance, N is the ID of the data disk.

            • The size of the destination data disk must be larger than the amount of data on the source data disk. For example, if the total size of the source data disk is 500 GiB but the size of data stored on this disk is only 100 GiB, you must set this parameter to a value greater than 100.

            • If there are no mount targets under the data disk or if all mount targets are not migrated, the data disk will not be migrated.

          • LVM: Logical Volume Manager (LVM) is a mechanism for managing disk partitions in Linux systems. LVM is more flexible than traditional disk partitions and allows for dynamic adjustment of disk space.

            You can select whether to enable LVM based on your needs. After enabling LVM, the destination will automatically rebuild the disk with an LVM structure.

            Example description:

            For each destination disk where LVM is enabled, the system will create one Physical Volume (PV) and its corresponding Volume Group (VG). On the VG, a number of Logical Volume Manager (LVM) corresponding to the mount targets are created. By default, the VG name is vgX (where X is the serial number of the disk), and the LVM name is lvX (where X is the serial number of the LVM). An example is provided in the following figure.

            image

            Important

            LVM is not supported in the following scenarios:

            • When the migration source is a Windows system.

            • When the system disk does not have a boot partition.

            After enabling LVM, the feature does not take effect in the following scenarios:

            • The migration source does not support lvm2 or the lvm2 package is not installed.

            • The migration source is a Debian system with a kernel version of 3.x or earlier, and disks with XFS file systems are mounted.

          Configure mount targets

          • Whether to Migrate: You can select whether to migrate the mount target based on your business needs.

          • Enable Block Replication: Enabling block replication can effectively improve the stability of migration transmission speed while ensuring consistency with the source partition structure. However, the partition size cannot be modified. SMC determines whether to support enabling block replication based on the migration source disk partition status.

            • If the migration source does not support block replication for partitions, the Enable Block Replication switch cannot be turned on, and default file replication method is used, allowing partition size modification.

            • If the migration source supports block replication for partitions, the Enable Block Replication switch is enabled by default to achieve partition-level disk migration.

            Note

            • When the migration source is a Windows operating system, the block replication feature is enabled by default and cannot be disabled.

            • If LVM is enabled on the disk and the partition size is not an integer multiple of 4 MiB, block replication does not take effect, and file replication is used for data transfer.

          • Set partition size: When block replication is not enabled, you can set the partition size based on your needs, but the sum of partition sizes cannot exceed the size of the disk they belong to.

          Note

          If the size of disks of the destination instance do not match that of the migration source disks, the migration task cannot be created. In this case, the system will automatically adjust the mount target positions to meet the disk size requirements. If the requirements cannot be met after the adjustment, handle the issue as prompted.

          You can also manually drag and drop mount targets to meet disk size requirements. However, drag-and-drop is not supported for partitions of type boot or system. The specific operations are as follows:

          1. Move your pointer over image before the mount target.

          2. Use your pointer to drag the mount target to another disk.

        Keep the default setting

      3. (Optional) To set parameters such as the network mode, private IP address, or transmission throttling, click Advanced Configuration and configure the advanced parameters. The following table describes the parameters.

        Note

        We recommend that you set Network Mode to Private Network. A private network provides faster and more stable data transmission than the internet and improves migration efficiency.

        Parameter

        Description

        Example

        Network Type

        The type of network that is used to migrate data from the source server to the intermediate instance. By default, data is migrated over the Internet. During the migration, SMC creates an intermediate instance that connects to a vSwitch in a VPC. If you select Public Network, a public IP address is assigned to the intermediate instance.

        Public Network (default value)

        SMC migrates data to the intermediate instance over the Internet. If you select Public Network, make sure that the source server can access the Internet. You can determine whether to specify a VPC and a vSwitch based on your business requirements.

        • If you specify a VPC and a vSwitch, SMC creates an intermediate instance that connects to the specified VPC and vSwitch.

        • If you do not specify a VPC or vSwitch, SMC creates an intermediate instance that connects to the VPC and vSwitch automatically created by the system.

        VPC

        SMC migrates data to the intermediate instance over a VPC. If you select VPC, you must specify a VPC and a vSwitch and make sure that the source server can connect to the VPC.

        Note

        If your server in a data center, your VM, or your third-party cloud server can connect to a VPC, we recommend that you select this network type to migrate data. Compared with migration over the Internet, migration over a VPC is more efficient and stable. You can use VPN Gateway, Express Connect, or SAG to connect a migration source to a VPC. For more information, see Connect a VPC to a data center or another cloud.

        Keep the default setting

        Private IPv4 Address

        If you need to change the private IP address of the destination instance, you can manually specify the private IP address. This parameter appears only when the Destination Type is selected as ECS Instance.

        • Remain Unchanged: The default value is the IP address of the destination instance after migration and does not change.

        • Manually Specify: You are allowed to enter an address within the available IP CIDR block of the vSwitch where the destination instance is located. When the migration source IP address is in the CIDR block of the vSwitch, you can change the destination instance IP address to the migration source IP address.

          • When the CIDR block of the destination instance is the same as that of the migration source: Enter the private IP address of the migration source.

          • When the CIDR block of the destination instance is different from that of the migration source: Change the VPC of an ECS instance to make the CIDR block of the destination instance the same as that of the migration source, and then enter the private IP address of the source.

        Transmission Speed Limit

        The maximum network transfer speed during the migration. Unit: Mbit/s. If you set the Compression Ratio parameter to a value greater than 0, the actual network transfer speed, which is the transfer speed of compressed data, is lower than the speed displayed in the Real-time Migration Status column.

        Keep the default setting

        Compression Ratio

        The compression ratio of the data to be migrated. Set the compression ratio based on your business requirements.

        • If the bandwidth is limited, a high compression ratio improves the transmission efficiency.

        • If a high bandwidth is available, we recommend that you do not compress data. Data compression consumes CPU resources of the migration source.

        Valid values: 0 to 10. Default value: 7. A value of 0 indicates that data is not compressed.

        Keep the default setting

        Checksum Verification

        Specifies whether to verify data integrity by using a checksum. By default, this feature is disabled. If you enable this feature, data integrity is ensured, but transmission speed may be reduced.

        Keep the default setting

        SSL-Encrypted Transmission

        Using SSL encryption for data migration enhances security and ensures data integrity. By default, this feature is enabled.

        Keep the default setting

        License Type

        The license type. Valid values:

        • Alibaba Cloud (default): Only a Microsoft Windows Server license is supported. After migration, you are charged license fees for an image when you use the image to create an ECS instance in Hong Kong (China) and regions outside China, and the image is automatically activated. The specific cost is subject to the information displayed when the instance is created.

        • BYOL: SMC allows you to bring your own license (BYOL). You can bring your own Microsoft license or register with Red Hat Enterprise Linux and SUSE Linux Enterprise Server. After migration, you are not charged license fees for an image when you use the image to create an ECS instance. You can use your own license for activation.

          Note

          If you have created an ECS instance, you can quickly purchase software licenses such as Red Hat Enterprise Linux and SUSE Linux Enterprise Server for specified ECS instances supported by Alibaba Cloud. For more information, see Purchase a software license for an ECS instance (invitational preview).

        Keep the default setting

        Image Check

        Specifies whether to enable the image check feature. The image check feature checks whether an image is valid and whether the image can be used to create full-featured ECS instances. You can use the image check feature when you migrate servers or VMware VMs without agents.

        This feature helps you identify potential issues in images or ECS instances after the migration job is complete, and provides solutions to the identified issues. This helps you improve the success rate of starting ECS instances.

        For more information, see Configure image check.

        Keep the default setting

        Tag

        The tags that you specify for the migration job. Each tag contains a key and a value. You can use tags to query and manage migration jobs. For more information, see Use tags to manage migration sources and migration jobs and Use tags to implement fine-grained access control.

        Note

        You can specify up to 20 tags for a migration job.

        Keep the default setting

        Intermediate Instance Type

        The type of the intermediate instance. Select an intermediate instance type based on your business requirements. This parameter is available only if you set the Destination Type parameter to ECS Image.

        • The instance type of the intermediate instance is automatically selected. If you specify an instance type, SMC creates an intermediate instance of the specified type. If the specified instance type is unavailable, the migration job fails to be created.

        • If you do not specify an instance type, SMC automatically creates an intermediate instance.

        Important

        Do not stop, start, restart, or release the intermediate instance during the migration to prevent migration failures. After the migration is complete, SMC automatically releases the intermediate instance.

        Keep the default setting

        Report diagnostic logs

        SMC client logs are automatically uploaded for diagnostic purposes and issue resolution. This feature is enabled by default.

        Client logs are generally stored in the /smc/go2aliyun_client*/Logs folder of your installation directory.

        Keep the default setting

    3. In the message that appears, read the migration notes and click Got It.

    4. On the Cross-account/Intra-account Migration page, view the real-time migration status.

      If you enabled the migration drill feature, SMC performs the drill first. The transmission time is affected by factors such as the data volume and network bandwidth. Wait for the migration task to complete.

      image

      Note

      • Speed: The amount of data transmitted per second. This value represents the transmission speed of uncompressed data. If you set Compression Ratio to a value greater than 0 when you created the migration task, the displayed speed is higher than the actual network transmission speed, which is the speed of compressed data.

      • Remaining Sync Time: The estimated time remaining for the synchronization to complete. This is calculated as (Total Data - Transmitted Data) / Speed.

      • If the transmission speed is too low, you can temporarily increase the fixed bandwidth of the source and destination servers. For more information, see Estimate migration time and test transmission speed.

      Subscribe to migration error events, modify the migration, and pause the migration

      • To prevent task errors from blocking the migration process, you can subscribe to SMC migration task error notifications in CloudMonitor. This lets you receive timely notifications by email.

      • When the migration task is in the Syncing state, you can perform the following operations on the task as needed:

        • Modify the migration task: In the Actions column, click Modify Migration to change parameters such as the transmission throttling rate, compression ratio, and checksum verification.

        • Pause the migration task: In the Actions column, click Pause Migration to pause the migration.

    5. Optional. To view details about the migration, perform the following steps:

      View migration details

      In the Migration Source ID /Name column of the destination migration source, click the migration source ID to view the job details.

      4f6e6910cfeda1780d1e406a91e2492b

    Verify the migration result

    • When the Real-time Migration Status is Completed, the migration is successful.

      • If you set the Destination Type parameter to ECS Image for the migration job, you can verify the migration result in the following way:

        After the migration is complete, an Alibaba Cloud custom image is generated. You can use your pointer to slide the scrollbar at the bottom to the right and click View Report in the Migration Deliverables column to view the check result of the image. For more information, see View the image check results step of the "Configure image check" topic.

        image

        (Recommended) Manually verify the migration result

        You can click Create Instance in the Actions column to go to the ECS instance creation page in the ECS console. The custom ECS image created by the migration job is selected by default for you to create an ECS instance. For more information, see Create an instance by using a custom image.

        Use the automatic migration result verification feature

        Note

        To use this feature, you must install the Cloud Assistant Agent in your instance, and the system version of the instance must support this feature. For more information, see Install Cloud Assistant Agent.

        This feature uses the ACS-SMC-CreateAndVerifyInstance template provided by Alibaba Cloud CloudOps Orchestration Service (OOS) to automatically verify whether the image generated by the migration job can be used to create an ECS instance and whether the ECS instance can start as expected.

        1. Click Verify Migration Result in the Actions column.

          image

        2. In the dialog box that appears, read the instructions on the verification process and click Verify Now.

          You can also click Customize Verification Parameters to configure the parameters.

        3. In the Verify Migration Result column, view the verification result. Valid values:

          • Verified: indicates that the migration is successful. You can click Details to check the verification result.

          • Not Verified: indicates that the migration failed. You can click View Cause to troubleshoot the failure.

          You can also click the ... icon in the Actions column and select View Verification Records in OOS Console to view the template history.

      • If you set the Destination Type parameter to ECS Instance for the migration job, you can click View Destination Instance in the Actions column to go to the details page of the destination ECS instance to verify the migration result.

      After the server is migrated, you must perform the following operations to ensure normal operation of your business:

      • Verify the integrity and correctness of the data. For more information, see the How do I check a Linux server after migration? or How do I check a Windows server after migration? section of the "FAQ" topic.

      • Manually start the applications and services after the migration if automatic start is not enabled for the applications and services on the source server.

      • The IP address changes after the migration job is complete. If the service involves the configuration of the IP address, modify the domain name resolution and ICP filing after the migration.

    • If Error is displayed in the Real-time Migration Status column, the migration failed.

      In this case, you need to perform the following operations:

      1. Click Troubleshoot Errors in the Actions column and fix the failure based on the error code and error message. For more information, see FAQ and Errors occurred during a server migration.

      2. In the migration source list, click Retry Migration Job.

        The migration job resumes from the point where it was suspended.

        Important

        If the intermediate instance is released, you must create another migration job. For more information, see the What do I do if I accidentally release an intermediate instance? section of the "FAQ" topic.

    • If Error is displayed in the Real-time Migration Status column, the migration failed.

      In this case, you need to perform the following operations:

      1. Click Troubleshoot Errors in the Actions column and fix issues based on the error code and description. For more information, see FAQ and Errors occurred during a server migration.

      2. After the issues are fixed, click Retry Migration in the Actions column of the migration job.

        The migration job resumes from the point where it was suspended.

        Important

        If the intermediate instance is released, you must create another migration job. For more information, see the What do I do if I accidentally release an intermediate instance? section of the "FAQ" topic.

    Clear resources

    • Migrate a server to an ECS image

      During the migration, SMC creates a temporary pay-as-you-go intermediate instance named No_Delete_SMC_Transition_Instance within the destination Alibaba Cloud account. The method to clear resources depends on whether the migration is successful.

      • If the migration is successful, the intermediate instance is automatically released. No manual operation is required.

      • If the migration failed, the intermediate instance is not automatically released and incurs fees as long as the migration job exists. You can release the intermediate instance in one of the following ways to reduce costs:

        • If you no longer need the migration job, click the ID the migration job. On the job details page, click image > Clear migration task in the Actions column in the Migration Jobs section to delete the migration job and release the intermediate instance at a time.

        • Manually release the intermediate instance. For more information, see Release an instance.

    • Migrate a server to an ECS instance

      During the migration, SMC creates a temporary pay-as-you-go intermediate cloud disk named SMC_Temp_Disk in the destination instance. The method to clear resources depends on whether the migration is successful.

      • If the migration is successful, the intermediate cloud disk is automatically released. No manual operation is required.

      • If the migration failed, the intermediate cloud disk is not automatically released and incurs fees as long as the migration job exists. You can release the intermediate cloud disk in one of the following ways to reduce costs:

        • If you no longer need the migration job, click the ID of the migration job. On the job details page, click image > Clear migration task in the Actions column in the Migration Jobs section to delete the migration job and release the intermediate cloud disk at a time.

        • Manually release the intermediate instance. For more information, see Release a disk.

    Relevant references

    • If you need to migrate incremental data multiple times, you can initiate incremental data migration multiple times at custom intervals after the first full migration is complete. This synchronizes the incremental data generated by the source server to Alibaba Cloud and reduces the suspension time and delivery time of the services provided by the source server. For more information, see Migrate incremental data from a server.

    • For more information about frequently asked questions (FAQ) and solutions, see FAQ and Errors occurred during a server migration.