KodExport FAQ: complete answers to every question

A comprehensive FAQ organized by where you are in your decision journey.

Stage 1: Awareness — “I’m noticing problems with Bubble”

Why is my Bubble app so slow?

Your app probably takes 5-30 seconds to load, and you’re wondering if you did something wrong. You didn’t.

Bubble apps are inherently slower than custom-coded apps because of how they work. Every page load involves loading Bubble’s runtime engine, interpreting your visual logic, and rendering through multiple abstraction layers. That adds seconds to every interaction.

A forum user compared their Bubble app to competitors: “Airbnb loads in 2.5 seconds, booking.com loads in 1.5 seconds” — meanwhile their Bubble app was taking 8 seconds on an iPhone 14 Pro.

You can optimize (reduce data calls, simplify workflows, use better queries), but there’s a floor to how fast a Bubble app can be. If your users are complaining or bouncing, optimization might not be enough.

Why did my Bubble bill suddenly spike?

Workload units. Everything in Bubble costs workload units — conditional statements, page navigations, database searches, API calls. All of it.

And they add up fast. One user reported: “7 million workload units used in less than 12 hours! A big fat auto charge bill on the credit card of $1000.”

Spikes can happen from legitimate growth, bot traffic, inefficient workflows, or even bugs in your logic that create infinite loops. The frustrating part is that diagnosing the cause isn’t straightforward.

If you’ve had one surprise charge, you’ll likely have more. Bubble’s pricing model makes costs unpredictable at scale.

Is Bubble going to keep raising prices?

Nobody knows for sure, but the track record isn’t reassuring. Bubble made major pricing changes that caught users off guard, walked them back partially, then implemented them anyway.

“You don’t make major pricing announcements and walk them back not once, but twice” — viable, Bubble Forum

The pattern suggests Bubble is under pressure to monetize more aggressively. Whether that means future price increases is speculation — but many users aren’t willing to wait and find out.

Can I export my Bubble app as code?

Not using Bubble’s built-in tools. The co-founder Emmanuel confirmed: “Bubble apps can only be run on the Bubble platform; there’s no way of exporting your application as code.”

They’ve also said they have “no plans to build an export tool in the next 1-2 years.”

Third-party services like KodExport can convert your Bubble app to custom code (we convert to Next.js/React), but this isn’t something Bubble offers or supports natively.

Stage 2: Consideration — “Should I migrate off Bubble?”

When does it make sense to migrate off Bubble?

Migration makes sense when one or more of these are true:

• Monthly Bubble costs exceed $200 and are climbing
• Your app takes more than 5 seconds to load
• You’re losing deals due to performance or compliance requirements
• Investors are asking about your tech stack
• You’ve had surprise workload charges and can’t predict costs
• You’re anxious about platform dependency

If your costs are stable under $100, you’re still validating your idea, or you have zero technical resources, staying on Bubble is probably fine for now.

What happens to my users’ passwords when I migrate?

This is a real concern. Bubble doesn’t export hashed passwords in a format other systems can use. You can’t take your users’ login credentials with you.

The solutions:

1. Password reset flow: Require all users to reset passwords after migration. Not ideal, but straightforward.

2. Magic link migration: Implement passwordless login (email magic links) before or after migration. Users click a link instead of entering passwords.

3. Gradual migration: Keep Bubble running in parallel during a transition period. Migrate active users first.

Most apps use option 1 or 2. It’s friction, but it’s one-time friction.

What about my database? Is the structure compatible?

Bubble’s database works differently than traditional relational databases. Bubble uses “objects” with references between them, while most code-based apps use PostgreSQL or MySQL with foreign key relationships.

“tables in Bubble works as Objects, because we relate each table with a reference to the other, not with single Ids like relational databases” — cdmunoz, Bubble Forum

The good news: this is a solvable problem. Your data structure gets mapped to a proper relational schema during migration. We’ve handled migrations with 3+ million records.

The complexity depends on how nested your relationships are and whether you have circular references. A simple app with straightforward tables is easy. An app with heavily interconnected data types takes more care.

What happens to my Bubble plugins?

Plugins are the trickiest part of migration. Some have direct equivalents in the React ecosystem. Others are Bubble-specific and need custom replacement.

