Migrate from Hermes Agent to OpenClaw

Page scope: You are moving to OpenClaw. For why you might switch, see OpenClaw vs Hermes Agent. For Hermes-specific uninstall or export, use official Hermes docs.

Stable OpenClaw releases include openclaw migrate with importers for Claude/Hermes setup artifacts (release notes). Migration is not a one-click clone—plan for dry-runs, channel re-auth, and skill gaps.

1. Install OpenClaw on the target host (installation) without stopping Hermes yet if you need overlap.
2. Back up both sides — ~/.hermes/ (Hermes) and ~/.openclaw/ (workspace backup).
3. Run migrate — openclaw migrate with dry-run/preview flags your build supports; read CLI output before applying.
4. Doctor — openclaw doctor --fix then openclaw security audit --deep.
5. Channels one at a time — Start with WebChat or Telegram; add Slack / Teams when ready.
6. Pairing — Tighten DM pairing before exposing WhatsApp/Telegram publicly.
7. Skills — Install must-haves from ClawHub with safe install; use install policy checks.
8. Smoke test — One search, one file tool, one channel reply; then personal assistant setup for daily habits.
9. Decommission Hermes — Stop Hermes Gateway only after OpenClaw replaces the channels you rely on.

openclaw backup create
openclaw migrate          # use --help for dry-run flags on your version
openclaw doctor --fix
openclaw security audit --deep
openclaw gateway restart

Exact migrate subcommands drift—check openclaw migrate --help and docs.openclaw.ai.

Valid pattern: Hermes for offline research that spawns skills; OpenClaw for Slack/Teams/WhatsApp your team sees. Rules:

• Never attach the same bot token to two live Gateways.
• Label channels so you know which agent answers where.
• Keep separate API budgets—double agents can double token spend.

• Follow Upgrading / Migrating for future OpenClaw bumps.
• Add Parallel web_search if you relied on Hermes web tools.
• Use Workboard if you need multi-agent boards instead of Hermes subagent patterns.