openclaw-migration

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/xu1713/openhorse --skill openclaw-migration-xu1713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/xu1713/openhorse --skill openclaw-migration-xu1713

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Moving from OpenClaw to Hermes Agent normally means manually copying persona files, memory entries, command allowlists, skills, and settings, with no clear record of what transferred and what was left behind. This Skill automates that migration and produces a structured report of every migrated, archived, skipped, or conflicting item. ## Core Features & Use Cases - Guided interactive migration: Runs a dry-run preview first, then uses structured clarify prompts to resolve SOUL.md conflicts, imported skill conflicts, migration mode, and workspace instruction destinations before executing. - Comprehensive data import: Converts MEMORY.md and USER.md into Hermes memory entries, merges command allowlists, copies user skills into ~/.hermes/skills/openclaw-imports/, mirrors TTS assets, and optionally imports allowlisted secrets such as TELEGRAM_BOT_TOKEN. - Transparent reporting: Writes a redacted report.json and summary.md listing exactly what was migrated, archived for manual review, or skipped and why, with backups preserved when overwriting. - Use Case: A user with an existing ~/.openclaw setup runs the migration, previews changes with --dry-run, chooses the user-data preset, and receives a full report showing their persona, memories, and skills now live in Hermes while unsupported config was archived. ## Quick Start Ask the agent to migrate your OpenClaw setup into Hermes, starting with a dry-run preview before any changes are written.

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 skill or the CLI command hermes claw migrate. It performs a dry-run preview first, then imports your SOUL.md, memory entries, command allowlist, skills, and compatible settings into ~/.hermes with a full report of the results.

How do I preview an OpenClaw migration before making changes?

Use hermes claw migrate --dry-run or run the openclaw_to_hermes.py script without the --execute flag. The dry run lists what would be migrated, archived, or skipped without writing anything to your Hermes directory.

Does the OpenClaw migration import API keys and secrets?

Secrets are not migrated by default. Only when you choose the full compatible migration mode with --migrate-secrets will a small allowlisted set such as TELEGRAM_BOT_TOKEN be imported; unsupported auth blobs are always reported as skipped.

What happens to conflicting files during OpenClaw migration?

Conflicting items like an existing SOUL.md or duplicate skill folders are flagged in the dry run. You choose to keep existing files, overwrite with a backup, or import skills under renamed folders via the --skill-conflict skip, overwrite, or rename modes.

Where do migrated OpenClaw skills go in Hermes?

OpenClaw user skills are copied into ~/.hermes/skills/openclaw-imports/. If a name conflict exists, they can be skipped, overwritten with backup, or placed under renamed folders depending on the conflict mode you select.

What data cannot be migrated from OpenClaw to Hermes?

Items without a clean Hermes destination, such as unsupported auth blobs, raw gateway config, and certain plugin or hook configurations, are archived into the migration output directory for manual review and listed in the skipped section of report.json.