Base44 Exporter

Free Base44 to MongoDB Exporter

Base44 is great for building. When you want more control over your data and backend, move your entity documents into MongoDB.

This free tool copies selected entities into an empty MongoDB database, or takes a plain ZIP backup. It uses the same export flow as our Lovable Cloud exporter and Replit exporter.

Your Base44 data belongs to you. This tool gives you a clear way to copy it into a MongoDB database you control.

  • Nothing shuts down. The exporter reads your selected entity documents while your Base44 app keeps running.
  • You can verify the copy first. A direct transfer compares document counts in Base44 and MongoDB before you cut over.
  • Just want a backup? Pick Download as ZIP in Step 2. You do not need a MongoDB account for that path.
Base44
Base44
MongoDB
MongoDB

What you'll need

  • A Base44 app with backend functions enabled
  • A MongoDB connection URI (skip it for a ZIP backup)
  • About 15 minutes

Want additional help? Book an expert migration review ($299, 90 min) or have us move the whole app for you (custom quote).

This page does not save your connection details.

Keep this tab open while you work. Refreshing or leaving clears the helper secret, MongoDB URI, and run status.

Step 1: Connect your Base44 app

Add a temporary export helper, then run preflight — a safe, read-only check that lists your entities and document counts so you can see what will move before anything happens.

1

Find your app ID

Base44 editor URL

2

Create the temporary export helper

In your Base44 app, paste our prompt into the AI builder. It creates a backend function named dreamlit-export-helper. Backend functions require an eligible Base44 plan.

The prompt tells Base44 to save this as EXPORT_SECRET. Keep it only until you verify the export.

Includes the helper source, your secret, and the instruction to include every entity.

Paste the prompt into the AI builder

Base44 AI builder

3

Publish your app so the helper is live, then paste its Base44 URL. We add /functions/dreamlit-export-helper automatically.

Preflight is a quick, read-only check of your app — it lists your entities and how many documents each has, so you can see what will move before anything happens. It never changes your Base44 app.

Ensure your app is published

Base44 Publish dialog

Step 2: Choose what to export

All app entities are selected by default. You can also include User profile records or choose a ZIP backup.

1

What we'll move

Everything in your Base44 app copied into MongoDB with the original Base44 IDs and timestamps kept so document relationships stay intact.

Run preflight in Step 1 to see everything we'll move.

What we can't move: backend functions and user login can't be migrated automatically — they're code and identities that live in Base44. Your finishing guide covers re-creating them.

2

How do you want to export it?

Move the documents into MongoDB, or download a ZIP you can keep and inspect later.

You'll connect an empty MongoDB database in Step 3.

Step 3: Connect MongoDB

Connect your Base44 app in Step 1 before connecting MongoDB.

1

Allow temporary network access

Make sure your MongoDB deployment accepts connections from the exporter. If you use MongoDB Atlas:

  1. Open Security → Network Access.
  2. Add 0.0.0.0/0 to the IP Access List.
  3. Turn on temporary access, choose 6 hours, then confirm.

This temporarily allows connections from any IP address. Atlas still requires your database username and password and will remove the entry after 6 hours. You can remove it sooner after you verify the transfer.

Allow temporary access in MongoDB Atlas

Add 0.0.0.0/0 to the IP Access List for 6 hours

2

MongoDB destination

Use a database user that can create collections and write documents. Make sure your MongoDB deployment allows network access from the exporter.

Paste the MongoDB connection URI and replace any password placeholder with the database user's real password.

Pick any name — MongoDB creates the database on the first write, so it doesn't need to exist yet.

MongoDB Atlas example

If you use Atlas, copy its connection URI into the field on the left

Step 4: Run the transfer

This copies your selected documents into MongoDB. Your Base44 app is only read from, never changed.

Finish setup to continue

Connect your Base44 app in Step 1 to unlock the export.

Step 5: Move your files to Supabase

Copy Base44's uploaded files into a Supabase bucket you own and update every file link in MongoDB. Or skip the file move and handle it later with your finishing guide.

1

Connect

Connect Supabase to move your uploaded files.

2

Choose a project and bucket

We'll create this public bucket if it doesn't exist.

Storage destination

Choose a Supabase project

base44-files

3

Move

Step 6: Verify and finish

Review the Base44 and MongoDB document counts, then follow the finishing guide to update your app.

Run the transfer in Step 4 and the verification report plus finishing guide will appear here.

Want additional help? Book an expert migration review ($299, 90 min) or have us move the whole app for you (custom quote).

FAQs

Frequently asked questions

Add the temporary Dreamlit export helper to your Base44 app, then connect it to this free tool. The exporter lists your entities and document counts before you choose a direct MongoDB transfer or a ZIP backup.
Connect the temporary helper, choose the entities you want, and enter an empty MongoDB database. The tool copies each Base44 entity into its own MongoDB collection and compares document counts when the transfer finishes.
Yes. Choose Download as ZIP backup. You will get one data file per entity, a manifest with source counts, and a finishing guide. The archive does not contain MongoDB credentials.
You need a Base44 Builder plan or higher so your app can run backend functions. The tool walks you through adding a temporary function named dreamlit-export-helper and a private secret that only you know.
No. The helper reads the entity documents you select. A transfer writes copies to your empty MongoDB database, and a backup only creates a ZIP. Your Base44 app keeps running until you decide to change it.
No. These details stay in the open tab while you use the exporter and are cleared when you refresh or leave. They are sent only when needed to run your checks and export.
You can copy User profile documents, but they do not include passwords, sessions, OAuth connections, or working sign-in accounts. Choose a new auth provider and connect those profiles as part of your app cutover.
No. The exporter moves entity documents. You will need to port backend functions and automations, reconnect integrations, and recreate their secrets. The finishing guide turns these into a clear checklist.
File URLs and references stay in your documents, but the uploaded file bytes are not copied by this version. Keep the original files available until you move them separately and update those references.
The first version creates a clean copy and does not merge with existing collections. The exporter checks that the database is reachable, empty, and writable before it starts.
You can use MongoDB Atlas, another hosted MongoDB service, or a self-hosted MongoDB deployment. Enter a mongodb:// or mongodb+srv:// URI with a username, password, and host, and make sure the exporter can reach it. The destination database must be empty and writable.
Keep it until you verify the transfer or backup. Then remove dreamlit-export-helper from Base44 and delete or rotate DREAMLIT_EXPORT_SECRET so the temporary access is closed.