Migrate OpenClaw to Simple Application Server - Server Migration Center

Prerequisites

Network connection: The source server must have public network access.
Target environment: An Alibaba Cloud Simple Application Server is prepared, and you understand the migration impacts.
System requirements: The target Simple Application Server must run the same OS type as the source server. Windows-to-Windows and Linux-to-Linux only; cross-OS migration is not supported.
Storage capacity: The target Simple Application Server must have disk space no less than the total disk size of the source server.
Account status: A credit card or PayPal account must be linked to your account.

Procedure

Step 1: Import the migration source

Go to the Server Migration page in the SMC console.
On the Server Migration page, click General Quick Migration.
In the Generate Migration Source section, click Generate.
Copy the activation code based on the OS type of the migration source.
Log on to the source OpenClaw server. With administrator privileges, paste and run the copied command to import the migration source.

A message like Import Source Server [s-bp18x8751kgz2oyh****] Successfully! confirms that the migration source is imported.
Return to the One-click Migration page in the SMC console and click Next.

Step 2: Configure the migration

On the Migration Settings page, set Destination Type to Simple Application Server.
Select the prepared Alibaba Cloud Simple Application Server from the Target Region and Destination Instance drop-down lists.
Confirm the other parameters, read and agree to the cost statement, and then click Start Migration.

For more information about other parameters, see Basic Information Configuration.
Return to the SMC console - Server Migration page. In the Start Migration Job column of the target migration source, click Start Migration Job.
Monitor the real-time migration status.

Transmission time varies with source data size and network bandwidth. Wait for the migration to complete.
Note
- Speed: The amount of uncompressed migration data transferred per second. If the Compression Ratio for the migration job is greater than 0, the displayed speed is higher than the actual network transfer speed of the compressed data.
- Time Remaining for Synchronization: This value is calculated by using the following formula: (Total data size - Transferred data size)/Speed.
- If the transfer speed is too slow for your needs, consider temporarily increasing 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 a migration job, and pause a migration job
- To prevent the migration process from being interrupted by errors, you can subscribe to SMC migration job error notifications in CloudMonitor to receive timely email alerts.
- While the migration job status is Synchronizing, you can perform the following operations:
  - Edit the migration job: In the Actions column, click Modify Migration Job to modify parameters such as the transmission speed limit, compression ratio, and checksum verification.
  - Pause the migration job: In the Actions column, click Pause Migration Job to pause the migration.

Verify the migration result

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.
2. Verify that OpenClaw is working correctly after the migration.
  1. Before verification, stop the OpenClaw service on the source server to prevent duplicate client responses. Use 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 connected channels.
  2. (Optional) If the web management console is enabled in the source OpenClaw server firewall, find its port number in the firewall rules and add it to the firewall rules of the target Simple Application Server.
  3. In your original chat application , send a message to OpenClaw. A reply confirms that the service is running correctly.
```
✅ Migration completed - Hardware platform information
Operating system: Linux 6.8.0-71-generic (Ubuntu)
Hostname: iZ2zexxx
Architecture: x86_64
CPU: Intel(R) Xeon(R) Platinum
Memory: 1.8Gi (780Mi used / 1.1Gi available)
Disk: 40G (9.7G used / 30G remaining / 25% used)
```
A Real-time Migration Status of InError indicates a failed migration. Troubleshoot the issue and retry:
1. In the Actions column, click Troubleshoot Errors and use the error code and message to fix the issue.
  
  For more information, see SMC FAQ and Troubleshoot Errors.
2. After fixing the issue, click Actions in the Retry Migration Job column. The migration resumes from where it stopped.