Bubble says its apps can only run on the Bubble platform, and there's no code to export. So leaving Bubble isn't a migration in the usual sense. Your data can come with you, and your app becomes the blueprint for a rebuild on a standard stack.
That's a bigger decision than moving an app that already has code. This guide covers what you can take, what gets rebuilt, the questions to answer before you commit, and how a rebuild usually runs.
What you own, and what you can take
Bubble says you own your app's design and the data your users upload, and that Bubble owns the underlying code that runs the app. In practice, you can take:
- Your database records, exported as CSV, JSON or NDJSON
- Larger data sets, read with scripts through the Bubble API
- Your design, as a reference for the new build
- Your workflows, as the specification for the new logic
What gets rebuilt
- Application logic and workflows
- Pages and responsive layouts
- Plugins, replaced with libraries or direct integrations
- Sign-in, with a plan for moving existing users
Bubble's data export documentation doesn't address passwords. Unless you can establish otherwise for your app, assume users will set a new password after the move, and plan what you'll tell them.
Three questions to answer first
1. Is moving the right call?
If Bubble still does the job, staying can be the better business decision. A rebuild makes sense when cost, performance, ownership or hiring is a real constraint. Be honest about which one is driving you.
2. How much do your plugins hide?
Each plugin is functionality someone has to replace. Complex workflows and plugin-heavy apps are often bigger than they look from the outside, so list every plugin and what it does before anyone estimates the work.
3. Will the data export cleanly?
Bubble exports share a queue with scheduled workflows, so they can be delayed. Date intervals export as descriptive text rather than the stored value. Check types and record counts at the destination, not just that the file arrived.
How a Bubble rebuild usually runs
- Decide if a rebuild makes sense. Review your data, workflows, plugins and users, along with why you want to leave.
- Turn the app into a specification. Write down screens, workflows and rules, and agree what must carry over and what can be simplified.
- Build on a standard stack, in code you own, on a host you choose, with a data model designed around your exported records.
- Load the data and cut over. Load and verify a final export, bring users across as agreed, and move the domain when you're ready.
A partial rebuild can also work if one part of the app is the real constraint. AppExit quotes Bubble rebuilds after reviewing your app, and nothing is charged until you've approved the quote. See the Bubble rebuild guide or tell us about your app.
Frequently asked
Can I export my Bubble app as code?
No. Bubble's documentation says apps can't be exported as code and can only run on the Bubble platform.
Why is a rebuild quoted rather than a flat price?
A flat-price migration moves an app's existing code and database. A Bubble app has no code to move, so the size of the job depends on its workflows, plugins and data.
How do I avoid lock-in next time?
Choose a stack where your code and data live in accounts you own. Our portability checklist covers what to look for.
Sources
Vendor documentation checked November 2026. Plans and export paths can change. AppExit is not affiliated with Bubble.