migrate-from-openclaw

Migrates OpenClaw installations into NanoClaw v2 through guided interactive phases.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill migrate-from-openclaw-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-openclaw
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/migrate-from-openclaw
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill migrate-from-openclaw-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Moving from OpenClaw to NanoClaw v2 requires manually translating agents, groups, credentials, scheduled tasks, and memory files between two structurally different systems, which is error-prone and risks leaking secrets or losing configuration. ## Core Features & Use Cases - Discovery and Extraction: Detects an existing OpenClaw installation, parses its config, and summarizes channels, groups, workspace files, cron jobs, MCP servers, and skills. - Credential Routing: Routes host-side channel tokens (Telegram, Discord, Slack) to .env and container-facing API credentials (Anthropic, OpenAI) to the OneCLI vault, with masked display and no secrets in chat transcripts. - Cron-to-Task Mapping: Converts OpenClaw cron schedules into NanoClaw v2 task rows with cron recurrence expressions and first-run timestamps, flagging intervals that have no clean cron equivalent. - Use Case: A user with an OpenClaw setup containing a Telegram bot, daily memory files, and five cron jobs runs the migration and ends with a registered NanoClaw agent group, migrated identity and memories, credentials in the vault, and tasks scheduled via the agent. ## Quick Start Ask the assistant to migrate from OpenClaw and it will detect 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 migration skill, which detects your OpenClaw installation at ~/.openclaw or ~/.clawdbot, summarizes what it finds, and guides you through phases covering agents, groups, credentials, identity, memory, and scheduled tasks. Each change is shown before it is applied.

How are OpenClaw cron jobs migrated to NanoClaw?

Cron schedules map directly to v2 recurrence expressions with a computed first-run timestamp. Fixed-interval jobs are approximated as cron when they divide evenly into minutes or hours, and one-shot 'at' jobs become single-run tasks created through the agent's schedule_task tool.

Where do OpenClaw credentials go during migration?

Host-side channel tokens for Telegram, Discord, and Slack are written to NanoClaw's .env file. Container-facing API credentials like Anthropic and OpenAI keys are registered in the OneCLI vault and injected per request, never placed in container environment variables.

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 would break encryption sessions, so you re-authenticate during NanoClaw setup instead.

What OpenClaw features do not transfer to NanoClaw v2?

Webhook delivery, failure alerts, per-task model and thinking configuration, exec approvals, human delay, and TTS have no v2 equivalent. Webhooks can be folded into a task prompt or pre-agent script that curls the endpoint.