openclaw-migration

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

6|2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/GregsGreyCode/Logos --skill openclaw-migration-gregsgreycode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/GregsGreyCode/Logos/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/GregsGreyCode/Logos --skill openclaw-migration-gregsgreycode

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

OpenClaw users often want to move their customization footprint into Hermes Agent without manual, error-prone setup. This skill automates the migration of memories, personas, workspaces, and allowed patterns to Hermes, preserving structure and surfacing conflicts.

Core Features & Use Cases

  • Import SOUL.md, memories, user profiles, and command allowlists from an OpenClaw footprint into Hermes.
  • Copy OpenClaw workspace assets and skills into Hermes-compatible locations and report any migration gaps for manual review.
  • Use to transition users from OpenClaw to Hermes with minimal reconfiguration, including conflict-resolution options and dry-run previews.

Quick Start

To begin, run a dry-run migration to review what would be migrated before executing the full transfer.

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

This skill migrates OpenClaw footprints into Hermes Agent by translating memories, SOUL.md, and workspace assets into Hermes-compatible forms, automatically merging settings and archiving unmapped docs during the transition.

Can I preview a footprint migration before committing changes to Hermes?

Yes, you can preview a footprint migration before committing changes to Hermes by running a dry-run migration. This allows you to review transferred memories, skills, and settings before executing the full transfer.

What happens to OpenClaw workspace assets and skills that Hermes cannot map?

During migration, OpenClaw workspace assets and skills that Hermes cannot map are organized into archived reports, surfacing migration gaps so you can manually review unmapped documents and resolve conflicts.

Does the OpenClaw to Hermes migration handle secret migration and conflict resolution?

The OpenClaw to Hermes migration enforces optional secret migration control and provides conflict-resolution options while merging memories, skills, and settings, ensuring a smooth transition without exposing sensitive data unexpectedly.

Do I need YAML dependencies to import OpenClaw footprints into Hermes?

Yes, the YAML dependency is required to import OpenClaw footprints into Hermes, as the migration scripts rely on YAML to parse configuration files and translate them into Hermes-compatible memory and config structures.

What is the best way to transition user profiles and command allowlists from OpenClaw to Hermes?

The best way to transition user profiles and command allowlists from OpenClaw to Hermes is using an automated migration skill that imports SOUL.md and allowed patterns, preserving structure and surfacing conflicts during the transfer.