If you ever leave Base44: what you take and what you don’t

On the Builder plan you take the code and the table schema. The data comes out separately, and login and the server that runs your functions stay in Base44.

Checked October 15, 2026Based on Base44’s docs and a real export2 min read

Piece by piece

Base44 changes often: this was true on the date above. Check their docs before you decide.

PieceComes out?What to know
Frontend codeYes, on Builder or aboveAs a ZIP (a one-time snapshot) or synced with GitHub. Free and Starter can’t export
Table schema (entities)Yes, in the ZIPThe base44/entities folder: fields, types, required fields and access rules. You still create the tables in the new database 1
DataNot with the codeDownload it table by table as CSV, or through the API (5,000 records per request max)
UsersAs rows, without passwordsEveryone has to set a new password
Backend functionsThe code, yesThe base44/functions folder. They need somewhere to run, and their Base44 SDK calls need rewriting
Login, uploaded files and automationsNoThey only work inside Base44

1 A ZIP exported in February 2026 didn’t include this folder; the one from October 15, 2026 does. If your export is old, download it again.

Does the exported code run on its own?

It starts, but it still depends on Base44. The file src/lib/app-params.js reads three environment variables that point at your app in Base44: VITE_BASE44_APP_ID, VITE_BASE44_APP_BASE_URL and VITE_BASE44_FUNCTIONS_VERSION. The ZIP leaves them empty.

Fill them in and deploy the app somewhere else, and it looks fine. But the data, login and functions are still in Base44. If the app disappears from Base44, your copy is left with no backend.

Before you connect GitHub

Try the ZIP first. Once GitHub is connected, version history can’t take you back to a version from before the connection. You can disconnect, though Base44 notes the button isn’t enabled on every account yet.

Six things to check before you leave

  1. An active Builder plan, since there’s no export without it.
  2. A CSV of every table, downloaded and saved.
  3. A list of your functions and the places where the code calls the SDK.
  4. Who logs in, and how you’ll tell them they need a new password.
  5. Where the files people upload are stored.
  6. Which automations run today.

Sources

Keep44 helps move Base44 apps onto your own servers: keep44.com