Backend migration

Supabase → Firebase

Move application data, authentication, authorization, storage, functions, triggers, realtime behavior, indexes, clients, and backups from Supabase into Firebase with an explicit exception ledger and evidence-based cutover.

Typical timeline20–45 business days100–190 hours active work

Statusneeds review

Source testedSupabase documentation reviewed 2026-07-19

Destination testedFirebase documentation reviewed 2026-07-19

Last reviewed2026-07-19

Sources2

Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Supabase

Reasons to stay

PostgreSQL, authentication, storage, realtime, and edge functions offer an open backend stack
Managed infrastructure removes a large amount of operational work

Reasons to leave

Production scaling and service integration still demand database and infrastructure judgment
Platform-specific services can create architectural lock-in

New platform

Firebase

What gets better

Authentication, realtime data, hosting, and mobile tooling enable very fast product delivery
Managed infrastructure removes a large amount of operational work

What gets worse

NoSQL modeling, usage-based costs, and Google-specific APIs can be difficult to unwind
Platform-specific services can create architectural lock-in

Best of the move

Firebase: Authentication, realtime data, hosting, and mobile tooling enable very fast product delivery. This removes a major source-side concern: Production scaling and service integration still demand database and infrastructure judgment.

Worst of the move

What you lose: PostgreSQL, authentication, storage, realtime, and edge functions offer an open backend stack. What you inherit: NoSQL modeling, usage-based costs, and Google-specific APIs can be difficult to unwind.

01At a glance

Know the shape of the move.

Transfer outcome12 features audited

Clean0

Partial6

Manual4

Lost2

Mapping route9 of 9 fields have a destination path

SourceSupabase9 mapped fields

Automatic0

Transform5

Manual4

Unsupported0

DestinationFirebase9 supported paths

This timeline assumes

Up to one million records, 100,000 users, 100 GB of files, and 100 functions
Application owners can ship coordinated client and server releases.
A production-shaped dataset and identity cohort are available for rehearsal.
The source remains authoritative until final consistency and security checks pass.
The migration team records evidence for every blocking verification check.

02Loss matrix

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

Item	Outcome	Impact	What happens	Mitigation
PostgreSQL data, authentication identities, storage objects, and application configuration	partial	critical	Core postgresql data, authentication identities, storage objects, and application configuration can move, but Supabase and Firebase use different models, limits, identifiers, and import behavior.	Pilot every feature class, preserve source IDs, and reconcile accepted, transformed, rejected, and excluded items.
Relational schema, SQL, RLS, Edge Functions, triggers, realtime, and client behavior	manual	critical	A relational Supabase application requires an explicit Firebase data model and rewritten authorization, functions, and clients.	Inventory every active dependency, approve its destination disposition, and test the replacement before source writes stop.
Primary application data	partial	critical	Records can move while source and destination data models, types, identifiers, and constraints differ.	Design the target schema and preserve stable source IDs.
Nested data and relationships	partial	critical	Document nesting, references, joins, and cascade behavior require explicit transformation.	Model relationships and verify orphan, duplicate, and cascade behavior.
Authentication users	partial	critical	Accounts may move while password hashes, providers, MFA, verification, and sessions require separate handling.	Choose a supported rolling or one-off identity strategy.
Authorization and security rules	manual	critical	Source rules do not execute as destination database or storage policy.	Translate into least-privilege policies and test every role.
File and object storage	partial	critical	Objects, metadata, signed URLs, paths, and access policies require separate copying.	Copy with checksums and verify authorized and anonymous access.
Serverless functions and triggers	manual	critical	Runtime APIs, triggers, regions, retries, and secrets differ.	Port and integration-test every function and failure path.
Realtime subscriptions	partial	high	Event ordering, payloads, filters, reconnects, and delivery guarantees differ.	Rewrite clients and test concurrency, disconnect, and replay behavior.
Offline behavior and local cache	lost	high	Source client SDK persistence does not automatically exist in the destination stack.	Choose and test an explicit offline and conflict strategy.
Indexes and query behavior	manual	critical	Query planners, indexes, limits, and transaction semantics differ.	Benchmark representative queries against production-shaped data.
Analytics, crash reporting, and messaging	lost	high	Adjacent platform products do not follow database data.	Keep, replace, or retire each service explicitly.

03Field and feature mapping

