Switch from Convex
Bring your Convex app and its users. Add SQL when you want it.
One command reads your Convex snapshot: Convex Auth users with their passwords, every table as a live document collection with the same ids, and your file storage.
What moves
Three commands
- 1
Export from Convex
A snapshot of your production deployment, files included.
npx convex export --path snapshot.zip --include-file-storage --prod - 2
Check everything, write nothing
A dry run reads the whole snapshot and lists what would move.
sov import convex --snapshot snapshot.zip --dry-run - 3
Import
Then add a rule per collection and check it with a simulation run.
sov import convex --snapshot snapshot.zip sov sim run
Everything has a place
Questions
Do my users have to reset their passwords?
No. Convex Auth’s password hashes (Lucia scrypt) are checked by Sovaria and upgraded at the first sign-in. OAuth users sign in with the same provider; anonymous users aren’t moved.
What happens to my queries and mutations?
They become SDK calls: reads and live queries on collections, writes and transactions, and Edge Functions for logic that must stay on the server.
What isn’t moved?
Convex components’ tables, scheduled jobs in flight, and Convex Auth’s sessions and tokens. The report lists them.
Start building on Sovaria
A free project takes a minute. Your data stays behind rules from the first request.