Overview
Myrm provides a complete data migration system that lets you transfer your AI assistant data from other platforms — including memories, skills, API keys, MCP configurations, and workspace rules — with full preview, conflict resolution, and one-click rollback. Supported Sources (14, 11 ready): Hermes, OpenClaw, Pi, Claude Code, Cursor, Codex, ChatGPT, gbrain, Mem0, native JSON, Myrm Archive, AgentMemory — Windsurf, Trae, and MemWeaver are on the roadmap (in development).Migration Wizard (3-Step GUI)
Step 1: Discover
Navigate to Settings → Memory Center → Migration to start the wizard.- Local/Desktop: Click Scan to auto-detect installed AI assistants on your system
- Cloud: Drag and drop a
.zipexport file from your previous assistant
Step 2: Preview (Dry-Run)
Click Preview on any detected source to see exactly what will be imported — without writing anything:- Coverage Matrix: Shows which data categories are ready, need review, or require manual action
- Migration Lanes: Persona → Agent, Facts → Memory, Skills → Review Queue, Keys → Explicit Confirm, MCP → Audit
- Token Economics: Compare token usage before and after migration
- MCP Server Preview: See which MCP tools will be available after import
- Conflict Detection: Highlights items that would overwrite existing data
Step 3: Confirm & Import
Choose a target Agent (or create a new one), then confirm the import:- Secrets are only imported with explicit opt-in (never silently)
- Skills go to a review queue — you approve each before it activates
- A transaction batch ID is generated for every import
- ZIP skill migration uses a stable two-phase error contract (
message + error_code) in both preview and confirm, so UI remediation stays deterministic.
Post-Import Readiness (First Chat Guidance)
After a successful import, Myrm live-resolves readiness before your first message — you are never left guessing why chat feels broken.
Design principles:
- Soft gate — the assistant can still reply; you get guidance, not a hard block
- Issue-aware CTA — each gap links to the exact settings page (
settings_pathSSOT) - Wizard recheck — Migration Result step can re-run readiness before “Start chat”
- Queue anchor — handoff state survives navigation until first chat consumes it
mcp_warning · provider_critical · diagnostic_critical) under parallel wave (≤8 leases, no stopping other pytest) · 65+ unit/integration tests · competitors typically silent-fail or CLI-only with no post-import UX.
Additional readiness checks after Hermes migration may surface voice or MoA advisor overlay setup hints when those capabilities were used in Hermes but are not configured in your Myrm Agent profile — each links to the relevant Settings page without blocking chat.
Hermes Cron Job Import (Paused by Default)
When migrating from Hermes, the wizard can import scheduled jobs fromcron/jobs.json:
Honest boundaries:
- Hermes model fields are not migrated — jobs use the target Agent’s default model
- Kanban boards are not auto-migrated (coverage matrix shows
kanban_not_migrated) - No Chrome MCP E2E sign-off for cron import yet — backend covered by
test_hermes_cron_converter.py7/7 passed (Aug 2026)
claw migrate, OpenClaw, Pi, deer-flow, LobsterAI, CoPaw, jiuwenclaw) offers a GUI migration wizard with cron preview + paused import + rollback.
Pi Migration (5-Lane Mapping)
When migrating from Pi, the wizard auto-scans~/.pi/agent/ and provides five-lane mapping:
Safety guards:
- Unknown session versions (≠ v3) are auto-skipped silently
- Empty messages, invalid JSON, non-dict content blocks are safely skipped
- Pi has no MCP configuration (tech stack difference) — does not affect migration completeness
test_pi_migration.py 25/25 PASS (covering discovery / loading / session parsing / skills / credentials / edge cases — 6 categories, 25 scenarios)
Hermes MoA Reference Import (Wizard Confirm)
When your Hermesconfig.yaml includes a moa block with reference models, the migration wizard can write them into the target Agent’s engine_params.moa_overlay on confirm:
Honest boundaries:
- Only the default Hermes preset’s reference set is imported (multiple presets with different ref pools → create multiple Agent Profiles)
- Hermes aggregator model is not migrated — Myrm primary model absorbs advisor output (by design)
- Provider keys must be configured in Myrm before refs resolve; unresolvable refs are skipped with logging
test_hermes_moa_migrator.py 19/19 + confirm integration path in import archive — part of 30/30 MoA server pytest suite.
Rollback
Every import can be fully reversed:- Go to Settings → Memory Center → Recent Imports
- Click Rollback on any import batch
- Preview what will be undone (rollback dry-run)
- Confirm to restore your previous state
Backup & Remote Sync
Local Backup
Create manual backups of all memories at any time:- Settings → System → Backup → Create Backup
- Stores: all memory types, shared contexts, conversation history
- List, restore, or delete backups as needed
Remote Backup (S3 / WebDAV)
Configure automatic sync to cloud storage:- S3-compatible: Any provider (AWS S3, Cloudflare R2, MinIO, etc.)
- WebDAV: NAS devices, Nextcloud, ownCloud, etc.
New User Onboarding
When you first launch Myrm, the Onboarding Wizard automatically checks for existing AI assistant data on your system. If found, it offers a one-click migration path — so your first conversation already has your personality, memories, and tools. A Discovery Banner also appears in the chat window when external data is detected, providing quick access to the migration wizard.Export
Full Archive Backup & Restore
Export your entire Myrm workspace as a structured archive that preserves all data relationships:- Conversations: Full message history including compaction state (compressed summary), session notes, tool usage stats, and token cost summaries
- Memory: All memory types (episodic, semantic, procedural, preferences, shared context)
- Agent Configurations: Complete Agent profiles (model, prompt, skills, MCP bindings) via JSON round-trip export/import
- Section-Selective Restore: Import the full archive or choose specific sections (conversations only, memory only, etc.)
Cross-Deployment Migration (Local ↔ Cloud)
Myrm uses SQLite as its single data store across all deployment modes. Migrating between Local WebUI, Tauri Desktop, and Cloud-hosted is seamless:- Volume Copy: Simply copy the SQLite database file between deployments — zero data loss, zero format conversion
- Archive Route: Export a full archive from one deployment, restore on another with section selection
Memory Archive Export
Export your Myrm memories as a structured JSON archive (myrm_memory_archive format) that can be imported into another Myrm instance or shared.
Dataset Export
Export conversation data in training-ready formats:- ShareGPT: Standard fine-tuning format
- PII Redaction: Optionally strip personal information
- Quality Filtering: Min turns, min content length, success-only
- Incremental: Export only new data since last export