migrate-from-openclaw

To migrate from OpenClaw to NanoClaw, an interactive assistant analyzes your existing deployment to inventory identity, channels, tasks, and configuration, then scaffolds the new setup phase by phase. It masks credentials and prompts for confirmation on critical decisions.

Moving OpenClaw scheduled tasks and channels to NanoClaw involves an interactive discovery phase that extracts your credentials and configuration, followed by a guided phase-driven workflow that sets up groups, settings, and skills with clear checkpoints.

No, the OpenClaw to NanoClaw migration does not expose channel credentials. The process enforces strict credential masking throughout the discovery and execution phases to ensure all steps remain safe and auditable.

You cannot skip configuration mapping entirely, but the migration assistant automates the extraction of OpenClaw settings and identity. It explains architectural differences and prompts you for collaborative decisions rather than requiring fully manual configuration.

Setting up NanoClaw after moving from OpenClaw follows a phase-driven workflow covering group setup, settings, skills, credentials, and containerization. Each phase presents a clear checkpoint to ensure safe, auditable migration progress.

Migrating OpenClaw to NanoClaw requires interactive confirmation to ensure safe, guided migration. By prompting for decisions on critical steps, the process maintains transparency, prevents data loss, and adapts the NanoClaw scaffold to your specific deployment.