Docs

ArkClaw Enterprise

Advanced features

Migrating OpenClaw to ArkClaw

Using the migration feature, you can quickly migrate existing OpenClaw (hereinafter referred to as the source) data to the target ArkClaw (hereinafter referred to as the destination). After migration, ArkClaw will use the memories, skills, and other data accumulated in OpenClaw to maintain consistency with your original usage habits and operation logic. This enables a smooth transition with zero learning cost and no service interruption.

Usage notes

Migrating OpenClaw deployed locally or on major cloud platforms (such as Alibaba Cloud, Huawei Cloud, and Tencent Cloud) is supported. You only need to ensure that OpenClaw is deployed on the Linux operating system, and its version is between 2026.2.13 and 2026.5.18 (including versions 2026.2.13 and 2026.5.18).

tip

You can confirm relevant information during a conversation. For example: "What is your current OpenClaw version, and is the OS of the deployment environment Linux?"

For details about the scope of data imported to ArkClaw, see Import scope instructions.

warning

Files larger than 200 MB will not be migrated.

Migration will not proceed if the total size of all OpenClaw files exceeds 1 GB.

Inference model information configured in OpenClaw will not be migrated to ArkClaw. ArkClaw uses models supported by the ModelArk Coding Plan by default. You can adjust the inference model as needed.

After the import, existing configurations in ArkClaw will be overwritten and unrecoverable. We recommend that you back up ArkClaw before importing data.

Procedure

Step 1: Obtain the OpenClaw export command at the destination

warning

Obtain the export command in the required destination ArkClaw. Otherwise, the import will fail.

In the upper-right corner of the ArkClaw chat page, click "··· > Migrate OpenClaw to ArkClaw".

Click the copy button to obtain the export command.

warning

The export command is valid for 1 hour. Use it within the validity period. If the command expires, reopen the page to obtain a new command.

The export command packages and uploads your OpenClaw data to a temporary dedicated ArkClaw space without modifying any configurations of your original OpenClaw.

After you perform the import operation (whether successful or failed), the temporarily stored OpenClaw data will be deleted immediately. If no import operation is performed, the data will be retained for 24 hours and automatically deleted upon timeout.

Step 2: Export OpenClaw at the source and obtain the import address

Execute the export command obtained in the previous step in the terminal to quickly export OpenClaw to the ArkClaw exclusive space for temporary storage, and generate an exclusive and secure OpenClaw import address.

After the command is executed, copy the OpenClaw import URL displayed in the output.

Step 3: Import OpenClaw

Return to the ArkClaw console and click "··· > Migrate OpenClaw to ArkClaw" in the upper-right corner.

warning

Select the same ArkClaw that is used to obtain the export command in Step 1. Otherwise, the import will fail.

Enter the import address you obtained in Step 2, and click the "Import and restart ArkClaw" button.

Confirm the risks in the pop-up window and click "Confirm" to start the import process.

After ArkClaw is imported, you can chat with ArkClaw to verify that all configurations are completely consistent with the original OpenClaw configurations.

If the import fails, ArkClaw will automatically roll back to its pre-import state. You can refer to Step 1 and Step 2 again to re-import OpenClaw.

tip

If ArkClaw fails to start and you backed it up before migration, you can use the backup to restore ArkClaw to a normal running state. Otherwise, you can try ArkClaw auto healing or restore ArkClaw to factory settings.

Step 4: Configure message channels

The migration feature does not migrate message channel configurations from OpenClaw to ArkClaw. You need to manually configure message channels for ArkClaw.

We recommend that you create new bots for the corresponding message channels and integrate them into ArkClaw. Learn more.

If you want to use an existing bot, make sure that it is not used by another OpenClaw instance. If it is already configured and used in another OpenClaw instance, you can:

Stop the OpenClaw service or disable the message channel.

Completely stop the OpenClaw service (recommended)
Only disable specific message channels
If you no longer use the original OpenClaw, you can stop its service directly.
Log in to the server where OpenClaw is deployed.
Execute the following command to stop the OpenClaw service.

sudo openclaw gateway stop 2>/dev/null
sudo systemctl --user disable openclaw-gateway.service
If you want to continue using your original OpenClaw, you can disable the message channels it integrates with while keeping OpenClaw running.
Log in to the server where OpenClaw is deployed.
Execute the following command to disable specific message channels.

# Disable the Feishu channel
openclaw config set channels.feishu.enabled false

# Disable the WeCom channel
openclaw config set channels.wecom.enabled false

# Disable the DingTalk channel
openclaw config set channels.dingtalk-connector.enabled false

# Disable the QQ channel
openclaw config set channels.qqbot.enabled false

Execute the following command to restart the OpenClaw gateway for the configuration to take effect.

openclaw gateway restart

Refer to the instructions in Configuring message channels to configure Feishu, WeChat, or other message channels for ArkClaw as needed.

Import scope instructions

This feature imports the following OpenClaw configurations into ArkClaw.

Module	Configuration imported to ArkClaw	Description
Identity (identity and soul)	SOUL.md: Contains OpenClaw information such as soul and personality definitions. IDENTITY.md: Contains OpenClaw name, profile, signature, and other information. USER.md: Contains information about you that OpenClaw has learned. AGENTS.md: Behavior guidelines for the workspace. TOOLS.md: Environment-specific tool notes. HEARTBEAT.md: Heartbeat check checklist. VOICE_GUIDE.md: Voice guidance (imported only if the file exists). BOOT.md: Boot guidance (imported only if the file exists).	These files define what OpenClaw is. Importing them to ArkClaw retains its original role and personality settings, ensuring it remains your familiar dedicated AI assistant after migration.
Memory	MEMORY.md: This file stores long-term curated memory of OpenClaw. memory/: This directory contains OpenClaw daily notes in the format of YYYY-MM-DD.md. Checkpoint: This file acts as a conversation context checkpoint. Status JSON files: Examples include heartbeat-state.json.	These files contain long-term memory of OpenClaw, including accumulated user preferences, project progress, and historical decisions. Importing them to ArkClaw prevents memory loss.
Skills	workspace/skills/: Workspace skills installed locally.	Skills equip OpenClaw with various capabilities (e.g., weather query, stock analysis, video generation). Importing them to ArkClaw maintains the full skill set of the AI assistant.
Plugins (plugins and extensions)	.openclaw/extensions/: Workspace extensions.	Plugins extend the underlying capabilities of OpenClaw, including message channel connectors (Feishu, WeCom, and DingTalk), memory engine, and browser control. tip The system will migrate all plugins for you as much as possible. However, to ensure stable operation of ArkClaw, plugins with compatibility issues will be automatically skipped and will not be migrated to ArkClaw.
Sessions (session history and scheduled tasks)	sessions.json: Stores session data for each OpenClaw instance. Conversation transcript files: Transcription files in .jsonl format. cron/jobs.json: Scheduled task configurations.	Session files store conversation context, and scheduled task files define automated behaviors such as regular reminders and checks. Importing them from OpenClaw to ArkClaw preserves continuity of your original workflow.
Source (source code)	Custom source code in the workspace/src/ directory	Custom scripts, tools, and other source code files you have written in the workspace will also be imported into ArkClaw. This ensures that your personalized code assets are ready for use out of the box.

Last updated: 2026.07.02 14:27:15