Base44 Exports Your Code, Not Your Data. We Fixed That.

Base44 has pulled off something real: people who never wrote code are running actual businesses on apps they described into existence. Some of our Dreamlit users are among them, and we're fans of what the platform makes possible.

But as those apps grow up, a question keeps coming back to us: "My whole business lives in this app. How do I get a copy of my data?"

Inside Base44, your entities live in a managed backend. That's part of what makes building so smooth, but it also means there's no bulk export and no connection string for outside tools. Your customer list, your orders, your content: getting them out means downloading CSVs one table at a time.

So we built the Base44 Exporter. It copies your data into a MongoDB database you own, or a ZIP you can hold. It's free.

Does Base44 allow export?

For your code, mostly yes. Ask around and that's where every answer points: GitHub export, downloader extensions, rebuild guides.

Your data is the other half, and the harder one. The built-in option is downloading individual tables as CSV files, one at a time, with no database on the other end. For the documents your app has collected (the customers, orders, and records that make the app worth anything), that's a thin safety net. Code you could rewrite in a weekend. Data you can't.

That's the gap this tool fills. It doesn't touch your code; it gets your data into a database you own, or a ZIP you can hold.

A helper you control, not credentials you hand over

We didn't want a tool that asks for your Base44 login. Instead, the exporter walks you through adding a small temporary backend function called dreamlit-export-helper to your own app, protected by a secret only you know.

Your app, your account, your rules. The helper reads data when you ask it to, and when you're done, you delete it and rotate the secret.

You don't need a specific plan for this. Base44's chat builder can create and deploy the function for you from a pasted prompt, even on the free tier. (Editing code by hand in the dashboard is the part that requires a paid plan.)

Pick your entities, pick your destination

Once connected, the tool shows you every entity with its document count, plus any warnings, before a single document moves.

You select what to export and choose one of two paths:

• Direct transfer into an empty MongoDB database you own. MongoDB Atlas, another hosted service, or self-hosted all work. Each entity lands in its own collection with Base44 ids and timestamps preserved.
• ZIP backup with one data file per entity, a manifest with source counts, and a finishing guide. No MongoDB account required.

Either way, the exporter compares source and destination document counts at the end. It's a completeness check rather than a value-by-value diff, and it catches the failure that matters most: something didn't arrive.

What moves, and what doesn't

• Your entity data moves. Every document in every entity you select, with counts compared at the end.
• User profiles move, but sign-ins don't. Profile documents copy across. Passwords, sessions, and OAuth connections stay behind, so a new app needs its own auth provider connected to those profiles.
• Backend functions, automations, and integrations don't move. They're built on Base44's runtime. If you're rebuilding elsewhere, you'll port them.
• File references move, file bytes don't yet. Keep the originals available until you move them separately.

The finishing guide included with every export turns this list into a concrete checklist. If what you want is a verified backup of your data, you're done in minutes. If what you want is your app running somewhere else, that's a rebuild, and it starts from a much better place when your data is already safe in a database you own.

Read-only, and nothing persisted

The export is read-only against your Base44 app, which keeps running as-is; the only change is the temporary helper you add and later remove. A transfer writes copies into a MongoDB database the tool has verified is empty and writable, so it can't collide with anything you already have.

We don't persist your helper secret or MongoDB URI. They stay in your open browser tab, are sent only to run your checks and your export, and clear when you refresh or leave.

Get started

Head to the Base44 Exporter and follow the connect step. You'll see your entities and counts before deciding anything. The ZIP backup is a safe first run if you just want a copy you can hold.

If you run an export and hit anything odd, r/dreamlitai is where we hang out. And tell us what you'd want moved next: uploaded files and an auth path are both on the list, and what people ask for decides the order.

---

Frequently asked questions

How do I export my Base44 data?

Add the temporary Dreamlit export helper to your Base44 app, then connect it to the free exporter. It lists your entities and document counts, and you choose a direct MongoDB transfer or a ZIP backup.

How do I move a Base44 app to MongoDB?

Connect the temporary helper, choose the entities you want, and enter an empty MongoDB database (Atlas, hosted, or self-hosted). The tool copies each Base44 entity into its own MongoDB collection and compares document counts when the transfer finishes.

Can I download a backup without using MongoDB?

Yes. Choose Download as ZIP backup. You get one data file per entity, a manifest with source counts, and a finishing guide. No MongoDB account required.

Does the exporter move backend functions, auth, and files?

No. It moves entity documents. User profiles copy across, but passwords and sessions don't; backend functions, automations, and integrations need to be ported; uploaded file bytes stay in Base44 for now. The finishing guide turns all of this into a checklist.

Does Dreamlit save my helper secret or MongoDB URI?

No. These details stay in your open tab while you use the exporter and are cleared when you refresh or leave. They're sent only when needed to run your checks and export.

Does Base44 allow export?

For code, yes: there are paths like GitHub sync. For data, the built-in option is downloading individual tables as CSV files one at a time. The free Dreamlit exporter goes further: it copies all your selected entities into a MongoDB database you own, or a ZIP backup, with document counts compared at the end.

How do I export from Base44 for free?

The Dreamlit Base44 exporter is free to use. Add the temporary helper function to your app, connect it in the exporter, select your entities, and choose a MongoDB transfer or ZIP download. Base44's chat builder can create the helper for you, so this works even on the free tier.