All Products
Search

This Product

    Server Migration Center:Migrate an OpenClaw server to a Simple Application Server

    Document Center

    Server Migration Center:Migrate an OpenClaw server to a Simple Application Server

    Last Updated:Mar 25, 2026

    Server Migration Center (SMC) provides a one-click migration feature to migrate OpenClaw servers from various sources, such as personal computers, on-premises servers, virtual machines, or other cloud platforms, to Alibaba Cloud Simple Application Server instances.

    Prerequisites

    • Network connectivity: Ensure that the source server has public network access.

    • Target environment: Prepare an Alibaba Cloud Simple Application Server instance as the migration target. Ensure that you understand the migration impacts.

    • System requirements: The target Alibaba Cloud Simple Application Server instance must run a Linux operating system. The Linux distribution does not need to match that of the source server.

    • Storage capacity: The disk space of the target Alibaba Cloud Simple Application Server instance must be greater than or equal to the total disk space of the source server.

    • Account status: Ensure that your Alibaba Cloud account has an available balance of at least CNY 100 to avoid service interruptions.

    Procedure

    Step 1: Import the migration source

    1. Go to the SMC Console - Server Migration page.

    2. On the Server Migration page, click General One-click Migration.

      image

    3. In the Generate Migration Source section, click Generate Activation Code.

    4. On the Linux Shell tab, click Copy to copy the command.

    5. Log on to the source OpenClaw server and run the copied command with administrator privileges to import the migration source.

      image.png

      After you run the command, a message similar to the following appears, indicating the migration source was imported successfully: Import Source Server [s-bp18x8751kgz2oyh****] Successfully!

    6. Return to the General One-click Migration page in the SMC console and click Next.

    Step 2: Configure the migration

    1. On the Migration Configuration page, set Destination Type to Simple Application Server.

    2. From the Destination Region and Destination Instance drop-down lists, select the Alibaba Cloud Simple Application Server instance that you prepared.

    3. Confirm the other parameters, read and agree to the cost statement, and then click Start Migration.

      For information about other parameters, see Basic information configuration.

    4. Return to the SMC Console - Server Migration page. In the Actions column for the target migration source, click Start Migration.

    5. Monitor the real-time status of the migration.

      The data transfer time depends on factors such as the amount of data on the source server and network bandwidth. Wait for the migration task to complete.

      image

      Note

      • Speed: The amount of migration data transferred per second, which is calculated based on uncompressed data. If the Compression Ratio is set to a value greater than 0 when you create the migration task, the displayed speed will be greater than the actual network transfer speed, which is the transfer speed of compressed data.

      • Remaining Sync Time: The estimated time to complete the synchronization, calculated as (Total Data Volume - Transferred Data Volume) / Speed.

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

      Subscribe to migration error events, modify the migration, or pause the migration as follows:

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

      • When the migration task status is Syncing, you can also perform the following operations as needed:

        • To modify a migration task, in the Actions column, click Modify Migration to change parameters such as the transfer speed limit, compression ratio, and Checksum verification.

        • To pause the migration task, click Pause Migration in the Actions column.

    Verify the migration results

    • A Real-time Migration Status of Completed indicates a successful migration.

      1. In the Actions column, click View Destination Instance to view the target Simple Application Server instance.

      2. Verify that the OpenClaw service is running correctly after the migration.

        1. Before verification, to prevent clients from receiving duplicate responses, stop the OpenClaw service on the source OpenClaw server using one of the following methods:

          • Shut down the source server.

          • Log on to the source server and run the openclaw gateway stop command to stop the service.

          • Delete the connected channels.

        2. (Optional) If the web management console is configured in the source OpenClaw server's firewall, find the port number in the firewall rules and add it to the firewall rules of the target Simple Application Server instance.

        3. Verify the service by sending a message to OpenClaw from your original chat application . If you receive a reply, the service is working correctly.

    • A Real-time Migration Status of Error indicates that the migration task has failed. You must troubleshoot the issue and retry the migration:

      1. In the Actions column, click Troubleshoot and apply the suggested fix for the displayed error code and message.

        For more information, see SMC FAQ and Troubleshoot Errors.

      2. After you fix the issue, click Retry Migration in the Actions column. The migration will resume from the point of failure.