How do I get my app out of Base44 and running somewhere I control?

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: You can download your Base44 code as a ZIP, but the ZIP is a copy of your code, not a way to move the app. Base44, an AI tool that builds apps from a prompt and hosts them, says the exported code still relies on Base44 to run: your data, logins, backend functions and integrations stay on its platform, and it does not support self-hosting. To run the app somewhere you control, you export the code, export each data table as a CSV, and have a developer replace the backend parts with your own.

Ranjit Bhinge

You want your Base44 app, your data and your users somewhere you own, and you need to know what actually comes out and what has to be rebuilt.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

What you get when you export

People often expect an Export button to hand them a finished app they can upload to any hosting company. With Base44 that is not how it works, and it is better to know before you plan around it.

According to Base44's developer documentation, here is what the ZIP contains:

  • A standard React project built with Vite. (React is a popular way to build web screens. Vite is a tool that packages them.)
  • Your frontend code, which is what users see.
  • Your backend functions, which are the small programs that run on a server.
  • Your data structure: the fields and permissions for each table.

And here is what it does not contain:

  • Your app's data. You export each table as a CSV separately.
  • Your secrets, which are the keys and passwords for outside services.
  • Your app users, meaning the accounts and logins.
  • Your version history. The ZIP holds only the current saved code.

You need a paid plan to export. Base44's documentation says a Builder plan or higher, edit access to the app, and a computer, since the option is not in the phone editor. Check the plans page for what a plan costs now.

Why the code does not run by itself

The documentation is direct about this. The exported code uses the Base44 SDK (a code library) to talk to your app's backend on Base44, for data, logins, backend functions and integrations. If you run the code somewhere else, those things still come from Base44 and use your live app's data. Base44 says it does not support self-hosting, so you cannot run its database, login system and integrations on your own servers.

To run fully outside Base44, someone has to replace those parts with a backend of your own, and change the code that calls them. That is the real work of leaving, and it is a rebuild of the back half of the app. The front half, the screens, usually carries over.

If you have not read it yet, my guide to exporting code from an AI app builder explains why each builder differs, and how to avoid getting locked in covers the longer-term fix.

What a developer has to rebuild

Part of your appWhat Base44 gives youWhat you need instead
ScreensReact and Vite code in the ZIPMostly reusable. Hosted on any frontend host.
DatabaseData structure in the ZIP, data as CSV per tableA database you own, such as Postgres (a widely used free database), with tables built from that structure and the CSVs loaded in.
Logins and usersNot exportedA new login system, and a plan for moving your users (see below).
Backend functionsCode in the ZIPRewritten to run on your own server or a serverless host.
Integrations (email, AI, files)Base44's built-in integrations layerDirect accounts with each provider, with their keys stored by you.
SecretsStay in Base44You re-create each key with its provider and store it safely.
Uploaded filesStored in the app's file libraryA storage bucket, with every file copied over and every link updated.

Your checklist, before anyone writes code

  1. Download the ZIP. In the app editor, click the More actions icon at the top right, choose Export project as ZIP, then Download ZIP.
  2. Export every table as CSV. In the Dashboard, click Data, open each table, click More actions, then Export. If a filter is on, the button says Export filtered records and only exports matches, so clear filters first.
  3. Connect GitHub. GitHub stores code with a history of changes. Base44 says its two-way GitHub sync needs the Builder plan or higher, only the app owner can connect it, and changes sync to the repository automatically. A developer will want this link more than a ZIP.
  4. List your uploaded files. Base44's documentation says files in the library are public by default, and that private files load through a temporary link. Make a list of every table field that holds a file, and ask a developer how they will copy the files themselves, since a CSV export of a table is not a copy of the files. Check Base44's help center for how to download files in bulk before you rely on one.
  5. List your integrations and keys. Write down every outside service you use, which account it belongs to, and who has the login.
  6. Record your users. Count them, and note how they sign in (email and password, Google, something else).
  7. Take a screenshot of every screen, and write a short list of what each screen must do. This is your test script later.

Also check your backups. Base44 says automatic data backups need the Elite plan or an Enterprise plan, with 7 days kept on Elite. Do not assume you have them.

Moving your users and logins

This is the part owners forget. Base44 does not export your app users, so a new login system starts empty. You have three realistic choices:

  1. Ask users to sign up again, with a clear email from you explaining why. Simple, and some users will be lost.
  2. Use a sign-in method that works anywhere, like Google sign-in, so users click the same button and are matched by email.
  3. Have a developer move the account records and send everyone a one-time link to set a new password. Passwords themselves should not be copied around, and I would not accept a plan that does that.

