openclaw-migration

Migrate OpenClaw memories, persona data, and workspace assets into Hermes Agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

OpenClaw footprints contain memories, persona data, and workspace configurations that Hermes can ingest. This skill provides an automated, auditable path to migrate those pieces into Hermes while reporting any items that cannot be migrated.

Core Features & Use Cases

  • Import SOUL.md as Hermes persona and merge MEMORY.md/USER.md into Hermes memories.
  • Transfer command approvals, skills, workspace assets, and workspace instructions with optional archiving of unmapped docs.
  • Generate a detailed migration report that highlights conflicts, skipped items, and recovery steps for manual review.

Quick Start

Run the migration script to import your OpenClaw footprint into Hermes and produce a migration report.

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 footprints to Hermes Agent?

Migrate OpenClaw footprints to Hermes Agent by running the migration script, which translates memories, persona data, allowlists, and workspace assets deterministically while generating backups and a final migration report.

What data is transferred when importing OpenClaw memories into Hermes?

Importing OpenClaw memories into Hermes transfers SOUL.md as persona data, merges MEMORY.md and USER.md into Hermes memories, and migrates command approvals, skills, and workspace assets.

How does the migration script handle conflicts between OpenClaw and Hermes workspace configurations?

The migration script handles conflicts during the OpenClaw to Hermes transfer by providing deterministic conflict resolution, creating backups of original data, and logging skipped items in a detailed migration report for manual review.

Do I need pyyaml installed to run the OpenClaw footprint migration?

Yes, you need pyyaml installed in your environment to run the OpenClaw footprint migration script, as it is a required dependency for parsing and translating the YAML workspace configurations.

What happens to unmapped OpenClaw documents during the Hermes migration process?

Unmapped OpenClaw documents are optionally archived during the Hermes migration process, ensuring no workspace assets are lost while keeping the Hermes workspace clean and generating a report of skipped items.

Can I restore my workspace if the Hermes Agent migration fails or skips important files?

You can restore your workspace after a failed Hermes migration using the automatic backups created before transfer, and review the migration report for specific recovery steps regarding skipped or conflicting items.