migrate-from-openclaw

Migrate OpenClaw deployments to NinjaClaw through phase-based discovery and credential handling.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill migrate-from-openclaw-ofirgavish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/OfirGavish/NinjaClaw-Nano/tree/main/.copilot/skills/migrate-from-openclaw
Command: npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill migrate-from-openclaw-ofirgavish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams migrate from OpenClaw to NinjaClaw by guiding a safe, decision-reviewed transition that prevents silent data copy, masks credentials, and preserves important configurations.

Core Features & Use Cases

  • Conversational, phase-driven migration: discovery, settings extraction, identity/memory mapping, channel credential handling, and post-migration validation.
  • Interactive decisions: you discuss and approve mappings (groups, identities, memory, and skills) with prompts that minimize risk and disclose changes before applying.
  • Reuse and portability: OpenClaw artifacts are translated into NinjaClaw equivalents (COPILOT.md templates, grouped folders, and stored credentials) to ensure a smooth handoff to /setup.

Quick Start

Begin by running the migration assistant and follow Phase 0 discovery to assess your OpenClaw setup.

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 NinjaClaw safely?

NinjaClaw migration preserves security by automating credential extraction, masking sensitive channel credentials, and translating OpenClaw artifacts into NinjaClaw equivalents like COPILOT.md templates and grouped folders.

How do I map OpenClaw groups to NinjaClaw groups during setup?

The migration process translates OpenClaw artifacts into NinjaClaw equivalents, including grouped folders and COPILOT.md templates, ensuring a smooth handoff to the NinjaClaw setup environment.

Does the OpenClaw migration process copy memory and task data automatically?

It extracts OpenClaw settings and translates them into NinjaClaw equivalents, ensuring memory and tasks are migrated while preserving important configurations.

What do I need to run the OpenClaw discovery and credential extraction scripts?

The environment must support phase-driven migration, including discovery, settings extraction, identity mapping, and channel credential handling, to successfully migrate from OpenClaw to NinjaClaw.

What are the limitations of migrating OpenClaw deployments to NinjaClaw?

It is designed for environments with existing OpenClaw deployments and relies on running specific migration scripts within the NinjaClaw skill environment to function correctly.