openclaw-migration

To migrate workspace memory and persona files, this tool imports SOUL.md, USER.md, MEMORY.md, and workspace instructions from OpenClaw into Hermes-compatible formats. It validates configuration, merges assets, and outputs a structured migration report detailing moved, archived, and skipped items.

The best way to transfer OpenClaw skills and project assets into Hermes is using a migration process that handles conflicts and optional secrets. It merges relevant items into Hermes structures while generating rollback backups and an auditable report for seamless continuation in Hermes workflows.

Yes, the OpenClaw to Hermes migration handles configuration conflicts and optional secrets during the transfer. It merges persona data, memories, and skill references into Hermes structures, ensuring data is structured for review and providing a detailed report of migrated items.

Yes, you can preview what gets moved by initializing the migration to assess what would be transferred. This assesses SOUL.md, MEMORY.md, USER.md, and related assets before you apply chosen settings to perform the full transfer into Hermes.

During the OpenClaw footprint migration, skipped and archived items are documented in a structured migration report. The tool preserves and structures migrated data for easy review and rollback backups, ensuring no assets are lost during the Hermes transition.

Yes, you need pyyaml installed as it is a required dependency to run the migration scripts. The tool uses this library to validate configurations and process the YAML structures involved in moving OpenClaw assets into Hermes.