Plan a Firebase to Supabase move: turn Firestore collections into tables, migrate users, swap SDK calls, and cut over safely.
Move my Firestore data and Firebase users over to Supabase
How it works
- Inventory what you use: Vovy lists your Firestore collections, Firebase Auth sign-in methods, Storage buckets and Cloud Functions, with a card of what maps where.
- Design tables from collections: Firestore documents are flexible; Postgres tables have fixed columns. Vovy samples your documents to design tables and flags inconsistent fields.
- Export and import the data: Vovy exports Firestore with a service account key you create, transforms it, and asks before importing into Supabase.
- Move your users: Vovy exports Firebase Auth users and imports them into Supabase Auth. Supabase's migration tools handle password hashes so users keep their passwords.
- Swap the code and compare: Vovy replaces Firebase SDK calls with supabase-js on a branch, then compares both apps screen by screen before you switch.
What you provide
- Your Firebase project
- A Firebase service account key
- A Supabase project
What you get
- Data moved into Postgres tables
- Users migrated with their logins
- App code on a migration branch
- A cutover checklist
FAQ
Will users have to reset their passwords?
Usually not. Supabase supports Firebase's password hashing, so imported users can sign in with the same password.
Can I run both during the move?
Yes. Your live app stays on Firebase until the new version is tested, then you do a final data sync and switch.
How long does this take?
Small apps take an afternoon. Apps with many collections or Cloud Functions can take days to test properly.
Related tasks
All tasks