openclaw-migration

Migrate OpenClaw memories, SOUL.md, allowlists, skills, and workspace assets into Hermes Agent.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill openclaw-migration-cloudliness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill openclaw-migration-cloudliness

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate a user's OpenClaw customization footprint into Hermes Agent. Imports 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

  • Migrates core footprint from OpenClaw into Hermes, including memories, SOUL.md, and command allowlists.
  • Merges OpenClaw workspace assets and user data into Hermes structures while preserving conflicts and reporting issues.
  • Produces a detailed migration report showing migrated items, skipped items, and unresolved conflicts.

Quick Start

Install and run the migration to import your OpenClaw footprint into Hermes and generate 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 my OpenClaw workspace memories and skills to Hermes?

You can migrate your OpenClaw workspace memories and skills by importing configurations from ~/.openclaw into Hermes Agent, which maps user profiles, command allowlists, and SOUL.md files to generate Hermes-ready structures.

What is the process for transferring OpenClaw SOUL.md and command allowlists into a Hermes Agent setup?

Transferring OpenClaw SOUL.md and command allowlists involves applying a defined mapping that reads local footprint data from ~/.openclaw and updates or creates equivalent Hermes-compatible user profiles and memory assets.

Can I migrate OpenClaw data on a remote server environment to Hermes?

Yes, you can migrate OpenClaw data on a remote server environment because the migration process applies to local OpenClaw data on both desktop and server platforms, reading directly from the ~/.openclaw directory.

What happens to unmapped OpenClaw workspace assets during a Hermes migration?

Unmapped OpenClaw workspace assets are archived during the Hermes migration, while the process produces a detailed report showing migrated items, skipped items, and unresolved conflicts to ensure no data is silently lost.

Why does my OpenClaw to Hermes migration report show unresolved conflicts?

Unresolved conflicts appear in your migration report when the defined mapping encounters overlapping or incompatible workspace assets between OpenClaw and Hermes structures, requiring manual review of the skipped or unmigrated items.