Migration from OpenClaw

What to expect when switching to an alternative

If you're running OpenClaw and considering a switch to ZeroClaw, TinyClaw, NanoClaw, or another alternative, this guide explains what transfers and what doesn't. Migration support varies—ZeroClaw has built-in tools; most others require a fresh start.

ZeroClaw: Built-in Migration

ZeroClaw is the only alternative with dedicated migration tooling from OpenClaw:

  • Config — Transfer gateway config, model settings, channel configs
  • Memory — Transfer long-term memory and context
  • Credentials — API keys and secrets must be re-added manually (by design, for security)
  • Skills — Custom skills have no direct equivalent; you'll need to rebuild or find alternatives

See the ZeroClaw guide and ZeroClaw's own migration docs for step-by-step instructions.

TinyClaw, NanoClaw, PicoClaw, Nanobot: Fresh Start

These alternatives have no migration path from OpenClaw. You'll need to:

  • Set up the new project from scratch
  • Reconfigure channels (Discord, WhatsApp, Telegram, etc.)
  • Re-enter API keys and credentials
  • Accept that memory and long-term context do not transfer
  • Recreate or replace custom skills and workflows

Expect a day or more of setup depending on how complex your OpenClaw config was. The trade-off is a smaller codebase, different performance characteristics, or different feature sets.

What You'll Lose (vs OpenClaw)

Regardless of which alternative you choose, you typically give up:

  • ClawHub skills — Hundreds of pre-built skills; alternatives have smaller or no skill ecosystems
  • Browser automation — OpenClaw's built-in browser, PinchTab, Unbrowse, camofox; most alternatives lack equivalents
  • Canvas — Visual workspace; alternatives generally don't have it
  • Voice features — Wake word, TTS; availability varies
  • Multi-agent teams — Subagents, shared context; OpenClaw has the most mature support
  • Community and docs — OpenClaw has the largest community and most tutorials

When Migration Makes Sense

  • ZeroClaw — You need minimal RAM, edge deployment, or stricter security defaults. Migration tools make the switch easier.
  • TinyClaw — You want a minimal Claude Code wrapper; you're okay with Discord/WhatsApp only and no skills.
  • NanoClaw — You prioritize container isolation and a smaller, auditable codebase.
  • PicoClaw — You're targeting edge/embedded (RISC-V, old phones) or need hardware I/O.
  • Nanobot — You prefer Python and want an agent loop with MCP.

Related