Migrate from bolt to firebase-studio.
1 documentation-derived translation pattern — what carries over and what to watch for. Cited to the Feature Parity Map; the audit tells you whether the move is worth it.
Both tools turn a natural-language prompt into a running full-stack web app, so a team standardizing on Bolt can retire the Firebase Studio App Prototyping agent. To move an in-progress idea: in Firebase Studio open the workspace, use 'Switch to Code' to confirm the generated files, then Zip & Download (or push to GitHub). In Bolt, either re-describe the app from the same prompt to regenerate natively, or import the exported repo and continue iterating with Bolt's diff-based edits. Recreate any Gemini Developer API / Genkit calls that the Studio app relied on, since Bolt does not provision Google AI keys for you.
- Warning: Firebase Studio's agent currently scaffolds Next.js specifically and auto-wires the Gemini Developer API via Genkit; Bolt generates across many Node.js frameworks (Vite, Next.js, Vue, Svelte) using Claude models by default, so AI-feature code and model wiring must be rebuilt rather than ported verbatim.
- Warning: Publishing differs: Firebase Studio deploys to Firebase App Hosting and requires a Cloud Billing (Blaze) account, whereas Bolt hosts on its own infrastructure with custom domains gated to paid plans — any Firestore/Firebase Auth backend stays in Google Cloud and must be reached as an external service from Bolt.
- Warning: Firebase Studio is being sunset (new workspaces blocked after 2026-06-22, shutdown 2027-03-22), so this is a one-way exit in practice; export source before the deadline rather than relying on the workspace persisting.