Switch from Firebase
Bring your Firebase app, keep your users’ passwords.
One command moves Firestore documents (subcollections included), Auth users with their Firebase password hashes, and Storage files, and turns your security rules into a report of Sovaria equivalents.
What moves
Three commands
- 1
Export your users
With the Firebase CLI, plus the password hash parameters from the Firebase console.
firebase auth:export users.json --format=json --project YOUR_PROJECT - 2
Check everything, write nothing
A dry run lists what would move and anything that needs a look.
sov import firebase --service-account sa.json \ --auth-export users.json --hash-config hash.json --rules firestore.rules --dry-run - 3
Import
Then prove access with a simulation run before you point the app at Sovaria.
sov import firebase --service-account sa.json \ --auth-export users.json --hash-config hash.json --rules firestore.rules sov sim run --fail-on critical
Everything has a place
Questions
Do my users need to reset their passwords?
No. Sovaria checks Firebase’s modified scrypt hashes with your project’s parameters, so existing passwords keep working.
Are my security rules applied automatically?
No. You get a report with the Sovaria equivalent of each rule; you add them yourself and check them with simulation.
Can I keep my Firestore code?
The SDK has a Firestore-style API for collections, documents and listeners, so most data code changes only its import and initialisation.
Start building on Sovaria
A free project takes a minute. Your data stays behind rules from the first request.