Academy → Using HermesOfficial documentation · clear explanation

Openclaw Migration — Import an OpenClaw setup (memories, skills) into Hermes

Openclaw Migration — Import an OpenClaw setup (memories, skills) into Hermes

Beginner16 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Openclaw Migration — Import an OpenClaw setup (memories, skills) into Hermes as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Skill metadata, Reference: full SKILL.md, CLI Command, then verify failure modes and version compatibility.

What do you need first?

No prior experience is required; follow the steps on a safe test setup first.

What will you know?

A clear outcome before you read.

  • Understand Openclaw Migration — Import an OpenClaw setup (memories, skills) into Hermes without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

Skill
An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Official page description

Import an OpenClaw setup (memories, skills) into Hermes

Topic map

What does the source say, and in what order?

  1. 01
    Skill metadata

    Start here to understand the core idea or structure.

  2. 02
    Reference: full SKILL.md

    Read this after the foundation, then connect it to the previous step.

  3. 03
    CLI Command

    Read this after the foundation, then connect it to the previous step.

  4. 04
    What this skill does

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Path resolution

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Default workflow

    Read this after the foundation, then connect it to the previous step.

  7. 07
    User interaction protocol

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Decision-to-command mapping

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Post-run reporting rules

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Migration presets

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

hermes claw migrate # Full interactive migration hermes claw migrate --dry-run # Preview what would be migrated hermes claw migrate --preset user-data # Migrate without secrets hermes claw migrate --overwrite # Overwrite existing conflicts hermes claw migrate --source /custom/path/.openclaw # Custom source
python3 ~/.hermes/skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py
{"command":"python3 /home/USER/.hermes/skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py","workdir":"/home/USER"}
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Openclaw Migration — Import an OpenClaw setup (memories, skills) into Hermes” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?