Profile
- Migration + deployment hardening — If you are moving from OpenClaw, keep openclaw-to-hermes in the toolkit even if you prefer the native migration path. For repeatable deploys, look at nix-hermes-agent, hermes-agent-docker, and evey-setup depending on how opinionated you want the stack to be.
Signals
Listed in the awesome-hermes-agent README
Sources: 2 / Surfaces: 1
What the upstream surface says
Short excerpt only, so you can decide whether to click out.
Migrate from OpenClaw to Hermes Agent — a complete, battle-tested migration tool.
Built from a real production migration. Fixes every issue we found in the existing hermes-migrate tool.
Note: As of Hermes Agent v0.3.0+, the native hermes claw migrate command now covers the full migration path — including the bugs this tool was originally built to fix. For new migrations, use the native command first: `bash hermes claw migrate # Interactive migration hermes claw migrate --preset full --overwrite # Full migration ` This tool remains useful as a reference implementation and for users on older Hermes versions (pre-v0.3.0) where the native migration had known issues.
- Discovers all OpenClaw agents, workspaces, channels, and credentials
- Migrates SOUL.md, MEMORY.md, workspace files, skills, and memory archives
- Maps OpenClaw config → Hermes config.yaml (models, channels, tools, advanced settings)
- Handles dict-type model configs (primary/fallbacks) correctly
- Migrates credentials from both ~/.openclaw/ and /etc/openclaw-tenants/
- Writes auth.json in the correct Hermes nested format
- Sets up systemd gateway service with lingering
- Creates backup archive before any destructive operations