Skip to content

Move from MongoDB to Axonio.

Documents from the collection. Axonio samples a few to find the text, embedding and tag fields. Map it once, review a sample, and start. Your agents keep everything they knew, and gain memory they can branch.

Start the import
You’ll need
  • A connection string
  • Database and collection names
Steps

Import from MongoDB.

  1. 01Open Imports and choose MongoDB.
  2. 02Paste a read-only connection string.
  3. 03Confirm the detected content, embedding and tag fields.
  4. 04Start the import.

What you get that MongoDB doesn’t give you.

Version what agents know

Fork memory to test a policy, diff it against main, then merge it or throw it away.

Relations, not just vectors

Imported content is linked into a knowledge graph as it lands, so recall can follow entities and time.

MIT core, run it anywhere

Same engine in our cloud, your VPC or on-device. No lock-in on the way out either.
FAQ

Migration questions.

Do I lose my MongoDB 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.

Other sources
Mem0 Zep Pinecone Qdrant Chroma Weaviate Postgres JSON or CSV

Your MongoDB memories, branchable.

Start freeRead the docs