openclaw-migration

Migrate OpenClaw memories, skills, and settings into ZeusAgent with dry-run previews.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill openclaw-migration-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/loteiron/ZeusAgent/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill openclaw-migration-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Moving an existing OpenClaw setup into ZeusAgent by hand means manually converting memory files, persona documents, skills, and configuration while risking overwrites and lost data. This Skill automates that migration with dry-run previews, conflict handling, and a structured report of everything migrated, archived, or skipped. ## Core Features & Use Cases - Guided interactive migration: Runs a dry run first, summarizes what can be migrated, and resolves conflicts (SOUL.md, imported skills, workspace instructions) through structured clarify prompts before writing anything. - Comprehensive data import: Converts MEMORY.md and USER.md into ZeusAgent memory entries, imports SOUL.md, merges command allowlists, copies skills into ~/.zeus/skills/openclaw-imports/, and mirrors compatible messaging settings and TTS assets. - Safe execution with reporting: Supports user-data and full presets, optional allowlisted secret migration, automatic backups on overwrite, and a JSON/Markdown report listing migrated items, conflicts, and skipped items with reasons. - Use Case: A user with an existing ~/.openclaw directory wants to switch agents. The Skill previews the migration, asks how to handle a conflicting SOUL.md and duplicate skills, then executes a user-data migration and reports exactly what moved and what was archived for manual review. ## Quick Start Ask the agent to migrate your OpenClaw setup into ZeusAgent, starting with a dry-run preview before any changes are written.

Frequently Asked Questions about openclaw-migration

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

FAQPage Schema
How do I migrate from OpenClaw to ZeusAgent?▼

Run the migration skill or the zeus claw migrate CLI command, starting with a dry run to preview changes. The script imports SOUL.md, converts MEMORY.md and USER.md into ZeusAgent memory entries, copies skills, and merges compatible settings, then reports what was migrated or skipped.

What data does the OpenClaw migration import?▼

The user-data preset imports SOUL.md, memory and user-profile entries, messaging settings, command allowlist patterns, skills, TTS assets, and archives unmapped docs. The full preset additionally imports a small allowlist of compatible secrets such as TELEGRAM_BOT_TOKEN.

Does the migration overwrite my existing ZeusAgent files?▼

No, not by default. Conflicting items like SOUL.md or existing skills are reported as conflicts, and you choose to keep existing files, overwrite with a backup, or import skills under renamed folders before anything is written.

Are API keys and secrets migrated automatically?▼

Secrets are never migrated by default. Only when you explicitly choose the full compatible migration with --migrate-secrets does the script import a small allowlisted set of ZeusAgent-compatible secrets; unsupported auth blobs are reported as skipped.

What happens to OpenClaw data that has no ZeusAgent equivalent?▼

Non-secret docs without a direct ZeusAgent destination are archived into the migration output directory for manual review. The report.json and summary.md files list every skipped item with its reason so nothing is silently dropped.