openclaw-migration

Migrate OpenClaw memories, persona data, and configurations into Hermes Agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate a user's OpenClaw customization footprint into Hermes Agent, bringing together memories, SOUL.md, command allowlists, user skills, and workspace assets from ~/.openclaw, and report exactly what could not be migrated and why.

Core Features & Use Cases

  • Import SOUL.md into Hermes home as a persona file.
  • Convert OpenClaw MEMORY.md and USER.md into Hermes memories.
  • Merge OpenClaw command approvals into Hermes command_allowlist.
  • Copy OpenClaw skills and workspace assets into Hermes.
  • Generate a structured migration report with conflicts and skipped items.
  • Supports interactive dry-run and guided conflict resolution.

Quick Start

Ask Hermes to run a dry-run migration of your OpenClaw footprint into Hermes and report any conflicts or skipped items.

Frequently Asked Questions about openclaw-migration

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

FAQPage Schema
How do I migrate my OpenClaw footprint into Hermes Agent?

Migrating OpenClaw memories and persona data into Hermes requires importing SOUL.md as a persona file, converting MEMORY.md and USER.md entries, and merging command allowlists with guided conflict resolution.

Can I merge OpenClaw MEMORY.md entries into Hermes without exceeding character limits?

Yes, the migration process merges OpenClaw MEMORY.md entries into Hermes memories while validating inputs and enforcing character limits to consolidate memory data safely.

Does the OpenClaw to Hermes migration support command allowlists and workspace assets?

Yes, the migration merges OpenClaw command approvals into the Hermes command_allowlist and copies workspace assets, consolidating full setups including skills and user configurations.

What happens to conflicts or skipped items during OpenClaw footprint migration?

Conflicts and skipped items during OpenClaw footprint migration are documented in a structured migration report, with optional interactive dry-run and guided conflict resolution for transparent handling.

Can I run a dry-run migration of OpenClaw configurations before committing changes?

Yes, you can run a dry-run migration of your OpenClaw footprint into Hermes to preview conflicts, skipped items, and memory merges before applying changes.

Do I need PyYAML to migrate OpenClaw skills and secrets into Hermes?

Yes, PyYAML is required to migrate OpenClaw skills and optionally migrate small secrets into Hermes, ensuring workspace assets and configurations parse correctly during the workflow.