openclaw-migration

To migrate OpenClaw memories and SOUL.md into Hermes Agent, run the migration script to import footprints from ~/.openclaw. It transfers memories, SOUL.md, command allowlists, skills, and workspace assets, resolving conflicts and generating a detailed report of unmigrated items.

Yes, you can preview the OpenClaw to Hermes migration using the automated dry-run mode. This feature allows you to see exactly what memories, skills, and workspace assets will be imported and identify potential conflicts before making any actual changes to your Hermes environment.

Yes, the migration tool handles conflicts between OpenClaw assets and existing Hermes data through per-item conflict decision and clean workspace-target handling. It optionally copies workspace instructions and applies conflict resolution strategies to ensure a smooth integration.

Before migrating your OpenClaw footprint, you need a local OpenClaw footprint at ~/.openclaw and a Hermes-compatible environment. The migration script also requires the pyyaml dependency to perform conflict resolution, backups, and final reporting during the transfer.

Some OpenClaw skills or memories may not transfer if they are not Hermes-compatible. The migration script generates a detailed report after completion that surfaces exactly which items could not be migrated and provides the specific reasons for each failure.