Caricamento in corso...
Caricamento in corso...
Last synced: Today, 22:00
Technical reference for the OpenClaw framework. Real-time synchronization with the official documentation engine.
Use this file to discover all available pages before exploring further.
OpenClaw supports three migration paths: importing from another agent system, moving an existing install to a new machine, and upgrading a plugin in place.
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.
Import Claude Code and Claude Desktop state, including `CLAUDE.md`, MCP servers, skills, and project commands.
Import Hermes config, providers, MCP servers, memory, skills, and supported `.env` keys.
The CLI entry point is openclaw migrate
openclaw onboard --flow importCopy the state directory (
~/.openclaw/openclaw.jsonauth-profiles.jsoncredentials/MEMORY.mdUSER.mdtext```bash} openclaw gateway stop cd ~ tar -czf openclaw-state.tgz .openclaw ``` If you use multiple profiles (for example `~/.openclaw-work`), archive each separately.
text```bash} cd ~ tar -xzf openclaw-state.tgz ``` Ensure hidden directories were included and file ownership matches the user that will run the gateway.
text```bash} openclaw doctor openclaw gateway restart openclaw status ```
On the new machine, confirm:
openclaw statusIn-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:
openclaw migrate© 2024 TaskFlow Mirror
Powered by TaskFlow Sync Engine