openclaw-migration

Migrate OpenClaw footprints into Hermes Agent by importing SOUL.md, memories, command allowlists, user skills, and workspace assets from the ~/.openclaw directory using a CLI-driven workflow. The skill supports interactive and dry-run migrations with per-item conflict resolution.

Yes, you can execute a dry-run migration from ~/.openclaw before applying changes. The built-in CLI controls dry-run presets and conflict resolution strategies, enabling safe offline transitions while generating a structured migration report of conflicts and unmapped items.

Yes, the Hermes Agent migration supports importing command allowlists and SOUL.md. It merges Hermes-compatible settings, including SOUL.md, command allowlists, and memory entries, while preserving a detailed report of any conflicts and unmapped items.

Importing OpenClaw user customization footprints migrates SOUL.md, memories, command allowlists, user skills, and workspace assets. The process merges Hermes-compatible settings and reports what could not be migrated, including optional secrets when explicitly enabled.

Per-item conflicts during OpenClaw workspace asset migration are resolved using built-in CLI controls for conflict resolution strategies. The skill performs interactive, script-driven migrations and generates a structured report detailing conflicts and unmapped items.

Yes, you need PyYAML installed to run the OpenClaw to Hermes migration script. PyYAML is a required dependency for the skill's scripts component to parse and merge Hermes-compatible settings from the ~/.openclaw directory.