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.

Why this exists

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.

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

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.

Production DATABASE_URL
Check my database
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.

What should happen to sign-in?
We'll check your users table in Step 1 and suggest the right sign-in path here.

• Move Replit Auth to Supabase Auth - Create Supabase Auth accounts from your app’s user rows. Replit does not expose password hashes, so users sign in once with a magic link.
• Keep Clerk or my current auth - Copy the database rows, but leave identity, sessions, verification, and Auth emails with the provider that owns those users.
• Skip session data - If your database has a sessions table, you can leave those disposable rows behind.
• Enable Row Level Security - Turns on Postgres Row Level Security for the copied tables. Your app keeps full access through its connection string. You can also change this later in your Supabase dashboard.

How do you want to move it?
Transfer straight into a Supabase project, or download a ZIP you can keep or restore later.

• Migrate to Supabase
• Download as ZIP backup
  You'll connect a Supabase project in Step 3.

Step 3: Pick your Supabase destination

Connect your Replit database in Step 1 before connecting Supabase.

1. Connect Supabase
   Approve access so the exporter can set up and verify the destination project for you.
2. Select project
   Create a fresh Supabase project (recommended), or pick an empty project you already have and enter its database password.

Step 4: Run the migration

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

Here’s what will happen

• Copy 0 tables into your Supabase project
  Start migration

Step 5: Verify and cut over

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

Step 6: Migrate your emails

You’ll need to make sure your app can still send emails. If your app doesn’t send emails, you can skip this step.

Set up your new email home

Moving your database won’t configure email delivery, so pick where your Auth and app emails will live next.

• Use DreamlitEmail API provider
  Dreamlit connects straight to your migrated Supabase project and keeps branded Auth and app emails working in a few clicks — no SMTP setup or template hand-coding.

Choose where your Auth emails will live
If you move Replit Auth to Supabase Auth, Dreamlit can handle confirmation, reset, and magic-link emails. If you keep Clerk or another provider, those emails stay there.

Ask AI for whichever emails you want set up

Describe receipts, reminders, onboarding, or weekly digests. Dreamlit builds the workflow end to end and applies your brand style and templates.

FAQs

How do I export my Replit database?

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.

How do I back up my Replit Postgres database?

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.

How do I migrate from Replit to Supabase?

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.

Does Replit lock you in?

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.

What happens to my users and Replit Auth?

Your user rows come across into your Supabase database untouched. If you choose to move Replit Auth, each user is also recreated in Supabase Auth and linked back to their original id. Replit does not expose password hashes to the app, so users sign in to Supabase once with a magic link instead of resetting a password. If you use Clerk or another Auth provider, keep identity, sessions, verification, and Auth emails there; the exporter copies your database rows without creating duplicate Supabase Auth accounts. If you are also moving your app off Replit, treat any Replit-managed Clerk setup as a separate Auth migration.

Is my app going to keep working after the move?

Your data moves first, then you point your app at Supabase by updating its connection string. If you chose to move Replit Auth users, the tool gives you a ready-to-paste prompt for swapping to Supabase Auth. If you kept Clerk or another provider, keep that Auth integration in place and update only its database connection where needed.

Do I need Agent credits to export my data?

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.

Is this safe, and is it open source?

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.

Will the export work if my app has a custom setup?

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.

Why can't the tool reach my development database?

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.

What about my object storage and uploaded files?

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.

Why does Replit pricing push people to export?

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.

Can I keep using Replit after I export?

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.