The documented way to migrate Hermes Agent to new machine hardware, hermes backup plus hermes import, earns an 8 out of 10 from me: strong on safety checks and completeness, weaker on messaging pairs and a confusing command name.

Book a free SEO strategy session →

This verdict scores the route criterion by criterion from the Hermes docs, then says who should use it and who should pick a different route.

Want a second opinion on your own setup before you move it? Book a free SEO strategy session.

The Scorecard

Ratings are my editorial judgement from the Hermes FAQ, the CLI reference and the credential vault docs.

CriterionRatingWhy
Completeness9/10Config, credentials, memories, skills, sessions and every profile go in one zip.
Integrity checks9/10Exit codes on backup, a CRC check on import, partial restores flagged as failures.
Live-install safety9/10The backup uses SQLite's backup API and is WAL-safe while Hermes runs.
Session protection8/10Restoring an older backup over newer work prints a warning with before and after counts.
Credential handling7/10Keys travel in the zip, but a keychain vault key doesn't, and the docs flag it.
Messaging continuity5/10WhatsApp's QR pairing is documented as needing a re-pair after a migration.
Naming clarity5/10hermes migrate sounds like the right tool and isn't.
Cross-OS guidance4/10The docs don't address moving between operating systems at all.
Overall8/10The core route is solid; the gaps sit around it.

How I Scored It

Each criterion asks one question about the move, answered from the published docs only.

Completeness asks whether everything you built comes across. Integrity asks whether a bad copy gets caught. Live-install safety asks whether you can back up without downtime.

Session protection asks what happens if you restore the wrong zip. Credential handling asks whether keys travel and what can go missing.

Messaging continuity, naming clarity and cross-OS guidance cover the edges where people get stuck.

No benchmarks were run for this verdict; the ratings weigh what the documentation promises and warns about.

What Was Rated

The route here is the FAQ's "Exporting Hermes to another machine" sequence.

  1. Install Hermes on the new machine with the install script.
  2. Run hermes backup on the source machine.
  3. Copy the zip across and run hermes import.
  4. Run hermes setup to verify API keys and providers.

Book a free SEO strategy session →

I also compare it with the two alternatives the docs offer: a single-profile export and a manual rsync copy.

Strength 1: It Checks Itself

Most "copy your folder" migrations fail quietly. This one doesn't.

hermes backup exits 0 when every file landed, 1 when files were skipped, and 2 when another backup was already running.

On the other side, hermes import decompresses every member and checks its CRC before writing anything.

A damaged archive leaves the Hermes home untouched and exits 1, and so does a partial restore.

That's the main reason the score sits at 8 and not lower.

Strength 2: Your Keys Come Too

A full backup includes .env and auth.json.

That's the opposite of a profile export, which strips credentials for safe sharing.

For a machine move, carrying the keys is what you want, and the FAQ's comparison table labels the full backup "Full machine migration" for exactly that reason.

๐Ÿ”ฅ Want the full Hermes trainings before you move anything? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members comparing their Hermes setups. โ†’ Join the AI Profit Boardroom

Strength 3: Safe On A Live Install

You don't have to shut Hermes down to back it up.

The backup uses SQLite's backup() API, and the docs describe it as WAL-safe.

SQLite sidecar files are left out and regenerate on the new machine.

The one stop the docs ask for is on the other end: stop the gateway before importing.

Strength 4: Sessions Are Protected From Old Backups

Databases like state.db, kanban.db and response_store.db are written into the existing database file instead of being renamed in.

If an older backup holds fewer messages than the database it replaces, the import says so, with session and message counts before and after.

It still lets you do it, which is the right call, but it no longer happens silently.

Limit 1: The Naming Trap

This is where the route loses points.

hermes migrate imports from other agents (OpenClaw, Claude Code, Codex, Cursor, Grok Bot, OpenBot) or rewrites config.

Book a free SEO strategy session →

It doesn't move Hermes between machines.

A new user searching the CLI for "migrate" will land on the wrong command first.

If moving off Grok Bot is actually your job, see the verdict on how to migrate Grok Bot to Hermes.

Limit 2: Messaging Pairs Need Work

The import guide notes that WhatsApp authenticates through Baileys QR pairing and has to be re-paired after a migration.

Whether a full backup carries the WhatsApp session folder isn't stated.

Profile exports explicitly exclude platform sessions and pairing stores.

So the route gets you the agent, but customer-facing channels need a manual step.

Limit 3: The Keychain Catch

If the vault key lives in the operating system keychain, backups and copied folders hold the vault without its key.

The docs tell you to run hermes vault key migrate --to file before moving.

That's documented, which is good, but it lives on the vault page, not in the FAQ migration steps, so it's easy to miss.

Limit 4: Silence On Cross-OS Moves

The docs say nothing either way about moving between operating systems.

The FAQ only says you may need to update paths or re-authenticate if the new machine has a different setup.

No guidance isn't the same as no support, but it does mean extra testing on your side.

๐Ÿ“ž Want a verdict on your own migration plan? Book a free SEO strategy session and my team will go through what moves cleanly and what needs a manual step in your setup. โ†’ Book a free call

