Symptoms
- The app builds but shows no data
- Logins fail outside Base44
- You see errors from Base44 SDK calls in the console
- The export option is missing in your editor
Why it happens
Base44 lets you export your code on the Builder plan or higher, either to GitHub or as a ZIP file. The export includes the front-end code and your backend functions. Your data is exported separately, collection by collection, as CSV files.
The catch is that the exported app still talks to Base44 to read and write data and to log users in. It does this through the Base44 SDK, with calls that start with base44. Outside the platform, those calls only work if they can still reach your Base44 backend. If they cannot, the app loads with no data, or not at all.
Try this first
-
Check your plan and export again
Export needs the Builder plan or higher. Each GitHub export is a snapshot, so push again after every change you make in Base44, or your repository will be out of date.
-
Run it on your computer first
Before you deploy anywhere, install and run the project locally. Errors are much easier to read there.
npm install npm run dev -
Find every Base44 SDK call
Search the code for calls to the Base44 SDK. This shows you how much of the app depends on the Base44 backend.
grep -rn "base44\." src/ -
Decide: keep the Base44 backend or replace it
If you only want your own hosting for the front end, the app can keep using the Base44 backend. If you want to leave Base44 fully, every SDK call needs a replacement on a new backend. That is a bigger job.
-
Export your data
In the Base44 editor, open Data, pick a collection and export it. Repeat for every collection. Keep these files safe before you change anything.
When to stop and call a person
Get a person involved if you want to leave the Base44 backend completely. Logins, data access, files and server functions all need a new home, and users must keep their accounts. It is a real project, so get a fixed estimate first.
Questions people ask
Does the code export include my data?
No. Data is exported separately from the Data section, one collection at a time, as CSV files.
Can I import my code back into Base44?
Base44 says its GitHub integration only supports exporting. Treat the export as a way out, not a two-way workflow, unless your plan says otherwise.