migrate-from-openclaw

Port OpenClaw installations to NanoClaw with phase-driven migration preserving identities and credentials.

5|Updated Apr 2, 2026

Search Tags:#automation #migration #memory #workspace #credentials #openclaw #nanoclaw

Ready to run

npx skills add https://github.com/thmtz/nanoclaw-fleet --skill migrate-from-openclaw-thmtz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/.claude/skills/migrate-from-openclaw
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill migrate-from-openclaw-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

OpenClaw migration to NanoClaw is complex and brittle if done manually. This skill guides the user through a safe, phase-driven process to discover an existing OpenClaw installation, port identities, credentials, scheduled tasks, channels, and memory, and to apply changes interactively with explicit user consent, never copying sensitive data unmasked.

Core Features & Use Cases

Phase-driven discovery, registration, and porting of groups and workspace identities from OpenClaw to NanoClaw.
Automated extraction and masking of credentials, with writes to .env or vault during setup, and a concrete plan for memory, CLAUDE.md, and migration-state tracking.
Supports OpenClaw features like cron jobs, MCP servers, and plugins with a structured approach to mapping to NanoClaw concepts, while documenting decisions for recovery.

Quick Start

Start by guiding the user through migrating their OpenClaw installation to NanoClaw, reading the OpenClaw state and making joint decisions about what to port.

Frequently Asked Questions about migrate-from-openclaw

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

FAQPage Schema

How do I migrate OpenClaw to NanoClaw without losing workspace credentials?▼

A guided OpenClaw to NanoClaw migration preserves workspace credentials by extracting and masking sensitive data, then writing it to .env or vault files with explicit user consent during the setup phase.

Can I port multi-group OpenClaw configurations with cron tasks and MCP servers to NanoClaw?▼

Yes, you can port multi-group OpenClaw configurations with cron tasks and MCP servers by discovering the existing state and mapping those features to NanoClaw concepts through a structured workflow.

What is the best way to transfer workspace memory and CLAUDE.md templates during an OpenClaw migration?▼

Transferring workspace memory and CLAUDE.md templates during migration involves a structured approach that imports settings, updates templates, and records all decisions in a migration-state file for recovery.

Does NanoClaw migration support single-group OpenClaw setups?▼

Yes, NanoClaw migration applies to OpenClaw environments ranging from single-group setups to complex multi-group configurations, guiding the interactive porting of identities and configuration.

How to recover from a failed OpenClaw to NanoClaw migration?▼

Recovering from a failed migration relies on the migration-state file that records all porting decisions, allowing you to track progress and safely resume or rollback the OpenClaw to NanoClaw transfer.