For Bolt apps a team built quickly that now hold customer data or need IT’s approval. We move the app to Next.js in your GitHub, move your database into a Supabase project you own, and set the app up on your hosting with company sign-in. Then we monitor search for 90 days after launch.
Bolt gets an app live fast and runs everything behind it in Bolt Cloud. Moving out means taking each of those pieces with you.
On Pro and Teams plans, Bolt lets you claim the database into your own Supabase account. On other plans, the data has to be exported and the database rebuilt. Either way, sign-in, files, server functions, and hosting still have to move.
Bolt Cloud covers hosting, domains, and databases in one place, along with sign-in, file storage, server functions, and payments, so all of it has to be replaced when you leave.
Bolt says a site that hits its plan’s limit stops displaying publicly until usage resets.
Single sign-on is part of Bolt’s Teams plan, at $27 per member per month billed annually.
Your design and pages carry over. The database, logins, and server code are rebuilt in accounts your company owns.
| Item | What happens | How we handle it |
|---|---|---|
| Pages and design | Moves, with changes | Each route becomes a Next.js page at the same URL, with your existing components and styles kept. |
| Database | Moves, with changes | If your plan allows it, we claim the database into your own Supabase account and check it. If not, we rebuild it in a Supabase project you own and import and count every row. |
| Users and passwords | Moves, with changes | When the database is claimed, we check that user accounts came with it. When it’s rebuilt, Bolt’s docs describe no way to export passwords, so users set a new password once. |
| Server functions | Rebuilt | Rewritten as server code in your Next.js app. |
| File storage | Moves unchanged | Moved to file storage you own, with links updated. |
| Payments | Moves, with changes | Stripe is connected to your own Stripe account in the new app. |
| Company sign-in | Rebuilt | Staff sign in through your identity provider, such as Google Workspace, Microsoft Entra ID, or Okta. |
| Forms and CRM | Moves, with changes | Form leads go to HubSpot, Salesforce, or Marketo instead of staying in the app’s database. |
AI builders get an app working. Before it holds customer data or carries your brand, it also needs what your IT, security, and marketing teams expect from any company system. Your quote lists which of these your app needs.
Staff sign in through your identity provider, such as Google Workspace, Microsoft Entra ID, or Okta. When IT turns off an account, that person can’t sign in again, and session limits end any open session.
We check who can read and change each table, move secret keys out of the browser, and test that one user can’t see another user’s records.
Forms send leads to HubSpot, Salesforce, or Marketo, so nothing is stuck in the app’s own database.
Google Analytics and Tag Manager are set up to respect your consent banner, so tracking matches the rest of your site.
We check the app’s templates against WCAG 2.1 AA before launch and tell you what needs fixing.
The code lives in your GitHub, the hosting and database in your accounts, with notes your engineers can pick up. We monitor search for 90 days after launch, as on every migration.
Redirects and URLs
Most URLs stay the same. The work is making sure users and search engines end up on the new app, not the old one.
Bolt sites get a free address ending in bolt.host. After launch we take it down or point people to the new app, so there aren’t two copies.
If the app uses your own domain, we move it to the new hosting at launch, so bookmarks and links keep working.
Login, invite, and password-reset links point to the new app, so users aren’t sent back to Bolt.
For public pages, we verify the domain, submit the sitemap, and request indexing for key pages at launch.
Next.js runs on the hosting your company already uses. We set it up in your account, not ours.
The company behind Next.js. Preview links for every change and the least setup.
Runs Next.js on Cloudflare Workers with vinext, the setup Cloudflare recommends, which is still in beta. We check your app works with it first and use OpenNext if it doesn’t.
For teams whose security policy requires company-owned infrastructure. We deploy into your account and document how it runs.
01
Send your site. We review it and send a quote and timeline within one business day.
02
We map every old page to its new address, rebuild your templates, and move content, images, and SEO on a private preview site you can check.
03
We compare the old and new sites page by page, point your domain to the new site, tell Google about the new pages, and test each redirect once it’s live.
04
For 90 days we watch which pages Google indexes and how much traffic your moved pages get. Anything our work caused, we fix at no cost, with reports at 30, 60, and 90 days.
Send your site and we’ll quote it within one business day.
For Bolt apps a team built that now hold company data or need IT’s sign-off.
From$3,500
Typical timeline2–4 weeks
“From” is the starting price for the kind of site described. Prices depend on your site’s size and setup. You get a quote before any work starts, and we don’t bill by the hour.
No one can promise how Google will rank your site after a move, including us. What we can promise is the work that protects your rankings, done carefully and put in writing.
Ask us about the guaranteeGoogle decides rankings, not us. Even a careful migration can cause some movement while Google recrawls the new site and works out what changed, and it can take a few weeks to settle.
Google also changes how it ranks sites throughout the year. If an update shifts your traffic, that isn’t something any migration team controls. Anyone who guarantees your rankings is promising something they can’t deliver.
We take every precaution we know of, and we stay accountable after launch.
Every page we can find gets a new home. We collect old addresses from your sitemap, Google Search Console, analytics, and links from other sites. Each one gets a destination: the matching page, the closest match, or a removal you’ve agreed to. You see the full list before launch.
Nothing is removed by accident. Pages you choose to retire are removed on purpose. If any other old link stops working after launch, we fix it.
We watch for 90 days. After launch we track which pages Google indexes, any errors it reports, and traffic to the pages we moved, and we send you a report at 30, 60, and 90 days.
If it’s our mistake, we fix it for free. If something we missed or broke causes a problem in those 90 days, we fix it at no cost.
The guarantee covers our work. It doesn’t cover Google algorithm updates, content you change after launch, pages removed at your request, or problems caused by your host, third-party plugins, or other vendors.
If the app is an internal prototype with no customer data, and your team is happy building in Bolt, staying is often the right call. Bolt’s Teams plan adds single sign-on. Move when the app holds data your company is responsible for, needs to pass a security review, or has to run on accounts your company owns.
Ask if you should stay on BoltCommon questions about moving from Bolt to Next.js. If yours isn’t here, send us your site and ask. You’ll hear back within one business day.
Get a migration quoteFrom $3,500 for apps up to 20 pages with your existing design kept. Apps with a database, logins, or app logic start at $5,500. Company sign-in and CRM connections are scoped in your quote. Apps whose database can’t be claimed cost more, because the database is rebuilt. You get a quote before any work begins.
You can download the code or connect it to GitHub, and on Pro and Teams plans you can claim the database into your own Supabase account. Sign-in, files, server functions, hosting, and the move to Next.js still have to be done and checked, which is the work this migration covers.
Every account moves. When the database can be claimed into your Supabase account, we check that accounts and passwords came with it. When it has to be rebuilt, users set a new password once after launch, and we send the reset emails from your domain.
Yes, for staff. We connect sign-in to your identity provider, such as Google Workspace, Microsoft Entra ID, or Okta, so staff use the accounts they already have. When IT turns off an account, that person can’t sign in again, and we set session limits so any open session ends too. Customers can keep signing in with email or Google.
Before launch we check who can read and change each table, move secret keys out of the browser, and test that one user can’t see another user’s records. The database runs in a Supabase project your company owns.
Yes. Cursor, Claude Code, and similar tools work in a Next.js codebase, and changes go through your GitHub so your engineers can review them.
Your URLs usually stay the same on this move, which keeps the risk low. The things that can hurt rankings here are a leftover bolt.host copy and missing titles or descriptions, and we check both at launch. Expect some movement while Google recrawls. We monitor search for 90 days and fix anything our work caused at no charge. No one can promise rankings, but our guarantee covers our work.
Most apps with up to 20 pages take two to four weeks. Company sign-in and larger data moves add time, and your quote includes the timeline.
Send us your Bolt site. We’ll review it, count the pages, and reply with a quote and timeline within one business day. It’s free, with no obligation.
Get a migration quote