openclaw-migration

Migrate OpenClaw user data into Hermes Agent with a structured report.

Updated May 2, 2026
One-click install
npx skills add https://github.com/AlvaroBiano/hermes-agent --skill openclaw-migration-alvarobiano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/AlvaroBiano/hermes-agent/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/AlvaroBiano/hermes-agent --skill openclaw-migration-alvarobiano

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate an OpenClaw user footprint into Hermes Agent by importing Hermes-compatible memories, SOUL.md, command allowlists, user skills, and selected workspace assets from ~/.openclaw, then reports exactly what could not be migrated and why.

Core Features & Use Cases

  • Imports Hermes-compatible memories via MEMORY.md and USER.md into Hermes memories, along with SOUL.md as the agent persona.
  • Merges OpenClaw command approvals into Hermes command_allowlist to preserve workflows.
  • Copies OpenClaw skills into ~/.hermes/skills/openclaw-imports/ and mirrors workspace assets into Hermes workspace paths.
  • Generates a structured migration report detailing migrated items, conflicts, archives, and any items that could not be migrated.

Quick Start

Run the migration tool in dry-run to preview results, then run with --execute to apply.

Frequently Asked Questions about openclaw-migration

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

FAQPage Schema
How do I migrate OpenClaw memories and workspace assets to Hermes Agent?

Migrate OpenClaw memories and workspace assets to Hermes Agent by importing MEMORY.md, USER.md, SOUL.md, and workspace assets from ~/.openclaw. The tool places imported skills under ~/.hermes/skills/openclaw-imports and generates a structured report detailing migrated items and conflicts.

Can I preview an OpenClaw to Hermes migration before applying changes?

Yes, you can preview an OpenClaw to Hermes migration by running the tool in dry-run mode. This allows you to review exactly what will be migrated, identify potential conflicts, and see items that could not be migrated before executing the actual import.

Does the OpenClaw to Hermes migration tool support handling file conflicts?

The migration tool supports interactive workflows with conflict strategies including skip, overwrite, and rename. It merges OpenClaw command approvals into Hermes command_allowlist and produces a structured report detailing any conflicts encountered during the import process.

What is included in the OpenClaw to Hermes migration report?

The OpenClaw to Hermes migration report details successfully migrated items, conflicts, archives, and any items that could not be migrated along with the reasons why. It covers memories, SOUL.md, command allowlists, user skills, and workspace assets.

How do I migrate command approvals and allowlists from OpenClaw to Hermes?

To migrate command approvals from OpenClaw to Hermes, the tool merges your OpenClaw command approvals directly into the Hermes command_allowlist. This preserves your existing workflows and permissions during the agent migration process.

Do I need Python and pyyaml to run the OpenClaw to Hermes migration script?

Yes, you need Python with the pyyaml dependency to run the OpenClaw to Hermes migration script. The CLI script requires this dependency to parse configuration files and execute the interactive, dry-run, and secret migration workflows.