Migrate a 50-screen app from Firebase to Supabase with Claude Code

Posted

Sep 4, 2025 by Prayag (@prayag_dalal)

·

Last checked

Oct 16, 2026

·

Method:

How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

Going feature by feature, the poster used Claude Code to generate database schemas, write queries and fix daily errors; they report migrating about 85% of a 45–50 screen Flutter app from Firebase to Supabase in 10–20 days.

Agent

Claude Code

The source didn't share its exact prompt, so we wrote this from what it describes.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Help me move my app's backend from Firebase to Supabase, one feature at a time.

Check with me first: Which feature should we move first?

What I'll give you:
- My app's code
- My current Firebase data structure
- A Supabase project

Rules:
- Move one feature at a time and make sure it works before the next.
- Design the database tables and explain them before creating them.
- If something is missing or unclear, ask me instead of guessing.
- Don't delete Firebase data.

Output: The migrated feature, the new tables, and a checklist of what's left.

You'll know it worked when: each migrated feature works on Supabase and I know what's left to do.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Move my app's backend from Firebase to Supabase one feature at a time, keeping each feature working before the next.

Quick check first: tell me if anything below is missing or unclear.

Inputs (fill in or confirm):
- App code
- Current Firebase data structure
- Supabase project
- Feature order

Rules:
- Design the Postgres schema for each feature from the Firestore structure; show it before creating tables.
- Write row-level security policies that match current Firebase rules.
- Migrate a copy of the data, never the live source, and verify counts.
- Switch one feature in the app, test it, then move on.
- Keep a log of daily errors and fixes.

Checkpoint: Ask before deleting Firebase data or switching production users.

If you get stuck: If a Firestore pattern doesn't map cleanly, explain the options. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: After each feature, compare record counts and run the feature's flows.

Output: Schema, migration scripts, RLS policies and a progress log.

Done when: each migrated feature works on Supabase with matching data.

Source

https://x.com/prayag_dalal/status/1963555583392714791