openclaw-migration

Migrating OpenClaw configuration to Hermes Agent involves transferring compatible user settings, memories, skills, and workspace assets using a structured migration workflow. This process preserves your assistant personality and accumulated knowledge while validating compatibility across installations.

Yes, the OpenClaw to Hermes Agent migration workflow supports dry runs. Running a dry run first generates detailed reports explaining which items will be migrated, skipped, archived, or flagged as conflicting before any actual changes are made to your environment.

Supported data types include Hermes-compatible memories, SOUL.md identity files, command allowlists, messaging settings, and selected workspace assets. Unsupported data is flagged during the migration validation process for review before finalizing the transfer.

Conflict resolution workflows handle incompatible settings by identifying issues, creating backups, and generating structured reports of conflicting items. You can review these reports to understand what was archived or skipped before finalizing the Hermes Agent setup.

Yes, the migration requires the pyyaml dependency to process configuration files. Ensure your Python environment has this package installed before attempting to transfer OpenClaw customizations into the Hermes Agent platform.