openclaw-migration

To migrate your OpenClaw persona and memory, you run a helper script that imports Hermes-compatible persona files, memory entries, and command approvals from your existing ~/.openclaw directory. The migration requires minimal manual cleanup and preserves compatibility across your workspace assets.

The safest way to transfer OpenClaw workspace assets is to run the migration script in dry-run mode first. This produces a redacted report listing exactly what will be migrated, skipped, or flagged as a conflict, allowing you to resolve sensitive or unsupported content before making changes.

Yes, the OpenClaw migration process supports copying custom skills into the import skill namespace and transfers command allowlists. It also mirrors compatible workspace settings, including messaging and TTS configurations, during the Hermes-compatible import.

OpenClaw files are skipped or marked as conflicts during migration when they contain sensitive or unsupported content. The helper script applies deterministic filesystem transformations and generates a structured report explaining exactly why each item was not moved.

Yes, you can use the OpenClaw migration helper for first-time agent setup. It is designed specifically for users with an existing OpenClaw directory, reading default and optional workspace variants to import your customization footprint with minimal manual cleanup.

To run an OpenClaw to Hermes-compatible persona import, you need an existing ~/.openclaw directory and the pyyaml dependency installed. The helper script then reads your directory and performs the deterministic filesystem transformations required for migration.