openclaw-migration

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate an OpenClaw footprint into Hermes Agent by importing the persona data, memory footprints, and workspace assets from ~/.openclaw, then report exactly what could not be migrated and why.

Core Features & Use Cases

  • Import Hermes-compatible memories, including MEMORY.md and USER.md, as Hermes memory entries.
  • Import SOUL.md as the Hermes persona file and merge OpenClaw command allowlists into Hermes command_allowlist.
  • Copy user skills and workspace assets into Hermes-compatible locations and generate a structured migration report.
  • Provide an interactive, guided migration with a dry-run preview and per-item conflict resolution.
  • Archive unmapped docs for manual review as needed.

Quick Start

Run the built-in CLI migration to import your OpenClaw footprint into Hermes Agent and review a dry-run report before proceeding.

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 persona data into Hermes Agent?

Migrate OpenClaw memories and persona data into Hermes Agent by importing MEMORY.md, USER.md, and SOUL.md from the ~/.openclaw directory into Hermes-compatible memory entries and persona files. The process is interactive and includes a dry-run preview before any data is moved.

Can I preview what gets migrated from OpenClaw before making changes?

Yes, you can preview what gets migrated from OpenClaw before making changes by running the built-in CLI migration in dry-run mode. The dry-run generates a structured report showing exactly what will be imported and flags any items that cannot be migrated.

What happens to OpenClaw command allowlists and workspace assets during migration?

OpenClaw command allowlists are merged into the Hermes command_allowlist during migration. Workspace assets and user skills are copied into Hermes-compatible locations, while unmapped docs are archived for manual review rather than being discarded.

How does conflict resolution work when importing OpenClaw footprints?

Conflict resolution when importing OpenClaw footprints is handled through per-item interactive prompts during the guided migration. You are prompted to resolve conflicts individually as the migration encounters overlapping memories, assets, or persona data.

Do I need a specific environment setup to run an OpenClaw footprint migration?

You need the pyyaml dependency and an existing ~/.openclaw directory containing your footprint data to run the migration. The process also supports optional secrets configuration and workspace handling to manage asset archiving and conflict reporting.

Why are some OpenClaw files not migrated into Hermes Agent?

Some OpenClaw files are not migrated into Hermes Agent because they lack direct Hermes-compatible mappings, such as unmapped docs. The structured migration report details exactly what was skipped and why, archiving those files for manual review.