Bubble to code
Going from Bubble to code means a rebuild, since Bubble exports no code. I rebuild your app on Next.js and Supabase in a repo you own and move your users across with their logins and subscriptions, the way I moved thousands of accounts to a new platform without a single password reset.
Where you are
Your product runs on Bubble, and people pay for it every month. You're asking whether it's time to move to code, and you can't afford to lose anyone on the way.
In August, agencies that build on Bubble wrote on its forum that their clients are moving off it, as AI tools make code easier to work in.
Source Bubble forum, 25 August 2026
What carries over
Bubble lets you export the app's JSON file and your data, and nothing else. So the data moves as data, the design and the logic come over as the spec the new code is written from, and everything that runs is rebuilt.
| In Bubble | In the code |
|---|---|
| Data types and records | Postgres tables on Supabase, loaded from the export, with a last sync on the day of the switch |
| Pages, reusable elements and styles | Next.js pages and components that match the design |
| Workflows | Server actions and API routes |
| Backend workflows and scheduled jobs | Background jobs and scheduled functions |
| Privacy rules | Row-level security in Postgres |
| Plugins | The libraries and APIs the plugins were wrapping |
| The user table | Supabase Auth, with each user's login moved as below |
How your users move
Bubble never gives out its users' passwords, so they can't come over with the data. The Bubble app keeps running beside the new one until the switch, and while it does, each sign-in on the new app is checked against Bubble once. If Bubble accepts it, the password the user typed becomes their password in Supabase, and they never know their sign-in moved. Anyone who hasn't signed in by the switch gets an email with a link that signs them straight in.
Subscriptions live in Stripe, so they stay where they are and each one is linked to its user's new account. That's how AI Toolbar's paying subscribers moved, with no card entered again.
What I do
- Your app rebuilt on Next.js and Supabase in a GitHub repo you own, read page by page and workflow by workflow from your Bubble editor.
- Every privacy rule checked against the row-level security that replaces it, so nobody sees a record Bubble kept from them.
- The new app run beside the Bubble one, with the domain moved on the day of the last data sync.
- Claude Code set up on the repo, with instructions that map each Bubble workflow to the code that replaced it, so the next feature starts as a request.
- A recorded walkthrough of the code and the agent, for you or whoever builds with you.