Back Up Your Replit Database (or Move It to Supabase)

Replit is one of the fastest ways to go from idea to deployed app. Describe what you want, and the Agent builds it, database included. A lot of Dreamlit users ship this way, and we're fans.

But over the past few months, the same questions kept landing in our inbox: "How do I back up my database?" "Can I move my data to my own Supabase?" And the one that surprised us: "Do I have to spend Agent credits just to get my data out?"

Fair questions. Your app's data on Replit is standard Postgres, and it's yours. You can even export it by hand with pg_dump. But a complete move is more than a dump: sorting out your users, setting up the destination, and checking that nothing got lost along the way.

So we built the Replit to Supabase Exporter. It's free.

Paste a connection string, hit export

You paste your app's production database connection string. The tool runs a preflight and shows you what it found: your Postgres version, database size, every table with its row count, and your users table.

Then you choose. Transfer everything directly into a Supabase project you own, or download the whole database as a ZIP backup you can keep offline and restore anywhere.

No Agent involved, no Agent credits spent. The exporter talks directly to your database, reads from Replit, and writes into Supabase. Your original stays intact until you decide to retire it.

Backups stopped being optional

Last summer, a story went viral: an AI coding agent deleted data from a company's production database during a code freeze. It happened on Replit, which restored the data from a rollback and has since separated development and production databases by default. Credit for the response. But the lesson outlives the fix, and it isn't about one platform: a production database you've never backed up yourself is a risk you're carrying whether you think about it or not.

The ZIP export exists for exactly this. A few minutes, no cutover, no commitment: a copy of your production database that lives wherever you keep important things. Run it before big changes, on a schedule, or once a quarter. Because it's standard Postgres, it restores with standard tooling.

Your users come with you

Here's the part that usually kills a manual migration: auth.

Your user rows copy across untouched. If your app uses Replit Auth, the exporter can also recreate each user in Supabase Auth, linked back to their original id. Replit doesn't expose password hashes, so instead of forcing everyone through a password reset, your users just sign in once with a magic link and carry on.

Using Clerk or another auth provider? The exporter knows to stay out of the way. It copies your database rows without creating duplicate Supabase Auth accounts, and your identity, sessions, and auth emails stay right where they are.

Verify before you cut over

Nothing about this process asks for trust. When the transfer finishes, you get a verification report comparing row counts on both sides. Counts are a completeness check rather than a value-by-value diff, so give your important tables a look too before you point your app anywhere new.

Cutover starts with a connection string change. If you moved Replit Auth, the tool hands you a ready-to-paste prompt for swapping your app to Supabase Auth. And because auth and app emails are easy to forget in a migration, there's a final step for those too: connect Dreamlit to keep branded emails working in a few clicks, or follow the provider checklist.

One caveat: object storage export hasn't shipped yet. If your app keeps uploaded files in Replit object storage, leave it running until file export lands. Your database is the hard part, and it can move today.

You don't have to leave Replit

The export is a copy, not a shutdown.

You can run the exporter and keep building in Replit, pointed at a Supabase project you control. That gets you direct database access for connecting tools like Zapier, Make, or Dreamlit, plus your own backups on your own schedule. And if you ever want to develop with Claude Code, Cursor, or host somewhere else, that door is open too.

The tool gives you options. What you do with them is up to you.

Under the hood

The migration runtime is the same open-source engine behind our Lovable Cloud to Supabase Exporter: native Postgres tooling doing what it's been doing reliably for years, wrapped so you don't have to think about dependency ordering or auth tables.

Get started

Head to the Replit to Supabase Exporter, paste your production connection string, and run the preflight. You'll see exactly what you have before anything moves. The ZIP backup path is always a safe first step if you just want a copy.

If the exporter saves you a headache (or a database), tell us on X or r/dreamlitai. And if there's something you'd want the verification report to check beyond row counts, we're collecting ideas for the next version there too.

---

Frequently asked questions

How do I export my Replit database?

Paste your Replit app's production database connection string into the free exporter. It reads your tables, users, and row counts, then either transfers everything into a Supabase project you own or hands you a ZIP backup. No Agent credits are spent.

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 a verification report compares row counts on both sides before you cut over.

Do I need Agent credits to export my data?

No. The tool talks directly to your production database over its connection string. You don't run the Replit Agent, so no Agent credits are spent getting your data out.

What happens to my users and Replit Auth?

Your user rows copy into your Supabase database untouched. If you choose to move Replit Auth, each user is also recreated in Supabase Auth and linked to their original id. Replit doesn't expose password hashes, so users sign in to Supabase once with a magic link instead of resetting a password. If you use Clerk or another provider, the exporter copies your rows without creating duplicate accounts.

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 your app at your own Supabase database, or move your app somewhere else entirely. Either way your data is already safe.

How do I back up my Replit database?

Choose the Download as ZIP option in the exporter. It connects to your app's production database, exports every table with its data, and gives you one archive you can keep offline or restore anywhere. It's a plain Postgres backup, no Supabase account required.

Does Replit have a database?

Yes. Published Replit apps get a production Postgres database, separate from the development database in your workspace. The production database is the one this exporter connects to, using the connection string from your app's production database settings.

Can Replit code be exported?

Yes, Replit supports pushing your code to GitHub. This tool covers the other half: your production database, its data, and your users. Replit-specific hosting, integrations, and secrets still need replacing if you move your whole app.