Contents
Bubble does not export an app’s code: migrating means rebuilding, reusing the data (CSV, JSON or API export) and the validated screens as requirements. For a business app, plan $6,800 to $22,400 (€6,000–€20,000)excl. VAT and 1 to 3 months, after an audit starting at $660 (€589)excl. VAT.
Bubble lets you build a complete app without writing code, and many companies have launched an internal tool or a first product that way. Growth tends to bring the same questions: performance, platform costs, dependence on a single tool, the wish to hire developers. Answering them means being clear on one point: a Bubble app does not “convert” into code. Here is what Bubble lets you recover, how a rebuild works, and when it is worth it.
What Bubble actually lets you export
Bubble’s documentation is explicit (checked in October 2026).
| Item | Exportable? | What the official documentation says |
|---|---|---|
| Application code | No | Bubble apps only run on Bubble; there is no way to export them as code (application and data ownership) |
| User-created data | Yes | Export from the Data tab as CSV, JSON or NDJSON, delivered by email |
| Programmatic data access | Yes | Through the Bubble API, for extraction scripts |
| Uploaded files | Needs planning | Links are in the data; files must be downloaded and re-imported |
| Logic (workflows, rules) | No | Rebuilt from the existing app |
Bubble states that you own your data and your app’s design, but that Bubble retains ownership of the underlying code. The documentation also says that if Bubble were discontinued, its source code would be released under an open-source license. That is a continuity safeguard, not a migration path.
A technical detail worth knowing: according to the same documentation, date interval fields export as text (“2 days”) rather than in their internal format. Details like this are handled during data migration.
The rebuild method
Rebuilding does not mean starting from a blank page. The Bubble app is a living specification: every screen, workflow and privacy rule has been tested by your users.
- Inventory. I list the data types, screens, workflows, privacy rules and integrations (payments, email, external APIs).
- Data model. I translate Bubble data types into clean PostgreSQL tables with explicit relationships. This is often where duplicates and repurposed fields get fixed.
- Rebuild in batches. The most-used modules first, tested by your team on real imported data.
- Trial data migration, then the final migration just before the switch.
- Switch-over at a quiet time, with Bubble kept read-only for a few days just in case.
The target stack is the one I use every day: React, TypeScript, Node.js, Supabase (PostgreSQL). The code and rights are transferred to you once paid in full: you are not trading one dependency for another.
The pitfalls to anticipate
- Privacy rules. In Bubble, part of the security relies on privacy rules. They must be translated one by one into database-level access rules. Forgetting them means exposing data.
- Plugins. Each Bubble plugin hides a feature (payments, PDFs, maps) that needs a proper integration.
- Scheduled workflows. Reminders, nightly calculations, cleanups: they are easy to forget because they are invisible on screen.
- User accounts. Check what can be carried over and plan a reset if needed.
What a Bubble migration costs
| Step | Price | Timeline |
|---|---|---|
| Audit of the Bubble app | Express audit $660 (€589)excl. VAT, full audit $2,300 (€1,990)excl. VAT | A few days to 7 days |
| Rebuild of a business app | $6,800 to $22,400 (€6,000–€20,000)excl. VAT | 1 to 3 months |
| Multi-area platform (clients, partners, staff) | Quoted individually, often from $16,800 (€15,000)excl. VAT in the estimator | 3 to 6 months or more |
| Data migration | Data migration module: $900 (€800)excl. VAT in the estimator | Within the schedule |
The estimator applies a 0.85 factor when a prototype exists, because the definition work has already been done. For your case, use the estimator. During the rebuild, the Bubble subscription remains your cost; afterwards, it is hosting (a few tens to a few hundred euros a year) and maintenance.
When to stay on Bubble
I will be straightforward: if your Bubble app handles the load, the platform cost stays reasonable and you do not need complex integrations, stay. A migration costs money and time, and it is only justified if it solves a real problem: slowness, a bill that climbs with usage, security that is hard to control, features Bubble handles poorly, or a client requirement about code ownership. The guide on custom vs no-code helps you set those criteria.
Where to start
- Export your data from the Data tab, to see what you have and what state it is in.
- List the pain points: what is slow, what costs money, what breaks.
- Ask for an audit through my AI and no-code project takeover offer: you get an inventory and a costed plan.
- Decide between staying, migrating module by module or rebuilding entirely, with a fixed quote after scoping.
Frequently asked questions
Can we migrate without interrupting service?
Yes, that is the norm. The new app is built and tested in parallel, data is migrated once for testing and a final time just before the switch. Downtime is limited to a few hours, scheduled at a quiet time.
Will users keep their passwords?
That needs checking during scoping, based on what the export allows. If passwords cannot be carried over, we plan a reset procedure: an email inviting each user to set a new password the first time they open the new app.
Should we keep Bubble during the migration?
Yes, until the switch. The Bubble subscription continues while the rebuild is under way, so include it in the budget. Once the new app is in production and the data has been checked, the old one can be shut down.
Will the new app be identical to the old one?
It keeps what works, but it is a chance to fix what got in the way: slow screens, unnecessary steps, rules people worked around. I advise against changing everything at once: the same logic for users, a sound technical base underneath.