openclaw-migration

You can migrate your OpenClaw setup to Hermes by running a dedicated migration script that automatically transfers persona files, memory entries, skill directories, and workspace configurations. The script requires Python 3 and access to your source OpenClaw directory to execute the transition logic.

The best way to handle file conflicts during an agent configuration migration is to use a tool that provides guided, interactive conflict resolution. This ensures a clean transition by letting you manage skill overlaps and existing file discrepancies before finalizing the import process.

Yes, the OpenClaw to Hermes migration requires Python 3 to run, along with the pyyaml dependency. You also need direct access to the source OpenClaw directory so the migration logic can properly read and transfer your existing workspace and messaging settings.

Yes, you can preview which workspace files will be imported by running the migration script in a dry run mode. This allows you to safely review the persona files, memory entries, and skill directories scheduled for import into your Hermes environment before making any actual changes.

When switching from OpenClaw to Hermes, the migration process transfers user data, SOUL.md files, memory entries, user profiles, skill directories, and messaging settings. This preserves your established workspace instructions and custom skills without requiring manual file manipulation.