Join us on Discord
Move from Bolt: step-by-step migration guides
Your Bolt app can run somewhere else and keep its backend. Choose where to go next and we'll walk you through every step.
Choose your destination
Keep building your Bolt app with
Host your Bolt app on
What happens to your app when you leave Bolt?
Bolt syncs your code to GitHub, and that code is yours. A Bolt Cloud backend stays in Bolt for now.
What you can keep
- Your app's code. Bolt syncs it to your GitHub repository both ways.
- Images and other files in the project folder.
- Your own Supabase project. Older Bolt projects use one, and it stays yours.
What doesn't move automatically
- Your Bolt Cloud database. Bolt has no supported way to move it to Supabase yet.
- API keys and secrets. Bolt keeps them under Secrets, not in the code.
- Your Bolt address. That stays with Bolt.
- Bolt chat history. It doesn't come with your code.
Our guides walk you through four stages
Your setup
Answer a few questions to get steps tailored to your app.
Preparation
Set up the accounts and tools needed for migration.
Migration
Follow the instructions and check the result of each step.
Final check
Test everything before switching. Your Bolt app stays online until you're ready.
Before you start
Export your data first
If the app runs on Bolt Cloud, export the row data of each table. Keep the files until the new setup has run for a while.
Connect GitHub
Click the GitHub icon in Bolt and create a repository. Every route starts from it.
Find your backend keys
The app on your computer needs the address and the public key of its backend.
Additional resources for your Bolt migration
All guidesExports and the parts that break most often. Each article links back to the step-by-step route it belongs to.
Your Bolt app, built by Vercel
Bolt to a repo you ownvs
Bolt Cloud or your own SupabaseMore Bolt articles are coming
Tell us what you are stuck on and we will write it up next.
Send feedback