Move from Zep to Axonio.
Messages, extracted facts and session summaries for each session you name, via Zep’s session memory API. Map it once, review a sample, and start. Your agents keep everything they knew, and gain memory they can branch.
- A Zep Cloud API key
- The session IDs to import
Zep doesn’t expose an account-wide session listing, so sessions are imported by ID. If your Zep account offers a data export, the file importer accepts it too.
Import from Zep.
- 01Open Imports in the dashboard and choose Zep.
- 02Paste a Zep Cloud API key.
- 03List the session IDs to bring over. Each session is imported as a self-contained unit, with its facts attached.
- 04Review and start. Facts become graph relations; messages become episodic memories.
What you get that Zep doesn’t give you.
Version what agents know
Relations, not just vectors
MIT core, run it anywhere
Migration questions.
Do I lose my Zep 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.