OpenClaw Migration for Openclaw

A systematic migration playbook for transitioning codebases, documentation, and tooling from the Clawd brand to OpenClaw.

chenyuan99
v1.0.0
Feb 2, 2026
2
5.6k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install openclaw-migration

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install openclaw-migration using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is OpenClaw Migration?

The OpenClaw Migration skill provides a structured framework for refactoring repositories during a brand transition. It acts as a shared source of truth for both human developers and AI helpers, ensuring that every step of a renaming process—from directory restructuring to CI/CD configuration updates—is executed consistently.

By utilizing this skill within the Openclaw Skills ecosystem, teams can avoid broken builds and fragmented documentation. It ensures that all legacy references to Clawd are systematically replaced with OpenClaw, preserving the integrity of the agent's personality, memory, and operational scripts.

OpenClaw Migration Use Cases

  • Managing a full-scale repository rename from clawdbot to openclaw.
  • Updating internal documentation, READMEs, and metadata to reflect new branding.
  • Synchronizing CI/CD workflows and workspace configurations with new directory paths.
  • Onboarding contributors to the new OpenClaw project structure to prevent legacy naming errors.

How OpenClaw Migration Works

  1. Inventory the current layout to identify the application root, metadata files (SOUL.md, AGENTS.md), and existing tooling.
  2. Create the new OpenClaw root directory while preserving essential hidden files and workspace lockfiles.
  3. Execute a case-sensitive search and replace for brand references across all documentation, source code, and configuration files.
  4. Relocate core metadata and skill definitions to maintain their functionality relative to the new application root.
  5. Run validation suites, including pnpm tests and linting, to ensure the new layout is fully operational.
  6. Update the primary repository README and archive legacy artifacts for traceability.

OpenClaw Migration Setup

This skill is integrated into the workspace repository. To begin the migration or verify current status, ensure your environment is initialized with the proper package manager:

# Bootstrap the workspace to ensure current paths are recognized
pnpm install

# After renaming, verify the new directory structure
cd openclaw && pnpm test

OpenClaw Migration Data Schema & Taxonomy

The skill manages the transition between the following key components and metadata files:

File/Directory Role in Migration
clawdbot/ The original application root to be migrated.
openclaw/ The target destination for the rebranded codebase.
package.json Updated to reflect new directory paths and script definitions.
SOUL.md Persona description updated to reflect the OpenClaw identity.
AGENTS.md Metadata file updated for agent discovery in Openclaw Skills.
skills.json Manifest file synchronized with updated skill directory paths.

OpenClaw Migration Advanced Features

  • Case-sensitive brand alignment across multi-agent metadata and soul files.
  • Automated validation of pnpm workspace references and tsconfig path mappings.
  • Support for preserving hidden configuration files like .github, .agent, and .ox during migration.
  • Comprehensive cleanup protocols for archiving legacy artifacts without losing history.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*