Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want my app off Firebase and onto a backend I control

Short answer

An app can be moved off Firebase, but it is a project, not a switch. Users, data, files and server code each move separately, and the app must be updated and released through the stores. Do not delete the Firebase project. Ask for exports of your data and keep them while the new backend is built.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Firebase costs grow with every user and I cannot predict them.
  • I am locked in and my developer says moving is impossible.
  • I need reports or searches that Firebase makes hard.
  • I want my data in my own database, in a country I choose.
  • My app is live and I cannot break it for current users.

Why does this happen?

  1. Firebase combines many services in one

    Login, the database, file storage, server functions and notifications all sit in one project. Each has its own way of storing things, so each needs its own plan to move.

  2. Your data is stored in a Firebase-specific shape

    Google documents exporting Firestore documents to a Cloud Storage bucket. It requires billing to be enabled, and the export is not an exact snapshot taken at one moment, since changes made while it runs may be included. It also incurs one read per exported document.

  3. User accounts and passwords need care

    Firebase's command line tool exports user accounts to a file. It only exports passwords in full if they were hashed with scrypt, and the hash settings are described as sensitive. The users' passwords are the reason this step is planned first.

  4. The app code talks to Firebase directly

    Mobile apps often call Firebase from the phone itself. Moving the backend means changing the app, building a new version and getting it through store review, while old versions are still in use.

  5. Server logic is written for Firebase

    Functions and security rules contain business rules that must be rewritten for the new backend, and tested against the old results.

What can I do about it today?

  1. Keep the Firebase project and its billingDo not delete or downgrade the project. It keeps serving your current users while you plan.
  2. Confirm you own the projectCheck that the Firebase and Google Cloud project is under an account of your company, and that you have an owner role.
  3. List what the app usesAsk which Firebase services are used: login, database, storage, functions, notifications, analytics. That list sets the size of the job.
  4. Write down your reasonsCost, limits, location or reports: the reason decides whether to move fully, partly or stay.
  5. Ask for an export of your dataRequest an export of the database and file storage, and store it where you control it.

When should I bring someone in?

  • The app has many users and cannot lose data or logins.
  • Your developer says it cannot be done, or nobody understands the Firebase setup.
  • You are unsure whether leaving is worth it.

How do I handle it?

  1. Map what you use and what it costsI list each Firebase service, how the app uses it and where your costs come from. Sometimes a smaller change solves the problem.
  2. Design the new backendI propose a database, server and file storage that match your needs and explain what each one asks of you to maintain.
  3. Move in stagesData is copied and checked, the new backend runs alongside Firebase, and parts of the app are switched one at a time, with a tested rollback.
  4. Release the app update carefullyThe app is updated so old and new versions both work for a while, and the store review is planned in.
  5. Switch off Firebase lastOnly after the new backend has run live and backups are proven do I suggest closing the old services.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can my users keep their passwords?

Sometimes. Firebase documents that only scrypt-hashed passwords are exported in full, so I check your accounts first and plan a fallback such as a password reset for the rest.

Is the export a perfect copy?

Google states a Firestore export is not an exact snapshot taken at the export start time. I plan a final catch-up so nothing is lost.

Should I leave Firebase at all?

Not always. If the main issue is cost or one feature, a smaller change may be enough. I say so before proposing a rebuild.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.