Categories:

• Easy to replace: Payment integrations (Stripe), authentication providers, analytics, basic UI components. These have well-established React equivalents.

• Medium effort: Complex map components, advanced charts, some third-party API integrations. Requires finding and integrating appropriate libraries.

• Significant work: Plugins that rely on Bubble’s specific architecture, custom-built plugins unique to your app, or plugins that do things there’s no standard library for.

Before starting migration, we audit your plugins and flag anything that needs special attention. No surprises.

How long does migration actually take?

Typical timelines:

• Simple apps (1-5 pages, basic logic): 1-2 weeks
• Medium complexity (5-15 pages, moderate workflows): 2-4 weeks
• Complex apps (15+ pages, heavy integrations, complex logic): 4-8 weeks

These timelines assume a standard export process. Highly custom requirements or unusual plugin dependencies can extend this.

One forum user who did it themselves reported: “I migrated to code. It wasn’t even that difficult to be honest. One month and I had an app ready for production.”

What if the migration doesn’t work out?

We agree the scope, milestones, monthly fee and terms before any work starts, so you know exactly what is being delivered and what it costs. We’d rather find potential problems while scoping than discover them mid-project, which is why we review your app first. If something is unclear, ask during that conversation: talk to us.

I’m not technical. Can I maintain the code after migration?

Honestly, you’ll need some technical capability — but less than you might think.

The exported code is clean, well-documented Next.js/React. It’s not spaghetti code that only the original developer can understand. Any React developer can work on it.

Options for non-technical founders:

1. AI coding assistants: Tools like Cursor and GitHub Copilot can help you make simple changes without deep coding knowledge. Many non-technical founders use these successfully.

2. Freelancer on retainer: $500-$2,000/month gets you a developer who handles updates, fixes, and small features.

3. Agency relationship: For larger ongoing work, agencies can manage the technical side entirely.

The key difference from Bubble: you’re now hiring from a massive pool of React developers instead of a small pool of Bubble specialists. Competition keeps rates reasonable.

Stage 3: Decision — “I want to migrate, but I’m comparing options”

Why KodExport vs. hiring a dev team to rebuild?

Cost: A full rebuild runs $30,000-$200,000. You pack, we load starts at $1,500 a month and a full-service move at $2,500 a month, each scoped from a $500 inspection.

Time: Rebuilds take 3-12 months. Export takes 1-8 weeks.

Risk: Rebuilds start from scratch — you’re recreating what you already have. Export preserves your existing logic and design.

A rebuild makes sense if you want to fundamentally rearchitect your app or you’ve outgrown your original design. But if your Bubble app works well and you just need it faster/cheaper/owned, export is more efficient.

Why KodExport vs. migrating to WeWeb, Xano, or another no-code platform?

Moving to another no-code platform trades one vendor lock-in for another.

“I switched to weweb and xano 6 months ago for all new projects and it has been an absolute dream” — mitchbaylis, Bubble Forum

Some people are happy with that tradeoff. WeWeb and Xano are good platforms with their own strengths.

But you still don’t own the code. You still depend on another company’s pricing decisions. You still can’t self-host.

KodExport gives you standard, self-owned code. You can host anywhere, hire from the largest developer talent pool, and never worry about platform pricing again.

The right choice depends on your situation. If you love visual development and just need better performance, another no-code platform might be fine. If you want complete independence, you need actual code.

Why Next.js specifically? Why not something else?

Next.js is the most popular React framework for a reason. It offers:

• Server-side rendering for fast initial loads
• Static generation for lightning-fast pages
• Edge deployment for global performance
• Huge ecosystem and community
• Easy deployment on AWS and Cloudflare
• Massive talent pool for hiring

For web apps migrating from Bubble, Next.js is the obvious choice. It handles both simple marketing sites and complex web applications. You won’t outgrow it.

If you specifically need a mobile app, React Native would be the target instead. But for web apps — which most Bubble apps are — Next.js is the standard.

Can I see examples of migrated apps?

Yes: the templates are popular Bubble apps rebuilt as Next.js, with before/after load times, monthly cost and a peek at the code. For your own app, the best validation is a technical review: we’ll show you what the migration would look like for your specific case, not a generic demo.

