# Firebase Studio Shutting Down: How to Migrate by March 2027
> Firebase Studio is shutting down on March 22, 2027, and remaining data is deleted. The timeline and migration paths, from Firebase pages checked Oct 21, 2026.
Canonical: https://app369.com/blog/firebase-studio-shutting-down-migrate-project-2027/
Last updated: 2026-10-21
[ **Simon Dziak** Founder & developer, App369](https://app369.com/about/szymon-dziak/) [LinkedIn](https://www.linkedin.com/in/szymondziak/)
Published October 18, 2026 · Updated October 21, 2026•Facts last verified October 21, 2026•8 min
App369https://app369.com/blog/firebase-studio-shutting-down-migrate-project-2027/
[← Back to Blog](https://app369.com/blog/)
## Key takeaways
- →Firebase Studio shuts down on March 22, 2027. Firebase says remaining data is permanently deleted and cannot be recovered after that date, so anything you want to keep must be migrated before then.
- →New workspace creation and new signups were disabled on June 22, 2026. You can still use and migrate existing workspaces until the shutdown.
- →Firebase names two destinations. Google Antigravity is for code-first, agentic work, and Google AI Studio is for browser-based prototyping. You can also zip and download your code, or export it to GitHub, and use it on another platform.
- →Only the sunset of the Studio development environment is announced. Firebase says Cloud Firestore, Authentication and App Hosting are not affected, and that apps already deployed to Firebase keep running.
- →Chat history is not included in the zip. Firebase says the App Prototyping agent and Gemini prompts and responses are stored in a separate folder you have to zip yourself.
Pricing an app? Try the free [app cost calculator](https://app369.com/tools/app-cost-calculator/) or get a range for your project in the [instant quote](https://app369.com/instant-quote/).
**Firebase Studio shuts down on March 22, 2027, and Firebase says any data still in it after that date is permanently deleted and cannot be recovered.** New workspaces and signups were already disabled on June 22, 2026. Firebase names two places to move your project, Google Antigravity and Google AI Studio, and also documents a zip or GitHub export for other platforms.
The facts below come from two Firebase documentation pages, as shown in the sources. I checked each one on October 21, 2026. Google can change a date, so open the linked page before you plan around it.
**Disclosure:** App369 is my studio. I build and fix Flutter and Firebase apps, and the last section mentions what I sell. Google doesn’t pay me for anything on this page.
## The dated timeline
| Date | What happens | Source |
| --- | --- | --- |
| March 19, 2026 | Sunset announced. Migration tools start rolling out | [Firebase](https://firebase.google.com/docs/studio/migrating-project) |
| June 22, 2026 | New workspace creation and new user signup are disabled. Existing workspaces can still be used and migrated | [Firebase](https://firebase.google.com/docs/studio/migrating-project) |
| **March 22, 2027** | Firebase Studio shuts down. Remaining data is deleted | [Firebase](https://firebase.google.com/docs/studio/migrating-project) |
Between those dates, Firebase says existing workspaces remain accessible and that it keeps providing critical security patches and Gemini model updates. The Studio overview page says: “You can continue to work in and migrate your existing workspaces to Google AI Studio or Google Antigravity.”
## What happens to your workspace, code and data
Firebase’s page is direct about this. Projects you want to keep must be migrated before March 22, 2027. After that date, remaining data is permanently deleted and cannot be recovered. I read that as: if the only copy of your code is in a Studio workspace, treat the date as a hard deadline.
Firebase also says what does not change:
- Cloud Firestore, Authentication and App Hosting keep working. The sunset applies only to the Firebase Studio development environment.
- The overview page says apps already deployed to Firebase keep running after the sunset date.
So the deadline is about your editing environment and the files inside it, not your live backend.
One more fact from the overview page. Firebase Studio is a preview, with no SLA, and it combines Project IDX with AI agents and Gemini assistance. Firebase says Project IDX is now part of Firebase Studio.
## Which path Firebase recommends
Firebase says its development focus now goes to two tools. Antigravity is for code-first, agentic development. AI Studio is for browser-based prototyping, with Cloud Firestore and Firebase Authentication integrated into it.
| Choose | If you |
| --- | --- |
| Google Antigravity | Prefer an agent-first desktop environment, the Antigravity IDE or the terminal. Created your app from a built-in template or imported repository. Mainly use Code View. Want multi-model support, including Claude and GPT-OSS alongside Gemini. Started in Prototyper mode but now need a local environment |
| Google AI Studio | Prefer a web-based experience for multi-device work or can’t install software. Created your app with the App Prototyping agent and want rapid, prompt-based generation. Want the fastest path from prompt to full-stack production app |
You aren’t locked in. Firebase says you can start in AI Studio and move to Antigravity later, using the Code tab, then Export, then Export to Antigravity.
My advice: if your project is a real codebase that you plan to keep editing, Firebase’s own criteria point to Antigravity. If it began as a prompt-built prototype, they point to AI Studio.
## Before you start
1. **Check who created the workspace.** Only the creator can use the Move now button. For a shared workspace, others can duplicate it or export the code manually. Its backend config still points to the owner’s Firebase project and keys, so create your own project and update the environment variables.
2. **Save your chat history.** It is not in the zip. Firebase says prompts and responses for the App Prototyping agent and Gemini are in `/home/user/.idx/ai`. To keep them, open the folder with File > Open Folder, right-click `.idx/ai`, choose Zip and Download, and cancel the environment rebuild prompt. For Prototyper sessions, check `git log` or Source Control history.
3. **Trim what you export.** If an export stalls or times out, Firebase says to delete `node_modules`, large media, database exports and build folders, and to avoid zipping a large `.git` history or logs.
4. **Allow pop-ups.** If the download does nothing, Firebase says to allow pop-ups in your browser or run Zip and Download manually.
## Move to Google AI Studio
Firebase’s steps for the transfer:
1. Click Move now at the top of your workspace, then select Prepare for AI Studio.
2. When preparation finishes, click Move to Google AI Studio.
3. If asked, review and accept the Terms of Service. Your code opens in a new AI Studio workspace.
Firebase says conversion can take several minutes and that AI Studio notifies you when it is done.
Then you choose how to publish.
### Option A: keep your existing URL
This uses App Hosting and GitHub sync. Firebase Studio stored your Gemini API key from the workspace `.env` file as an App Hosting environment variable. After migrating, you must set the environment variable manually in the Firebase console, because the `.env` file shouldn’t be stored in GitHub to avoid API key exposure. Firebase notes the key stays accessible to anyone with access to the Firebase project, and suggests Secret Manager for finer control.
1. In the Firebase console, open App Hosting and click View on your backend, usually named `studio`. Go to Settings > Environment, click Add new, and enter your `.env` contents in the Key field.
2. In AI Studio, open Settings, then the GitHub panel. Sign in to GitHub and install the Google AI Studio GitHub App. Click Create GitHub repository, confirm `.env` is not in the file list, and select Stage and commit all changes.
3. In the App Hosting backend’s Settings > Deployment, select Connect to GitHub. Install the Firebase App Hosting GitHub App, select your repository, set the branch to `main` and the root directory to `/`, then click Save and deploy.
For later updates, you stage and commit in the AI Studio GitHub panel and watch the deployment in the Firebase console.
### Option B: one-click publish to Cloud Run
This gives you a new URL. In AI Studio, click Publish, click Import project in the project selector, choose the project name shown in the top bar of your Studio workspace, click Import, then Publish.
Firebase warns about custom domains here. You must map the domain to the new Cloud Run service, mapping can take up to 24 hours, and it may cause downtime. Firebase offers staying on App Hosting through AI Studio’s GitHub sync (Option A) as the way to avoid migrating domains.
My advice: if you have a custom domain or real users, pick Option A. It keeps your URL, so you don’t have to remap the domain.
## Move to Google Antigravity
Firebase lists three prerequisites: the Antigravity IDE (choose the IDE, not the other download options), Node.js 20 or higher, and Firebase CLI 15.10.0 or higher.
**Step 1: export and initialize.** Firebase gives an automated way and a manual one.
- Automated: click Move now, then Zip and Download if it is shown. If not, run Firebase Studio: Zip & Download from the command palette. Extract the folder and open it in the Antigravity IDE. In the Agent pane, enter `@fbs-to-agy-export`. Firebase recommends the Gemini Flash model for this task. Follow the agent’s prompts, and if errors occur, ask it to try again.
- Manual, with no AI tokens: run `npx firebase-tools@latest studio:export PATH`, where PATH is your project folder or zip file, or `.` if you are already in it. Firebase says this command is optimized for Next.js, Flutter and Angular, and that other workspace types may not be fully updated.
**Step 2: preview.** Open Run and Debug in the left sidebar, click the play button to start the local dev server, and follow the terminal instructions.
**Step 3: publish.** In the agent chat, enter `Publish my app`. When prompted to run `firebase deploy`, choose Yes. Firebase says that if you have published before, the app keeps its existing URL. Otherwise the agent walks you through App Hosting setup.
If the Antigravity terminal can’t find `npx` or the Firebase CLI, Firebase says to add a block to `~/.bash_profile` that sources `~/.bashrc` if it exists, then restart Antigravity.
## Move to another platform: zip or GitHub
Firebase documents a third route that doesn’t use either tool.
1. Click Move now, then Zip and Download, and extract the archive. Firebase says you can also export to GitHub.
2. Pick how to publish:
- **Firebase CLI, which keeps your URL.** Install with `npm install -g firebase-tools`, run `firebase init apphosting`, choose Link to an existing backend, select `studio`, then run `firebase deploy`.
- **External hosting.** It works with any provider, but you get a new URL.
- **Local only.** Use the Firebase Local Emulator Suite for offline testing.
My advice: even if you plan to use AI Studio or Antigravity, download the zip first. It is a copy of your code that lives outside Google’s workspace.
## What the App Prototyping agent and Gemini become
Firebase’s migration page has no dedicated guidance on either. What it does say is narrow. Apps built with the App Prototyping agent fit the AI Studio path, where you get prompt-based generation. Gemini model updates continue in Studio until the shutdown, and Firebase recommends the Gemini Flash model for the automated Antigravity step. The Gemini API key in your workspace `.env` is the thing you have to move yourself.
## A short checklist
1. Find out who created each workspace you care about. The free [Firebase shutdown checker](https://app369.com/tools/firebase-shutdown-checker/) can’t see Studio workspaces, but it reminds you to check them and flags the other Firebase shutdowns in your code.
2. Download a zip now and store it somewhere you control.
3. Zip the `.idx/ai` folder if you want your chat history.
4. Choose AI Studio, Antigravity or another platform using Firebase’s criteria above.
5. Move your Gemini API key out of `.env` and into App Hosting settings or Secret Manager.
6. Test sign-in. Firebase says that if Google Sign-In breaks after migration, you add the AI Studio app’s domain under Authentication > Settings > Authorized domains.
7. Finish well before March 22, 2027.
For the other Firebase retirements that fall in 2027, see my [Firebase deprecations table](https://app369.com/blog/firebase-deprecations-shutdown-dates-2026/). If your app came from Builder.ai, which shut down in 2025, the [Builder.ai guide](https://app369.com/blog/builder-ai-shut-down-what-to-do-with-your-app-2026/) covers what to do with it.
For every other dated Apple, Google Play and Firebase requirement in 2026 and 2027, see [App Store and Google Play deadlines for 2026 and 2027](https://app369.com/blog/app-store-google-play-deadlines-2026-2027/).
## Need a hand?
Google’s Move now tool does the export, and only the workspace’s creator can run it. After that, I can check the moved app’s code, Firebase rules and deploy setup and fix what breaks, at fixed prices: see [Firebase Studio migration help](https://app369.com/fixed-price/firebase-studio-migration/). If one thing broke after the move, the [App Fix Ticket](https://app369.com/fixed-price/flutter-firebase-bug-fix/) covers it in two fixed-price steps: a $450 Diagnosis with a fixed repair quote within 3 business days, credited toward the $1,200 Fix, which takes 5 business days and comes as a pull request. Or [send me a short description](https://app369.com/contact/).
## **Want this done at a fixed price?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [**App Fix Ticket**from $450One reproducible bug in an existing mobile or web app, diagnosed and fixed.](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
## **Frequently asked questions**
- **When does Firebase Studio shut down?**
- On March 22, 2027. Firebase's migration page says new workspace creation and new user signup were disabled on June 22, 2026, and that existing workspaces stay accessible until the shutdown date. After March 22, 2027, remaining data is permanently deleted and cannot be recovered.
- **Will my deployed app stop working when Firebase Studio shuts down?**
- Firebase's overview page says apps already deployed to Firebase keep running after the sunset date. The migration page says Cloud Firestore, Authentication and App Hosting are not affected, and that the sunset applies only to the Firebase Studio development environment. What you lose is the workspace itself, so move your code out before March 22, 2027.
- **Where does Google tell me to move my Firebase Studio project?**
- To Google Antigravity or Google AI Studio. Firebase says Antigravity suits code-first, agentic development, and AI Studio suits browser-based prototyping. The migration page also covers other platforms: you zip and download the workspace, or export it to GitHub, then publish it with the Firebase CLI or an external host.
- **Does the zip download include my chat history?**
- No. Firebase says chat history is not in the zip. Prompts and responses for the App Prototyping agent and Gemini are stored in /home/user/.idx/ai, and you can zip that folder separately. For Prototyper sessions, Firebase says to check git log or Source Control history.
- **Can someone other than the creator migrate a shared workspace?**
- Not with the Move now button. Firebase says only the workspace creator can use it. Other people can duplicate the workspace or export the code manually. The backend configuration still points to the owner's Firebase project and keys, so you create your own project and update the environment variables.
## **Sources**
1. [Firebase, Firebase Studio sunset and project migration (page last updated 2026-10-20 UTC, checked October 21, 2026)](https://firebase.google.com/docs/studio/migrating-project)
2. [Firebase, Firebase Studio overview (page last updated 2026-10-20 UTC, checked October 21, 2026)](https://firebase.google.com/docs/studio)
Tags
#firebase studio shutting down #firebase studio sunset #firebase studio migration #migrate firebase studio to google ai studio #firebase studio to antigravity #firebase studio export zip #firebase studio github export #project idx shutdown #firebase studio march 22 2027 #firebase studio app prototyping agent
Generated from app369.com . © 2026 App369. All rights reserved.
**Share:**
[Share on Twitter](https://twitter.com/intent/tweet?text=Firebase%20Studio%20Shutting%20Down%3A%20How%20to%20Migrate%20by%20March%202027&url=https%3A%2F%2Fapp369.com%2Fblog%2Ffirebase-studio-shutting-down-migrate-project-2027%2F) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fapp369.com%2Fblog%2Ffirebase-studio-shutting-down-migrate-project-2027%2F) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fapp369.com%2Fblog%2Ffirebase-studio-shutting-down-migrate-project-2027%2F)
## **Related Resources **
[Firebase ML Model Hosting Shutting Down: How to Migrate](https://app369.com/blog/firebase-ml-model-hosting-shutting-down-migrate-2027/) [Firebase Deprecations: Every Shutdown Date, 2024 to 2027](https://app369.com/blog/firebase-deprecations-shutdown-dates-2026/) [Firebase Test Lab Shutting Down: Alternatives for 2027](https://app369.com/blog/firebase-test-lab-shutting-down-alternatives-2027/) [Firebase Extensions Shutting Down: Replace Them by 2027](https://app369.com/blog/firebase-extensions-shutting-down-replace-2027/) [Google Play Games Services v1 Shutdown 2027: Migrate to v2](https://app369.com/blog/play-games-services-v1-shutdown-migrate-to-v2-2027/) [How to Transfer a Firebase Project to a New Owner (2026)](https://app369.com/blog/transfer-firebase-project-new-owner-2026/)
## **Related guides **
[**Firebase Deprecations: Every Shutdown Date, 2024 to 2027**
Firebase deprecations from 2024 to 2027 in one dated table: what stops working, the deadline, and what to move to, from Firebase docs checked Oct 21, 2026.**Read more **](https://app369.com/blog/firebase-deprecations-shutdown-dates-2026/) [**App Store and Google Play Deadlines for 2026 and 2027**
Dated table of App Store, Google Play, Firebase and Google API deadlines for mobile apps in 2026 and 2027, each linked to its source. Checked Oct 21, 2026.** Read more **](https://app369.com/blog/app-store-google-play-deadlines-2026-2027/) [**Builder.ai Shut Down: What to Do With the App It Built for You**
Builder.ai alternative: Builder.ai entered insolvency in May 2025. What it means for an app it built for you, and how to keep the app, listings and data yours.** Read more **](https://app369.com/blog/builder-ai-shut-down-what-to-do-with-your-app-2026/)