How to move an OpenClaw setup into Hermes safely
Hermes can import an OpenClaw, older Clawdbot, or Moldbot setup with `hermes claw migrate`. A normal run first shows a full preview, then asks for confirmation before changing anything. `--dry-run` only shows the preview, while `--preset full --migrate-secrets --yes` imports compatible settings and API key values without asking again.
Hermes reads from `~/.openclaw/` by default and also detects older `~/.clawdbot/` and `~/.moltbot/` folders, plus older such as `clawdbot.json` and `moltbot.json`. The migration can bring over persona files such as SOUL.md, AGENTS.md, , user profile data, skills, settings, provider settings, agent behavior, rules, , TTS settings, messaging settings for services like Telegram, Discord, and Slack, approval rules, and browser settings. API key values are not moved by default; `--migrate-secrets` must be added.
Hermes looks for API key values in OpenClaw config values, the `.env` file, env fields inside the config, and auth profiles, then copies only keys on its supported allowlist. Items without a direct Hermes match are not thrown away; they are saved under `~/.hermes/migration/openclaw/<timestamp>/archive/` for manual review, including cron jobs, plugins, hooks, lists, and complex channel settings. After migration, the setup should be checked by reading the report, reviewing archived files, starting a new session, running `hermes status`, restarting the gateway if messaging tokens were moved, checking settings, re-pairing WhatsApp, and using `hermes claw cleanup` only after everything works.
Key points
- Use `hermes claw migrate --dry-run` first to see what would be imported without changing files.
- API key values move only when `--migrate-secrets` is added, and only supported keys are copied.
- Skill conflicts default to keeping the existing Hermes version unless `overwrite` or `rename` is chosen.
- Cron jobs, plugins, hooks, lists, and complex channel settings are archived for manual review.
- After migration, start a new session and run `hermes status` to confirm the imported setup actually works.