openclaw-migration

Migrate OpenClaw memories, persona files, skills, and settings into Hermes Agent.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill openclaw-migration-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill openclaw-migration-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve? Moving from OpenClaw to Hermes Agent normally requires manually copying persona files, memory entries, skills, and configuration settings, with a high risk of losing data or overwriting existing Hermes state. This Skill automates that migration with dry-run previews, conflict handling, and a structured report of everything migrated, archived, or skipped. ## Core Features & Use Cases - Guided migration with dry-run previews: Inspect exactly what would be imported from ~/.openclaw before any changes are written, then resolve conflicts interactively. - Broad data coverage: Imports SOUL.md, MEMORY.md, USER.md, command allowlists, messaging settings, user skills, TTS assets, MCP servers, cron jobs, and dozens of other config categories, with optional migration of allowlisted secrets like TELEGRAM_BOT_TOKEN. - Structured reporting: Produces report.json and summary.md listing migrated items, conflicts, skipped items with reasons, backups, and overflow files. - Use Case: A user switching from OpenClaw to Hermes runs a dry run, chooses the user-data preset, resolves a SOUL.md conflict by keeping a backup, and receives a full report of what moved and what needs manual review. ## Quick Start Ask the agent to run a dry-run migration of your OpenClaw setup into Hermes and show what can be imported before executing anything.

Frequently Asked Questions about openclaw-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from OpenClaw to Hermes Agent?

Run the migration script in dry-run mode first to preview what would be imported, then execute with a preset such as user-data or full. You can also use the built-in CLI command 'hermes claw migrate' for a non-interactive migration.

What data does the OpenClaw migration import into Hermes?

It imports SOUL.md, MEMORY.md and USER.md entries, command allowlists, messaging settings, user skills, TTS assets, MCP servers, cron jobs, and many config categories. Secrets are excluded by default and only an allowlisted set is imported with the full preset.

Does the migration overwrite my existing Hermes files?

No, not by default. Conflicting targets are reported as conflicts unless you pass --overwrite, in which case the script creates backups of existing files before replacing them. Imported skill conflicts can be skipped, overwritten, or renamed.

Are my API keys and secrets migrated automatically?

No. Secrets stay out of Hermes unless you explicitly enable secret migration with the full preset and --migrate-secrets flag. Even then, only an allowlisted set such as TELEGRAM_BOT_TOKEN and provider API keys is imported.

What happens to OpenClaw data that cannot be migrated?

Unmapped or unsupported items are either archived into the migration output directory for manual review or reported as skipped with a specific reason. The final report.json and summary.md list every skipped item and why.

Why does the dry run skip workspace instructions?

Workspace instructions are skipped when no workspace target path is provided. You must explicitly supply an absolute workspace path via --workspace-target before the AGENTS.md file can be copied.