Skip to main content

Overview

ScopeEffortDowntime
Infrastructure & CodeLow (~30 mins)None (Parallel run possible)
Using Mem0 Open Source with hosted Qdrant? You can migrate your existing memories to Mem0 Platform with a one-line script below.
Why migrate to Platform?
  • Time to Market: Set up in 5 minutes vs 30+ minutes for OSS configuration
  • Enterprise Ready: Audit logs, workspace governance, and dedicated support
  • Advanced Features: Webhooks, memory export, analytics dashboard, custom categories
  • Multi-tenancy: Organizations, projects, and team management out of the box
  • Zero Infrastructure: No vector database, LLM provider, or maintenance overhead
  • Enhanced Search: Reranking, keyword expansion, and advanced filters
  • Production Grade: Auto-scaling, high availability, dedicated support

Plan

  1. Sign up: Create an account on Mem0 Platform.
  2. Get API Key: Navigate to Settings > API Keys and generate a new key.
  3. Review Usage: Identify where you instantiate Memory and where you call search or get_all.

Migrate with Agent Skill

Paste this prompt into your coding agent. It uses a migration skill to produce a plan; once you review and approve it, the agent implements the changes.

Migrate

1. Import Memories Into Platform

If your Mem0 Open Source setup uses hosted Qdrant as the vector store, you can import your existing memories to Mem0 Platform with one command:
This migration script currently supports hosted Qdrant only. Support for local Qdrant, pgvector, and other vector stores is coming soon.
If you are using a different vector store and want to migrate to Platform, please contact Mem0 support and we’ll send you a custom migration script for your setup.

2. Install or Update SDK

Ensure you have the latest version of the SDK, which supports both OSS and Platform clients.

3. Update Initialization

Switch from the local Memory class to the managed MemoryClient.
Open Source (Old)
Platform (New)
Run client.get_all(filters={"user_id": "test_connection"}) to verify your API key works. It should return an empty list or valid results.

4. Update Retrieval Calls (Critical)

Critical Change: Platform uses v2 endpoints that require filtering parameters to be nested inside a filters dictionary.
The limit parameter has been removed in favor of top_k across all SDKs. Update any code using limit= to use top_k= instead.
MethodOpen SourcePlatform
search()m.search(query, user_id="alex")client.search(query, filters={"user_id": "alex"})
get_all()m.get_all(user_id="alex")client.get_all(filters={"user_id": "alex"})
add()m.add(memory, user_id="alex")client.add(memory, user_id="alex")
delete()m.delete(memory_id)client.delete(memory_id)
delete_all()m.delete_all(user_id="alex")client.delete_all(user_id="alex")
Note: add() and delete() methods remain unchanged. The update() method is not available in Platform - use delete + add pattern instead.

Platform-Exclusive Features

The Platform introduces powerful capabilities not available in OSS:
Why it matters: Manage multiple teams and projects with hierarchical access control.
Why it matters: Instantly react to memory changes in your application. Build features like notifications, audit logs, or sync with external systems.
Why it matters: Export your data for compliance, analytics, or migration with custom schemas and filters.
Why it matters: Get better search results with AI-powered reranking and keyword expansion.
Why it matters: Use domain-specific categories instead of generic ones for better organization.
Why it matters: Track all memory operations for audit trails, usage analytics, and debugging.

Summary of Changes

FeatureOpen SourcePlatformAction Required
InitializationMemory.from_config(config)MemoryClient(api_key)Replace config object with API key
Search Methodm.search(query, user_id="x")client.search(query, filters={"user_id": "x"})Move filtering params into filters dict
Get All Methodm.get_all(user_id="x")client.get_all(filters={"user_id": "x"})Move filtering params into filters dict
Add Methodm.add(memory, user_id="x")client.add(memory, user_id="x")No change
Delete Methodm.delete(memory_id)client.delete(memory_id)No change
Delete Allm.delete_all(user_id="x")client.delete_all(user_id="x")No change
Update Methodm.update(memory_id, new_memory)Use delete + add patternReplace with delete then add
ConfigLocal vector store + LLM configManaged cloud infrastructureRemove local config setup

Rollback plan

If you encounter issues, you can revert immediately by switching your import back.
  1. Revert Code: Change MemoryClient back to Memory.
  2. Restore Config: Uncomment your local vector store and LLM configuration.
  3. Verify: Ensure your local vector database is still running and accessible.

Next Steps

Platform Features

API Reference