Migration guide

How to migrate from Bolt.new to Bolt.diy

AI chat conversations rarely migrate between different platforms — what usually matters is your history of useful prompts, not the full conversation.

1
Export your conversation history from Bolt.new
If Bolt.new allows it, export your conversations (usually as JSON) before switching — at least as a reference file, even if it can't be re-imported as-is.
2
Set up your model provider in Bolt.diy
Bolt.diy needs you to connect an API key (OpenAI, Anthropic, or a local model) — decide whether to use a cloud provider or local models based on your budget and privacy needs.
3
Recreate your saved prompts and flows
Review your exported history and re-save the prompts, templates or "custom instructions" you used most often in Bolt.diy.
4
Validate response quality with real cases
Test Bolt.diy with 3-5 real tasks you used to solve in Bolt.new before relying on it fully — quality varies depending on the model you connect.

Before cancelling Bolt.new

Before cancelling Bolt.new, confirm you've exported any conversation with information you don't have saved anywhere else.

Ready to deploy Bolt.diy?

Full profile with license, tech stack and ready-to-copy docker-compose.

These steps are a general guideline — the exact export menu can vary depending on Bolt.new's plan and version.

Export your conversation history from Bolt.new