migrate-from-openclaw

Migrate OpenClaw deployments to NanoClaw with guided credential and configuration transfer.

5|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill migrate-from-openclaw-chiptoe-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/chiptoe-svg/nanoclaw_gccourse/tree/main/.claude/skills/migrate-from-openclaw
Command: npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill migrate-from-openclaw-chiptoe-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrating from OpenClaw to NanoClaw normally requires manually transferring credentials, scheduled tasks, identity files, and channel configurations, with high risk of data loss, misconfiguration, or missing critical setup steps.

Core Features & Use Cases

  • Guided Interactive Workflow: Walks you through 7 structured migration phases, from initial OpenClaw discovery to final summary, with user confirmation at each step.
  • Automated Data Mapping: Automatically extracts and maps OpenClaw configs (channel credentials, cron jobs, sender allowlists, identity files, MCP servers) to NanoClaw's native format.
  • Edge Case Handling: Supports unsupported channels, masked credential display, deferred task creation for unregistered groups, and context recovery via a migration state file.
  • Use Case: An instructor using OpenClaw for their classroom can migrate all their student group configs, scheduled assignment reminder cron jobs, and Telegram channel credentials to NanoClaw in minutes without manual data entry or risk of exposing raw API keys.

Quick Start

Tell your AI assistant to start the guided OpenClaw to NanoClaw migration to transfer all your existing configurations, credentials, and scheduled tasks.

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 cron jobs and channel credentials from OpenClaw to NanoClaw?

Migrate cron jobs and channel credentials from OpenClaw to NanoClaw using a guided interactive workflow that automatically extracts and maps your configurations to NanoClaw's native format without manual data entry.

Can I transfer my OpenClaw identity files and MCP server settings to NanoClaw?

Yes, you can transfer OpenClaw identity files and MCP server settings to NanoClaw. The migration process automatically maps these configurations across platforms while applying credential masking to protect sensitive API keys.

What is the best way to handle unsupported channels when moving from OpenClaw to NanoClaw?

The best way to handle unsupported channels during OpenClaw to NanoClaw migration is through the workflow's built-in edge case handling, which safely processes unsupported channels and defers task creation for unregistered groups.

Does the OpenClaw to NanoClaw migration support resuming interrupted transfers?

Yes, interrupted OpenClaw to NanoClaw migrations support context recovery. The process saves a migration state file at each of its 7 structured phases, allowing you to resume from your last confirmed step.

How long does it take to migrate a full OpenClaw deployment to NanoClaw?

Migrating a full OpenClaw deployment to NanoClaw takes minutes. The automated data mapping extracts channel credentials, sender allowlists, and scheduled tasks, eliminating manual configuration and minimizing transfer time.

Are raw API keys exposed during the OpenClaw to NanoClaw configuration transfer?

No, raw API keys are not exposed during the OpenClaw to NanoClaw configuration transfer. The migration workflow applies credential masking to ensure sensitive channel authentication data remains protected throughout the mapping process.