migrate-from-openclaw

You can migrate OpenClaw to NanoClaw v2 by running the migration script, which guides you through a structured plan from Phase 0 to Phase 8. It validates OpenClaw data shapes, handles credential routing, and translates cron jobs to v2 recurrence.

OpenClaw cron job migration works by translating cron-based schedules into NanoClaw v2 task representations through automated analysis and user-driven decisions. The tool converts cron expressions to v2 recurrence formats, validating OpenClaw data shapes before transferring content into per-group containers.

Yes, you can migrate multi-group OpenClaw deployments to NanoClaw v2. The tool handles per-group wiring, workspace mapping, and credential routing for both single and multi-group setups, applying a phase-driven process to ensure each group is migrated correctly.

The structured plan spans Phase 0 through Phase 8, guiding identity mapping, credential handling, cron transformations, and content transfer. It produces a repeatable migration plan and includes optional removal guidance via REMOVE.md for clean rollback after the transition.

Credential mapping during OpenClaw to NanoClaw v2 migration is handled through the tool's credential routing feature within the phased workflow. It ensures credentials are correctly transferred and mapped per-group, validating data shapes to maintain secure and accurate routing.

Yes, the migration provides rollback guidance through a generated REMOVE.md file. This removal guidance supports clean rollback after the migration, allowing you to safely remove the old OpenClaw installation once the NanoClaw v2 transition is validated.