migrate-from-openclaw

Migrate OpenClaw installations to NauggieClaw by analyzing configs and state data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrating from OpenClaw to NauggieClaw requires careful handling of isolated containers, per-group CLAUDE.md files, channel credentials, and scheduled tasks, and this guided skill orchestrates that conversation so nothing is silently copied or overlooked.

Core Features & Use Cases

  • Discovery & Planning: Run the discovery script, summarize the existing installation, and document decisions in migration-state.md before touching any files.
  • Groups, Identity, and Memory: Decide on shared versus isolated models, register groups, migrate identity/SOUL/USER/MEMORY content into the appropriate CLAUDE.md and supporting files, and optionally copy over daily memory archives.
  • Channels, Credentials, and Tasks: Extract channel credentials with dedicated scripts, map allowlists, insert scheduled tasks via the SQL template, and record MCP servers or custom plugins that need later attention to keep the system operational.

Quick Start

Ask Auggie to run migrate from openclaw to begin the guided migration conversation.

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 OpenClaw installations to a containerized architecture?

Migrate OpenClaw installations to NauggieClaw by running discovery scripts, updating .env entries, copying CLAUDE.md context, registering groups, and documenting deferred tasks for a safe transition into containerized environments.

What is the best way to transfer scheduled tasks and channel credentials during an OpenClaw migration?

Transfer scheduled tasks and channel credentials by running dedicated extraction scripts, mapping allowlists, and inserting tasks via the SQL template to keep the system operational post-migration.

How do I migrate identity files and group memory when moving OpenClaw setups?

Migrate identity files and group memory by deciding on shared versus isolated models, then migrating identity, SOUL, USER, and MEMORY content into appropriate CLAUDE.md and supporting files.

Do I need to run a discovery script before migrating OpenClaw to NauggieClaw?

Yes, you must run the discovery script first to summarize the existing installation and document decisions in migration-state.md before touching any configuration files.

How does the guided OpenClaw to NauggieClaw migration process handle MCP servers?

The migration process records MCP servers and custom plugins that need later attention during the transition, documenting them as deferred tasks to ensure continuous system operation.

Can I copy daily memory archives directly when migrating OpenClaw groups?

Yes, you can optionally copy over daily memory archives when migrating identity and group content into the appropriate CLAUDE.md and supporting files during the transition.