hiclaw-migrate

Migrate OpenClaw instances into HiClaw Workers with a migration ZIP.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill hiclaw-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiclaw-migrate
Source: https://github.com/agentscope-ai/HiClaw/tree/main/migrate/skill
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill hiclaw-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrating an existing OpenClaw setup into HiClaw’s managed Worker environment is complex and easy to get wrong because runtime, storage, communication, and scheduling behaviors all change during the move.

Core Features & Use Cases

  • Dependency discovery: Analyzes your current OpenClaw workspace, skills, shell history, and cron payloads to identify extra system packages, Python packages, and Node packages you may need in a custom worker image.
  • Config migration guidance: Helps you adapt AGENTS.md, SOUL.md, and cron jobs to match HiClaw’s Manager-Workers architecture and Matrix-based communication.
  • Migration package generation: Bundles the migrated configuration, your custom skills, cron adaptations, and an installation Dockerfile into a ZIP ready for import into HiClaw.

Quick Start

Run the migration analysis script with your OpenClaw state directory and review the generated tool-analysis report to know what to include in your custom worker image.

Frequently Asked Questions about hiclaw-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an OpenClaw instance into a HiClaw Worker?

Migrating OpenClaw into a HiClaw Worker involves analyzing workspace dependencies, adapting AGENTS.md and SOUL.md configurations, converting cron jobs, and packaging custom skills into a migration ZIP for import.

What does the OpenClaw to HiClaw migration process include?

The migration process includes dependency discovery for system and Python packages, configuration adaptation for the Manager-Workers architecture, and generation of a Dockerfile and migration ZIP for MinIO-backed state and Matrix rooms.

Can I keep my existing cron jobs when moving to the Manager-Workers architecture?

Yes, you can keep existing cron jobs when moving to the Manager-Workers architecture by adapting the scheduled task payloads to match HiClaw's communication assumptions and runtime behavior during the migration analysis.

How are custom skills and tool dependencies handled during HiClaw migration?

Custom skills and tool dependencies are handled by analyzing shell history and workspace directories to identify required system, Python, and Node packages, then bundling them into an installation Dockerfile within the migration package.

Do I need a custom Dockerfile to run migrated OpenClaw agents with MinIO and Matrix?

Yes, you need a custom Dockerfile generated during migration to ensure the resulting Worker container can properly run with MinIO-backed state and Matrix rooms in the HiClaw managed environment.

Why does my OpenClaw migration to HiClaw fail during import?

OpenClaw migration to HiClaw can fail if the migration ZIP lacks properly adapted AGENTS.md configurations, missing dependency declarations from shell history, or incorrectly bundled custom skills for the Worker container.