OpenClaw supports three migration paths: importing from another agent system, moving an existing install to a new machine, and upgrading a plugin in place.Documentation Index
Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt
Use this file to discover all available pages before exploring further.
Import from another agent system
Use the bundled migration providers to bring instructions, MCP servers, skills, model config, and (opt-in) API keys into OpenClaw. Plans are previewed before any change, secrets are redacted in reports, and apply is backed by a verified backup.Migrating from Claude
Import Claude Code and Claude Desktop state, including
CLAUDE.md, MCP servers, skills, and project commands.Migrating from Hermes
Import Hermes config, providers, MCP servers, memory, skills, and supported
.env keys.openclaw migrate. Onboarding can also offer migration when it detects a known source (openclaw onboard --flow import).
Move OpenClaw to a new machine
Copy the state directory (~/.openclaw/ by default) and your workspace to preserve:
- Config —
openclaw.jsonand all gateway settings. - Auth — per-agent
auth-profiles.json(API keys plus OAuth), plus any channel or provider state undercredentials/. - Sessions — conversation history and agent state.
- Channel state — WhatsApp login, Telegram session, and similar.
- Workspace files —
MEMORY.md,USER.md, skills, and prompts.
Migration steps
Stop the gateway and back up
On the old machine, stop the gateway so files are not changing mid-copy, then archive:If you use multiple profiles (for example
~/.openclaw-work), archive each separately.Install OpenClaw on the new machine
Install the CLI (and Node if needed) on the new machine. It is fine if onboarding creates a fresh
~/.openclaw/. You will overwrite it next.Copy state directory and workspace
Transfer the archive via Ensure hidden directories were included and file ownership matches the user that will run the gateway.
scp, rsync -a, or an external drive, then extract:Run doctor and verify
On the new machine, run Doctor to apply config migrations and repair services:
Common pitfalls
Profile or state-dir mismatch
Profile or state-dir mismatch
If the old gateway used
--profile or OPENCLAW_STATE_DIR and the new one does not, channels will appear logged out and sessions will be empty. Launch the gateway with the same profile or state-dir you migrated, then rerun openclaw doctor.Copying only openclaw.json
Copying only openclaw.json
The config file alone is not enough. Model auth profiles live under
agents/<agentId>/agent/auth-profiles.json, and channel and provider state lives under credentials/. Always migrate the entire state directory.Permissions and ownership
Permissions and ownership
If you copied as root or switched users, the gateway may fail to read credentials. Ensure the state directory and workspace are owned by the user running the gateway.
Remote mode
Remote mode
If your UI points at a remote gateway, the remote host owns sessions and workspace. Migrate the gateway host itself, not your local laptop. See FAQ.
Secrets in backups
Secrets in backups
The state directory contains auth profiles, channel credentials, and other provider state. Store backups encrypted, avoid insecure transfer channels, and rotate keys if you suspect exposure.
Verification checklist
On the new machine, confirm:-
openclaw statusshows the gateway running. - Channels are still connected (no re-pairing needed).
- The dashboard opens and shows existing sessions.
- Workspace files (memory, configs) are present.
Upgrade a plugin in place
In-place plugin upgrades preserve the same plugin id and config keys but may move on-disk state into the current layout. Plugin-specific upgrade guides live alongside their channels:- Matrix migration: encrypted-state recovery limits, automatic snapshot behavior, and manual recovery commands.
Related
openclaw migrate: CLI reference for cross-system imports.- Install overview: all installation methods.
- Doctor: post-migration health check.
- Uninstall: removing OpenClaw cleanly.