Firebase to Supabase Migration

Point this agent at your Firebase codebase and ask it to plan your migration to Supabase. It maps Firestore, Firebase Auth, Cloud Functions, and Storage usage, designs a relational schema, generates SQL DDL plus Row Level Security policies, and validates the result against a Supabase test project.

What it does

1. Map your Firebase usage: Firestore collections, queries, and listeners; security rules; Auth providers; Cloud Functions triggers; Storage buckets; Realtime Database paths.
2. Plan the migration: collections become tables, subcollections become child tables with foreign keys, security rules become RLS policies, and Auth users move through export/import with explicit password-hash handling. Each item gets a mechanical / rework / redesign tier.
3. Scaffold the Supabase side: SQL migration files, RLS policies, per-platform client-call translations, Edge Function stubs, and a backfill script sketch.
4. Sandbox — apply the DDL to your Supabase test project, seed sample rows, run paired queries for parity, dry-run an auth import batch, and report PASS/PARTIAL/FAIL evidence.

Prerequisites

• SUPABASE_URL — your Supabase test project URL
• SUPABASE_SERVICE_ROLE_KEY — service-role key for that test project
• SUPABASE_DB_URL — optional; direct Postgres connection string for DDL and RLS probes
• FIREBASE_SERVICE_ACCOUNT_JSON — optional; read-only service account for live inventory of the source project

Current scope

This solution migrates Firestore data models, security rules, Auth users, and Cloud Functions structure. It does not migrate Firestore offline persistence behavior, does not port Firebase Cloud Messaging, Remote Config, Crashlytics, or Analytics, and does not move Storage objects in bulk (it scaffolds bucket setup and leaves object transfer to a planned copy job). Password-hash import is attempted only when the hash format is verified as supported; otherwise the plan falls back to a reset flow.