migrate-from-openclaw

Guide OpenClaw to NanoClaw migrations while masking sensitive credentials.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Guide users through migrating from OpenClaw to NanoClaw in a conversational, transparent process, ensuring sensitive data is masked and decisions are clearly explained.

Core Features & Use Cases

  • Interactive, phase-based migration planning that discovers an OpenClaw installation, maps groups, and translates settings to NanoClaw concepts.
  • Guardrails and auditing: credentials are masked, decisions are discussed with the user, and migration artifacts are generated for recovery.
  • Supports generating artifacts like migration-state.md and CLAUDE.md templates, ready for post-migration setup.

Quick Start

Initiate the migration skill and respond to prompts; begin with discovery of your OpenClaw installation and confirm which groups to migrate.

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 from OpenClaw to NanoClaw?

To migrate from OpenClaw to NanoClaw, you initiate a phase-based conversational process that discovers your installation, maps groups, translates settings, and generates migration artifacts like migration-state.md for recovery.

Are credentials masked during the OpenClaw to NanoClaw migration?

Yes, credentials are masked during the migration process to ensure sensitive data is protected. The interactive flow includes guardrails and auditing so that all identity and memory decisions are discussed transparently with the user.

What artifacts are generated for post-migration setup after moving to NanoClaw?

The migration process produces artifacts like migration-state.md and CLAUDE.md templates. These files are generated to support post-migration setup and provide recovery points throughout the phase-by-phase transition.

What is the best way to map OpenClaw groups to NanoClaw concepts?

The best way to map OpenClaw groups to NanoClaw concepts is through the interactive discovery phase, which evaluates your existing installation and translates the group settings into the corresponding NanoClaw structure transparently.

Can I use this guided migration for large OpenClaw installations with complex identity settings?

Yes, the guided migration handles complex installations by breaking the process into phases. It evaluates identity and memory decisions step-by-step, ensuring all group mappings and credential handling are explicitly confirmed before execution.