How much does it cost?

There are two routes:

• Automated export: test one page free, then export up to 200 public pages as a ZIP of static files for $49, once. See pricing and the export tool.
• Site inspection: $500 for a written plan and a fixed quote. See how we move.
• You pack, we load: from $1,500 a month. You build with Claude or Codex; we review, harden and launch.
• Full-service move: from $2,500 a month for the rebuild, data, users and launch. The scope, fee and milestones are agreed before work begins.

Stage 4: Post-Decision — “I’m ready to start”

What do I need to provide to start the migration?

1. Your live app’s address: the public pages are rebuilt from the live app. We only ask for editor access if the agreed scope needs it.
2. Database export: CSV or JSON exports of your data (we can guide you through this)
3. Plugin list: What third-party plugins you use and for what purpose
4. Priority features: Which features are critical vs. nice-to-have
5. Timeline needs: Any deadlines or constraints

Most of this takes an hour to gather.

Will my app have downtime during migration?

No. Your Bubble app keeps running throughout the migration process. Users won’t notice anything.

Once the new version is ready, you’ll test it thoroughly on a staging environment. Only when you’re satisfied do we switch traffic to the new system. This can be instant (DNS change) or gradual (percentage-based rollout).

Zero downtime migrations are standard. We won’t take your production app offline.

What support do I get after migration?

Full-service moves include 30 days of fixes after handoff. Support covers bugs and issues with the migrated code. It doesn’t cover new feature development, which is a separate engagement if you want it.

After that, you’re free to maintain the code yourself, hire your own developers, or continue with us. Your code, your choice.

What if I need changes after migration?

Bug fixes are covered during the 30-day support window. For ongoing development beyond that, we can scope a further engagement. Alternatively, since the code is standard Next.js, any React developer can work on it. You’re not locked into us.

That’s the whole point: after migration, you have options. Unlike Bubble, where you’re dependent on one platform forever.

Technical Questions

What tech stack does KodExport output?

• Frontend: Next.js 15 with React 19
• Styling: Tailwind CSS
• Database: PostgreSQL (or your preferred database)
• Hosting: AWS and Cloudflare, in accounts you own
• API: RESTful endpoints or tRPC depending on complexity

Everything is TypeScript for type safety and maintainability. Code is formatted, documented, and follows modern best practices.

Is the exported code clean and maintainable?

Yes. We don’t just dump a pile of generated code and walk away.

The output is production-ready: properly structured, documented, using standard patterns that any React developer would recognize. We write code the way a senior developer would write it.

That matters because you’ll eventually need to modify or extend this code. If it’s a mess, you’ll pay for that later. We make sure you won’t.

What about SEO? Will my rankings transfer?

If SEO matters to you, we handle:

• URL structure mapping (old URLs → new URLs)
• 301 redirects for any changed paths
• Meta tag migration
• Structured data implementation
• Sitemap generation

This helps your existing rankings carry over. We can also improve SEO during migration since Next.js offers server-side rendering that’s better for search engines than Bubble’s client-rendered approach.

Can you help with the domain/DNS switch?

Yes. We provide detailed instructions for your specific registrar, or we can do it for you if you grant access. The actual switch takes minutes and can be done at low-traffic times to minimize any potential issues.

Pricing & Business Questions

Why is it so much cheaper than hiring a dev team?

Automation. We’ve built tools that convert Bubble app structures to Next.js code. This isn’t 100% automated — there’s always human review and customization — but it eliminates the majority of manual coding work.

A from-scratch rebuild means a developer looking at your Bubble app, understanding what it does, then recreating every feature manually. That takes months.

Export means starting with a working codebase that already matches your app, then refining it. That takes weeks.

Same result, fraction of the time, fraction of the cost.

Can I just export my public pages for less?

Yes. The automated export takes the public pages and assets of a Bubble, Framer, Webflow, WordPress or Wix site and gives you a ZIP of static files: test one page free, then export up to 200 pages for $49, once. It does not move your database, user accounts or workflows. For those, see the full-service move above.

Still have questions? Talk to us, or book an inspection for answers specific to your app.