If you need to migrate Hermes Agent to new machine hardware for your business, the job is a full backup on the old computer and an import on the new one, and the agent comes back with its memory, skills, sessions and API keys.
Book a free SEO strategy session →
That matters when the agent answers customers, runs scheduled reports or keeps notes on your clients.
This guide is for owners who want to know what the move involves, what it puts at risk and who should do it.
If you want my team to talk it through with you first, book a free SEO strategy session and tell us what your agent does today.
Why A Business Moves Its Agent In The First Place
Most small businesses start Hermes on whatever computer is nearest.
A laptop, an office desktop, a spare machine in the back room.
Then the agent becomes useful, and that computer becomes a weak point.
It gets switched off, taken home, replaced or shared with staff.
The Hermes FAQ describes the common next step in one line: you've built up skills, cron jobs and memories on one machine and want to move everything to a new dedicated Linux box.
A new laptop, an always-on office machine or a rented server are all the same move.
What The Move Looks Like In Plain Terms
There are four parts.
- Someone runs
hermes backupon the old computer. It produces one zip file. - Hermes gets installed on the new computer.
- The zip is copied over and restored with
hermes import. hermes setupruns on the new computer to check the API keys and AI providers work.
Those steps are the documented route.
A command called hermes migrate also exists, and the name misleads people.
The CLI reference says it imports from other agent tools such as OpenClaw, Claude Code, Codex, Cursor, Grok Bot and OpenBot, or rewrites config. It isn't for moving Hermes between your own computers.
What Comes Across And What Doesn't
This is the part owners care about most, so here it is in one table.
| Business asset | In the full backup? | What to plan |
|---|---|---|
| The agent's memories about clients and your business | Yes | Spot-check a few after the move |
| Past conversations (sessions) | Yes | Open one old conversation to confirm |
| Skills and scheduled jobs | Yes | Check the schedule list on the new machine |
| API keys (.env, auth.json) | Yes | Treat the zip as sensitive |
| Every profile (every agent) | Yes | Nothing extra |
| Downloaded models and runtimes | No | They download again |
| Browser profiles and saved browser logins | No | Sign in again where needed |
| WhatsApp pairing | Not stated | Plan to re-pair |
Book a free SEO strategy session →
The exclusions come from the CLI reference. The docs say runtime downloads are often tens of GB, which is why they stay out of the backup.
🔥 Want the step-by-step Hermes trainings for your business setup? 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 agents in their own businesses. → Join the AI Profit Boardroom
Example: A Local Shop Moving Its Agent Off The Front-Desk PC
Picture a bike shop whose agent drafts replies to booking messages and keeps notes on regular customers.
It runs on the till computer, which also handles card payments and gets restarted every morning.
The owner buys a small always-on machine for the back office.
The move: back up on the till PC after closing, copy the zip on a USB stick, install Hermes on the new box, import, run setup.
Customer notes and the booking-reply skill come across in the zip.
The one job left is re-pairing WhatsApp, so the owner does the move on a quiet evening, not a Saturday morning.
Example: A Service Firm Moving To A Dedicated Linux Box
Now picture a three-person bookkeeping firm.
Their agent runs weekly cron jobs that pull reports and summarise them for each client.
The partner who set it up is replacing her laptop.
This is the exact scenario in the Hermes FAQ, so the firm follows it step by step.
Because a full backup includes credentials, the zip is handled like any other file with client logins in it: copied directly, deleted once the move is checked.
After the import, hermes setup confirms the provider keys, and someone checks that every client's scheduled job shows up.
Example: An Agency Moving One Client Agent At A Time
A small marketing agency runs one Hermes profile per client.
One client wants its agent on a server in its own account, while the rest stay where they are.
A full backup is the wrong tool here, because it carries every profile and every key.
Instead the agency uses hermes profile export, which packs one profile into a .tar.gz and strips the credentials.
Book a free SEO strategy session →
On the client's server it runs hermes profile import, then adds that client's own keys.
The profile distributions page says exports can still include memories, sessions and USER.md, and recommends listing the contents with tar -tzf before handing the file to anyone.
The Credentials Question Owners Should Ask
A full backup includes .env and auth.json.
That's what makes the move painless, and it's also why the zip deserves care.
Keep it off shared drives, copy it directly to the new machine, and remove spare copies once you've confirmed the new setup.
One more check: if your Hermes vault key sits in the operating system keychain, the credential vault docs say the backup won't carry the key.
Whoever does the move runs hermes vault key migrate --to file first.
Messaging Channels: Plan For A Re-Pair
If customers reach your agent through WhatsApp, plan for a re-pair.
The Hermes import guide notes that WhatsApp authenticates through QR pairing and needs re-pairing after a migration, and profile exports leave out platform sessions entirely.
So pick a time when a short gap in replies won't hurt, have the business phone ready to scan the QR code, and test a message straight after.
📞 Not sure your agent setup is ready to move? Book a free SEO strategy session and my team will look at what your agent handles today and what to check before and after the move. → Book a free call
Risks To Plan Around
- An incomplete backup.
hermes backupexits with code 1 when files are skipped. The zip still exists, which is exactly why someone has to read the report. - An old zip. If you restore last month's backup, newer conversations are gone. The import prints a warning with before and after counts when that happens.
- Running processes. The CLI reference says to stop the gateway before importing.
- Logins. The FAQ says you may need to update paths or re-authenticate with providers.
- A different operating system. The docs don't address moving between operating systems, so leave extra testing time if your new machine runs a different one.
Choosing Where The Agent Should Live Next
Before the move, decide what the new home needs to do.
Book a free SEO strategy session →
If the agent runs scheduled jobs overnight, it needs a machine that stays on, such as a small office box or a rented server.
If it mostly helps one person during the day, a new laptop is fine.
If staff need it from several places, a server is usually the cleaner choice, because nobody's personal computer becomes the single point of failure.
The FAQ's example is a dedicated Linux box, and the install script covers that case directly.
Who Should Do The Move
If you're comfortable typing a handful of commands, you can do it yourself in an evening.
If not, hand it to whoever installed Hermes in the first place, and give them this page.
Either way, the person needs access to both machines and the business phone for any re-pairing.
One thing to never delegate: deciding when the old computer gets wiped. Make that your call, after the checks pass.
A Simple Move-Day Plan
- Pick a quiet window and tell staff the agent will be offline briefly.
- Run the full backup and confirm it exited cleanly.
- Install Hermes on the new machine and import the zip.
- Run
hermes setup. - Re-pair messaging channels and send a test message.
- Check memories, an old conversation and the scheduled jobs.
- Keep the old machine untouched for a week.
The docs back step 7: review the skipped-file report before you remove the source install.
Questions To Ask Whoever Does The Move
If someone else is handling it, these five questions keep it on track.
- Did the backup finish with exit code 0, and if not, what was skipped?
- Is the vault key a file, or was it in the keychain?
- Was the gateway stopped on the new machine before the import?
- Did
hermes setuppass for every AI provider? - Which messaging channels were re-paired, and has each one answered a test message?
You don't need to understand every command to ask these. You just need clear yes or no answers.
Keeping Customers In The Loop
If your agent replies to customers, a short gap is the only thing they'll notice.
Post a simple note on your usual channel if replies might pause for an hour or so.
Book a free SEO strategy session →
Do the WhatsApp re-pair first once the import passes, because that's the channel customers see.
Then send a test message from a staff phone and check the reply before you call the move done.
Make The Backup A Habit, Not A One-Off
The same hermes backup command that powers the move is also your safety net.
It keeps the three most recent full backups by default, and --keep N changes that number.
Running it regularly means that if a computer dies, you restore from a recent zip instead of rebuilding the agent from memory.
Store at least one copy somewhere other than the computer it came from, and treat it with the same care as a password list.
Is It Worth Doing Now?
If your agent lives on a computer that gets switched off, shared or replaced, yes.
The move itself is short, and the backup step is worth running regularly anyway.
If you're also thinking about bringing Bots over from Grok Bot, read the guide on how to migrate Grok Bot to Hermes; that uses a different command.
For the trainings and the installable Agent OS behind setups like these, join the AI Profit Boardroom.
Book a free SEO strategy session →
Also On Our Network
- 🌐 The seven-step backup and import run, flags and exit codes included
- 🌐 The backup and import route scored criterion by criterion, with the gaps
- 🌐 Five copy-paste prompts that let your agent prepare and audit the move
- 🌐 Which models to run after the move, using live GoldieBench scores
FAQ: How To Migrate Hermes Agent To New Machine Hardware For Your Business (Without Losing Client Memory)
Will my agent remember my customers after the move?
Yes, if you use a full hermes backup. It covers memories, sessions, skills and profiles, so the agent's notes come across in the zip.
Is the backup file sensitive?
Yes. A full backup includes your API keys in .env and auth.json. Copy it directly to the new machine and remove spare copies once the move is checked.
Can I move just one client agent?
Yes. Use hermes profile export for that one profile. It strips credentials, so you add that client’s keys again on the new machine.
Will WhatsApp keep working after the move?
Plan to re-pair it. The Hermes docs note that WhatsApp uses QR pairing and needs re-pairing after a migration.
When can I wipe the old computer?
Only after the checks pass. The docs say to review the skipped-file report before removing the source install.
📺 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
Pick your quiet window, run the backup, and if you want a second opinion, book a free strategy session so you can migrate Hermes Agent to new machine hardware without your customers noticing.











