How to export your Base44 database, users and files

Your Base44 data exports from the Data page, one table at a time, as CSV. Code exports don’t include it, so if you’re backing up or leaving, export every table separately, including the User table, and download any uploaded files your records point to. Entity schemas come out through the Base44 CLI.

This is part of level 2 in the Base44 migration guide.

Export each table to CSV#

From Base44’s data documentation:

1. Click Dashboard in your app editor.
2. Click Data. Every table appears as a card.
3. On a table’s card, click the More actions icon and choose Export.
4. Repeat for each table.

The same menu has View Data, Schema, Backup & Restore, Recently deleted, Delete all records and Delete entire table. Be careful with the last two.

Array, object and reference fields#

Base44 tables support text, number, yes/no, date/time, file, reference and object fields. In a CSV:

• Object and array fields come out as JSON text in a single cell. Parse them when you import elsewhere.
• References hold the ID of the linked record. Export both tables and keep the IDs, or the links break.
• File fields hold URLs to Base44’s storage (see below).

Entity schemas#

The CSV has your records. The schema (field names, types, required fields, enums) comes from:

• The Data page: the Schema option on each table’s card shows it.
• The CLI: base44 eject copies every entity schema into a new local project, as JSON files. The new project’s database is empty; your original app is untouched. See running Base44 locally.

You need the schemas to recreate tables in another database. The Supabase migration guide maps Base44 field types to Postgres columns.

Users#

Your users are in the built-in User table, which exports like any other: names, emails, roles and any fields you added. Base44 doesn’t document a way to export password hashes, so if you move users to another auth system, plan on password reset emails or a switch to magic links or social login.

Uploaded files#

Images and documents uploaded through your app live on Base44’s media storage, and your records store their URLs. A CSV export gives you the URLs. To keep the files, download each one:

# files.txt: one URL per line, taken from the file columns of your CSVs
mkdir -p files && while read -r url; do
  curl -sL "$url" -o "files/$(basename "${url%%\?*}")"
done < files.txt

Do this before you cancel a plan or delete an app.

Recently deleted and backups#

Two safety nets exist inside Base44.

• Recently deleted: deleted records are kept for 30 days. Open the table, click More actions at the top, and choose Recently deleted to restore them.
• Backup & Restore: on the Elite plan (7 days of history) and Enterprise (30 days), Base44 backs up table data automatically as it changes. You can view, download or restore one table or all of them to a point in time, from Data → Backup & Restore. Backups cover data only; code has its own Version History.

On other plans, your own CSV exports are the backup.

Importing data back in#

Base44 imports CSV, Excel and JSON, either from the dashboard or by uploading a file to the AI chat and asking it to import into an entity. Imports add rows and don’t overwrite existing records. To replace a table’s contents, delete its records first, then import.

What to do next#

1. Export every table now, including User.
2. Collect the file URLs and download the files.
3. Put a monthly export on your calendar if you’re not on Elite.