openclaw-migration

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

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill openclaw-migration-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill openclaw-migration-kaminocorp

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, command allowlists, and skills, 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, 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, skill conflicts, migration mode, and workspace instruction destinations before executing. - Comprehensive data import: Converts OpenClaw MEMORY.md and USER.md into Hermes memory entries, merges exec-approval patterns into the Hermes command_allowlist, copies skills into ~/.hermes/skills/openclaw-imports/, and mirrors compatible messaging settings and TTS assets. - Safe execution with reporting: Supports user-data and full presets, optional allowlisted secret migration, automatic backups on overwrite, and a JSON/Markdown report listing exactly what could not be migrated and why. - Use Case: A user with an existing ~/.openclaw setup runs the migration, previews changes in dry-run mode, chooses to keep existing skills, and receives a report showing imported memories, archived docs, and skipped secrets. ## 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, starting with a dry run to preview changes. The script imports SOUL.md, memory files, command allowlists, skills, and compatible settings, then reports anything that could not be migrated.

What data does the OpenClaw migration import into Hermes?▼

It imports SOUL.md, MEMORY.md and USER.md as Hermes memory entries, exec-approval patterns into command_allowlist, messaging settings like TELEGRAM_ALLOWED_USERS, user skills into ~/.hermes/skills/openclaw-imports/, and compatible TTS assets. Non-secret docs without a Hermes destination are archived for review.

Does the migration transfer API keys and secrets automatically?▼

No, secrets are excluded by default. Only when you explicitly choose the full migration mode with --migrate-secrets does it import a small allowlisted set such as TELEGRAM_BOT_TOKEN, and unsupported auth blobs are still reported as skipped.

What happens when imported skills conflict with existing Hermes skills?▼

The dry run flags skill conflicts, and you choose between keeping existing skills, overwriting with a backup, or importing under renamed folders. The chosen policy maps to the --skill-conflict flag with skip, overwrite, or rename modes.

Can I preview the OpenClaw migration before making changes?▼

Yes, the script runs in dry-run mode by default and only writes changes when you pass --execute. The preview lists every item with its planned status so you can resolve conflicts before committing.

Why were some memory entries not imported during migration?▼

Hermes enforces character limits on memory files, so entries exceeding the limit overflow instead of importing. When overflow occurs, the full list is exported to an overflow file referenced in the migration report.