LZLZL/AI toolchain/Always-on · Migration
FREEShallow · Start here C · Always-onmigration

Moving house
in one command

2026-08-21 · The value is not the time saved. It is not having deleted it

Switching from OpenClaw to Hermes does not mean starting over. One command carries persona, memory, skills, API keys and settings. Here is how — and the more durable selection test that falls out of it.

In this pagethe command, what to check, a general test. Not in this pagewhat I migrated.

1Two commands

hermes claw migrate --dry-runsee what it intends to do
hermes claw migratethen do it

It reads ~/.openclaw and brings across:

ItemWorth it because
PersonaMonths of tuned tone and preference; re-doing it is tedious
MemoryThe irreplaceable one — what it knows about you and your projects cannot be reconstructed
SkillsAccumulated reusable procedure
API keysSaves hunting them down again
SettingsAll the switches and preferences

2Dry-run first, for three reasons

① "Import" may overwrite what you have

If you already configured things in the new tool, does an import layer on top or paint over? A dry run answers that faster than the docs will.

② Keys come along — good, and also a risk

Importing API keys means they land in the new tool's secrets file (~/.hermes/.env for Hermes). This is the best moment you will get to audit which keys you are carrying: expired ones, unused ones, ones you cannot account for — clear them now rather than moving them into the new house to keep sitting there.

③ You may not want all of it

Long-accumulated memory can contain conclusions that stopped being true — a project convention you changed months ago, an approach you abandoned. Import everything and you inherit the stale beliefs too.

Dry-run, read the list, then decide.

3Check three things afterwards

CheckHow
Memory really cameAsk about something only the old memory would know
Keys landed in the right fileConfirm they are in .env and not the main config — this determines your backup strategy
Skills are not staleRead the skill list and delete the obviously outdated (previous page §5)

4The actual lesson: this works because I did not delete

The command is only useful to me because on shutdown day the whole ~/.openclaw directory was archived rather than wiped as no-longer-needed. It was caution at the time; it turned out to be what preserved the assets from page 12.

Which yields a selection test more durable than "which is better"

When choosing an always-on agent, alongside what it can do, ask: "where does it keep my assets, and can I take all of them with me?"

Good answer: a few directories, readable formats, copyable wholesale. Bad answer: scattered through a database, sprayed across the system, or existing only inside somebody's cloud account.

That test does not decide how much you enjoy today. It decides whether switching in three months is one command or a fresh start.

5The same property is a backup discipline

This matters even if you never switch tools, because "can be taken away wholesale" and "can be backed up wholesale" are the same property. Page 6's backup list is fundamentally asking the same question: which directories hold your assets?

If you cannot answer, you can neither back up nor leave.

Commands hermes claw migrate (interactive import) and hermes claw migrate --dry-run (preview); imports persona, memory, skills, API keys and settings from ~/.openclaw. Official docs, checked 2026-08-21.
Where keys land Hermes stores API keys in ~/.hermes/.env, other settings in ~/.hermes/config.yaml.
My side The knowledge base was archived in full at shutdown on 2026-07-13, which is the precondition for any of this. See page 12.
What I did not test I have not exercised this command across the range of conflict cases — so this page says "dry-run first" rather than asserting how it merges.
Not in this page What I migrated, or any keys and configuration.

RelatedRead next

C · Always-on
OpenClaw, and why I switched that machine off
C · Always-on
Hermes Agent: where OpenClaw leads next
B · Access
How accounts die, and what to back up first
C · Always-on
Telegram: lock down who, then discuss what
An educational and engineering record — not a review or endorsement of any third-party product. Commands, config keys, prices and terms are per each vendor's official docs; this page states when it was checked and all of them can change without notice — verify before you copy anything. Self-hosting is your own responsibility: keys, accounts and data are on you.