openclaw-migration

Migrate OpenClaw customization footprints into ZedClaw with dry-run reports.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill openclaw-migration-zardli1115
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/ZardLi1115/zedclaw/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill openclaw-migration-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires argparse, hashlib, json, os, re, shutil, yaml, and includes scripts (resource) components.

What problem does it solve?

OpenClaw users need a safe, low-effort way to move their persona, memory, command permissions, and compatible workspace assets into ZedClaw without breaking existing setups or unintentionally overwriting important data.

Core Features & Use Cases

  • Guided migration with dry-run reporting: Previews exactly what will migrate, archive, conflict, or fail, along with reasons.
  • Conflict-aware imports: Handles SOUL.md and imported-skill destination conflicts using explicit user decisions and backs up when overwrite is enabled.
  • Optional workspace instructions + asset mirroring: Copies OpenClaw workspace instructions (AGENTS.md) into a selected ZedClaw workspace and mirrors compatible assets like TTS files when present.

Quick Start

Ask the agent to run an interactive dry-run migration by converting your OpenClaw footprint into a ZedClaw-compatible setup and reporting what cannot be migrated.

Frequently Asked Questions about openclaw-migration

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

FAQPage Schema
How do I migrate persona, memory, and workspace assets from OpenClaw to ZedClaw?▼

You can migrate your OpenClaw footprint into a ZedClaw home by running the openclaw_to_zedclaw.py helper script, which transfers persona files, memory, command permissions, and compatible workspace assets.

Can I preview what will be migrated before making changes to my ZedClaw setup?▼

Yes, you can run a guided dry-run migration to preview exactly which items will be migrated, archived, skipped, or conflict, along with the specific reasons for each decision.

How are SOUL.md and imported-skill conflicts handled during the ZedClaw migration?▼

Conflict-aware imports handle SOUL.md and imported-skill destination conflicts by requiring explicit user decisions and automatically backing up existing data when overwrite mode is enabled.

Does the OpenClaw to ZedClaw migration support moving secrets and allowlisted commands?▼

Yes, the migration script supports command allowlists and offers optional allowlisted secret migration using preset or flag options while producing structured, redacted output reports.

What workspace assets and instructions can be copied when migrating to ZedClaw?▼

The migration copies OpenClaw workspace instructions like AGENTS.md into a selected ZedClaw workspace and mirrors compatible assets such as TTS files when they are present.

What limitations should I expect when moving my OpenClaw workspace instructions?▼

Limitations include items that are skipped or fail to migrate if they are incompatible with ZedClaw layouts, requiring you to review the structured dry-run report to resolve conflicts manually.