0
lines of source code you can export
Bubble has no code export. Pages, workflows and logic can’t leave the editor. Only your data can.
Source 3 ↗Bubble migration services by X & Company
Migrate off Bubble.
Finally own your code.
Bubble has no code export. Your pages, workflows and logic only exist inside the Bubble editor. X & Company rebuilds your app as a modern, standard codebase, moves every record, file and user, and runs it on servers you own.
- Rebuilt as code you own
- Every record & file moved
- Users kept, not re-invited
- Fixed-scope quote
Bubble editorLives only on Bubble
- WhenButton “Place order” is clicked
- Step 1Create a new Order…
- Step 2Make changes to Current User…
- Step 3Send email to Current User
orders.tsIn your GitHub
export async function placeOrder(user, cart) {
const order = await db.orders.create({ user, cart });
await db.users.update(user.id, { lastOrder: order.id });
await email.send(user.email, 'order-placed');
return order;
}Bubble, by the numbers
The facts that decide a Bubble migration.
From Bubble’s own pricing page and documentation. None of this makes Bubble a bad tool. It explains why a migration off Bubble is a rebuild, and why the running costs keep climbing as you grow.
$0.30
per 1,000 extra workload units
The overage rate without a workload tier subscription. Every search, workflow and page load consumes WU.
Source 4 ↗175K
WU on Starter
50K on Free, 250K on Growth, 500K on Team. Busy apps burn through it.
Source 1 ↗100
records per Data API call
Getting data out via the API means paging through with a cursor, 100 rows at a time.
Source 2 ↗6 hrs
of server logs on Free
Two days on Starter, 14 on Growth, 20 on Team. Your own stack keeps logs as long as you like.
Source 1 ↗$3
per 100 GB of extra storage, per month
File storage beyond your plan is an add-on. On S3 or R2, you pay the cloud provider directly.
Source 1 ↗- Bubble pricing
- Bubble Docs: Data API requests
- Bubble Forum: “Export your Bubble app’s source code” idea
- Bubble Docs: Pricing and workload FAQ
Checked September 2026. Bubble changes plans from time to time; confirm current numbers on bubble.io.
Why teams leave Bubble
Brilliant for launching. Hard to grow out of.
Bubble let you ship without a developer, and that was the right call. The same abstraction that made it fast is what makes leaving a rebuild, so the sooner you plan it, the cheaper it is.
There is no export button
Your app’s logic lives as Bubble workflows and elements, not code. If you leave, you can take your data. The app itself has to be rebuilt.
You pay for every unit of work
Workload units meter searches, workflows, API calls and page loads. Success costs more, and a single inefficient search can spike the bill.
A database you can’t query
No SQL, no joins you control, no direct backups or read replicas. Reporting means paging through an API 100 records at a time.
A small hiring pool
Bubble developers are a niche. React, TypeScript and Postgres developers, and every AI coding tool, work in standard code.
Performance you can’t tune
Page load, workflow speed and capacity are set by the platform and your plan. You can’t add a cache, an index or a bigger server.
Compliance on someone else’s terms
Data residency, SOC 2 scope and HIPAA questions depend on Bubble’s plan tiers and attestations, not controls you implement and own.
Datais all that exports
What a Bubble migration involves
Migrating off Bubble is a rebuild, not an export.
This surprises a lot of founders. Bubble lets you export your data, but not the app. The upside: you get a clean, modern codebase designed for where your product is now, not a copy of every workaround from year one.
What you can take
- Every data type’s records, table by table, as CSV from the Data tab
- Records through the Data API, paged 100 at a time with a cursor
- Uploaded files, downloaded from their hosted URLs
- User records: emails, names, roles and your custom fields
What gets rebuilt
- Every page, reusable element and responsive layout
- Every workflow, backend workflow and scheduled event
- Privacy rules, which become authorization checks in your API
- Plugins and API Connector calls, re-wired to the real services
- Password hashes, which don’t leave. Plan a reset or magic link
- Relationships between data types, rebuilt as proper foreign keys
The X & Company process
Five steps from Bubble to real code.
A rebuild sounds scary. It doesn’t have to be. The same method on every project, with a fixed scope up front and your live Bubble app untouched until cutover day.
Start with a free auditAudit & scope
We walk through every page, workflow, backend workflow, privacy rule, plugin and API Connector call in your Bubble editor, and every data type and field.
- Feature inventory
- Data model map
- Fixed-scope quote & timeline
Design the data model
Your Bubble data types become a proper relational schema in PostgreSQL, with foreign keys, indexes and constraints. Privacy rules become explicit authorization rules.
- Schema & migrations
- Permission matrix
- Target architecture
Rebuild the app
We rebuild the UI in React and the workflows as a typed API and background jobs, matching what your users know while fixing what never worked well.
- React frontend
- API & background jobs
- Integrations re-wired
Migrate data & users
We pull every record through CSV and the Data API, transform it into the new schema and reconcile row counts. Files move to your storage and users get a smooth sign-in.
- Row-count reconciliation
- Files in your storage
- User onboarding emails
Cut over & hand off
We deploy to your server behind Nginx and SSL, run a final sync, switch your domain with a rollback plan ready, then hand over the repo, runbooks and every key.
- Production deploy
- Monitoring & backups
- Docs & walkthrough
Bubble vs. real code
What changes when you get off Bubble
A fair comparison. Bubble is a strong place to start. A real codebase is where you go when control, cost predictability and performance start to matter more than building without code.
| Topic | Staying on Bubble | After migration |
|---|---|---|
| Code ownership | No code export; the app exists only in the editor | 100% of the code in your repository |
| Logic | Visual workflows and backend workflows | Typed functions you can test, review and version |
| Database | Data types behind the platform; CSV or Data API export | PostgreSQL with SQL, indexes, backups, reporting |
| Pricing model | Plan + workload units; $0.30 per 1K WU overage | Infrastructure cost you can see and tune |
| Performance | Shared capacity set by plan | Caching, indexes and servers sized to your load |
| Logs & debugging | 6 hours to 20 days of server logs by plan | Logs, traces and alerts you keep as long as you want |
| Version control | Bubble branches on higher plans | Git, pull requests and CI on every change |
| Hiring & tooling | Bubble specialists only | Any developer, and every AI coding tool |
What you get
A finished product, not a rewrite spec.
X & Company delivers a working production system on infrastructure you own, and a team that understands how it works.
Talk to X & CompanyYour full source code
A modern React and TypeScript codebase in your GitHub organization, written to be read and extended.
A production database
Your Bubble data types as a real relational schema, with migrations, indexes, backups and every record reconciled.
Users, preserved
Accounts, roles and ownership carried over, with a smooth sign-in flow for your customers.
Hardened hosting
Your server behind Nginx with Certbot SSL, firewalling and monitoring. AWS, a VPS or on-prem.
A deploy pipeline
Push to main and ship. Staging and production environments you can reason about.
Runbooks & handoff
Docs for deploys, backups, restores and on-call, plus a walkthrough with your team.
Readiness check
Is it time to get off Bubble?
Tick every statement that’s true for your app. It takes 20 seconds.
0/8signals
Check the statements that apply to you.
Your score updates as you go. Nothing is sent anywhere; it all runs in your browser.
Get an expert opinionWorkload calculator
What does your Bubble workload really cost?
Enter your plan price and the workload units your app actually uses (it’s in Bubble’s Logs → Workload tab). Overage uses Bubble’s published $0.30 per 1,000 WU rate for apps without a workload tier subscription.
Free Bubble migration guides
Prefer to do it yourself? Start here.
Everything we’ve learned about getting off Bubble, written up in plain language. If you decide you’d rather have it done for you, we’re one click away.
How to Migrate Off Bubble (Step-by-Step)
Bubble has no code export, so leaving means a rebuild. Here's the seven-step method that keeps it predictable.
Read guideHow to Export Your Data from Bubble
Your data is the one thing Bubble lets you take. Here's how to get all of it out, relationships included.
Read guideBubble Workload Units, Explained for Founders
What WU measures, how much each plan includes, what overage costs, and how to tell when it's time to leave.
Read guideDone for you
Skip the guides. We’ll migrate it.
X & Company takes your Bubble app from audit to live on your own server, for a fixed-scope quote.
Get a free assessment →Questions
Bubble migration FAQ
Can I export my code from Bubble?
No. Bubble does not offer a code export. Your pages, workflows, privacy rules and logic exist only inside the Bubble editor and run only on Bubble. What you can export is your data: records from each data type as CSV from the Data tab, or through the Data API, plus the files your users uploaded.
So how do you migrate off Bubble?
By rebuilding the app as real code and moving the data into it. We inventory every page, workflow and data type in your editor, design a proper relational schema, rebuild the frontend and backend in a standard stack (usually React, TypeScript and PostgreSQL), then migrate every record, file and user and switch your domain over.
Isn’t a rebuild expensive?
It is more work than an export, which is why the audit matters: you get a fixed scope and quote before anything starts. Rebuilds are also where teams get to drop years of workarounds. And running costs usually fall, because you pay for servers directly instead of workload units that rise with every search and workflow.
What happens to my users and their passwords?
User records (emails, names, roles and custom fields) come across with your data. Password hashes can’t be exported from Bubble, so we import every user into the new auth system and send a branded “welcome to the new app” email with a password-reset or magic-link. Users keep their accounts and everything they own.
How do workload units affect the decision?
Bubble plans include a monthly workload allowance, from 50K WU on Free to 500K on Team. Every search, workflow, API call and page load uses WU, and apps without a workload tier subscription pay $0.30 for each extra 1,000. As an app grows, WU is often the line item that pushes teams to look at their own stack.
How long does a Bubble migration take?
It depends on the number of pages, workflows, data types, plugins and integrations. A focused internal tool is much faster than a marketplace with payments, messaging and scheduled jobs. The audit gives you a firm timeline before work starts, and your Bubble app keeps running untouched until cutover.
Will my app look and work the same?
It will do the same things, and it can look the same if you want continuity for your users. Many teams use the rebuild to fix what never worked well in Bubble, like slow pages, awkward mobile layouts and fragile workflows, while keeping the flows customers know.
Can I keep building without code after migrating?
You can keep building faster than ever with AI coding tools like Cursor and Claude Code, which work best on a standard codebase. And any developer can pick up the project, instead of only Bubble specialists.
Is this site affiliated with Bubble?
No. This is an independent resource run by X & Company, a software studio that provides Bubble migration services. Bubble is a trademark of Bubble Group, Inc.
Ready to migrate off Bubble?
Tell X & Company about your app. You’ll get a straight answer on scope, timeline and cost, and a plan to own your whole stack.