Docs/Resonant Mind/Migration

Migration from Mind Cloud

If you’re currently using Mind Cloud, this guide covers migrating to Resonant Mind. The upgrade brings Postgres support, Gemini multimodal embeddings, enhanced security, and active development.

What Changes

	Mind Cloud	Resonant Mind
Version	v2.4.0 (maintained)	v3.0.0 (active development)
Storage	D1 + Vectorize only	D1 + Vectorize OR Postgres + pgvector
Embeddings	Workers AI BGE (text-only)	Gemini Embedding 2 (multimodal text + image)
Tools	28	27 (mind_spark removed, functionality merged into mind_surface)
Security	Basic auth	SQL injection fixes, timing-safe HMAC, error sanitization, daemon cooldown
Images	R2 with signed URLs	R2 with WebP conversion + multimodal embeddings

Migration Steps

1. Deploy Resonant Mind

Follow the Getting Started guide to deploy a fresh Resonant Mind instance. You can use a new D1 database or set up Postgres — either works.

2. Export Your Mind Cloud Data

Mind Cloud stores data in D1. Export it using Wrangler:

# Export all tables
npx wrangler d1 export ai-mind --output=mind-cloud-backup.sql

3. Import to Resonant Mind

If using D1 for both:

npx wrangler d1 execute resonant-mind --file=mind-cloud-backup.sql

If migrating to Postgres, you’ll need to transform the SQL. The schema is compatible but the syntax differs (SQLite vs Postgres). The migration SQL file at migrations/postgres.sql in the Resonant Mind repo provides the target schema.

4. Revectorize

This is the important step. Because Resonant Mind uses Gemini embeddings (768d) instead of Workers AI BGE, you need to regenerate all vector embeddings.

The revectorization process is documented in detail in the repo’s migration guide, including scripts that automate the process.

5. Update Your MCP Configuration

Point your MCP client to the new Resonant Mind endpoint:

{
  "mcpServers": {
    "mind": {
      "type": "url",
      "url": "https://resonant-mind.your-subdomain.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_NEW_API_KEY"
      }
    }
  }
}

6. Test

Run mind_orient and mind_ground to verify everything loaded correctly. Search for known entities to confirm vectors are working.

Tool Changes

Most tools are identical. The main difference:

mind_spark (Mind Cloud) is removed. Its functionality — random associative memory surfacing — is now a mode of mind_surface (use mode spark).
All other tools (mind_orient, mind_ground, mind_write, mind_search, etc.) work the same way with the same parameters.

Keeping Mind Cloud Running

You don’t have to migrate immediately. Mind Cloud v2.4.0 is maintained and will continue to work. You can run both in parallel during migration to verify everything transferred correctly.