Today News

Migrate from OpenClaw

Migrate from OpenClaw

hermes claw migrate imports your OpenClaw (or legacy Clawdbot/Moldbot) setup into Hermes. This guide covers exactly what gets migrated, the config key mappings, and what to verify after migration.

tip

If your OpenClaw setup was multi-provider, hermes setup --portal collapses it to one OAuth — 300+ models plus the Tool Gateway in a single login. See Nous Portal.

Quick start

# Preview then migrate (always shows a preview first, then asks to confirm)
hermes claw migrate

# Preview only, no changes
hermes claw migrate --dry-run

# Full migration including API keys, skip confirmation
hermes claw migrate --preset full --migrate-secrets --yes

The migration always shows a full preview of what will be imported before making any changes. Review the list, then confirm to proceed.

Reads from ~/.openclaw/ by default. Legacy ~/.clawdbot/ or ~/.moltbot/ directories are detected automatically. Same for legacy config filenames (clawdbot.json, moltbot.json).

Options

OptionDescription
--dry-runPreview only — stop after showing what would be migrated.
--preset <name>full (all compatible settings) or user-data (excludes infrastructure config). Neither preset imports secrets by default — pass --migrate-secrets explicitly.
--overwriteOverwrite existing Hermes files on conflicts (default: refuse to apply when the plan has conflicts).
--migrate-secretsInclude API keys. Required even under --preset full — no preset imports secrets silently.
--no-backupSkip the pre-migration zip snapshot of ~/.hermes/ (by default a single restore-point archive is written before apply, under ~/.hermes/backups/pre-migration-*.zip; restorable with hermes import).
--source <path>Custom OpenClaw directory.
--workspace-target <path>Where to place AGENTS.md.
--skill-conflict <mode>skip (default), overwrite, or rename.
--yesSkip the confirmation prompt after preview.

What gets migrated

Persona, memory, and instructions

WhatOpenClaw sourceHermes destinationNotes
Personaworkspace/SOUL.md~/.hermes/SOUL.mdDirect copy
Workspace instructionsworkspace/AGENTS.mdAGENTS.md in --workspace-targetRequires --workspace-target flag
Long-term memoryworkspace/MEMORY.md~/.hermes/memories/MEMORY.mdParsed into entries, merged with existing, deduped. Uses § delimiter.
User profileworkspace/USER.md~/.hermes/memories/USER.mdSame entry-merge logic as memory.
Daily memory filesworkspace/memory/*.md~/.hermes/memories/MEMORY.mdAll daily files merged into main memory.

Workspace files are also checked at workspace.default/ and workspace-main/ as fallback paths (OpenClaw renamed workspace/ to workspace-main/ in recent versions, and uses workspace-{agentId} for multi-agent setups).

Skills (4 sources)

SourceOpenClaw locationHermes destination
Workspace skillsworkspace/skills/~/.hermes/skills/openclaw-imports/
Managed/shared skills~/.openclaw/skills/~/.hermes/skills/openclaw-imports/
Personal cross-project~/.agents/skills/~/.hermes/skills/openclaw-imports/
Project-level sharedworkspace/.agents/skills/~/.hermes/skills/openclaw-imports/

Skill conflicts are handled by --skill-conflict: skip leaves the existing Hermes skill, overwrite replaces it, rename creates a -imported copy.

Model and provider configuration

WhatOpenClaw config pathHermes destinationNotes
Default modelagents.defaults.modelconfig.yamlmodelCan be a string or {primary, fallbacks} object
Custom providersmodels.providers.*config.yamlcustom_providersMaps baseUrl, apiType/api — handles both short ("openai", "anthropic") and hyphenated ("openai-completions", "anthropic-messages", "google-generative-ai") values
Provider API keysmodels.providers.*.apiKey~/.hermes/.envRequires --migrate-secrets. See API key resolution below.

Agent behavior

WhatOpenClaw config pathHermes config pathMapping
Max turns<co…

     
                    WhatsApp Channel                             Join Now            
   
                    Telegram Channel                             Join Now            
   
                    Instagram follow us                             Join Now            

Written by

View all posts

Leave a Reply

Your email address will not be published. Required fields are marked *

Loading...