Migrate from OpenClaw
A migration guide for people who have already decided the move is worth doing and now want a careful, lower-drama way to execute it.
Should you migrate now?
Migrate now if you want to standardize on the current Hermes docs path and you can afford to verify the environment after the move. Do not migrate in the middle of a fragile production week just because the cleaner stack is appealing.
Recommended migration flow
- Run
hermes claw migrate --dry-run. - Inspect what the migration says it will move.
- Run the actual migration when the mapping looks correct.
- Verify providers, workspace rules, and messaging after the move.
What gets moved
- Identity files such as SOUL.md
- Memory and user-profile content
- Skills from OpenClaw skill locations
- Provider and model-related configuration
- Some messaging and integration configuration that still needs post-migration verification
This is not a promise that every part of the old environment becomes production-ready the moment migration completes. Migration moves data and config; it does not replace verification.
What you must verify after migration
- Run hermes status and check provider authentication
- Review whether AGENTS.md belongs in the workspace you actually use
- Test messaging separately instead of assuming tokens alone are enough
- Review archived items that do not map directly into Hermes
When to stop and review manually
Stop and review manually if the migration report shows conflicts, if your provider auth does not validate, or if your messaging flows still require platform-specific repair. Treat those as operator checkpoints, not as signs the whole migration failed.