All Products
Search

This Product

    Server Migration Center:Migrate OpenClaw to Simple Application Server

    Document Center

    Server Migration Center:Migrate OpenClaw to Simple Application Server

    Last Updated:Mar 30, 2026

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

    Prerequisites

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

    • Destination environment: Prepare an Alibaba Cloud Simple Application Server as the destination. Make sure you understand the impacts of migration.

    • System requirements: The destination Simple Application Server instance must run Linux. The distribution does not need to match that of the source server.

    • Storage capacity: The destination Alibaba Cloud Simple Application Server must have at least as much disk space as the source server.

    • Account status: Ensure that you have linked a credit card or PayPal account.

    Procedure

    Step 1: Import the migration source

    1. Go to the SMC console - Server Migration.

    2. On the Server Migration page, click one-click migration.

      image

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

    4. Click the Linux Shell tab, and then click Copy to copy the activation code command.

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

      image.png

      After you run the command, a message appears, such as Import Source Server [s-bp18x8751kgz2oyh****] Successfully!. The message confirms a successful import.

    6. Return to the 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 Simple Application Server instance that you prepared.

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

      For information about other parameters, see Basic information configuration.

    4. The migration task is now created and appears on the SMC console - Server Migration page. To begin the data transfer, find the task and click Start Migration in the Actions column.

    5. Monitor the migration progress.

      The time required for data transfer depends on factors such as the data size and network bandwidth. Wait for the migration task to complete.

      image

      Note

      • Speed: The transfer rate of migration data, measured based on the data size before compression. If you set the Compression ratio to a value greater than 0, the displayed speed is higher than the actual network transfer rate of the compressed data.

      • Time Remaining: Calculated as (Total Data - Transferred Data) / Speed.

      • If the transfer rate is too slow for your plan, you can temporarily increase the fixed bandwidth of the source and destination servers. For more information, see Estimate the migration duration and test the transfer rate.

      Subscribe to migration error notifications, and modify or pause a migration

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

      • While a migration task is in the Synchronizing state, you can also perform the following operations on the task:

        • Modify a migration task: In the Actions column, click Modify migration job to change parameters such as the rate limit, compression ratio, and checksum verification.

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

    Verify the migration results

    • When the Migration Progress status changes to Completed, the migration is successful.

      1. In the Actions column, click View Destination Instance to go to the destination Simple Application Server.

      2. Verify that the OpenClaw service is available after migration.

        1. Before you start verification, stop the OpenClaw service on the source server to prevent clients from receiving duplicate responses. You can do this in one of the following ways:

          • 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 a web management console is configured on the source OpenClaw server's firewall, find the port number in the firewall rules and add a new firewall rule for that port on the destination Simple Application Server.

        3. To verify, send a message to OpenClaw from your chat application. If you receive a reply, the service is working correctly.

    • If the Migration Progress status is Error, the migration has failed. Troubleshoot the issue and then retry the task:

      1. In the Actions column, click Troubleshoot. Use the error code and message to fix the issue.

        For more information, see the SMC FAQ and Troubleshoot errors.

      2. After resolving the issue, click Retry Migration in the Actions column. This resumes the migration from the last checkpoint.