migrate-from-openclaw

Migrate OpenClaw configurations and identities into NanoCrew with user approvals.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CjLogic/nanocrew --skill migrate-from-openclaw-cjlogic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/CjLogic/nanocrew/tree/main/.codex/skills/migrate-from-openclaw
Command: npx skills add https://github.com/CjLogic/nanocrew --skill migrate-from-openclaw-cjlogic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrate OpenClaw configurations and identities into NanoCrew to preserve critical settings while adopting containerized isolation and safe data handling.

Core Features & Use Cases

  • Phase-driven, conversational migration from OpenClaw to NanoCrew, including identity, memory, channels, and tasks.
  • Safe credential handling with masking and user approvals, mapping to NanoCrew environment and AGENTS.md templates.
  • Incremental, auditable migration across Phases 0-7 with reusable templates and automation hooks for future migrations.

Quick Start

Begin Phase 0 by initiating discovery of your OpenClaw setup and follow the guided questions to complete the migration.

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 configurations to NanoCrew?

OpenClaw migration to NanoCrew uses a phase-driven workflow across Phases 0-7, analyzing the OpenClaw state directory to map groups, memory, channel credentials, scheduled tasks, and plugins into NanoCrew artifacts with user approvals.

Can I safely migrate channel credentials from OpenClaw without exposing secrets?

Channel credentials migration masks all sensitive values and presents safe mappings for explicit user approval, ensuring secret protection while generating NanoCrew environment and AGENTS.md templates.

What is the OpenClaw to NanoCrew migration process?

The migration process is an incremental, auditable workflow spanning Phases 0-7 that discovers OpenClaw state, migrates identities and memory, handles channel credentials, and configures optional plugins into NanoCrew artifacts.

Do I need any specific tools or dependencies to start the OpenClaw migration?

No external dependencies are required to start the OpenClaw migration; the guided workflow uses script components to analyze the existing OpenClaw state directory and generate NanoCrew artifacts interactively.

What are the limitations of migrating OpenClaw state to NanoCrew?

Migration requires interactive user approvals at each mapping step and relies on analyzing the OpenClaw state directory, meaning incomplete or corrupted state data may impede the phase-driven workflow progression.