Migrate from Self-Hosted to Platform

Overview

Transitioning from a self-hosted sovseal deployment to the managed sovseal Platform shifts infrastructure maintenance, database hosting, and scaling overhead to our secure cloud. The managed platform unlocks advanced features such as real-time webhooks, organizational collaboration, and AI-powered reranking.

1. Import Memories into the Platform

If your self-hosted setup uses Qdrant as the vector database, you can run our migration utility script to copy your vector collections directly into the managed cloud:

curl -fsSL https://raw.githubusercontent.com/sovseal/core/main/scripts/oss-to-platform-migrate.sh | bash

Note: For self-hosted pgvector or custom database stores, contact support to request a customized migration script.

2. Update Client SDK Configuration

Replace the self-hosted local client initializations with the managed MemoryClient.

Python Client SDK

# Self-Hosted (Old)
from mem0 import Memory
config = {
    "vector_store": {"provider": "qdrant", "config": {"host": "localhost"}},
    "llm": {"provider": "openai", "config": {"model": "gpt-4"}}
}
m = Memory.from_config(config)

# Platform (New)
from mem0 import MemoryClient
client = MemoryClient(api_key="sov_live_...")

TypeScript Client SDK

// Self-Hosted (Old)
const client = new Memory({
  vectorStore: { provider: "qdrant" }
});

// Platform (New)
const client = new MemoryClient({
  apiKey: "sov_live_..."
});

3. Nest Filters in Queries (Critical Change)

When upgrading to the Platform, filter parameters must be nested within a filters object inside search and recall operations:

Search Examples

Python SDK

# Self-Hosted (Old)
results = m.search("What are my location preferences?", user_id="alice")

# Platform (New)
results = client.search("What are my location preferences?", filters={"user_id": "alice"})

TypeScript SDK

// Self-Hosted (Old)
const results = await client.search("preferences", { user_id: "alice" });

// Platform (New)
const results = await client.search("preferences", {
  filters: { userId: "alice" }
});

Rollback Plan

If you encounter integration issues during migration, revert to your self-hosted environment by reverting the client import:

1. Restore code references from MemoryClient to Memory.
2. Re-enable your local configuration parameters mapping your self-hosted vector database.
3. Ensure your local Docker database services are active and reachable.