Move from Supabase or Firebase
Backenly copies a project into a new Backenly project: its tables and rows, its users with their passwords, and its files. Your old project is only read, so your app keeps running there until you switch it over.
- Backenly only reads your old project. Nothing there changes.
- Users who sign in with a password keep it.
- Every table is counted on both sides before the move is done.
courtside
Supabase, East US (North Virginia)Backenly, N. Virginia (us-east-1)
Backenly only reads Supabase. Nothing there changes. Its 3 database functions stay on Supabase for your agent to rebuild.
How a move works
A move copies a project into a new Backenly project and checks it: every table is counted on the old side and the new, and any count that differs is reported. Start one after you sign up, from Import it under Create your first project.
Move a project
- Connect
- Review
- Move
Connect Supabase
Paste the project’s connection string. Backenly only reads Supabase, and never writes to it.
postgresql://postgres.qwertyuiop@aws-0-us-east-1.pooler.supabase.com:5432/postgres
- Project
- courtside East US (North Virginia)
- Tables
- 9 tables, 118,344 rows
- Authentication
- 12,904 users, with their password hashes
- Storage
- 13,467 files, 2.1 GB
- Access
- Reads only, never writes
Review the move
courtside moves into a new Backenly project. Nothing changes on Supabase, so your app keeps running there until you switch it over.
- Tables
- 9 tables, 118,344 rows
- Users
- 12,904, with the passwords they have
- Files
- 2 buckets, 13,467 files, 2.1 GB
- Access rules
- 7 tables’ row-level security policies, translated for Backenly. Until you approve them, only your server key can read or write those tables.
- Stays behind
- 3 database functions. Your agent can rebuild them as Backenly functions.
courtside
Supabase, East US (North Virginia)Backenly, N. Virginia (us-east-1)
Backenly only reads Supabase. Nothing there changes. Its 3 database functions stay on Supabase for your agent to rebuild.
What moves, and what stays
Pick where your project lives now. Backenly only reads it, so your app keeps running there until you switch it over.
What you need
- The project’s connection string: in Supabase, press Connect and copy the Session pooler string (port 5432).
- To move Storage files too, the Project URL and the service_role key from Project Settings, then API. Backenly only reads with them, keeps them encrypted while the move runs, and erases them when it ends.
postgresql://postgres.qwertyuiop@aws-0-us-east-1.pooler.supabase.com:5432/postgres
- Project
- courtside East US (North Virginia)
- Tables
- 9 tables, 118,344 rows
- Authentication
- 12,904 users, with their password hashes
- Storage
- 13,467 files, 2.1 GB
- Access
- Reads only, never writes
What comes across
Tables and rows
Moves: The public schema’s tables and rows, counted on both sides before the move is called done.
Users and their passwords
Moves: The same users, with the same ids. Their bcrypt hashes move as they are, so each signs in with the password they have. Phone-only and anonymous users stay behind.
Storage buckets and files
Moves: The same buckets, public or private as they were, and their files, once you add the Project URL and service_role key. Files over 100 MB stay behind, and the move says how many.
Row-level security policies
Waits for your approval: Translated into Backenly access rules when they use the usual shapes, like auth.uid() = user_id, and held for your approval. A table whose policies do not translate answers only your server key.
Edge Functions and database functions
Stays behind: Not moved. Your coding agent can rebuild them as Backenly functions.
Good to know
- A table whose id is not a UUID, such as a number, keeps it in a legacy_id column and gets a UUID id. The rows that point at it follow, so no row loses its link.
- A table named users becomes profiles, because Backenly keeps your app’s users in its own users table.
- Enums arrive as text, and arrays stay arrays. The review lists the columns that change type before anything moves.
- Foreign keys are created with their tables. A key rows cannot satisfy while they arrive, such as one from a table to itself, is added once the rows are in.
- Calls to rpc() do not work on Backenly. Your agent moves that logic into Backenly functions.
What you need
- A service account key for the project: in the Firebase console, open Project settings, then Service accounts, and press Generate new private key.
- Backenly only reads with it (Firestore and its rules, Authentication, Storage), keeps it encrypted while the move runs, and erases it when the move ends. Delete the key in Firebase afterwards if you like.
courtside-7f3c2-firebase-adminsdk.json
- Project
- Courtside courtside-7f3c2
- Firestore
- 8 collections, 118,332 documents
- Authentication
- 12,904 users, with their password hashes
- Storage
- 13,467 files, 2.1 GB
What comes across
Firestore collections
Moves: Tables, one per collection and subcollection, and one row per document.
Users and their passwords
Moves: The same users, with their Firebase password hashes, which Backenly checks at sign-in. Phone-only and anonymous users stay behind.
Users who sign in with Google or another provider
Moves: The same users. Google, GitHub and Facebook users sign in again once that provider is set up in Backenly; Apple users and others can set a password with a reset email.
Cloud Storage files
Moves: The default bucket’s files, paths kept, in a private Backenly bucket named files. Files over 100 MB stay behind.
Security Rules
Stays behind: Not translated. Each moved table answers only your server key until you or your agent add access rules for it.
Cloud Functions and Realtime Database
Stays behind: Not moved. Your coding agent can rebuild the functions as Backenly functions; Realtime Database data stays in Firebase.
Good to know
- Each document becomes a row, with its document id in firebase_id. Fields found in up to 1,000 documents of a collection become columns, and a value that does not fit one is kept in an extra_fields JSON column, so nothing is dropped.
- Subcollections become tables of their own, with a parent_id column that points at the parent document’s row.
- Firebase hashes passwords with its own version of scrypt. Backenly checks those hashes at sign-in and stores a fresh hash the first time each user signs in. If the key cannot read the hashes, the review says so.
- Only Firestore moves. Realtime Database data stays in Firebase.
What you need
- A connection string for a database Backenly can reach over the internet. Backenly connects on port 5432 only.
- A read-only user is enough, as long as row-level security hides none of the rows from it.
postgresql://courtside_ro@ep-misty-river-a5k2…/courtside
- Host
- Neon, US East (Ohio)
- Tables
- 9 tables, 118,344 rows
- Access
- Reads only, never writes
What comes across
Tables and rows
Moves: The same tables and rows, from public or the schemas you name, counted on both sides.
Primary and foreign keys
Moves: Kept, except keys over more than one column, which the review lists. A primary key that is not a UUID keeps its values (in legacy_id when it was id), and the rows pointing at it follow.
Enums, arrays and binary columns
Moves: Arrays stay arrays and binary columns stay binary; enums arrive as text. The review lists the columns whose type changes.
Row-level security policies
Waits for your approval: Translated into Backenly access rules when they use shapes Backenly understands, and held for your approval. Any other table answers only your server key.
Roles, extensions and server settings
Stays behind: Not moved. Backenly runs the database for you.
After the move
Your old project keeps running, untouched, until you point your app at Backenly.
Approve the access rules
Backenly translates the row-level security policies it understands into its own access rules and holds them for your approval on the project’s Autonomy page. Firestore Security Rules are not translated. Until a table has rules, only your server key can read or write it, so nothing is open while you check.
Point your app at Backenly
From Supabase, most supabase-js code keeps working: import
createClientfrom@backenly/sdk/supabaseinstead, and pass it your Backenly project URL and key. Calls torpc()are the exception. From Firebase, the app’s SDK calls change; your coding agent can make that change for you.Rebuild what stayed behind
Connect your agent over MCP and ask it to rebuild your Edge Functions or Cloud Functions as Backenly functions. Each change it makes is planned, checked and can be undone.
Switch when you are ready
Your old project keeps running, untouched. Move again right before you switch, so the copy is fresh (each move makes a new project), then point your app at Backenly.
Questions
Anything else about your move? Ask the people who build it.
Book a call with the founders (opens in a new tab)No. Backenly only reads it. Your app keeps running there until you point it at Backenly.
Not those who sign in with a password. Supabase’s bcrypt hashes move as they are, and Backenly checks Firebase’s scrypt hashes at sign-in. The review counts the users who sign in another way, and says what happens to them.
From Supabase or Postgres, a move copies one snapshot, taken as it starts; from Firebase, it says which collections changed while it ran. Rows written later stay where they are. Move again right before you switch your app over: each move makes a new Backenly project, so delete the earlier one.
It depends on the size of the project and how fast its source answers; one move can run for up to two hours. It runs on Backenly’s servers, so you can close the tab, and your Projects page shows it as Importing until it is done.
Yes. Connect Claude Code, Cursor or Codex over MCP and ask it to rebuild what stayed behind and to point your app at Backenly. Each change it makes to the backend is planned, checked and can be undone.
Move your project
Sign up, choose Import it when Backenly asks you to create your first project, and connect Supabase, Firebase or Postgres.



