openclaw-migration

To migrate OpenClaw to Hermes Agent, import your persona, memories, and workspace data using the migration tool. It handles conflicts, supports dry-run previews, and generates a structured report detailing all migrated items and issues for manual review.

Converting OpenClaw MEMORY.md into Hermes memories is handled automatically by merging memory entries with size limits. The migration process preserves data integrity by applying size constraints during the merge and backing up original files before overwriting them.

Yes, you can preview an OpenClaw to Hermes migration using the dry-run feature. Dry-run previews allow you to review per-item decisions across SOUL.md, MEMORY.md, and workspace assets before any actual overwrite occurs, ensuring safe configuration imports.

Yes, the Hermes migration tool supports importing OpenClaw command approvals by merging them into Hermes config. It also supports optional secrets migration, allowing you to selectively transfer sensitive configuration data during the workspace import process.

Conflicts encountered when importing OpenClaw workspace assets into Hermes are reported in a structured migration report. The tool preserves backups on overwrite and flags unmapped items, allowing you to make per-item decisions for manual cleanup of workspace instructions.

Yes, you need pyyaml installed to run the OpenClaw to Hermes migration script. The migration tool depends on pyyaml to parse and process YAML configuration files during the import of persona, memories, and workspace data into the Hermes Agent.