Should You Migrate Grok Bot To Hermes? An Owner's Guide

Business owners who want to migrate Grok Bot to Hermes can now do it without rebuilding their assistants from scratch.

Hermes v0.22.6, out on 2 November 2026, added a command that pulls each Bot's routines, skills and memory into Hermes.

The real question for a small business isn't whether it works.

It's whether moving is worth an afternoon of your time, and which Bots should go first.

If you want a straight answer for your own setup, book a free SEO strategy session with my team.

The Short Answer For Owners

Move if you want your assistants on infrastructure you control, with schedules and memory you can open as plain files.

Stay put for now if your Bots lean on event triggers and app logins you don't want to set up twice.

Grok Bot is a capable hosted product, and many teams will keep using it for some jobs.

Hermes is the better fit when you want one place for your agents, your own choice of model, and profiles you can copy between machines.

The good news is that the move isn't all or nothing.

You can bring over one Bot, run it for a week, and leave the rest where they are.

What The Move Actually Involves

There's no export button in Grok Bot, so Hermes asks each Bot to export itself.

Someone on your team runs hermes migrate grok-bot, and Hermes prints a message to paste into the Bot's chat.

The Bot replies with a file called grok-bot-export.json, or with the same data as a block of text.

Your team saves that file to the Downloads folder, and Hermes picks it up from there.

Nothing in Grok Bot is changed by the export.

That means you can test the whole process with zero risk to the assistants your staff use today.

The official import guide has the full detail for whoever does the technical part.

What Your Business Keeps And What It Redoes

This table is the one I'd print out before deciding.

Part of your Bot	Comes over?	Work left for your team
Timed jobs like a daily sales summary	Yes, as paused scheduled jobs	Switch them on once the Grok copy is paused
Jobs that fire on Slack, email or webhooks	Written to a notes file	Set the trigger up again in Hermes
Saved skills and procedures	Yes	Spot-check a couple
What the Bot remembers about your business	Yes	Remove anything out of date
The Bot's job description and rules	Yes	Review the wording
Connected apps with a remote MCP address	Yes	Log in again
Other connected apps and every password	No	Logins stay in Grok Bot

The pattern is simple: knowledge and schedules move, logins don't.

Scheduled jobs also keep their exact timing, time zone and the skills they use, so a report that went out at eight in the morning still goes out at eight.

For most small teams that's the right way round.

Three Real Business Setups And How Each One Moves

A local shop with one helper Bot

Say the owner of a bike shop has one Bot that writes a morning stock note and remembers supplier quirks.

That's one export, one import, and one scheduled job to switch on.

The memory about suppliers lands in the Hermes memory file, where the owner can read and edit it directly.

A service firm with an inbox Bot and a reporting Bot

An accounting practice might run one Bot for client email and another for month-end reports.

The docs say to import each Bot into its own profile, using hermes -p <profile>.

So the practice ends up with an inbox profile and a reporting profile, each with its own memory and schedules.

The inbox Bot's email trigger is an event routine, so that one gets rebuilt by hand from the notes file.

An agency with a Bot per client

An agency running a Bot for each client gets the cleanest result of all.

Each client becomes its own Hermes profile, so one client's memory never mixes with another's.

You can move your quietest client first and keep the busy ones in Grok Bot until the process feels routine.

It also makes handover easier later, because a whole profile can be exported from the Hermes Desktop app as one file with the API keys stripped out.

🔥 Want the setup trainings for a Bot-per-client agency? The AI Profit Boardroom gives you step-by-step video trainings, the installable Agent OS with Hermes inside, four coaching calls a week and 3,400+ members running agents for their own businesses. → Join the AI Profit Boardroom

Five Questions To Answer Before Anyone Types A Command

Spend ten minutes on these with whoever manages your Bots today.

How many Bots do we run, and who on the team relies on each one?
Which of their routines run on a timer, and which wait for a Slack message, an email or a webhook?
Which apps does each Bot log in to on our behalf?
Which Bots belong together, and which should get a profile of their own?
Where should each daily or weekly report land once it runs from Hermes?

The answers turn into your migration list.

Timed routines are the easy wins.

Triggered routines and app logins are the follow-up work, so they decide how long the move takes.

A single Bot can own up to 50 routines, according to the Grok Bot docs, so count them before you promise anyone a finish date.

If the Grok Bot desktop app is installed on the computer doing the move, Hermes reads the app's local cache to list your Bots and the routine names from recent chats.

It uses that list to warn you when a Bot leaves a routine out of its export, which is a useful safety net for busy teams.