Where each thing goes.

Source	Destination	Method	Notes
Supabase project	Firebase project	manual	Record regions, environments, owners, and billing.
Collection, document, or record	Destination table and row	transform	Preserve source IDs and types.
Nested object or reference	Column, JSON, or relation	transform	Choose explicit relational semantics.
Authentication user	Destination auth user or federated identity	transform	Preserve verification and provider identifiers where supported.
Security rule	Destination authorization policy	manual	Translate and test every role and path.
Storage object	Destination storage object	transform	Preserve path, metadata, checksum, and access.
Function or trigger	Destination function, hook, or scheduled job	manual	Port retries, idempotency, and secrets.
Realtime listener	Destination subscription	transform	Rewrite payload and reconnect handling.
Index and query	Destination index and query	manual	Benchmark production-shaped workloads.

04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Supabase data, configuration, and operating evidence before any destination write.

Export Supabase data, schema, identities, security rules, storage, functions, indexes, configuration, and logs.
Record counts, checksums, sizes, auth states, policies, and query baselines.
Capture client versions, SDK configuration, integrations, backups, and recovery procedures.
Hash raw exports and transform working copies only.

Proof to capture: A signed manifest reconciles every scoped record class, runtime dependency, export file, count, and hash.

Transformation · Schema migration and ETL tools

Target schema and identity map

Translate records, relationships, users, and stable IDs.

Inventory source values and exceptions.
Define explicit destination mappings.
Reject unmapped critical records.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Policy tests, feature flags, and integration suite

Policy and client compatibility layer

Preserve authorization and support controlled client rollout.

Normalize encoding, dates, identifiers, and blanks.
Run a representative pilot.
Reconcile accepted, rejected, and transformed rows.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Transform

Data-model transformation changes meaning

criticalpossible likelihood

Nested values, identifiers, timestamps, or relationships differ after import.

Consequence: Applications read incorrect or incomplete data.
Mitigation: Use deterministic transforms and record-level reconciliation.

Stop if: Any critical invariant fails.

Security

Authorization is weaker than the source

criticalpossible likelihood

A destination role can read or write unauthorized rows or objects.

Consequence: Sensitive data is exposed or changed.
Mitigation: Default-deny and test every policy with real client identities.

Stop if: Any unauthorized operation succeeds.

Cutover

Old and new backends both accept writes

criticalpossible likelihood

Client versions or triggers write to different systems.

Consequence: Data diverges permanently.
Mitigation: Use version gates, a write freeze, or an approved dual-write reconciliation design.

Stop if: Unreconciled writes appear in either system.

06Precise timeline

Do the work in this order.

Estimate forUp to one million records, 100,000 users, 100 GB of files, and 100 functions

Total elapsed20–45 business days

Active work100–190 hours

BufferAdd time for large exports, unsupported Supabase features, destination limits, identity exceptions, regulated data, or strict downtime requirements.

Days 1–3Inventory and decisions2–3 days

Days 3–5Backup and reconcile1–3 days

Days 5–12Map and pilot3–8 days

Days 10–20Final delta and switch1–5 days

Days 12–40Observe and close3–10 days

1
Days 1–3 · inventory
Inventory and decisions
6–12 hours active2–3 days elapsedOwner review waiting
- Inventory Supabase data, features, users, domains, and integrations.
- Approve scope, owners, mappings, and exclusions.
Depends on: Supabase and Firebase administrator access
Stop / go checkpoint
Export?
Go when: Every critical item has an owner and disposition.
Stop when: Consent, billing, access, or system ownership is unclear.
2
Days 3–5 · backup
Backup and reconcile
5–10 hours active1–3 days elapsedExport processing waiting
- Create immutable exports and configuration evidence.
- Reconcile counts, totals, and hashes.
Depends on: Approved inventory
Stop / go checkpoint
Transform?
Go when: Source totals and export manifests agree.
Stop when: Any critical dataset or configuration is absent.
3
Days 5–12 · pilot
Map and pilot
10–35 hours active3–8 days elapsedDestination processing and review waiting
- Configure Firebase and transform representative data.
- Run a pilot containing normal records and every critical edge case.
Depends on: Verified backup
Stop / go checkpoint
Scale?
Go when: Pilot mappings, behavior, access, and evidence pass.
Stop when: Any critical check fails or produces unexplained variance.
4
Days 10–20 · cutover
Final delta and switch
5–25 hours active1–5 days elapsedDNS, import, or sync propagation waiting
- Freeze production writes in Supabase.
- Apply the final delta, switch ownership, and run blocking checks.
Depends on: Passed pilot and approved rollback
Stop / go checkpoint
Open production?
Go when: Counts reconcile and one destination system owns production.
Stop when: A source writer remains active or a blocking check fails.
5
Days 12–40 · observe
Observe and close
3–18 hours active3–10 days elapsedOperating-cycle evidence waiting
- Monitor one complete operating cycle.
- Sign the verification report and close rollback only after stability.
Depends on: Verified cutover
Stop / go checkpoint
Close rollback?
Go when: No trigger occurs during the agreed observation period.
Stop when: Data, access, delivery, routing, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Firebase the only production system without losing the final Supabase delta.

