Skip to content

Move a tool out of Bolt and share it elsewhere, with its data (2026)

Your tool was born in Bolt, and now the whole team uses it. Keeping it elsewhere requires neither rebuilding it nor knowing how to code: its code leaves through GitHub, and your AI handles the rest. Here is the path, data included.

By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 18, 2026.

View as Markdown

Move a tool out of Bolt with its data: the code retrieved through GitHub, the data brought along, and the tool shared on while with colleagues without a Bolt account and a client with a password

Your tool was born in Bolt: you described it, it worked, and now the whole team uses it. Bolt hosts it, but for a team, its Teams plan counts each member, and company sign-in only comes with Enterprise2. Moving the tool out, though, requires neither rebuilding it nor knowing how to code.

The short version. Connect the project to GitHub in Bolt, have your AI export the data, then give it the repository so it puts the tool on while. Your colleagues use it with their email account, a client with a password, and the data is backed up every day in France.

What you take with you, and what to prepare

What leavesHow
The tool’s codeThrough Bolt’s GitHub integration, with the full history
The dataExported as CSV by your AI, then brought into while
SettingsThe credentials of your other software, to enter again in while

Move the tool out of Bolt, in four steps

The switch happens in one conversation with your AI, without a line of code to write.

  1. Connect GitHub. In the project, click the GitHub icon at the top right, sign in with your personal GitHub account, authorize Bolt and install its GitHub app. Only the project owner can do this1.
  2. Export the data. Ask your AI to export what the tool keeps as CSV: the rows the team entered, the clients, the orders.
  3. Give the repository to your AI. Claude, ChatGPT or Cursor puts the tool on while, brings in the data from the CSV, and gives you its address. Without a while account, it does so as a trial, for free, and gives you a link to keep it.
  4. Choose who uses it. Keep the tool for your colleagues, share it with a client, then tell the team its new address.

You, to your AI: Here is the GitHub repository of the tool Bolt built for me, and the export of its data. Put it on while, bring in the data, and keep it for the team.

The steps to move a tool out of Bolt: the code retrieved through GitHub, the data exported as CSV, the message given to your AI, and the tool running on while with its data backed up
The code through GitHub, the data as CSV, and your AI putting the tool on while.

What the tool gains on while

  • Your colleagues sign in with a while account for up to 3 people, or, on the Pro plan, with their email account, Google or Microsoft, whatever their number. See keep a tool for your colleagues.
  • A client uses the tool with an access link and a password, valid for 1, 7 or 30 days.
  • The data is backed up every day, and goes back to any moment in the last 14 days, once a person has approved it.
  • The credentials of your other software stay in while, and your AI never sees them. Your tools are hosted in France by Nextmap.

For a detailed comparison, read Bolt vs while, and for Bolt against Lovable, Lovable vs Bolt.

Try it with your tool

Give this message to your AI, then the link to your GitHub repository. The trial is free, with no sign-up, and your tool has its address in 3 minutes.

The message to give your AI
Read while.sh/agents and help me get started with while.

Sources

  1. Bolt, GitHub integration, accessed November 18, 2026
  2. Bolt, Pricing, accessed November 18, 2026

Questions

Can you get the code of a Bolt tool?

Yes. Bolt connects to GitHub from the project, with a personal GitHub account, and keeps the code there with the full history of its changes1.

Who can connect GitHub?

Only the project owner: they connect and manage the GitHub integration1.

What about the tool’s data?

Before leaving, ask your AI to export the tool’s data as CSV, then bring it into while. On while, it is then backed up every day.

Do you need to code?

No. You connect GitHub in Bolt, then give the repository to your AI, Claude or Cursor, which puts the tool on while.

Why move a tool out of Bolt?

So your colleagues use it without a Bolt account and without a per-member price, to share it with a client through a password, and to keep its data backed up in France.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh