Bubble.io App Import: how to move a Lovable, v0, Replit or Bolt app to Bubble
Short answer: Bubble App Import lets you upload a .zip or .html export of an app built with Lovable, v0, Replit, Bolt, Base44 or Claude, and Bubble rebuilds it as a Bubble app you can edit visually or with the Bubble AI Agent. It's in beta and available to a subset of users for now. It brings over the interface, the app logic, assets and structure. API keys, database records and connected services such as a Supabase database usually don't come with the export, so you reconnect those yourself. You'll still need to review privacy rules, data and integrations before real users arrive.
Until this month, moving an AI prototype to Bubble.io meant rebuilding it by hand, with the prototype as the specification. That's what we wrote in our Lovable-to-Bubble migration guide. Bubble has now announced App Import, which does a large part of that rebuild automatically.
What Bubble App Import is
Import takes the codebase of an app built somewhere else and converts it into a Bubble app. Bubble's pitch is "You built a prototype. Now build the business", with a real database, logic you can read and change, and hosting included. After the import you land in the Bubble editor, and from there you keep building visually or with the AI Agent, backend included.
According to the manual, Import brings over four things:
- The interface: visual elements and styling
- The code: application logic and configuration
- Assets: images and related files
- App structure: how the pages and components fit together
When the source code defines a database, Bubble creates the database structure from it. That's the structure only, not the records (more on that below).
Which platforms are supported, and how to export
Bubble names Lovable, v0, Base44, Replit and Claude in the manual, and Bolt and GitHub on the announcement page. The manual adds that Import "works with a standard codebase, so it isn't strictly limited to these platforms", as long as you can export a ZIP or reach the repository.
| Built with | How to get a file Bubble accepts |
|---|---|
| Lovable | "Download codebase" (paid Lovable plans only), or connect Lovable to GitHub and download the repository as a ZIP |
| v0, Replit, Bolt, Base44 | Use the platform's download or export option, or connect it to GitHub and download the ZIP from there |
| Any GitHub repository | Green Code button → Download ZIP |
| Claude Code, Codex, Cursor | No file needed: connect the agent to the Bubble MCP and let it rebuild the app in Bubble (see below) |
One tip from Bubble's FAQ is easy to miss: export the full project folder, not just the build output. A built bundle has lost most of the structure Bubble needs to understand the app.
How it works: upload or MCP
Method 1: upload in Bubble
- Export your app as a .zip (or a single .html file) from the platform you built it on.
- Upload it at bubble.io/import while logged in. You can drag and drop the file.
- Wait for the conversion. Bubble says the time depends on the size and complexity of the project.
- Open the editor. You're redirected into Bubble and can keep building with the AI Agent or by hand.
Method 2: rebuild through the Bubble MCP
If you work with Claude Code, Codex or Cursor, you can connect the agent to the Bubble MCP, give it your codebase and let it recreate the app using Bubble elements. The difference that matters: usage is billed by your AI provider, not in Bubble AI credits.
| Upload in Bubble | Rebuild via MCP | |
|---|---|---|
| What you need | A .zip or .html export | Claude Code, Codex or Cursor connected to the Bubble MCP |
| Who does the conversion | Bubble | Your AI agent, step by step |
| Who pays for the AI | Not stated by Bubble | Your AI provider account |
| Best for | Founders with an export from an AI app builder | Builders already working in an agentic environment |
What gets imported and what doesn't
The announcement page promises "nothing to rebuild". The manual is more careful: "An exported codebase often isn't complete on its own. Some platforms leave out things like API keys, database contents, or connected services (a Supabase database, for example)." In practice, plan for this split:
| Part of your app | Imported? | What you do |
|---|---|---|
| Screens, layout and styling | Yes | Check them on desktop and mobile |
| App logic and configuration | Yes, converted | Test every workflow, especially the ones that change data |
| Images and assets | Yes | Check that file links work |
| Database structure | Created from the code | Review data types and fields before adding data |
| Database records | Usually not | Import separately, for example with CSV import |
| API keys and secrets | Usually not | Add them again in the API Connector, marked private |
| Supabase and other connected services | Usually not | Move the data into Bubble, or reconnect the service |
| User passwords | Not covered by Bubble's docs | In our migrations, password hashes can't be moved, so users set a new password |
After the import: a checklist before real users arrive
Import gets you into the editor. These steps get you to an app you can launch. This list is from our own Bubble.io migrations, not from Bubble's docs:
- Review the data model. AI-generated schemas often duplicate data or store lists in the wrong place. Fix the data types before you import any records, because everything else builds on them.
- Set privacy rules on every data type that holds personal or business data, then run Bubble's security dashboard. Turn off the Data API for types that don't need it.
- Move secrets to the server. Add API keys in the API Connector, mark them private, and rotate any key that was ever in front-end code.
- Import data into the development database first. Check relationships, dates and file links before you touch live.
- Plan the user move. Import accounts, then email users on launch day so they can set a new password.
- Reconnect payments and email. Stripe keys and webhooks, transactional email and any automations the old app called.
- Test like an outsider. Log out and open every page, then log in as one user and try to open another user's records by changing the ID in the URL.
- Watch workload units. Converted logic isn't always efficient. Check the usage logs on development before you pick a plan (how Bubble pricing and workload units work).
- Deploy to live, and keep the old app read-only for a week or two, so nothing gets lost.
If the imported app also has AI features, such as a chatbot or document analysis, the API calls need to move server-side with usage limits. We cover that in AI features for Bubble.io apps.
What Bubble hasn't said yet
Import is a beta, and some answers aren't public yet. As of October 21, 2026, Bubble's pages don't specify:
- Who gets access and when. Access is rolling out to a subset of users. If you don't see the upload option, Import hasn't reached your account yet.
- Cost and plan. No plan requirement or price is listed for the upload method, and nothing says whether the conversion uses AI credits.
- Size limits. Only that larger and more complex projects take longer.
- How complex backend logic converts. For example, scheduled jobs, webhooks or server functions that call several services.
To report a problem, Bubble asks you to contact support through the Agent and include the platform you exported from, the file type and the approximate size of your app.
Should you import your app?
Import is a good bet when…
- Your prototype found users and you want a platform a non-developer can maintain
- Each AI prompt now fixes one thing and breaks another
- You want the backend, database and hosting in one place with one bill
- Import has reached your account and you can test it on a copy first
Slow down when…
- Real users and live payments run on the current app and you can't afford a broken launch day
- Other systems depend on your Supabase database (a hybrid setup may fit better, see our migration guide)
- You're still validating the idea, so the prototype tool is still the cheaper place to change things
- You need native iOS and Android apps: Bubble builds them, but plan that part separately from the web import
Not sure whether to stay on your AI builder at all? Our comparison of Bubble.io vs Lovable, Replit and Bolt covers that decision.
Imported your app? We can finish it
The import does a large part of the build. What's left is what makes an app safe to launch: privacy rules, data, users, payments and testing. That's the work we do every week on Bubble.io expert help:
- A free review of your imported app, with a written estimate in hours within 2 business days
- Fixes from $40/hour, done in development and deployed to live only after you approve them
- One month of free bug fixing after every fix we deliver
Not imported yet? Send us the link to your prototype. We'll tell you whether to import, rebuild or keep what you have.
Frequently asked questions
What is Bubble App Import?
Bubble App Import is a beta feature that converts an app built on another platform into a Bubble app. You upload a .zip or .html export of the project, Bubble rebuilds the interface, logic, assets and structure, and you continue in the Bubble editor, visually or with the Bubble AI Agent.
Can I import my Lovable app into Bubble.io?
Yes, if Import has reached your account. Export the code with Lovable's Download codebase option (paid Lovable plans) or through GitHub as a ZIP, then upload it at bubble.io/import. Data in Supabase and API keys are usually not in the export, so you move the data and reconnect the keys separately.
Does Bubble import my database and users?
Bubble creates the database structure from your source code, but records that live in an external database such as Supabase are not part of the export and must be imported separately, for example with Bubble's CSV import. Passwords can't be carried over in our experience, so users set a new one on launch day.
Is Bubble App Import available to everyone?
Not yet. As of October 2026, Import is in beta and available to a subset of users, with access rolling out over time. Bubble hasn't published a price or plan requirement for it. If you use Claude Code, Codex or Cursor, you can also rebuild an app through the Bubble MCP, with usage billed by your AI provider.
Is an imported app ready to launch?
Usually not straight away. Review the data model, set privacy rules on every data type, add API keys in the API Connector, import and check the data, reconnect payments, and test the app logged out and as different users before real users arrive.
Sources: bubble.io/import · Bubble manual: App import · Bubble support: App import. Checked October 21, 2026.
Co-founder and CEO of Webziper. Since 2019 he has led 150+ Bubble.io projects for founders worldwide, from scoping and estimates to launch and support. LinkedIn →