Migrate from OpenClaw to Hermes with a Dry Run

A migration is not a blind directory copy. Hermes maps compatible OpenClaw persona, memory, skills, providers, MCP servers, behavior, and messaging settings into Hermes-native locations and formats.

Operating checklist

Back up the source directory.
Run hermes claw migrate --dry-run.
Choose full or user-data deliberately.
Set the workspace target for AGENTS.md.
Choose skip, overwrite, or rename for skill conflicts.
Use --migrate-secrets only after explicit review.
Keep the default destination backup.

How the workflow works

The migrator detects current and legacy source layouts, previews planned changes, merges and deduplicates memory, namespaces imported skills, and translates compatible configuration. Neither preset silently imports secrets. Messaging authentication may still require fresh pairing, and unsupported source features should be recorded rather than presumed to have moved.

Common pitfalls

Using --yes before reviewing the plan.
Assuming the full preset includes secrets.
Overwriting skills without a rollback story.
Treating a copied token as proof a channel works.
Backing up only the source and not Hermes.

Verification steps

Run hermes config check and hermes doctor.
Review persona, memory, and workspace instructions.
Load a representative imported skill.
Verify the provider without printing credentials.
Test MCP servers and messaging channels one at a time.

Use the official Hermes documentation for the current source of truth.