To migrate Grok Bot to Hermes, run hermes migrate grok-bot in Hermes Agent, paste the message it prints into each Bot's chat, save the JSON file the Bot writes, and run the import. Your routines, skills, memories and the Bot's role come over. Routines arrive paused, so nothing runs twice.
📺 Watch: Hermes Bot Mode DESTROYS Grok Bot? (FREE!)
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
Nous Research shipped this in Hermes Agent v0.22.6, published on 2 November 2026. The release notes list "hermes migrate and setup moving Grok Bot and OpenBot users over". The same day, the official agent-importers plugin got version 1.2.0 with a new command, hermes import-agent grok-bot, and a 1.2.1 fix release a few hours later.
This guide covers every step, the full mapping table, and what stays behind in Grok Bot.
Why you migrate Grok Bot to Hermes with an export prompt
Grok Bot keeps your Bots, routines and skills in its cloud account. The Hermes docs point out that it has no export button. So each Bot exports itself.
Hermes solves that with a prompt. When you run the migrate command with no export file yet, Hermes prints a message for you to paste into a Bot's chat. The Bot reads its own setup and writes it out as JSON. Per the docs, it does this "without changing anything" on the Grok side.
The agent-importers commits add a few guard rails to that prompt. The Bot is told to list what it could not read and never guess. Long exports can be split over several code blocks, and Hermes merges them per Bot. Curly quotes and trailing commas from copying get repaired. If an export looks cut off, Hermes says so.
Want the full playbook for moving your whole AI stack into one agent setup? The AI Profit Boardroom has the step-by-step training, templates and weekly calls for $69/mo.
Step by step: migrate Grok Bot to Hermes
- Update Hermes. CLI users run hermes update. Docker and Hermes Cloud use the nousresearch/hermes-agent:stable image. The Microsoft Store app updates through the Store. The Desktop app from the .exe or .dmg installer gets it with the next bundled release.
- Start the migration. Run hermes migrate grok-bot. If the agent-importers plugin is missing, Hermes installs it from the catalog first. You can also run hermes import-agent grok-bot once the plugin is installed.
- Copy the export prompt. With no export found, Hermes prints the message to paste into a Bot's chat.
- Let the Bot export itself. The Bot writes grok-bot-export.json, or replies with one JSON block. Per the 1.2.1 commits, it names the file grok-bot-export-<name>.json and saves it in Downloads when it can write to your computer, so several Bots' exports don't collide.
- Bring the export back. Files saved in Downloads as grok-bot-export-something are found without any flag. You can also paste the reply in the same run: pressing Enter reads your clipboard. For a file elsewhere, run hermes import-agent grok-bot --source path-to-file.
- Review the plan. Hermes prints a per-item plan before anything is written. Confirm it.
- Turn the routine off in Grok Bot, then resume it in Hermes. Run hermes cron resume with the job id the import prints.
- Repeat for each Bot.
Fresh install? You may not need step 2. On first run, hermes setup checks for the Grok Bot desktop app, or a grok-bot-export file in Downloads, and asks if you want to import it.
Migrate Grok Bot to Hermes mapping table
This is how each Grok Bot item lands in Hermes, from the Nous Research import docs.
| Grok Bot | Lands in Hermes as | Notes |
|---|---|---|
| Routine on a schedule | Cron job named Bot: routine | Same schedule, time zone and skills, created paused |
| Routine on an event (Slack, GitHub, email, webhook) | A note in grok-bot-import/bot-event-routines.md | Instruction and trigger saved for you to rebuild |
| Skills | skills/grok-bot-imports/name/ | Two skills whose names clash both stay, with a -2 suffix |
| What the Bot remembers | memories/MEMORY.md | Deduplicated against existing entries |
| Facts about you | memories/USER.md | Same dedupe rules |
| The Bot's role | SOUL.md | Only while SOUL.md still holds the Hermes default, else memory entries |
| Apps with a remote MCP URL | mcp_servers in config.yaml | Existing servers count as conflicts and are skipped |
| Credential-looking keys | Not imported | The export is refused; token-shaped text is redacted |
Grok Bot's own docs describe a routine as something that tells one Bot when to run a workflow, on a schedule or when something happens, such as a Slack message, a GitHub event, an email or a webhook. Scheduled ones map straight to Hermes cron. Event ones need you to rebuild the trigger, which is why Hermes saves them as notes.
📺 Watch: Grok Bot DESTROYS Hermes Agent?
What stays behind when you migrate Grok Bot to Hermes
- Chats. Chat history is not in the Grok Bot mapping. Your conversations stay in Grok Bot.
- API keys and logins. The import docs say credentials are never imported. An export carrying credential-looking keys is refused, and token-shaped text is redacted. Add provider keys with hermes setup or in the .env file in your Hermes home.
- Event triggers. They arrive as notes, not live jobs.
- Anything the Bot could not read. The export prompt tells the Bot to list it instead of guessing.
One more safety check from the 1.2.1 commits: Hermes compares the export against the Grok Bot desktop app's local cache. That cache holds the Bot roster and recent chats that name routines a Bot created. After an import, Hermes names Bots no export covered and routines a Bot left out. The commit notes say login files beside that cache are never opened.
📺 Watch: 20 NEW Hermes Skills Just Changed Everything!
Migrate Grok Bot to Hermes flags: --dry-run, --bot, --activate-routines
The hermes migrate command takes these options for Grok Bot:
- --dry-run previews the plan and writes nothing.
- --bot name imports only the Bot you name. An unmatched name imports nothing.
- --activate-routines creates the cron jobs live instead of paused. Only use it once the Grok copy is off.
- --source points at an export file. A dash reads a pasted reply from stdin.
- --overwrite replaces skills or MCP servers that already exist.
- -y skips the confirmation prompt. In non-interactive sessions, Hermes stops at the preview without it.
After the import, point a job's output somewhere with hermes cron edit plus the job id and --deliver telegram. Before hermes migrate edits config.yaml, Hermes saves a point-in-time copy under backups/config in your Hermes home.
Per-Bot and per-profile imports when you migrate Grok Bot to Hermes
Run the import once per Bot. Each one can go into its own Hermes profile, so your research Bot and your support Bot keep separate memory, skills and cron jobs. Use hermes -p research migrate grok-bot style commands with your profile name.
This is the same pattern as the Hermes multiple profiles setup. If you came from OpenClaw too, the migrate OpenClaw to Hermes guide covers that import, and the hermes import-agent page covers Claude Code, Codex and Cursor.
Need help mapping your Bots to profiles and cron jobs for your business? Book a free AI strategy session and we will plan it with you.
After you migrate Grok Bot to Hermes: next steps
Check the cron list, resume each job, and test one skill by name. Then rebuild event routines from the notes file using Hermes hooks or webhooks.
If you are still weighing the switch, read Grok Bot vs Hermes. For a refresher on how routines work on the Grok side, see Grok Bot routines. Picking a model for the imported jobs? Julian's own model testing lives at Goldie Bench. To run everything from one place, the Agent OS guide shows how the pieces fit. Moving OpenBot instead? The same release added hermes migrate openbot.
Want this done with you, not just read about? Get a free AI strategy session with the team.
Migrate Grok Bot to Hermes FAQ
Does migrating delete anything in Grok Bot?
No. The docs say the Bot writes its export without changing anything. Your Bots keep running until you turn routines off yourself.
Why are my routines paused after the import?
So they don't run twice while the Grok copy is still on. Turn the routine off in Grok Bot, then run hermes cron resume with the job id, or import with --activate-routines.
Do my Grok Bot chats come over?
No. The mapping covers routines, skills, memories, the Bot's role and apps with a remote MCP URL. Chats stay in Grok Bot.
Which Hermes version do I need?
Hermes Agent v0.22.6, released 2 November 2026, with agent-importers 1.2.1, the current release from the same day. hermes migrate grok-bot installs the plugin for you when it is missing.
Ready to run Hermes, imported Bots and all, as a real system for your business? Join the AI Profit Boardroom, or book a free AI strategy session to map out your setup.
