migrate-from-openclaw

Migrate OpenClaw installations to NanoClaw v2 architecture.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the complex transition from OpenClaw to NanoClaw v2, ensuring that your identity, channel credentials, scheduled tasks, and agent configurations are safely and accurately transferred to the new architecture.

Core Features & Use Cases

  • Automated Discovery: Scans existing OpenClaw installations to map agents, groups, and workspace files to the v2 entity model.
  • Credential Routing: Securely migrates channel tokens to the host environment and container-facing API keys to the OneCLI vault.
  • Task Mapping: Converts legacy cron jobs into v2-compatible tasks using a robust transformation engine.

Quick Start

Initiate the migration process by telling the agent to migrate from openclaw to begin the discovery phase.

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 agents and scheduled tasks from OpenClaw to NanoClaw v2?

To migrate agents and scheduled tasks from OpenClaw to NanoClaw v2, this skill automates the mapping of legacy agents, messaging groups, and cron jobs to the v2 entity model using a robust transformation engine.

What is the process for converting OpenClaw cron jobs to NanoClaw v2 recurrence tasks?

Converting OpenClaw cron jobs to NanoClaw v2 recurrence tasks is handled by a robust transformation engine that maps legacy scheduled items to v2-compatible tasks and validates them through automated testing.

How are channel credentials and API keys handled during an OpenClaw to NanoClaw migration?

During an OpenClaw to NanoClaw migration, channel tokens are securely routed to the host environment, while container-facing API keys are transferred to the OneCLI vault to ensure structural compatibility with v2 container isolation.

Can I automatically discover OpenClaw workspace files and map them to the NanoClaw v2 entity model?

Yes, you can automatically discover OpenClaw workspace files and map them to the NanoClaw v2 entity model. The skill scans existing installations to map agents, groups, and workspace files directly to the v2 architecture.

Do I need cron-parser or vitest installed to validate my OpenClaw migration?

Yes, you need cron-parser and vitest installed to validate your OpenClaw migration. The skill relies on these dependencies to execute automated testing of cron-to-recurrence transformations and verify credential routing logic.