migrate-from-openclaw

Migrate OpenClaw installations into NanoClaw v2 through guided interactive phases.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/RADHA0-max/selfhealbackend --skill migrate-from-openclaw-radha0-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/RADHA0-max/selfhealbackend/tree/main/nanoclaw/.claude/skills/migrate-from-openclaw
Command: npx skills add https://github.com/RADHA0-max/selfhealbackend --skill migrate-from-openclaw-radha0-max

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cron-parser, vitest, tsx, and includes scripts (resource) components.

What problem does it solve? Moving from OpenClaw to NanoClaw v2 requires manually translating identity files, channel credentials, scheduled cron jobs, access control lists, and MCP server configs into a fundamentally different entity model, which is error-prone and easy to get wrong. ## Core Features & Use Cases - Discovery and Extraction: Scans the OpenClaw state directory to detect identity files, channels, groups, cron jobs, skills, and MCP servers, emitting a structured status summary. - Credential Routing: Classifies each credential and routes host-side channel tokens (Telegram, Discord, Slack) to .env while sending container-facing API keys (Anthropic, OpenAI) to the OneCLI vault, with masked display and SecretRef handling. - Cron-to-Task Mapping: Converts OpenClaw cron, interval, and one-shot schedules into v2 messages_in task rows with cron recurrences and process_after timestamps, flagging intervals with no clean cron equivalent. - Use Case: You have an OpenClaw bot with a Telegram channel, a personality defined in SOUL.md, and five recurring cron jobs. Run this Skill to interactively recreate the agent group, wire the messaging group, move the tokens, and reschedule every task in NanoClaw v2. ## Quick Start Ask the assistant to migrate from OpenClaw and it will discover your existing installation, then walk you through each migration phase interactively.

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 v2?

Run the migrate-from-openclaw skill, which discovers your OpenClaw state directory and guides you through phased migration of agents, groups, credentials, identity files, and scheduled tasks. It tracks progress in a migration-state.md file so interrupted migrations can resume.

How are OpenClaw cron jobs migrated to NanoClaw v2?

Cron schedules map directly to v2 recurrence expressions with a computed next-fire timestamp, while fixed intervals are approximated as cron when they divide evenly. The agent creates each task via its schedule_task MCP tool since v2 tasks live in per-session inbound.db files.

Where do OpenClaw credentials go during migration?

Host-side channel tokens for Telegram, Discord, and Slack are written to NanoClaw's .env file, while container-facing API credentials like Anthropic and OpenAI keys are registered in the OneCLI vault. Credential values are masked when displayed and never echoed to chat transcripts.

Can WhatsApp credentials be migrated from OpenClaw?

No, WhatsApp authenticates via QR code or pairing code, so there is no token to migrate. Copying Baileys auth state breaks encryption sessions, so you re-authenticate during NanoClaw setup with /add-whatsapp instead.

What OpenClaw features cannot be migrated to NanoClaw v2?

Webhook delivery, failure alerts, per-task model and thinking config, wake modes, and exec approval lists have no v2 equivalent. Webhooks can be folded into task prompts or pre-agent scripts, while other features are noted as not applicable.