Migrate Grok Bot To Hermes: Move Every Bot In 6 Steps (2026)

To migrate Grok Bot to Hermes, you run one command, paste one prompt into each Bot, and import the JSON file each Bot writes back.

That's the whole loop, and it shipped with Hermes v0.22.6 on 2 November 2026.

Below is the exact order I'd run it in, with the flags, the file paths and the switch-over step most people get wrong.

If you'd rather have my team plan the move with you, book a free SEO strategy session and bring your list of Bots.

The Six Commands You'll Actually Type

Here's the full run on one screen before we go step by step.

hermes update                                   # get v0.22.6
hermes migrate grok-bot                         # installs agent-importers if missing, prints the export prompt
# paste the prompt into each Bot, save grok-bot-export.json to ~/Downloads
hermes import-agent grok-bot --dry-run          # preview only
hermes -p research import-agent grok-bot --source ~/Downloads/grok-bot-export.json
hermes cron resume <id>                          # after you pause the routine in Grok Bot

Everything else on this page explains what each line does and what to check before the next one.

Step 1: Update Hermes To v0.22.6

The v0.22.6 release notes list hermes migrate and setup moving Grok Bot and OpenBot users over.

On the CLI, run hermes update or re-run the installer one-liner.

Docker users pull nousresearch/hermes-agent:stable, and the Microsoft Store app updates through the Store.

The .exe and .dmg Desktop installs don't change in this release; they pick it up with the next bundled release.

So if you live in the Desktop app, run the migration from a terminal with the updated CLI.

Step 2: Let Hermes Install The Importer For You

The importer isn't in Hermes core any more.

It's the official agent-importers plugin, maintained by Nous Research.

You don't need to install it by hand, because hermes migrate grok-bot installs it when it's missing and then runs hermes import-agent grok-bot.

If you prefer to see each piece, install it yourself first with hermes plugins install agent-importers.

Install it once per profile, which matters in Step 5.

On a brand-new machine, hermes setup does this for you: it looks for the Grok Bot desktop app, or a grok-bot-export* file in ~/Downloads, before anything else.

When it finds one, it asks whether to import, installs the plugin and runs the same preview.

Step 3: Get The Export Prompt

There's no export button: your Bots, routines and skills all live inside Grok Bot's cloud account.

So each Bot exports itself.

Run hermes migrate grok-bot with no export file around and Hermes prints a message for you to paste.

It also saves that message as grok-bot-import/export-prompt.txt in your Hermes home, so you can copy it again for the next Bot.

If the Grok Bot desktop app is on the same computer, the importer reads its local cache to list the Bots you should export.

That cache gives it Bot names and routine names from recent chats, and it never touches the app's login files.

The app doesn't store schedules, skills or memory locally, which is exactly why the Bot has to export itself.

Step 4: Paste The Prompt Into Each Bot

Open a Bot's chat in Grok Bot and paste the message.

The Bot writes grok-bot-export.json and attaches it, or it replies with one JSON code block.

Nothing in Grok Bot changes while it does this.

Download the attachment into ~/Downloads, and leave the filename starting with grok-bot-export.

If the Bot replied in chat instead, copy the whole reply into a text file, or pipe it straight in from your clipboard:

pbpaste | hermes import-agent grok-bot --source - -y

The - tells --source to read stdin, and -y skips the confirmation prompt, so only use it once you've seen a preview.

A long export can arrive in several parts, as files or code blocks.

Hermes merges the parts per Bot, and a part you send twice adds nothing.

🔥 Moving a whole roster of Bots this week? Inside the AI Profit Boardroom you get step-by-step video trainings on Hermes, the installable Agent OS, four coaching calls a week and 3,400+ members comparing how they set up their profiles. → Join the AI Profit Boardroom

Step 5: One Bot, One Profile

This is the decision that keeps a migrated setup tidy.

The docs say to run the import once per Bot, into the profile that should own that Bot's work.

So a research Bot and an inbox Bot become two Hermes profiles, each with its own memory, skills and cron jobs.

hermes -p research import-agent grok-bot --source ~/Downloads/grok-bot-export.json
hermes -p inbox    import-agent grok-bot --source ~/Downloads/grok-bot-export-inbox.json

If one export file holds several Bots, pick them with --bot <name>, and repeat the flag for more than one.

Point --source at a folder and it takes every export in it.

Leave out -p and the import goes into your active profile.

Step 6: Preview, Then Import

Every run prints a per-item plan before it writes anything.

Add --dry-run and nothing touches disk at all.

In a non-interactive session the command stops at the preview unless you pass --yes.

Read the plan for three things: the cron jobs it will create, the skills it will add and any items it lists as conflicts.

A skill or MCP server that already exists under the same name is skipped unless you pass --overwrite.

Before memory entries are merged, the previous MEMORY.md is backed up as MEMORY.md.bak.<timestamp>.

Where Each Piece Of Your Bot Lands

Here's the map from the import guide, laid out as the folders you'll open afterwards.

