agentos.guide › blog
You can migrate Hermes Agent to new machine hardware from inside your Agent OS by letting your agent prepare and check the move, while you run the one restore step yourself.
Book a free SEO strategy session →
The documented route is hermes backup on the old machine and hermes import on the new one, then hermes setup.
This guide gives you a quick start, five prompts to hand your agent, and the move-day workflow I'd follow.
Want a hand planning it? Book a free SEO strategy session.
# old machine
hermes vault key migrate --to file # only if the vault key is in the keychain
hermes backup
scp ~/hermes-backup-<timestamp>.zip newmachine:~/
# new machine
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
hermes import ~/hermes-backup-<timestamp>.zip && hermes setup
The order follows the Hermes FAQ section on exporting Hermes to another machine.
The vault step comes from the credential vault docs, and the stop-the-gateway warning from the CLI reference.
On the old machine, your agent can do almost everything: check the vault key, take the backup, read the exit code, list what's in the zip.
The backup is WAL-safe, so it's fine to run while the agent itself is working.
On the new machine it's different.
The import overwrites files in the Hermes home, and the docs say to stop the gateway before importing.
So I run the restore in a plain terminal, not through a live agent session, and hand control back to the agent once hermes setup passes.
And one naming note: hermes migrate is for importing from other agents such as OpenClaw, Claude Code or Grok Bot. It isn't the command for this job.
The FAQ does document an rsync fallback that copies ~/.hermes/ across while leaving out the code repo.
It works, but it gives your agent nothing to check.
The backup and import pair hands you exit codes, a CRC test on every file and a warning if older sessions replace newer ones.
Those are exactly the signals an agent can read and report on, which is why every prompt below leans on them.
Before I move this Hermes install to a new machine, run a pre-flight check:
1. Run `hermes vault key` and tell me whether the vault key is a file or in the keychain.
2. List every profile, every cron job and every messaging platform that is paired.
3. Tell me which of those platforms will need re-pairing on a new machine.
Don't change anything yet. Give me the results as a short checklist.
Book a free SEO strategy session →
This gives you the list of things to check on the other side.
If the key is in the keychain, approve hermes vault key migrate --to file before going further.
Expect the platform list to matter most. Those are the channels your customers or team actually use, and the ones you'll test first on the new machine.
Save the agent's checklist somewhere outside the Hermes home, such as a note on your phone, so you still have it while the new machine is being set up.
Run a full `hermes backup` (not --quick). When it finishes:
1. Tell me the exact path of the zip.
2. Tell me the exit code. 0 = complete, 1 = incomplete, 2 = another backup was running.
3. If any files were skipped, list them and tell me what to fix.
Don't delete or prune any existing backups.
The FAQ is clear that a quick backup doesn't replace a full one before a machine migration.
On exit code 1 the zip still exists, which is why the prompt makes the agent read the skipped-file list out loud.
🔥 Moving your Agent OS to a server?
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 running Hermes on their own machines.
Run this one yourself in a terminal on the new machine, after installing Hermes:
hermes gateway stop # if a gateway is already running
hermes import ~/hermes-backup-<timestamp>.zip
hermes setup
The import checks every member's CRC before writing, so a damaged zip leaves the home untouched.
If an older backup replaces newer sessions, it prints a warning with the counts. On a fresh machine that usually means you copied the wrong file.
If the import exits with code 1, read the lines under "Warnings" before you do anything else. The docs say a database can be skipped when another process still holds it open, and the fix is to stop that process and re-run.
Don't start the agent again until the import comes back clean and setup passes.
Book a free SEO strategy session →
Once setup passes, open your agent on the new machine and give it this:
We just moved to a new machine with hermes backup + hermes import.
Audit the move against this pre-flight list: [paste Prompt 1's checklist]
1. Confirm every profile and cron job is present.
2. Open one old session and summarise it so I know sessions came across.
3. Check each provider responds.
4. List every messaging platform that still needs re-pairing, with the command.
5. Tell me whether the gateway service needs `hermes gateway install` on this machine.
For WhatsApp the answer is usually hermes whatsapp: the import guide notes that QR pairing has to be redone after a migration.
I want to move only the "work" profile to another machine.
1. Run `hermes profile export work ./work-backup.tar.gz`.
2. List the archive contents with `tar -tzf ./work-backup.tar.gz | less` and show me anything personal.
3. Tell me which credentials I'll need to add again on the target, because profile exports strip them.
On the target, run hermes profile import ./work-backup.tar.gz work.
The profile distributions page lists what exports leave out: auth.json, .env, token files, vault/, platform sessions, pairing stores and more.
Use Prompts 1 to 4 when the whole Agent OS is moving: every profile, every cron job, every key.
Use Prompt 5 when only one agent is going somewhere else, such as a client profile heading to its own server.
The difference that matters is credentials. The full backup carries .env and auth.json; the profile export never does.
Profile import also refuses to overwrite an existing profile and can't import as default, so pick a fresh name on the target if one already exists.
And if you use Honcho or another memory provider, add a line to Prompt 4 asking the agent to rerun its setup.
| When | Who runs it | What happens |
|---|---|---|
| Before | Agent (Prompt 1) | Vault key, profiles, cron jobs, paired platforms |
| Backup | Agent (Prompt 2) | Full zip, exit code, skipped files |
| Copy | You | Zip to the new machine |
| Restore | You (Prompt 3) | Stop gateway, import, setup |
| After | Agent (Prompt 4) | Audit, re-pair list, gateway service |
| A week later | You | Retire the old machine |
Book a free SEO strategy session →
Moving from Grok Bot instead? That's a different flow, covered in migrate Grok Bot to Hermes in your Agent OS.
📞 Want my team to plan the move with you?
Book a free SEO strategy session and we'll go through your profiles, cron jobs and messaging channels before you switch machines.
If you'd rather sync the folder by hand, the FAQ's rsync fallback still works, but your agent loses the exit codes it relies on in Prompts 2 and 4.
hermes honcho setup or hermes memory setup if you use them.Prompt 2 isn't only for moving day.
Ask your agent to run it as a cron job each week and report the exit code, so you always have a recent full backup ready.
By default the command keeps the three most recent full backups and prunes older ones; --keep N changes that.
Copy one of them off the machine now and then, because a backup that lives only on the computer it protects doesn't help if that computer fails.
The docs say to review the skipped-file report before you remove the source installation.
I'd go further and leave the old machine untouched until Prompt 4 comes back clean and your channels are answering.
For the full trainings and the installable Agent OS, join the AI Profit Boardroom.
Book a free SEO strategy session →
It can run the pre-flight check, the backup and the post-move audit. Run the import yourself in a plain terminal, because it overwrites the Hermes home and the gateway should be stopped first.
Where the vault key lives, every profile and cron job, and which messaging platforms are paired, so you know what to verify on the new machine.
It reads the exit code: 0 means complete, 1 means files were skipped, 2 means another backup was running.
Plan for it. The Hermes import guide notes WhatsApp QR pairing has to be redone after a migration, so run hermes whatsapp on the new machine.
Paste Prompt 1 into your agent now, and if you want help with the rest, book a free strategy session and we'll plan how you migrate Hermes Agent to new machine hardware.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
→ Migrate Grok Bot To Hermes In Your Agent OS: Quick Start, Five Agent Prompts And A Roster Workflow
→ Hermes Webapp: Run Your Whole Agent OS From A Browser Tab, With Five Copy-Paste Prompts
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