openclaw-migration

Migrate OpenClaw memories, SOUL, workspaces, and settings into CLAWG-compatible assets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrate a user's OpenClaw footprint into CLAWG by importing memories, SOUL.md, command allowlists, user skills, and selected workspace assets, then reporting exactly what could not be migrated.

Core Features & Use Cases

  • Imports SOUL.md and memories
  • Merges OpenClaw command allowlists into CLAWG config
  • Copies user skills into ~/.clawg/skills/openclaw-imports/
  • Manages selected workspace assets and reports conflicts
  • Generates a detailed migration report with conflicts and archivals

Quick Start

Run the migration to move your OpenClaw footprint into CLAWG and review the resulting 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 OpenClaw memories and SOUL.md files into CLAWG?

Migrate OpenClaw footprints into CLAWG by converting memories, SOUL.md, and settings into compatible assets. The process imports your files, merges command allowlists, and generates a detailed report of any conflicts encountered during the transfer.

Can I merge OpenClaw command allowlists and user skills into a CLAWG workspace configuration?

Yes, merging OpenClaw command allowlists into CLAWG config is supported. The migration also copies your user skills directly into the ~/.clawg/skills/openclaw-imports/ directory, preserving your existing workspace configurations.

What happens to workspace assets that have conflicts during an OpenClaw to CLAWG migration?

During an OpenClaw to CLAWG migration, workspace asset conflicts are managed using configurable resolution modes. The tool reports exactly what could not be migrated and handles conflicts based on your chosen settings.

How does the migration process handle OpenClaw secrets and workspace instructions?

The migration process optionally migrates secrets and workspace instructions based on your specific choices. It enforces structured migration steps to preserve data integrity while moving your OpenClaw footprint into the new environment.

Does the OpenClaw to CLAWG migration require a yaml dependency?

Yes, the migration requires a yaml dependency to function. It uses scripts to execute the structured migration steps, converting your OpenClaw configurations and memories into CLAWG-compatible assets.

Why should I generate a migration report when moving OpenClaw footprints to CLAWG?

Generating a migration report when moving OpenClaw footprints to CLAWG provides a detailed record of conflicts and archivals. It ensures you know exactly what could not be migrated, preserving data integrity and visibility.