Short answer
Download a copy, then connect a GitHub repository so the code lives in an account you own. Move the database by claiming your Bolt Database in Supabase, which needs a Pro or Teams plan and a Supabase org owner, rather than connecting a fresh Supabase database, which can lose data. Deploy the repository to your new host, add the environment variables there, and move the custom domain. Then test sign-in, emails, payments and webhooks before you switch users over.
The move, in the order that keeps the app working
01
Keep a copy first
“You can download a copy of your site to use locally or to restore it in Bolt later.” Bolt, Rollback and backup
Download the project from its title menu so there’s a known version to go back to. Bolt says restoring an earlier version doesn’t change your Bolt or Supabase database, so the copy protects the code, not the data: leave the database untouched until the new setup has served real traffic.
02
Get the code into a repository you own
“Connect a GitHub repo to your Bolt project to back up code, sync commits automatically, work across branches, and keep your project current in both Bolt and GitHub.” Bolt, GitHub integration
Connect a GitHub repository and Bolt commits your changes there automatically. Your new host builds from that repository, and you keep the history.
03
Claim the database, don’t replace it
“If your project already has a Bolt database, connecting a Supabase database will replace the connection, which may cause data loss.” Bolt, Supabase integration
The supported path is claiming your Bolt Database in Supabase, which Bolt says lets you migrate an existing Bolt database to Supabase. It needs a Pro or Teams plan, and the person claiming it must be the Supabase organization owner. Connecting a different Supabase database instead swaps the connection and can lose the data you have.
04
Deploy the repository on the new host
“Add a redirect rule so client-side routes survive a page refresh.” Netlify, Deploy your Bolt app to Netlify
On Netlify, add a new site, import the repository and confirm the build settings: for a Vite app, the build command is npm run build and the publish directory is dist. Add a public/_redirects file containing /* /index.html 200 so pages still load when someone refreshes them.
05
Add the environment variables
“Bolt stores these in its own environment; Netlify does not see them until you add them.” Netlify, Deploy your Bolt app to Netlify
Keys and URLs your app depends on, such as the Supabase URL and key, don’t travel with the code. Add each one on the new host with the prefix your framework expects (VITE_ for Vite, NEXT_PUBLIC_ for Next.js), then rebuild so the values reach the app.
06
Move the custom domain last
“Custom domains don't carry over between Bolt and Netlify automatically.” Bolt, Netlify integration
If the project is on Bolt hosting with a custom domain, Bolt says to disconnect the domain, then unpublish, and add the domain again on the new host. Unpublishing takes the Bolt site down, so pick a quiet window. From our own checklist, not Bolt’s: update the sign-in redirect URLs and the Stripe webhook endpoint that still point at the old address.
Checked against the vendor’s docs on : Bolt help: GitHub integration; Bolt help: Supabase integration and claiming your database; Bolt help: Netlify integration and switching hosts; Bolt help: Rollback and backup; Netlify: Deploy your Bolt app to Netlify.
Rather hand it over?
Start with a paid consultation to agree the plan, then get a written quote with a fixed price.
- $100 per 15 minutesPaid consultationGo through the app and the move with Simon and agree the plan.Book a consultation
- Written quoteDescribe the app, such as its database, sign-in providers, payments and domain, and get a fixed price and timeline in writing; we reply by email, usually within one business day.Describe your project
Related: Hire a Bolt developer · Build failed on Netlify or Vercel · Supabase auth email links go to localhost · Stripe webhook signature verification failed