Replit Exporter

Free Replit to Supabase Exporter

Replit is great for building. As your app takes off and you want more control and ownership of your data, you'll need to move to your own Supabase.

This free tool runs on our open-source migration engine and moves your database, data, and users into a Supabase project you own. Or take a plain ZIP backup.

Your database is standard Postgres, and it's yours. This tool exists so you can take it out cleanly, whenever you want, into a Supabase project you own.

  • No Agent credits to leave. It connects straight to your production database over its connection string, so you never run the Agent to get your data out.
  • Nothing breaks. The export is a copy, not a shutdown. Your Replit app keeps running untouched until you decide to cut over to Supabase.
  • Just want a backup? Pick Download as ZIP in step 2 and keep a full copy of your database offline. No Supabase account required.
Replit
Replit
Supabase
Supabase

What you'll need

  • Your app's production database connection string
  • A Supabase account (skip it if you just want the ZIP backup)
  • About 10 minutes

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

This page does not save your connection details.

Keep this tab open while you work. Refreshing or leaving clears the form and any run status.

Step 1: Connect your Replit database

Paste your Replit app's production database connection string. We'll take a quick look and show you exactly what's in there before anything moves.

We connect read-only over your connection string — nothing on Replit is deleted or changed, and this uses no Agent credits. The engine is open source.

Step 2: Choose what happens

We picked sensible defaults based on what's in your database. Change anything you like.

How do you want to move it?

Transfer straight into a Supabase project, or download a ZIP you can keep or restore later.

You'll connect a Supabase project in Step 3.

Step 3: Pick your Supabase destination

Send your data into a Supabase project you own. Create a fresh one (recommended) or use an empty project you already have.

Checking your Supabase connection...

Step 4: Run the migration

This copies your data across. Your Replit database is only read from, never changed.

Connect your Replit database in Step 1 to unlock the run.

Step 5: Verify and cut over

Review the verification report comparing row counts on both sides, then point your app at Supabase.

Run the migration in Step 4 and your verification report plus cutover steps will appear here.

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

FAQs

Frequently asked questions

Paste your Replit app's production database connection string into this free tool. It reads your tables, users, and row counts, then either transfers everything into a Supabase project you own or hands you a ZIP backup. You do not spend any Agent credits to leave.
Choose the Download as ZIP option. The tool connects to your production database, exports every table with its data, and gives you a single ZIP archive you can keep offline or restore anywhere. It is a plain backup, no Supabase account required.
Connect your Replit production database, connect a Supabase project, and run the transfer. Your tables and data copy across, your users can optionally be recreated in Supabase Auth, and you get a verification report comparing row counts on both sides before you cut over.
No. Your data is standard Postgres, and it is yours. This tool exists so you can take it out cleanly whenever you want, whether you are moving to Supabase or just keeping a backup. Leaving should be easy.
Your user rows come across into your Supabase database untouched. If your app uses Replit Auth (the standard users table the Replit Agent creates) and you turn on the move-users option, each user is also recreated in Supabase Auth linked back to their original id, so they keep their account and sign in again once with a magic link. There are no passwords on Replit to lose, so nobody has to reset one. If your users live somewhere else, like Clerk, keep using that service after the move and leave the option off. Custom auth setups need a users table with an email column for the option to work.
Your data and users move first, then you point your app at Supabase by updating one connection string and swapping Replit Auth for Supabase Auth. The tool gives you a ready-to-paste prompt for your coding agent that describes exactly how to make the auth swap.
No. This tool talks directly to your production database over its connection string. You do not run the Replit Agent and you do not spend credits to get your data out.
The tool is non-destructive. It reads from your Replit database and writes into a new Supabase project, so your original stays intact until you decide to retire it. The migration runtime is the same open-source engine behind Dreamlit's other exporters, and you can also take a ZIP and do the restore yourself.
Most apps transfer in a few minutes, but very custom setups, like multiple databases, unusual Postgres extensions, or data stored outside Postgres, may not transfer cleanly. The preflight report shows exactly what we found before anything moves, the final verification compares row counts on both sides, and the ZIP backup path is always safe to try first.
Replit development databases are only reachable from inside your Replit workspace, so no outside tool can connect to them. Connect your app's production database instead. Production databases exist once your app is published, and their connection string lives in your App's production database settings.
Object storage export is coming later. Right now the tool moves your Postgres database (tables, data, and users). If your app relies on Replit object storage, keep it running until file export ships, and move your database now so the hard part is done.
As an app grows, usage-based and Agent-credit costs can climb. Owning your own Supabase project puts the database, auth, and storage costs in your hands and lets you connect any tool you like. This exporter is the fastest way to move without losing users or data.
Yes. The export is a copy, not a shutdown. You can keep building in Replit while pointing it at your own Supabase database, or move your app somewhere else entirely. Either way your data is already safe.