Migration to Resonant Mind

Ready to upgrade? This page covers the migration path from Mind Cloud to Resonant Mind. For the full detailed guide, see the Resonant Mind migration docs.

Quick Summary

1. Deploy Resonant Mind — fresh instance alongside Mind Cloud
2. Export Mind Cloud data — npx wrangler d1 export ai-mind --output=backup.sql
3. Import to Resonant Mind — load the data into your new D1 or Postgres instance
4. Revectorize — regenerate embeddings (Gemini vs Workers AI BGE)
5. Update MCP config — point your client to the new endpoint
6. Test — verify with mind_orient and searches
7. Decommission Mind Cloud — when you’re confident everything transferred

What You Keep

All your data transfers: entities, observations, relations, journals, images, identity graph, threads, and context. The schema is compatible — it’s the same cognitive architecture, evolved.

What Changes

• Embeddings — new vectors from Gemini Embedding 2 (multimodal, higher quality)
• mind_spark — merged into mind_surface with mode spark
• Security — hardened auth, SQL injection protection, timing-safe HMAC

Can I Run Both?

Yes. Keep Mind Cloud running during migration. Test Resonant Mind in parallel. Switch your MCP config when ready. No downtime required.

See the full migration guide for step-by-step instructions.