Move from Qdrant to Axonio.
All points in the collection with vectors and payloads, page by page. Named-vector collections are supported. Map it once, review a sample, and start. Your agents keep everything they knew, and gain memory they can branch.
- Your Qdrant URL
- An API key if the cluster requires one
- The collection name
Import from Qdrant.
- 01Open Imports and choose Qdrant.
- 02Enter the cluster URL, API key and collection.
- 03Confirm which payload field holds the text and which hold tags.
- 04Start the import.
What you get that Qdrant doesn’t give you.
Version what agents know
Relations, not just vectors
MIT core, run it anywhere
Migration questions.
Do I lose my Qdrant 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.