twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

Firebase Studio shuts down March 22, 2027. Migrate the workspace, not the database

Google is sunsetting Firebase Studio on March 22, 2027 and deleting remaining workspace data. Firestore, Auth and App Hosting keep running—the IDE is what you have to leave.

Editorial engraving of a sunny app studio where a mobile lead packs a laptop and circles a spring week while an engineer copies a soft project tree.

Firebase Studio ends on March 22, 2027; Google says remaining Studio data is permanently deleted. New workspace creation was already disabled June 22, 2026. Core Firebase services such as Cloud Firestore, Authentication and App Hosting continue outside Studio. Migrate projects you still need to Google Antigravity for code-first agentic work or Google AI Studio for browser prototyping, and inventory which production apps still depend on a Studio workspace before the deletion date.

What is ending—and what is not

Google's Firebase Studio migration page states the product is sunsetting on March 22, 2027. On that date Firebase Studio shuts down and remaining data is permanently deleted and cannot be recovered. New workspace creation and signup were disabled on June 22, 2026. The March 19, 2026 announcement started migration tooling.

Core Firebase services—Cloud Firestore, Authentication, App Hosting and the rest of the platform—continue to work outside Firebase Studio. The sunset applies to the Firebase Studio development environment, not to your production Firebase backends.

Google points builders toward Google Antigravity for code-first, agentic development and toward Google AI Studio for rapid browser-based prototyping with Firestore and Authentication integrated. The Studio preview's lessons are being folded into those flagship tools.

The backend is not retiring. The browser IDE is. Treat March 22 as a workspace evacuation, not a Firebase exit.

Decision guide

Studio sunset vs Firebase platform

ConsiderationEndingContinuing
Firebase Studio IDEShut down March 22, 2027.Firestore / Auth / App Hosting
Workspace data left behindPermanently deleted.Production user and app data in Firebase
New Studio signupsDisabled since June 22, 2026.Antigravity / AI Studio paths
Dev habitBrowser Studio editing.Repo, CI, and flagship AI tools
Dates from Firebase Studio migrating-project docs read November 6, 2026; illustrative scope comparison.

Inventory before you pick a destination

List Studio workspaces that still matter. Anything you have not opened since signup disability may still hold prompts, app scaffolds or env notes you will miss after deletion.

Separate workspace from production. For each app, write down the Firebase project ID, hosting target and whether day-to-day development still happens in Studio or already moved to a local IDE.

Classify the work. Prototypes that only need AI Studio. Codebases that need Antigravity or a normal repo. Abandoned experiments you will let delete.

Export what Studio uniquely holds. Prompt histories, generated app trees and internal notes are the easy losses. Databases and Auth users are not on the deletion list—but your ability to open the old editor is.

The backend is not retiring. The browser IDE is. Treat March 22 as a workspace evacuation, not a Firebase exit.

Choose a migration path on purpose

Antigravity if you want agent-first desktop workflows and deeper control over the codebase. Google positions it for high-velocity multi-agent work.

Google AI Studio if the value was browser prototyping wired to Firestore and Auth. That path is about speed from prompt to a hosted experiment, not about keeping Studio's UI.

Neither, yet a repo if the app is already real. Clone what you need into Git, keep Firebase as the backend, and stop pretending the browser IDE is the system of record.

Do not migrate by rewriting the product under a deadline. Migrate by moving the development surface while production keeps serving.

A ninety-day working plan (adjust to your calendar)

You still have months as of November 2026. Use them.

  1. Week 1: inventory workspaces and owners.
  2. Weeks 2–3: export or mirror anything Studio-only.
  3. Month 2: move active apps to Antigravity, AI Studio or a repo+CI path; run a release from the new path.
  4. Month 3: confirm no one needs the old workspace for a hotfix; mark evacuation complete.
  5. Before March 22, 2027: accept deletion for anything left behind.

Sequence of work

Evacuate the workspace

  1. Week 1

    Inventory workspaces, owners, and production links.

  2. Weeks 2–3

    Export Studio-only artifacts; mirror to Git.

  3. Month 2

    Ship a release from Antigravity, AI Studio, or repo+CI.

  4. Before Mar 22, 2027

    Confirm no hotfix depends on Studio; accept deletion.

Illustrative migration plan; compress if your Studio footprint is small.

Mistakes to avoid

Do not tell leadership "we're leaving Firebase"—you are leaving Studio. Do not wait until March to discover a contractor's only copy of an admin tool lived in a workspace. Do not invent downtime for Firestore; the docs say services continue. Do not start a greenfield rewrite solely because the IDE sunsets.

How to brief non-engineers.

Product and finance hear "Firebase sunset" and imagine production outages. Your first slide should say: databases and Auth stay; the browser IDE goes away; deletion hits leftover workspaces on March 22, 2027. Then show the inventory of apps that still open in Studio versus apps that already build from GitHub Actions.

Contractors are a special risk. Studio made it easy to spin a prototype without a repo. If a contractor owns a workspace you need, transfer ownership or export before their contract ends—not in March.

For mobile clients that used Studio only as a scaffold, the durable path is the same as any app: store listing, signing keys, CI, crash reporting. Studio never owned those. Make sure your [mobile] runbooks do.

If you were using Studio mainly to chat an app into existence, evaluate Antigravity or AI Studio on a throwaway prototype first. Do not migrate the revenue app on the first afternoon you open the new tool.

Put this into practice

If any production mobile or web app was born in Firebase Studio, assign an owner to the inventory this month. For help moving Studio-built clients onto a durable mobile applications delivery path while Firebase backends stay put, get in touch with your workspace list and Firebase project IDs.

Keep a short evidence packet: migration doc URL, workspace inventory spreadsheet, destination choice per app, and the date production builds moved off Studio. Deletion day should not be archaeological.

Security should confirm that Studio env vars and secrets were rotated into the new path rather than merely copied into a doc. IDE sunsets are when secrets leak into tickets.

If an app was only ever a demo, label it abandon-on-delete and move on. Not every workspace earns a migration.

Design and PM stakeholders often "work in Studio" without realizing they are outside source control. Invite them to the inventory meeting. Their Figma-to-Studio habits may be the real migration debt.

For Flutter or mobile teams, confirm signing and store listing ownership are already outside Studio. Those are the assets that hurt when people confuse IDE loss with release loss.

Create a shared calendar event for March 1, 2027 labeled "Studio evacuation complete check" so the deletion date is not the first reminder. Between now and then, refuse new features that only exist inside a Studio workspace. If a stakeholder asks for "just one more Studio prototype," redirect them to AI Studio or a repo branch with an owner. Update vendor questionnaires that still list Firebase Studio as your IDE so security reviews match reality. When migration is done, remove Studio from onboarding docs the same week—stale instructions recreate the risk. Keep Antigravity and AI Studio decisions reversible until you have shipped one real change from each path you keep.

Tell recruiting to stop listing Firebase Studio in job posts. Candidates should hear the current stack, not a sunset IDE. That small cleanup prevents a year of confused onboarding.

If two teams share one Studio workspace, split ownership before migration day so deletions do not become blame exercises. Write the split in the inventory sheet with dates. A clean handoff is part of the evacuation, not an afterthought. Confirm App Hosting and store releases still succeed from the new path under the same Firebase project numbers you already monitor in crash and analytics dashboards.

Related work: Spin Market.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