Move from Mem0 to Axonio.
Every memory for each user ID through Mem0’s paginated memories API, including text, metadata and timestamps. Map it once, review a sample, and start. Your agents keep everything they knew, and gain memory they can branch.
- A Mem0 API key
- The user IDs whose memories you want to bring over
Export from Mem0, upload the file.
- 01In the Mem0 dashboard, open Project settings → Memory Exports.
- 02Download the export as JSON.
- 03In Axonio, open Imports → File and upload it. The Mem0 shape is recognised automatically.
Use the live Mem0 connector.
- 01In the Axonio dashboard, open Imports and choose Mem0.
- 02Paste your Mem0 API key. It is encrypted at rest and only used for this import.
- 03List the user IDs to import. Each becomes an end-user tag, so multi-tenant agents keep their separation.
- 04Review the field mapping, then start. Memories are re-embedded and linked into the knowledge graph as they land.
What you get that Mem0 doesn’t give you.
Version what agents know
Relations, not just vectors
MIT core, run it anywhere
Migration questions.
Do I lose my Mem0 embeddings?
No. Existing vectors are kept when their dimensions match your Axonio database; otherwise content is re-embedded on import so search quality is consistent.
Is anything written before I confirm?
No. You see a live sample of what will be imported and the field mapping first. Nothing is written until you start the job.
What happens to my credentials?
Keys and connection strings are encrypted at rest and used only by the import job. The file importer needs no credentials at all.
Can I run both side by side while I switch?
Yes. Import a snapshot, point one agent at Axonio, and compare. Re-running an import is safe; it reports what was imported and what was skipped.