openclaw-migration

Migrate OpenClaw user data, memories, and configurations to Quill Agent.

3|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/Quill-Agent/Quill-Agent --skill openclaw-migration-quill-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-migration
Source: https://github.com/Quill-Agent/Quill-Agent/tree/main/optional-skills/migration/openclaw-migration
Command: npx skills add https://github.com/Quill-Agent/Quill-Agent --skill openclaw-migration-quill-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of transferring a user's OpenClaw customization to Quill Agent, ensuring a seamless transition with minimal manual intervention.

Core Features & Use Cases

  • Data Import: Migrates memories, command allowlists, user skills, and workspace assets from OpenClaw to Quill Agent.
  • Conflict Resolution: Handles conflicts and skipped items, providing detailed reports for manual review.
  • Use Case: Ideal for users who have built extensive customizations in OpenClaw and wish to leverage them in the Quill Agent ecosystem.

Quick Start

To initiate the migration, use the command: quill claw migrate

Frequently Asked Questions about openclaw-migration

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

FAQPage Schema
How do I migrate OpenClaw data to Quill Agent?

Migrate OpenClaw data by running `quill claw migrate`, which imports memories, command allowlists, user skills, and workspace assets into Quill Agent. The process handles SOUL.md files and specific configurations automatically with minimal manual intervention.

What data configurations can I transfer from OpenClaw to Quill Agent?

Data transfer from OpenClaw supports memories, command allowlists, user skills, SOUL.md files, and workspace assets. The migration process maps these customizations directly into the Quill Agent ecosystem for immediate use.

Do I need Python to run the OpenClaw migration to Quill Agent?

Python is required to run the OpenClaw migration to Quill Agent, along with specific Quill Agent configurations. Ensure your Python environment is properly set up before initiating the transfer process.

Can I do a dry run before migrating OpenClaw data to Quill Agent?

A dry run is supported before migrating OpenClaw data to Quill Agent, allowing you to preview the transfer. The migration also provides detailed conflict resolution reports for skipped items requiring manual review.

How does conflict resolution work when importing OpenClaw workspace assets?

Conflict resolution during OpenClaw workspace asset import handles discrepancies by skipping conflicting items and generating detailed reports. These reports outline exactly what needs manual review to complete the migration.

Why are some items skipped during the OpenClaw to Quill Agent migration?

Items are skipped during OpenClaw to Quill Agent migration when conflicts are detected in configurations or workspace assets. The process generates a detailed report listing these skipped items for you to review and resolve manually.