Move your Bolt project into EzCoder
A Bolt export is an ordinary front-end project. Of the four platforms here it is the one that arrives closest to something that simply runs, because Bolt does not leave an SDK behind that points at its own backend.
Getting the code out
What the export contains: Vite with React and Tailwind CSS — a standard tree with no runtime tie back to Bolt.
- Use Bolt’s export action to download the project. You get a .zip archive of the whole tree.
- Do not unzip it. EzCoder takes the archive as it comes.
- In EzCoder, choose ZIP upload and select the file.
Import source to choose in EzCoder: ZIP upload. Platform interfaces change; if a control has been renamed since this page was written, look for the action that gives you the outcome each step describes.
Your keys do not come with the export
Anything you configured through Bolt’s interface rather than in a file — API keys, tokens, service URLs — stays behind. The code that reads them arrives; the values do not. EzCoder reads the variable names out of your code and gives you the list to fill back in, encrypted, before you run the app.
The Bolt files EzCoder targets
EzCoder recognizes a Bolt project by these marker files, and these are the Bolt-specific paths it targets for removal so you do not inherit config for a platform you have left.
Recognized by.bolt/bolt.config.js
Targeted for removal.boltbolt.config.js
This page is the same for everyone, so it can only tell you the list the importer carries. Anything actually removed from your project is itemised on the import result screen when the import finishes. If that screen itemises nothing, nothing was removed — the files above are still in your tree, and deleting them is a one-line ask to the AI once the project opens.
node_modules, .git, dist, build and .next are dropped as well, for every import regardless of platform.
What you get on the other side
- A Vite project with your components, routes and Tailwind setup intact.
- A checklist of every environment variable your code refers to, waiting for values.
- The Bolt config paths listed above on the importer’s cleanup list. Bolt does not leave an SDK behind, so once its config is gone there is nothing still calling Bolt — but a mention of Bolt inside your own source stays until you change it.
Coming from somewhere else
Bring it over
Import is open on every plan, including the free one.