ERR-108/stack trace

ERR-108

How to migrate off Bolt.new and deploy independently (2026)

How to migrate off Bolt.new and deploy independently (2026)

Last updated 17 April 2026 · 10 min read · By Hyder Shah

Emergency triage — $299 Free diagnostic

Direct answer

Bolt.new code is yours — it runs in StackBlitz but can be exported and deployed to Vercel, Netlify, or Railway. The code export itself is easy. The hard parts: (1) your Supabase instance might be auto-created and need manual export, (2) your environment variables exist only in StackBlitz’s context, (3) your deploy target needs different configuration than StackBlitz’s auto-setup. This guide walks every step.

Quick fix for How to migrate off Bolt.new and

Start here

Step 1 — Export your code

In StackBlitz, click the hamburger menu → Download Project. This gives you a ZIP of the full codebase.

Unzip it, run npm installlocally. If it doesn’t run with npm run dev, fix those errors first before attempting to deploy.

Deeper fixes when the quick fix fails

02
Step 2 — Migrate your Supabase database
If Bolt auto-created a Supabase project: go to supabase.com, find your project, go to Settings → Database → Connection String.
Export your data with pg_dump. Create a new Supabase project (your project, with your credentials). Import the data. Update your env vars to point at the new project.
03
Step 3 — Configure environment variables
Create .env.local with:
```
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...
SUPABASE_SERVICE_ROLE_KEY=...
STRIPE_SECRET_KEY=...
STRIPE_WEBHOOK_SECRET=...
```
Test locally with npm run dev. Then add the same variables to your Vercel project: Settings → Environment Variables.
04
Step 4 — Deploy to Vercel
Push your code to GitHub. Connect the repo to Vercel. Set the framework to Next.js (or your actual framework). Verify the build command matches your package.json.
Deploy. Check Vercel build logs for errors — most failures at this step are missing env vars.

Other migration targets

The same process works for Netlify (use dist or .next as publish dir), Railway (auto-detects framework), and Render. The code export stays the same; only the deploy target configuration changes.

Why AI-built apps hit How to migrate off Bolt.new and

Bolt.new runs in StackBlitz WebContainers, which auto-inject environment variables, auto-configure Supabase connections, and handle CORS automatically. When you export, none of that follows you. You’re starting fresh on a real hosting environment.

That’s why the same users who report “every new deployment deploys into another universe rather than updating the existing site” struggle with migration: the code works in preview because StackBlitz props it up. On Vercel or Netlify, you have to wire every connection by hand.

“Every new deployment deploys into another universe rather than updating the existing site.”

Reddit — r/bolt

Diagnose How to migrate off Bolt.new and by failure mode

Follow these steps in order. Each step has a common failure mode noted.

Step	Common failure	Prevention
Export code from StackBlitz	Missing files not tracked in StackBlitz	Download full ZIP, not copy-paste
Set up Supabase outside Bolt	Using Bolt's auto-created project with lost credentials	Export database, create new project
Configure env vars on Vercel	Forgetting NEXT_PUBLIC_ prefix for client-side vars	Copy from Supabase project settings
Deploy to Vercel	Build fails due to missing dependencies	Run npm install locally first

Related errors we fix

Still stuck with How to migrate off Bolt.new and?

Emergency triage · $299 · 48h turnaround

We restore service and write the root-cause report.

If any of these apply, a fixed-price migration will get you off Bolt in 48 hours:

→You've been stuck on the migration for >8 hours
→You don't have admin access to your Supabase project
→Your production deploy keeps failing with env var errors
→You need custom domain, SSL, and monitoring set up

start the triage →

Free Rescue Diagnostic

$0

30-min call, we scope the migration

Emergency Triage

$299 · 48h

Fix one blocking migration issue

Deployment & Launch

From $1,999

Full migration off Bolt.new + monitoring

Security Audit

$499 · 48h

Lock down RLS, secrets, webhooks post-migration

How to migrate off Bolt.new and questions

Can I export my Bolt.new code and own it completely?+

Yes. Bolt.new gives you a Download Project button in the StackBlitz menu. The ZIP contains the full codebase including package.json, config files, and source. You own the code — Bolt's license doesn't restrict where you deploy it. The only thing you don't own automatically is the Supabase instance if Bolt auto-created one.

What's the fastest way to get off Bolt.new?+

Download the ZIP, run npm install locally, fix any missing env vars, push to GitHub, connect to Vercel. Most teams finish in under 2 hours. The long pole is usually migrating Supabase data — a pg_dump + pg_restore takes 15 minutes for a small database but can uncover RLS, foreign key, and extension issues that need manual fixes.

Do I need to migrate Supabase if Bolt set it up for me?+

Yes, if you want full ownership. Bolt's auto-created Supabase projects are tied to Bolt's account infrastructure, and you may not have admin access to rotate keys, configure backups, or upgrade the plan. Create a new Supabase project in your own organisation, export data with pg_dump, import with psql, update connection strings.

Why does my app break after migrating off Bolt.new?+

Three common causes: (1) env vars missing on the new host — Bolt auto-injects them, Vercel does not, (2) CORS errors because the new domain isn't in Supabase's allowed origins, (3) OAuth redirect URLs still point at the Bolt preview domain. Fix all three before declaring the migration complete.

Can I deploy my Bolt.new app to Netlify instead of Vercel?+

Yes. The export process is identical. On Netlify, set build command to npm run build, publish directory to dist (Vite) or .next (Next.js). Add a _redirects file with /* /index.html 200 for SPA routing. Copy env vars into Netlify Environment Variables. The code is framework-native — it doesn't care which host runs it.

What does a full Bolt.new migration cost?+

Self-service migration is free — just your time, typically 2-8 hours. Hiring it out: a Deployment & Launch package at $1,999 covers code export, Supabase migration, env var setup, DNS, SSL, and production monitoring. Most teams pay for this to skip the debugging cycle and launch in 48 hours with a known-good production environment.

Next step

Ship the fix. Keep the fix.

Emergency Triage restores service in 48 hours. Break the Fix Loop rebuilds CI so this error cannot ship again.

Emergency triage — $299 Free diagnostic

About the author

Hyder Shah leads Afterbuild Labs, shipping production rescues for apps built in Lovable, Bolt.new, Cursor, Replit, v0, and Base44. our rescue methodology.

How to migrate off Bolt.new and experts

If this problem keeps coming back, you probably need ongoing expertise in the underlying stack.