Upgrade & Migration Guide
This guide covers upgrading OpenClaw to a newer version and migrating from earlier projects (Moltbot, Clawd). It explains version differences, upgrade steps, and where to find release notes.
📘 Before upgrading: Back up your config and data. Check the official release notes for breaking changes in your target version.
Upgrading OpenClaw
OpenClaw is distributed via npm and official install scripts. To upgrade:
- Back up your config directory (e.g.
~/.openclawor the path shown byopenclaw doctor) and any custom skills or credentials. See Backup & Restore. - Check release notes for the target version at GitHub Releases. Look for config schema changes, deprecated options, or required migration steps.
- Upgrade the binary: If you installed via npm:
npm update -g openclaw(or the package name you use). If you used the official install script, re-run it or follow the project’s recommended upgrade path from the official docs. - Restart the Gateway and run
openclaw doctorandopenclaw config validateto ensure config is valid. - Test at least one channel and one agent before relying on the upgraded instance in production.
Version Differences & Release Notes
Version numbering and changelog are maintained by the OpenClaw project. Key places to check:
- GitHub Releases - Release notes, binary downloads, and breaking changes.
- Official documentation - Config schema and feature docs for the current version.
- History of OpenClaw (this site) - Project evolution from Clawd to Moltbot to OpenClaw.
Migrating from Moltbot or Clawd
OpenClaw is the successor to Moltbot and earlier Clawd. If you were using one of those:
- Config layout may have changed. Export or copy your existing config and compare with the current OpenClaw config structure. Map old keys to new ones using the official migration guide if the project provides one.
- Credentials and tokens (API keys, channel tokens) can usually be reused-store them in the same way (e.g. environment variables) in the new config.
- Skills and extensions from the earlier ecosystem may need to be reinstalled or updated for OpenClaw/ClawHub. See Skills Marketplace and Installing Skills.
- Channel adapters (Telegram, Discord, etc.) are typically compatible in concept; verify channel config keys against the current channel docs.
For the exact migration steps from a specific Moltbot/Clawd version, check the OpenClaw release notes and the official site for any published migration guide.
After Upgrading
- Run Quick Diagnostics (
openclaw doctor) and fix any reported issues. - Review Security Best Practices in case new versions introduce new security options.
- If something breaks, see the Troubleshooting Guide and Community for support.
Related
- Backup & Restore - Before and after upgrades
- Installation Hub - Fresh install by platform
- Config File Structure
- History of OpenClaw