Bolt.new migration services by X & Company
Migrate off Bolt.Keep the code. Own the cloud.
Bolt writes real React code, and you can download it today. The database, users, secrets and hosting live on Bolt Cloud, and that’s the part a ZIP doesn’t carry. X & Company moves all of it to infrastructure you control, and stops the token meter for good.
- Code, data & users moved
- Secrets rotated, not lost
- Zero-surprise cutover
- Fixed-scope quote
~/my-bolt-app — migration audit
- x&co audit ./my-bolt-app
- React + Vite sourceZIP or GitHub
- package.json + .env fileexported
- Bolt Database rows & userson Bolt Cloud
- Secrets panel valuesnot exported
- *.bolt.host deploymentdoes not move
- Version Historystays in Bolt
- x&co migrate --target=your-cloud
Free plan daily token cap300K
Every prompt draws on it. On your own stack, the meter disappears.
Bolt by the numbers
The spec sheet nobody reads until the bill arrives.
Straight from Bolt’s own pricing and help pages. Bolt is a great way to build fast. These are the numbers that start to matter once an app has customers.
- 1Mtokens / mo
- Free plan allowanceWith a 300K daily cap. Every prompt, fix and retry draws from the same pool.[1]
- $25/ mo
- Pro starts at 10M tokensTeams is $30 per member per month. Bigger token bundles cost more.[1]
- 1extra month
- Token rollover windowSince July 1, 2025, unused paid tokens roll over for one additional month, then expire.[1]
- 333Krequests
- Free hosting ceilingPro raises website hosting to 1M web requests. Traffic beyond your plan is the platform’s call.[1]
- 0DB restores
- From Version HistoryBolt’s docs state Version History does not support database restores. Code rolls back, data doesn’t.[2]
- 2code exits
- ZIP download or GitHubBoth carry application code only. The database, secrets and deployment are separate problems.[3]
- [1] Bolt pricing page
- [2] Bolt Help Center: Bolt Database
- [3] Bolt Help Center: projects & files
- Checked September 2026. Plans change; confirm on bolt.new.
Why teams leave Bolt
Fast to build. Expensive to keep renting.
Bolt gets an idea running in minutes, and the code it writes is real. The friction starts once the app has users: the token meter, the managed backend and the limits you can’t tune.
Every change costs tokens
Bolt bills building by the token. Bigger projects send more context with each prompt, so the same small fix gets more expensive as your app grows.
The backend lives on Bolt Cloud
Bolt Database, auth, file storage and server functions are managed for you. The code downloads in a ZIP. The running backend and its data don’t come with it.
Secrets are write-only
Values in the Secrets panel aren’t included in an export. Every API key has to be collected again from its provider, and ideally rotated.
Hosting has a ceiling
Plans cap website hosting by web requests: 333K on Free, 1M on Pro. A launch, a press mention or a busy season doesn’t check your plan first.
Rollbacks skip your data
Version History restores code, not databases. When a prompt runs a bad migration, there’s no one-click undo for the rows it touched.
A browser is not production
Bolt runs your dev environment in the browser on StackBlitz WebContainers. Great for building. Not where you want to debug a customer’s outage.
What a Bolt migration involves
Bolt’s code is portable. Its cloud isn’t.
This is the good news about Bolt: the frontend is standard code you can run anywhere. The work is everything around it. Data, users, keys and hosting need a plan, or the exported app boots up to an empty database and a login page nobody can get past.
Comes with you
- Your full application source (React, Vite and friends) as a ZIP from Export → Download
- A GitHub repository, pushed straight from the Bolt toolbar
- package.json, so npm install rebuilds every dependency
- Variables already defined in the project’s .env file
- Bolt Database tables, one at a time as CSV or JSON, or by claiming the database into your own Supabase organization
Needs a migration plan
- Secrets panel values. They’re write-only and never included in an export
- The running backend: auth sessions, server functions, storage buckets and their files
- Your *.bolt.host URL. A new host means a new address and a DNS plan
- Version History. Only commits you pushed to GitHub travel with you
- Anything the claim flow doesn’t document, like password hashes and bucket files, until it’s verified
migration.diff — what actually changes in a Bolt app
# .env
- VITE_SUPABASE_URL=https://<bolt-managed-project>.supabase.co
+ VITE_SUPABASE_URL=https://<your-project>.supabase.co # or your own Postgres + API
# secrets
- STRIPE_SECRET_KEY=•••••• (Bolt Secrets panel, can’t be read back)
+ STRIPE_SECRET_KEY → rotated, stored in your secret manager
# deploy
- Publish → https://your-app.bolt.host
+ git push origin main → CI → Nginx + Certbot SSL on your serverThe React code barely changes. What changes is where it points, and who holds the keys. That’s the part we plan, test and cut over for you.
The X & Company process
Four steps from Bolt to your own stack.
The same method on every project, whether it’s a small internal tool or a SaaS product with paying customers. You always know what’s happening, what’s next and what it costs.
Audit & plan
We clone your Bolt export and inventory every database table, auth flow, storage bucket, server function and secret. We map what lives in code and what lives on Bolt Cloud, and flag the risks early.
- Dependency inventory
- Target architecture
- Fixed-scope quote & timeline
Stand up your backend
Your own Supabase project or plain PostgreSQL behind a typed API, your auth provider, your storage, and every third-party key re-issued on your accounts. Server functions get ported and tested.
- Database + row-level security
- Auth & storage
- Secrets rotated
Migrate data & users
We claim or export every Bolt Database table, validate it and load it into your new database. Bucket files move to your storage, URLs get rewritten, and users come across without a broken login.
- Row-count reconciliation
- Files moved to your storage
- User onboarding emails
Cut over & hand off
We deploy to your server behind Nginx and SSL, run a final sync, and move traffic off *.bolt.host to your domain with a rollback plan ready. Then we hand over the repo, runbooks and every key.
- Production deploy
- Monitoring & backups
- Docs & knowledge transfer
Bolt Cloud vs. your stack
What changes when you get off Bolt
A fair comparison. Bolt is a strong place to start. Your own stack is where you go when control, cost predictability and uptime start to matter more than build speed.
| Topic | Staying on Bolt | After migration |
|---|---|---|
| Code | Exportable as ZIP or GitHub push | Same code, in your repo with full history |
| Database | Bolt Database on Bolt Cloud; no restores from Version History | Your Postgres with point-in-time backups |
| Auth & users | Managed in Bolt Cloud settings | Your provider, your user table, your rules |
| Secrets | Write-only Secrets panel | Your secret manager, rotated and audited |
| Hosting | *.bolt.host, capped by web requests per plan | AWS, any VPS or on-prem, scaled to traffic |
| Pricing model | Plan + tokens for every AI change | Infrastructure cost you can see and tune |
| Dev environment | Browser-based WebContainers | Local, staging and production you control |
| AI tooling | Bolt’s agent, billed per token | Any tool: Cursor, Claude Code, Copilot |
What you get
A finished migration, not a zip file.
X & Company delivers a working production system on infrastructure you own, and a team that understands how it works.
Talk to X & CompanyYour full source code
A clean repository in your GitHub organization, building and deploying without Bolt.
A production database
Every Bolt Database table moved, with migrations, indexes, row-level security and backups.
Users, preserved
Accounts, roles and ownership carried over, with a smooth sign-in flow for your customers.
Hardened hosting
Your server behind Nginx with Certbot SSL, firewalling and monitoring. AWS, a VPS or on-prem.
A deploy pipeline
Push to main and ship. Staging and production environments you can reason about.
Runbooks & handoff
Docs for deploys, backups, restores and on-call, plus a walkthrough with your team.
Readiness check
Is it time to get off Bolt?
Tick every statement that’s true for your app. It takes 20 seconds.
0/8signals
Check the statements that apply to you.
Your score updates as you go. Nothing is sent anywhere; it all runs in your browser.
Get an expert opinionCost calculator
What does staying on Bolt really cost?
Move the sliders to match your situation. The numbers are illustrative and use your own inputs, and cost is rarely the only reason teams migrate. It still helps to see it.
Free Bolt migration guides
Prefer to do it yourself? Start here.
Everything we’ve learned about getting off Bolt, written up in plain language. If you decide you’d rather have it done for you, we’re one click away.
How to Migrate Off Bolt (Step-by-Step)
The full playbook, from the Export button to switching DNS. Seven steps that cover code, data, users, secrets and hosting.
Read guideHow to Export Your Data from Bolt Database
Tables, users and files. The two ways to get data out of Bolt Database, and how to prove nothing went missing.
Read guideThe Bolt Migration Checklist
Every item to tick off before you cancel your Bolt plan, grouped by code, data, secrets, hosting and cutover day.
Read guideDone for you
Skip the guides. We’ll migrate it.
X & Company takes your Bolt app from audit to live on your own server, for a fixed-scope quote.
Get a free assessment →Questions
Bolt migration FAQ
Can I export my code from Bolt?
Yes. Bolt lets you download the whole project as a ZIP (Export → Download) or push it to a new GitHub repository from the toolbar. It is standard code, usually React with Vite, and npm install rebuilds its dependencies. What the export does not include is your Bolt Database data, secrets from the Secrets panel, or your *.bolt.host deployment.
Will my Bolt app keep working after I export it?
The frontend will build, but it still points at the database, auth and storage running on Bolt Cloud. If you cancel without moving those, the app loses its backend. A real migration moves the database, users and files, re-issues every secret, and redeploys on hosting you control.
How do I get my data out of Bolt Database?
There are two routes. You can export tables one at a time as CSV or JSON, or claim the database into your own Supabase organization from the Advanced settings, which turns it into an ordinary Supabase project you administer. Bolt’s public docs don’t fully spell out what the claim includes for users and storage files, so we verify both before planning the cutover.
What happens to my API keys and secrets?
Values stored in Bolt’s Secrets panel are write-only and are not included in an export. We collect each key from its provider (Stripe, OpenAI, email and so on), rotate it where possible, and store it in your own secret manager.
Why not just keep building on Bolt with a bigger token plan?
For some apps that’s the right call. Bolt bills AI work in tokens, larger projects use more tokens per prompt, and unused paid tokens only roll over for one extra month. Once an app has customers, most teams want predictable infrastructure costs, real backups and a normal deploy pipeline, and they keep using AI tools like Cursor or Claude Code on the exported repo.
How long does a Bolt migration take?
Usually less time than other platforms, because Bolt code is already portable. The scope depends on how many tables, users, storage buckets, server functions and integrations you have. The audit gives you a firm timeline and a fixed quote before any work starts.
Where can I host my app after I leave Bolt?
Anywhere. Common choices are an AWS EC2 instance or a VPS behind Nginx with Certbot SSL, a frontend host like Vercel or Netlify paired with your own Supabase or Postgres, or your own data center when compliance requires it.
Will there be downtime?
Very little. The new stack runs in parallel with your Bolt app while we test it. At cutover there’s a short write freeze for a final data sync, then traffic moves from *.bolt.host to your domain, with a rollback plan ready.
Is this site affiliated with Bolt or StackBlitz?
No. This is an independent resource run by X & Company, a software studio that provides Bolt migration services. Bolt and Bolt.new are trademarks of StackBlitz, Inc.
Ready to migrate off Bolt?
Tell X & Company about your app. You’ll get a straight answer on scope, timeline and cost, and a plan to own your whole stack.