skills.rest
ever-oli
ever-oliCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openclaw-migration

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

3|Updated Mar 20, 2026
Search Tags:#migration#skills#memory#workspace#io#openclaw
One-click install
npx skills add https://github.com/ever-oli/io --skill openclaw-migration-ever-oli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/ever-oli/io/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/ever-oli/io --skill openclaw-migration-ever-oli

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate an OpenClaw footprint into IO by importing memories, persona data, and workspace assets, and by generating a comprehensive migration report that catalogs what was migrated, archived, or left behind.

Core Features & Use Cases

  • Import SOUL.md, MEMORY.md, USER.md, and command allowlists from ~/.openclaw into IO memories and settings.
  • Copy OpenClaw skills into ~/.io/skills/openclaw-imports/ and bring workspace assets over to the IO workspace.
  • Produce a structured report detailing migrated items, conflicts, and items archived for manual review.

Quick Start

Run the migration to import your OpenClaw footprint into IO and review the resulting 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 an OpenClaw footprint into IO?▼

Migrating an OpenClaw footprint into IO involves importing memories, SOUL.md, allowlists, user skills, and workspace assets from ~/.openclaw. The tool validates configurations, merges memories with size limits, and archives unmapped docs for manual review.

Can I preserve existing IO data when importing OpenClaw memories?▼

Yes, importing OpenClaw memories preserves existing IO data. The migration tool applies the import to scenarios where users want to retain current IO data, merging memories with size limits while bringing over compatible artifacts from ~/.openclaw.

What happens to OpenClaw files that cannot be migrated into IO?▼

Files that cannot be migrated into IO are archived for manual review. The tool generates a structured migration report detailing migrated items, conflicts, and unmapped documents left behind during the import process.

Does the OpenClaw to IO migration tool import secrets and workspace assets?▼

The migration tool copies OpenClaw skills and workspace assets into the IO workspace. It optionally migrates secrets when requested, alongside importing SOUL.md, MEMORY.md, USER.md, and command allowlists into IO settings.

What is the best way to track conflicts during an OpenClaw to IO migration?▼

To track conflicts during an OpenClaw to IO migration, review the generated structured report. This comprehensive migration report catalogs exactly what was migrated, archived, or left behind for manual review.

Related Skills

Explore More Software Engineering Skills→
math-incmath-inc
1.2k

openclaw-migration

Migrate OpenClaw customization files into Gauss Agent with a structured report.

Official
Advanced
cloudlinesscloudliness

openclaw-migration

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

Community
Advanced
twjarviszyra-webtwjarviszyra-web
3

openclaw-migration

Migrate OpenClaw user footprints into Hermes Agent with YAML parsing and backups.

Community
Advanced
GregsGreyCodeGregsGreyCode
6

openclaw-migration

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

Community
Advanced