Bring every memory with you.

Reused when they’re compatible with the destination. Importing straight into a Studio database always works regardless of embeddings, because Axonio’s engine embeds content itself, the same as anything created directly in Studio. Importing into a raw vector collection instead requires the source’s embeddings to already match that collection’s dimensions.

Not necessarily. Where a provider has its own export (mem0’s dashboard, for one), the wizard points you to it directly so you can download a file and skip sharing a key entirely. When a live connection is the only option, or simply the one you prefer, a Postgres connection string or API key is encrypted at rest before it’s stored, and a connection is tested before it’s ever saved. You can revoke or delete a saved connection at any time.

Export it to JSON, NDJSON, or CSV and use the file import path. It covers any provider that can produce a file, with the same field-mapping and preview steps as every other source.

Progress is checkpointed after every batch, so retrying an import resumes from where it stopped instead of starting over and re-writing records that already landed.