# Free Base44 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](/content/tools/lovable-cloud-to-supabase-exporter/index.html) and [Replit exporter](/content/tools/replit-to-supabase-exporter/index.html).

## Why this exists

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.

## What you'll need

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

## 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. **Base44 app ID**  
   Where do I find my app ID?  
   Expand

2. **Create the temporary export helper**  
   Copy the prompt and paste it into your app's AI builder. It creates a backend function named dreamlit-export-helper from the code below.

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

## Step 2: Choose how to export

Everything moves — every entity plus User profile records. Pick a direct MongoDB transfer or a ZIP backup.

How do you want to export it?  
Move the documents into MongoDB, or download a ZIP you can keep and inspect later.

## Step 3: Connect MongoDB

1. **Allow temporary network access**  
   Make sure your MongoDB deployment accepts connections from the exporter — without this, the exporter can't reach your database and the transfer can't start. If you use MongoDB Atlas:
    - Open Security → Network Access.
    - Add `0.0.0.0/0` to the IP Access List.
    - Turn on temporary access, choose 6 hours, then confirm.

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.
   - MongoDB URI: Paste the MongoDB connection URI and replace any password placeholder with the database user's real password.
   - Database name: Pick any name — MongoDB creates the database on the first write, so it doesn't need to exist yet.

## Step 4: Run the transfer

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

## Step 5: Transfer your files to Supabase

1. **Connect Supabase**  
   Approve access so the exporter can copy your uploaded files into storage you own.

2. **Choose a project and bucket**  
   Pick the Supabase project that should hold your files. We'll copy them into the specified bucket.

## Step 6: Verify and finish

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

### FAQs

**How do I export my Base44 data?**  
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.

**Can I download a backup without using MongoDB?**  
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.