Production Auth Migration — March 10, 2026
Problem
Production Supabase (vxabwjsddplhnpqtnuef) only had 6 organic signups. The 77 Firebase auth users were never migrated to production — only to dev.
Migration Process
Step 1: Auth User Creation
Script: migration-data/migrate-auth-prod.py
- Reads
auth_users.json(Firebase export) - Creates each user in prod Supabase via Admin API (
/auth/v1/admin/users) - Outputs
id-mapping-prod.json(firebase_uid → prod_supabase_uuid) - Result: 77 auth users created
Step 2: Users Table + Assignments Sync
Script: migration-data/sync-users-to-prod.py
- Uses
id-mapping.json(dev) andid-mapping-prod.json(prod) to build dev_uuid → prod_uuid mapping - Fetches all users from dev, inserts into prod with mapped UUIDs
- Syncs assignments (user-restaurant mappings)
- Result: 77 user rows synced, 6 assignments created
Step 3: Manual Fixes
- Ariane’s account existed on prod before migration (organic signup), required manual role update to
super_adminand 4 restaurant assignments added directly
Key Files
| File | Purpose |
|---|---|
migration-data/migrate-auth-prod.py |
Creates auth.users entries on prod |
migration-data/sync-users-to-prod.py |
Syncs users table + assignments |
migration-data/id-mapping-prod.json |
Firebase UID → prod Supabase UUID mapping |
Admin Roles on Production
| User | Role |
|---|---|
| nicky.dawda@gmail.com | super_admin |
| arianemb96@gmail.com | super_admin |
| nelson@phasefoundry.com | super_admin |
| antonioalx66@gmail.com | admin |