Which Plan Do You Need On Each Side?

You need Grok Bot access to run the export, because each Bot writes its own file.

Per the X subscription docs, Premium, Super and Ultra include Grok Bot, and Plus doesn't.

On the Hermes side, the importer is the official agent-importers plugin from Nous Research.

Hermes installs it for you when you run the migrate command.

The Risks To Plan Around

The biggest one is jobs running twice.

Imported scheduled jobs arrive switched off for exactly that reason, because the Grok version keeps running until you pause it.

Tell whoever runs the move to pause the routine in Grok Bot first, then switch on the Hermes copy.

The second risk is a rushed delete.

The Grok Bot routines docs say deleting a routine can't be undone, so pause instead and delete later.

The third is expecting logins to carry over.

They don't, and an export that contains anything that looks like a password or key is refused outright.

Plan a short session to reconnect the apps each Bot needs.

How Much Of Your Time It Takes

I won't put a number on it, because it depends on how many Bots and routines you have.

What I can say is where the time goes.

The export itself is a paste and a download per Bot.

The import is one command per Bot, with a preview first.

The real work is the follow-up: switching on schedules one by one, reconnecting apps, and rebuilding event triggers.

A shop with one timed Bot has very little follow-up.

A firm with many Slack- and email-triggered routines has more, and should book time for it.

A Safe Rollout Plan For A Small Team

Pick the one Bot your business would miss least if it stopped for a day.
Export it, import it into its own profile, and read the preview together.
Pause its routines in Grok Bot and switch on the Hermes copies.
Run it for a week and compare the results with what the Grok version produced.
Move the next Bot only when the first one is boring.

That last step is the one owners skip.

Boring is the goal.

A boring week means the schedule fired on time, the memory was right and nobody on the team had to chase a missing report.

Once that's true, the second Bot takes a fraction of the thinking, because the order of operations is already written down.

📞 Not sure which Bot your business should move first? Book a free SEO strategy session and we'll look at your Bots, your routines and the order that keeps your team working. → Book a free call with my team

What Changes For Your Staff After The Move

Your team chats with Hermes instead of the Grok Bot app for anything you've moved.

Scheduled reports keep their timing and time zone, because the import copies both.

Where a report lands is a choice you make again: Hermes keeps job output in Hermes until someone points it at Telegram, Slack, Discord or another channel.

Model choice also changes hands.

The Grok Bot FAQ says it picks the model for each task, with no picker.

In Hermes, you pick the model per profile, which lets you match a cheaper or stronger model to each job.

Who Should Hold Off

Teams whose Bots are mostly Slack or webhook triggers should wait until someone has time to rebuild those triggers.

Teams that rely on shared Bots across many staff should plan the profile layout first, per the Bots docs on how they share and organise Bots today.

And anyone who just wants things to keep working with no change can simply stay; the export never breaks anything on the Grok Bot side.

If You've Also Used Claude Code Or Cursor

The same plugin imports those setups, and it can keep them in sync over time.

I wrote that up separately in how to use Hermes import agent, so this guide sticks to the Grok Bot move.

Grok exports are one-off files, so they aren't part of that sync.

Updating Hermes Before You Start

The v0.22.6 release is the one that added the Grok Bot move.

Whoever runs your Hermes install updates with hermes update.

If your team only uses the Desktop app from the installer, note that installer builds get this with the next bundled release, so run the move from the command line.

For hands-on help with the bigger picture, join the AI Profit Boardroom.

Also On Our Network

FAQ: Should Your Business Migrate Grok Bot To Hermes? What Moves, What Your Team Redoes, And Where To Start

Will moving to Hermes break our current Grok Bot assistants?

No. The export only asks each Bot to write a file, and nothing in Grok Bot changes. Your Bots keep working until you pause them.

Do our app logins and passwords come across?

No. Credentials are never imported, and an export carrying credential-looking keys is refused. Your team signs in to apps again in Hermes.

Which Grok Bot plans can run the export?

Any plan that includes Grok Bot. The X subscription docs list Premium, Super and Ultra as including it, and Plus as not.

Can an agency keep each client separate after the move?

Yes. Import each client Bot into its own Hermes profile with hermes -p, and each profile keeps its own memory, skills and scheduled jobs.

Do we have to move every Bot at once?

No. Each Bot exports and imports on its own, so you can move one, run it for a while, and leave the rest in Grok Bot.

📺 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 least critical Bot, move it this week, and if you want a plan for the rest of your business, book a free strategy session and we will map how to migrate Grok Bot to Hermes with you.