Migration
Coming from another agent system? This section helps you transition to the Super Agents architecture.
Why Migrate?
If you’ve been using another Claude-based agent setup, you’ve already proven that LLM-assisted workflows work for you. The Super Agents architecture builds on that foundation with:
| Capability | Typical Setup | Super Agents |
|---|---|---|
| Context management | Manual prompting or single config file | Layered context architecture with auto-refresh |
| Memory | In-session only or basic DB | PARA vault + structured knowledge base |
| Commands | Few or none | Large slash-command library across domains |
| Agents | Generic assistant | Specialized role-based personas |
| Automation | Manual triggers | LaunchAgents + scheduled pipelines |
| Thinking tools | None | Challenge, discovery, planning, and learning tools |
| Multi-domain | Single-purpose | Unified system across all life/work domains |
Migration Paths
From OpenClaw / ClaudeClaw
If you’ve been using the Telegram-based OpenClaw/ClaudeClaw setup (Agent SDK subprocess architecture), see From OpenClaw.
Key changes: Telegram relay becomes optional, SQLite memory converts to vault files, single-purpose bot becomes multi-domain system.
From Scratch
No existing agent system? Start fresh with the From Scratch guide, which walks you through assessment and setup in a recommended order.
From Other Setups
If you’re migrating from a different system (custom GPT workflows, LangChain agents, AutoGPT, etc.), the general approach is:
- Audit what you have — list every workflow, command, and automation
- Map to Super Agents components — which become commands, agents, or skills?
- Migrate memory/context — convert any stored knowledge to vault markdown files
- Set up context loading — create your AGENT_GUIDE.md and /contxt bundles
- Migrate automations — convert scheduled tasks to LaunchAgents
- Verify — run Day 1 Verification to confirm everything works