openclaw-migration

Migrate OpenClaw persona and memory data to Hermes by running a structured import process that transitions SOUL.md files, memory entries, and user profiles while preserving your established agent identity and configurations.

Yes, you can preview configuration changes using the built-in dry-run mode, which simulates the import of workspace instructions and command patterns to report migrated, archived, and skipped items without modifying your system.

During an OpenClaw import conflict, the process provides guided interactive options to resolve overlapping workspace settings and file conflicts, ensuring you maintain control over which configurations are kept or overwritten.

Yes, the migration process includes an archiving system specifically designed to store non-migratable assets, ensuring you always retain a complete record of your data even if certain items cannot be transitioned.

The best way to transfer command allowlists is through an automated migration skill that validates compatibility and imports your established command patterns directly into the new Hermes Agent architecture.

No, you do not need to manually validate compatibility because the migration skill automatically checks your imported skill sets and provides detailed reporting on system integrity during the transition.