Whichever you choose, send a notice a week before the switch. Never surprise customers with a login that stopped working.

A cutover plan

A cutover is the day you switch from the old app to the new one. Here is a plan that keeps risk low.

  1. Week 1: inventory. The checklist above, plus a written list of what the app does.
  2. Weeks 2 to 3: build the new backend on a test address, with a copy of your data. Test every screen from your list.
  3. Week 4: dress rehearsal. Export your data again, load it into the new system, and time how long it takes. Fix whatever breaks.
  4. Cutover day. Pick a quiet hour. Put up a short notice that the app is read-only. Export the final data, load it, test the five things customers do most, then switch your domain.
  5. Keep Base44 running for at least a few weeks. Do not cancel until the new app has been used by real customers. Base44 says that if a workspace falls to the Free plan, a custom domain stops working and apps beyond five are unpublished, so check the cancellation screen before you click.

Where the new app lives matters too. My guide to where to host an AI-built app compares the options, and how to move an AI-built app to production covers the checks before go-live.

What it costs, and how to think about it

Cost varies a lot with the size of the app, so here is a labeled worked example with made-up numbers.

Say your app has six screens, four data tables, a login and two integrations. A developer tells you the rebuild is about 60 hours at $80 an hour. That is $4,800, plus hosting you pay for yourself. Now compare it with what you pay Base44 over the next two years, and with the risk of being tied to a platform you cannot move away from. If the numbers are close, staying put is a fair answer.

The cost climbs fast when the app has many integrations, custom backend functions, or user records that need careful moving. It falls when the app is mostly screens and a few tables. Blur Studio fixes and finishes start around $1,500, but a migration like this needs a look at your app first. Get a written fixed price from anyone you ask, and make sure it covers data, users, files and the cutover, not just the code.

Red flags when hiring for this

  • A promise that the ZIP "just works" on any host. Base44's own documentation says it does not.
  • A quote that mentions only the code and not the data, users or files.
  • No test plan, and no dress rehearsal before cutover.
  • The developer wants to hold the new accounts (hosting, database) in their name.

If you want a developer who already knows this builder, see hiring a Base44 developer.

Who should not leave yet

Do not migrate just because a monthly bill annoys you. If your app works, your users are happy and you can export a copy for safety, staying is fine. Leaving makes sense when you need things the platform cannot give you, such as your own database, a specific region, or a custom backend. Make the exported ZIP and CSVs a monthly habit either way, and read what production ready means for a vibe-coded app before you decide how much to invest.

How I'd approach this

I would start by exporting everything today, even if you are not sure you are leaving. A ZIP, a CSV for each table, a GitHub connection and a list of your keys cost an afternoon, and they turn a platform problem into a choice you can make calmly.

Then I would ask one question: is the problem the price, or is it a limit? If it is the price, compare the full cost of rebuilding against the bill. If it is a limit, such as something you cannot do or cannot move, get a fixed quote for the rebuild and set the cutover for a quiet week. Either way, I would insist that the new hosting, database and code repository are in your name from the first day, and that a second person can get in. That is the whole point of leaving.

Questions people ask

Can Base44 export my code?

Yes, as a ZIP from the app editor, on a Builder plan or higher. It holds your frontend code, backend functions and data structure, but not your data, secrets, users or version history. Base44 says the code still relies on its platform to run. See how to export code from an AI app builder.

Is Base44 code export free?

Base44's documentation says exporting a ZIP needs a Builder plan or higher, so the free plan does not include it. Check Base44's plans page for what each plan costs now. Data export to CSV is a separate option in the Data section of your dashboard.

Can I host a Base44 app on my own server?

Not the whole thing. Base44 says it does not support self-hosting, so you cannot run its backend, database, login system and integrations on your own servers. You can host the frontend elsewhere while it still talks to Base44, or have a developer replace the backend. See where to host an AI-built app.

Will my users and their passwords come with me?

No. Base44 says app users are not included in the export. Plan to have users set up access again on the new system, ideally with a one-time link, and warn them in advance.

How do I get my data out of Base44?

In your app editor, click Dashboard, then Data, open a table, click More actions and choose Export. You get a CSV that opens in Excel or Google Sheets. Repeat for each table, and remember that a table export is a CSV of records, so uploaded files from your file library need to be copied separately.

My Base44 app is not working or too expensive. Should I rebuild?

Not automatically. If it works, export a backup and compare the full rebuild cost against the bill. If it is broken, a fix may be cheaper than a move. My guide to hiring a Base44 developer covers what to ask.

More in this topic: Problem solving: AI-built and no-code apps (26 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…