New to Synap’s model first? Read What is Synap? and Memory scopes before migrating — the migration is mostly a mapping exercise, and it goes faster once the scope model is clear.
Start here
How migration works
The method every migration follows: map scopes, configure the instance, backfill, pilot, verify, cut over. Read this once, then pick your platform.
Memory scopes
The client / customer / user model your source data has to map onto.
Pick your source platform
From Mem0
User-scoped memory bag of untyped strings. Straightforward user-scope mapping.
From Zep
Sessions, Users, and automatic facts. Maps onto conversations plus typed context.
From Letta (MemGPT)
Agent-coupled core / archival memory. A re-architecture, not a drop-in.
From Supermemory
Documents and memories under flat container tags. Ships with a ready-to-run script.
More platforms
We’re building careful, first-class guides for the memory layers customers ask about most. The following are on the roadmap:
If your source isn’t listed, the shared method still applies — the only platform-specific part is the export and the concept mapping. Email [email protected] with what you’re using and we’ll prioritise a guide.
What every migration gains
- Typed extractions — facts, preferences, episodes, emotions, and temporal events as separate lists, not one flat pool of strings.
- Three scopes — client, customer, and user, with roll-up, so shared knowledge is stored once instead of copied per user.
- Entity resolution — the same person or product recognised across conversations.
- Context compaction — long histories stay usable without you managing the window.