01
Find where everything lives
We identify the database, sign-in provider, storage, server functions and environment variables your project uses.
MIGRATE FROM BOLT.NEW
The code is the easy part.
Your backend decides the rest.
Coming soon. We’re launching with Base44 migrations first. Contact us and we’ll let you know when Bolt migrations open.
Bolt.new lets you download a project or connect it to GitHub. What the move really involves depends on where your data, logins and server logic live: Bolt’s own cloud, Supabase, or something else.
Coming soonWE’RE STARTING WITH BASE44
Contact usTO HEAR WHEN BOLT OPENS
WHAT MOVES
What exports,
and what stays behind.
Bolt describes its download as a zip of your project files. Its backups cover the project too, and restoring one doesn’t change your database.
Usually moves
EXPORTABLE- Project files, through a zip download or GitHub
- A web project you can install and run on your own machine
- Row data, exported from the tables in Bolt Database
- Data in Supabase, if your project is already connected to it
Needs separate work
VARIES BY PROJECT- Sign-in and user accounts managed in Bolt Cloud
- Files in Bolt Cloud storage buckets
- Server functions, rebuilt or redeployed for your host
- Environment variables and build settings
THE BOLT CATCH
Three things that
trip up a move.
Two Bolt apps can look identical and need very different migrations. That’s why we start by finding out where everything lives.
Bolt Database has no direct route to Supabase
Bolt says there’s currently no supported way to migrate an existing Bolt database to Supabase. Bolt does describe exporting row data, so we plan the data move table by table and verify it at the destination.
Downloads don’t include your data
A project zip gets you the files, not a working copy of your live app. Bolt’s docs don’t list a complete backend export, so we check what your project really depends on instead of assuming.
Unpublished databases can pause
Bolt says a low-usage database in an unpublished project may pause automatically after six days or more. If your app isn’t live yet, we account for that before planning the export.
THE PATH
How a Bolt
move usually runs.
This is how we expect a move to run once we support this platform. Your current app keeps running until the new one is proven.
02
Get the code building elsewhere
The project goes into a repository you control, and we confirm it builds with the settings your chosen host needs.
03
Move the backend
Data, users, files and functions move to your destination. Row counts and access rules get checked along the way.
04
Verify and switch over
We test the core workflows on the new host, then schedule the final data copy and domain change.
Can’t I just download the zip and host it?
For a simple site with no backend, possibly. If your app has logins or stored data, the downloaded code still needs a database, sign-in and functions to talk to, and those are the parts that need moving.
Does it matter if I use Bolt Database or Supabase?
Yes. If your project already uses your own Supabase account, the backend may be able to stay where it is while the app moves. Bolt Database takes more planning, because Bolt doesn’t document a direct migration path to Supabase.
When can you move Bolt apps?
We’re launching with Base44 first. Contact us and we’ll let you know when Bolt migrations open, along with pricing.
SOURCES
Bolt: manage your projects and downloadsBolt: backups, restore and version historyBolt: Bolt Cloud database
Vendor documentation checked November 2026. Plans and export paths can change, and every app gets its own review. AppExit is not affiliated with Bolt.new. Brand names belong to their owners.
BUILT SOMEWHERE ELSE?
Compare all platforms START HERE
Bolt migrations
are coming soon.
We’re launching with Base44. Tell us about your Bolt app and we’ll let you know as soon as we can move it.
Contact us We’ll reply by email