openclaw-migration

Migrate OpenClaw memories, SOUL.md, workspaces, and user data into Hermes Agent structures.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Yangel-hide/video-production-planner-agent --skill openclaw-migration-yangel-hide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/Yangel-hide/video-production-planner-agent/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/Yangel-hide/video-production-planner-agent --skill openclaw-migration-yangel-hide

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 translating memories, SOUL.md, workspaces, and user data into Hermes-compatible structures.

Core Features & Use Cases

  • Import OpenClaw SOUL.md as Hermes persona to establish the agent's identity.
  • Copy and convert memory and user-profile data into Hermes memories for continuity across sessions.
  • Merge command approvals and workspace assets, while reporting exact migration outcomes for review.
  • Archive unmapped docs and provide a detailed migration report to support manual follow-up.

Quick Start

Run the migration to import compatible OpenClaw data into Hermes using the built-in CLI or the openclaw_to_hermes.py script, then review the migration report for conflicts.

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 SOUL.md to Hermes?

To migrate OpenClaw memories and SOUL.md to Hermes, use the openclaw_to_hermes.py script to translate persona, memory, and user data into Hermes-compatible structures. The process converts your footprint semi-automatically while generating a detailed conflict report for review.

Can I run a dry-run OpenClaw to Hermes migration before committing?

Yes, you can run a dry-run OpenClaw to Hermes migration to preview changes safely. The migration helper supports dry-run mode and selective option activation, allowing you to review exact migration outcomes and conflicts before modifying your Hermes workspace data.

Does the OpenClaw migration to Hermes support transferring secrets?

Yes, the OpenClaw migration to Hermes supports transferring secrets via the optional --migrate-secrets flag. This allows you to securely migrate secret configurations alongside memories, workspace assets, and persona data during the semi-automated translation process.

What happens to unmapped docs during an OpenClaw to Hermes migration?

Unmapped docs encountered during the OpenClaw to Hermes migration are archived automatically. The tool provides a detailed migration report highlighting these unmapped items to support manual follow-up and ensure no data is silently lost during the translation.

Do I need pyyaml installed to migrate OpenClaw footprints to Hermes?

Yes, you need pyyaml installed to migrate OpenClaw footprints to Hermes. This dependency is required by the openclaw_to_hermes.py migration script to parse and translate YAML configuration files into Hermes-compatible structures during the automated migration process.

What is the best way to merge OpenClaw command approvals into Hermes?

The best way to merge OpenClaw command approvals into Hermes is using the built-in migration CLI. It automatically merges command approvals and workspace assets while reporting exact migration outcomes, ensuring continuity of your agent's approved actions across platforms.