whiskSign in

Guides

Move your Bolt app to Whisk

Bolt gets an app built fast. Moving it somewhere your team can rely on takes a bit more: the code comes out of Bolt, an AI coding assistant on your computer swaps Bolt's sign-in and database for Whisk's, and the app goes online with your team's own logins.

The screens you built in Bolt look and work the same afterwards.

An example

An equipment hire business built a booking app in Bolt. Staff use it to see which trailers, scaffolds and mixers are out, who has them and when they're due back. It started as a test. Now the front counter and the yard both use it all day, and it holds real bookings.

That's the point to move it. The business wants each staff member to sign in as themselves, the bookings backed up, and the app sitting next to its other tools. The rest of this page follows that app.

Three checks before you move

  1. Is the data real? If the app only has test bookings, you can start fresh on Whisk and skip the export.
  2. Where does Bolt keep the data? Most Bolt apps use Bolt's database, which runs on Supabase. Some connect to a Supabase project of your own. Either way, the move works the same, but you export from the place the data actually lives.
  3. Who signs in? Staff, customers or both. Whisk handles both, and the AI needs to know which screens are for whom.

Moving it

Get the code out first. In Bolt, connect the project to GitHub, or download it as a zip file. Either way, put the code on your computer. Bolt's built-in terminal can't run the Whisk command line, so the rest happens there.

If the data is real, export the tables to files and put them in a folder called export inside the project.

Open the project with an AI coding assistant like Claude Code, Cursor or Codex, and give it this prompt:

Read https://whisk.run/skill and follow it to move this Bolt app to Whisk. Keep every screen looking and working the same. Replace Supabase sign-in with Whisk's: people are signed in before they reach the app, and the app reads who they are from Whisk's headers. Move every Supabase database call into a small server part of the app that uses the Postgres database Whisk provides, and create the tables with migrations. Move stored files to Whisk storage. Remove the Supabase settings. Import the exported data in the export folder. Install the whisk command line, run whisk doctor until it passes, then deploy and tell me the web address.

The biggest change is one you won't see. In a Bolt app, the browser often talks to the database directly. On Whisk, the browser talks to a small server part of the app, and only that part touches the database. That's what keeps one person from reading data that isn't theirs.

When the AI runs whisk login, open the web address it shows, sign in to Whisk or create an account, check the code matches, and approve it. The AI then deploys and gives you the app's web address.

For the hire business, the check is simple. Open the app, find a few bookings you know, and make sure the dates and customers are right. Then invite the counter staff and the yard from the app's page in Whisk.

If something doesn't come across

  • A screen is blank. Usually a database call the AI missed. Tell it which screen, and ask it to move that call to the server part.
  • Some rows are missing. Check the export folder has every table. Ask the AI to import the missing file.
  • People can't sign in. Make sure you invited them in Whisk and gave them the app. Whisk only lets in people you've chosen.

After the move

Make changes with your AI coding assistant from now on, and ask it to deploy when you're ready. Bolt's preview expects Bolt's own database, so it won't show the moved app properly.

What it costs

A booking app like this one can run as your free app, which every business gets forever, with up to three staff. If more of the team needs it, or you move other apps too, Starter is $49 (US) a month for 10 apps with no limit on staff. See pricing.