Recommended window: A low-volume weekday morning with platform, data, DNS, and business owners available.

Freeze production writes and scheduled actions in Supabase.
Export, transform, and reconcile the final delta.
Apply the approved delta to Firebase.
Switch domains, forms, integrations, sending, or sync ownership as applicable.
Run every blocking verification check and keep the source intact.

Proof to capture: Firebase owns production, totals reconcile, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Supabase without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, or billing are changed.

Stop new writes and scheduled actions in Firebase.
Restore the prior Supabase routing, forms, integrations, sending, or sync ownership.
Export the Firebase post-cutover delta.
Review and apply safe destination-era changes to Supabase.
Run the same blocking checks against the restored source.

Proof to capture: Supabase again owns production with current data and no duplicate destination action.

Rollback immediately when

Unexplained critical count or value variance
Missing or exposed critical data
Duplicate production action
Failed access, routing, delivery, or integration check
A critical feature has no safe destination replacement

08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

ID	Check	Method	Expected result	Evidence
`V-01`Blocking	Record reconciliation	Compare counts, checksums, aggregates, and stratified records.	Every scoped record is accounted for.	Data ledger.
`V-02`Blocking	Types and relationships	Test constraints, identifiers, nulls, dates, arrays, and cascades.	All critical invariants hold.	Schema report.
`V-03`Blocking	Authentication states	Test every provider, verification, reset, MFA, and session path.	Users can authenticate only as approved.	Auth matrix.
`V-04`Blocking	Data and storage policy	Run allowed and denied operations for every role.	Every policy defaults and resolves correctly.	Policy test report.
`V-05`Blocking	Object coverage	Compare paths, sizes, hashes, metadata, and signed access.	Every required object is durable and correctly protected.	Storage manifest.
`V-06`Blocking	Triggers and side effects	Run success, retry, timeout, duplicate, and failure cases.	Idempotent approved outcomes.	Function log.
`V-07`Blocking	Query, realtime, and offline behavior	Run supported client versions through representative workloads.	Correct reads, writes, events, and recovery.	Client matrix.
`V-08`Blocking	Backup and rollback	Restore a destination backup and execute the rollback rehearsal.	Recovery objectives and integrity pass.	Recovery report.

09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check.

Create final Supabase exports and archive verification evidence.
Revoke temporary credentials, API keys, webhooks, and elevated roles.
Remove obsolete embeds, forms, jobs, integrations, and DNS records.
Keep the source intact through the approved retention window.
Cancel paid plans only after billing, legal, and recovery review.
Schedule the next Firebase backup, access, and migration-playbook review.

Sources and maintenance

Built to be reviewed.

Tested 2026-07-19. Next scheduled review: 2026-10-19.

Supabase: official migration documentationAccessed 2026-07-19
Firebase: official migration documentationAccessed 2026-07-19

Know the shape of the move.

This timeline assumes

What survives the move.

Where each thing goes.

Make the move recoverable.

Create the source-of-truth backup

Target schema and identity map

Policy and client compatibility layer

The things most likely to hurt.

Data-model transformation changes meaning

Authorization is weaker than the source

Old and new backends both accept writes

Do the work in this order.

Inventory and decisions

Export?

Backup and reconcile

Transform?

Map and pilot

Scale?

Final delta and switch

Open production?

Observe and close

Close rollback?

Cut over with a way back.

Cutover

Rollback

Prove the migration worked.

Remove the scaffolding safely.

Built to be reviewed.