migrate-from-openclaw

Migrate OpenClaw installations to NanoClaw with a Phase 0–7 plan.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill migrate-from-openclaw-stevengonsalvez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/.claude/skills/migrate-from-openclaw
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill migrate-from-openclaw-stevengonsalvez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrating from OpenClaw's single-process, all-in-one setup to NanoClaw's container-isolated architecture can be risky. This skill guides the user step-by-step, ensuring identity, channels, memories, and tasks are migrated deliberately with safeguards and clear decisions.

Core Features & Use Cases

  • Guided Phase-by-Phase Migration: supports discovery, architecture decisions, and file placement to minimize downtime.
  • Credential masking and risk awareness: credentials are masked in previews and only written to secure storage during setup.
  • Interactive decision logging: records choices like group structure (shared vs. separate) and assistant naming for reproducible migrations.
  • Applicable to OpenClaw environments with multiple channels, cron jobs, and MCP settings, enabling a smooth transition.

Quick Start

Begin the migration by answering questions and reviewing the proposed changes to complete a safe OpenClaw to NanoClaw transition.

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 channels and memory to NanoClaw safely?

To migrate OpenClaw channels and memory to NanoClaw safely, use a guided phase-by-phase plan that maps existing concepts to NanoClaw equivalents, validates decisions interactively, and masks credentials during the transition.

What is the best way to move OpenClaw identity and groups to isolated containers?

The best way to move OpenClaw identity and groups to isolated containers is to follow a structured Phase 0–7 migration plan that orchestrates component mapping and records your group structure decisions for reproducibility.

Can I migrate OpenClaw cron jobs and MCP settings to NanoClaw?

Yes, you can migrate OpenClaw environments with multiple channels, cron jobs, and MCP settings to NanoClaw by mapping them through an interactive discovery and architecture decision process.

How does credential masking work during an OpenClaw to NanoClaw migration?

Credential masking during an OpenClaw to NanoClaw migration ensures sensitive data is hidden in previews and only written to secure storage during the final setup phase to prevent exposure.

Do I need to validate architecture decisions when moving from OpenClaw to NanoClaw?

Yes, you need to validate architecture decisions like shared versus separate group structures and assistant naming when moving from OpenClaw to NanoClaw to ensure a deliberate and recoverable migration.

What are the limitations of migrating OpenClaw setups to NanoClaw containers?

Limitations of migrating OpenClaw setups to NanoClaw containers include the need to map single-process architectures to isolated ones deliberately, requiring interactive input to avoid downtime and prevent data misplacement.