Backup + Import vs Profile Export vs rsync

RouteBest forCredentialsBuilt-in checks
hermes backup + hermes importMoving a whole installIncludedExit codes, CRC, session warning
hermes profile export / importMoving or sharing one agentStrippedRefuses to overwrite an existing profile
rsync fallbackHand-managed syncsWhatever is in the folderNone from Hermes

The profile distributions page adds a fourth option, hermes profile install from a git repo, but that's for deploying the same agent to several machines and never ships memories, sessions or keys.

Why Update Backups Don't Count

Hermes also takes backups around updates, and it's tempting to reuse one.

Book a free SEO strategy session →

The updating page draws the line: update backups protect an in-place update, and a move to different hardware uses hermes backup plus hermes import.

The quick mode gets the same treatment. hermes backup --quick saves config.yaml, state.db, .env, auth and cron jobs, and the FAQ says it isn't a replacement for a full backup before a machine migration.

So the verdict applies to the full backup only. Anything lighter scores lower by the docs' own account.

The Credential Trade-Off In Plain Terms

Carrying keys inside the zip is convenient, and it's also a responsibility.

Anyone holding that file holds your provider logins.

The docs handle this by giving you two tools: a full backup for your own machines, and a profile export that strips credentials for sharing.

That split is the right design, and it's why credential handling still scores a 7 despite the keychain catch.

In practice: copy the zip directly, don't park it on shared storage, and delete spare copies once the new machine checks out.

How The Route Handles A Single Profile

The profile path deserves its own short rating: 7 out of 10.

hermes profile export writes a .tar.gz of one profile, and hermes profile import restores it under a name you choose.

It loses points because credentials, platform sessions and pairing stores are always stripped, and the FAQ warns you may need to update paths or re-authenticate.

It gains them back with safe defaults: it refuses to overwrite an existing profile, and the docs tell you to list the contents with tar -tzf before sharing a file, since exports can include memories, sessions and USER.md.

In chat, /export does the same job, and the desktop app has Export profile and Import profile in its command menu.

The rsync Fallback, Rated

The manual fallback gets a 5 out of 10.

The FAQ documents it as an rsync of ~/.hermes/ that leaves out the code repo, and it does move the files.

What it doesn't do is check anything: no exit codes, no CRC test, no session warning, no skipped-file report.

The vault rule still applies too, since a copied folder doesn't carry a keychain key.

Book a free SEO strategy session →

Who Should Use It

  • Anyone moving a whole Hermes install to a new laptop, desktop or server.
  • Anyone with cron jobs, memories and skills they don't want to rebuild.
  • Anyone who wants the move to fail loudly instead of quietly.

Who Should Pick Another Route

  • If only one agent is moving, use a profile export instead and add its keys on the target.
  • If you're handing an agent to someone else, a profile export is safer because it strips credentials.
  • If you're deploying the same agent to many machines, look at profile distributions.
  • If you're coming from a different agent tool, that's hermes migrate.

What I'd Want Fixed

Three changes would push this route to a 9.

First, put the keychain warning inside the FAQ migration steps, not only on the vault page.

Second, say plainly whether a full backup carries messaging sessions such as WhatsApp's.

Third, add a line on moves between operating systems, even if it's only what to test.

None of these break the route today; they're the places where users have to piece the answer together themselves.

Final Verdict

8 out of 10.

The backup and import pair is complete, self-checking and safe to run on a live install.

It drops points for a misleading neighbouring command, a keychain step that lives on another page, and messaging channels that need re-pairing.

Run the full backup, check the exit code, import, run hermes setup, and keep the old machine until everything checks out.

For the trainings that go with it, join the AI Profit Boardroom.

Book a free SEO strategy session →

Also On Our Network

FAQ: Migrate Hermes Agent To New Machine Verdict

What score does the Hermes backup and import route get?

8 out of 10 overall. It scores highest on completeness, integrity checks and live-install safety, and lowest on cross-OS guidance and naming clarity.

Why does messaging continuity score low?

The Hermes docs note WhatsApp needs re-pairing after a migration, and whether a full backup carries the WhatsApp session is not stated.

Is a profile export a better choice than a full backup?

Only when one agent is moving or you are handing it to someone else. It strips credentials, so you add keys again on the target.

Is the rsync fallback safe?

It works, and the FAQ documents it, but it skips the exit codes, CRC check and session warning that backup and import give you.

๐Ÿ“บ Video notes + links to the tools ๐Ÿ‘‰

๐ŸŽฅ Learn how I make these videos ๐Ÿ‘‰

๐Ÿ†“ Get a FREE AI Course + Community + 1,000 AI Agents ๐Ÿ‘‰

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

  • I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
  • I've grown a YouTube channel to 400,000+ subscribers.
  • I wrote "Link Building Mastery".
  • My Udemy courses have taught over 29,000 students.

โ†’ Get my best AI training inside the AI Profit Boardroom

The route is sound, so use it, check every exit code, and if you want my team to look over your plan, book a free strategy session before you migrate Hermes Agent to new machine hardware.