What you had in Grok Bot	Path or setting in Hermes	What to do next
Scheduled routine	Cron job named `<Bot>: <routine>`, paused	Resume it after the switch-over
Event routine (Slack, GitHub, Linear, Sentry, PagerDuty, email, webhook)	`grok-bot-import/<bot>-event-routines.md`	Rebuild the trigger by hand
Skills	`skills/grok-bot-imports/<name>/SKILL.md`	Open one and test it
What the Bot remembers	`memories/MEMORY.md`	Skim for stale entries
Facts about you	`memories/USER.md`	Check names and preferences
Role and lasting rules	`SOUL.md` if it still holds the default, else memory entries	Edit the persona if needed
Apps with a remote MCP URL	`mcp_servers` in `config.yaml`	Sign in again in Hermes
Other connected apps	Listed in the report	Logins stay in Grok Bot

Scheduled routines keep the same cron expression, time zone and skills.

Event routines aren't scheduled at all; their full instruction and trigger are written out so you can rebuild them.

The Switch-Over: Pause First, Then Resume

Imported routines arrive paused on purpose.

The Grok copy keeps running until you turn it off, and two live copies would do the same work twice.

In Grok Bot, open the Bot's details and use the switch on the routine row, or right-click the routine and choose Pause, as the routines docs describe.

On the phone, turn off Active on the routine.

I'd pause rather than delete, because deleting a routine in Grok Bot can't be undone.

Then resume the Hermes copy with the id the import printed:

hermes cron resume <id>
hermes cron edit <id> --deliver telegram

Cron output stays inside Hermes until you pick a destination, and --deliver also takes discord, slack and the other platforms.

If you're happy to run both briefly, --activate-routines creates the jobs running instead, but then you own the double runs.

The cron docs cover schedules and delivery in more depth.

📞 Want a second pair of eyes on the switch-over plan? Book a free SEO strategy session and my team will walk through which routines to move first and which to leave where they are. → Book your free session

What Stays Behind In Grok Bot

Credentials never come over.

An export that carries credential-looking keys is refused whole, and token-shaped strings inside text become [redacted].

Apps without a remote MCP URL are only listed in the report, and their logins stay in Grok Bot.

Apps that do have one land in config.yaml, and you sign in to them again in Hermes.

Add new secrets to the profile's .env, or run hermes setup for model providers.

The Model Choice Moves To You

Grok Bot picks the backend model for each task and has no model picker, per its FAQ.

Hermes works the other way round: you choose the provider and model yourself with hermes model.

So budget five minutes after the first import to pick a main model for each profile.

A research profile and an inbox profile don't need the same one.

Side tasks such as compression and session titles use your main model by default, and you can point them at a cheaper model later in config.yaml.

Re-Runs, Missed Routines And Sync

Re-running the import skips routines whose cron job already exists, so a second pass is safe.

When the desktop app is installed, the importer uses its cache to flag a routine a Bot created but left out of its export.

If that happens, paste the prompt again and ask the Bot to include that routine by name.

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

Sync is for sources that live on disk, such as Claude Code or Cursor folders.

Common Problems And Fast Fixes

The import didn't find the file. Check it sits in ~/Downloads with a name starting grok-bot-export, or pass --source with the full path.
The run stopped after the preview. You're in a non-interactive shell, so add --yes once the plan looks right.
A skill shows as a conflict. One with that name already exists; rename yours or rerun with --overwrite.
An MCP app won't connect. It came over without its login; sign in again in Hermes.
The export was refused. It held credential-looking keys; ask the Bot for a fresh export without them.

Coming From Claude Code Or Codex As Well?

The same plugin handles those too, with folder-based imports and a sync mode.

I covered that side in the Hermes import agent walkthrough, so this page stays on the Grok Bot path only.

Run the Grok Bot import first, then layer the folder imports on top of the same profiles.

My Order Of Operations For A Full Roster

Update Hermes and run hermes migrate grok-bot once to get the prompt.
List every Bot, using the desktop cache list if the app is installed.
Export one Bot, dry-run it into its own profile and check the plan.
Import it, open two skills and read the new MEMORY.md.
Pause one routine in Grok Bot, resume its Hermes copy, and watch the next run.
Repeat Bot by Bot until the roster is done.

Doing one Bot end to end before the rest catches profile mistakes while they're cheap to fix.

It also gives you one clean before-and-after to compare: the same routine, the same schedule, now running from a cron job you can read and edit.

Keep the Grok Bot copy paused, not deleted, until the Hermes job has run cleanly a few times.

If you want the trainings and the Agent OS that wraps all of this, join the AI Profit Boardroom.

Also On Our Network

FAQ: Migrate Grok Bot To Hermes

Which command starts the move from Grok Bot?

Run hermes migrate grok-bot. It installs the agent-importers plugin if it is missing, then runs hermes import-agent grok-bot, which prints the export prompt when no export file exists yet.

Where should I save the export file?

Save it in ~/Downloads with a name starting grok-bot-export and Hermes finds it without --source. Anywhere else, pass --source with the path.

Why are my imported routines paused?

So they do not run twice while the Grok Bot copy is still on. Pause the routine in Grok Bot, then run hermes cron resume with the id the import printed.

Can I import several Bots into one profile?

You can, but the docs recommend one import per Bot into the profile that should own its work, using hermes -p <profile>.

Does the import change anything in Grok Bot?

No. The Bot only writes an export file or a JSON reply, and nothing in Grok Bot changes.

📺 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

Export one Bot today, dry-run it into its own profile, and if you want my team to map the rest, book a free strategy session before you migrate Grok Bot to Hermes.