July 31, 2026Updated November 11, 20265 minute read

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

How to back up your Replit database or move it to Supabase: our free exporter copies your tables, data, and users, or makes a ZIP backup, with no Agent credits.

Andrew Kim

Andrew Kim

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

To back up your Replit database, paste your app's production database connection string into our free Replit to Supabase Exporter⁠ and download a ZIP. To move it, the same tool copies your tables, data, and users into a Supabase project you own. It never runs the Replit Agent, so it spends no Agent credits.

Why we built it

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. But the same questions kept reaching us: "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?"

Your Replit data is standard Postgres, and you could export it by hand with pg_dump. But a complete move also means sorting out your users, setting up the destination, and checking that nothing got lost. So we built a tool for it.

Paste a connection string, choose backup or transfer

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

Then you choose. Copy everything into a Supabase project you own, or download the whole database as a ZIP backup. Before a transfer, you can also choose to recreate your users in Supabase Auth, skip Replit session data, and turn on row-level security for your tables.

Your original database stays intact until you decide to retire it.

The hosted Replit to Supabase Exporter on dreamlit.ai

Why you want your own backup

In July 2025, Replit's Agent deleted data from the production database of an app built by SaaStr co-founder Jason Lemkin. Replit says he restored it with its rollback feature⁠, and Replit has since separated development and production databases by default⁠. Credit for the response.

The lesson isn't about one platform. Replit's own production database restore goes back 7 days by default, or up to 28 on Pro if you extend it. A copy you keep yourself doesn't expire and doesn't depend on the platform that holds the original.

The ZIP export takes a few minutes, with no switchover and no commitment. Run it before big changes or once a quarter. Because it's standard Postgres, it restores with standard tools.

Your users come with you

Sign-in is usually what breaks a manual migration.

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

Using Clerk or another sign-in provider? The exporter copies your database rows without creating duplicate Supabase Auth accounts, and your sign-ins, sessions, and auth emails stay where they are.

Verify before you switch

When the transfer finishes, you get a verification report comparing row counts on both sides. Row counts check completeness, not every value, so spot-check your important tables before you point your app anywhere new.

Switching over starts with changing your app's connection string. If you moved Replit Auth, the tool gives you a ready-to-paste prompt for switching your app to Supabase Auth. Auth and app emails are easy to forget in a migration, so there's a final checklist for those as well: set up custom SMTP and templates for Supabase Auth, and point your app's other emails at your email provider.

One gap: object storage export hasn't shipped yet. If your app keeps uploaded files in Replit object storage, leave it running until file export arrives. 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 keep building in Replit, pointed at a Supabase project you control, with direct database access for tools like Zapier, Make, or a BI dashboard. If you later want to build with Claude Code or Cursor, or host elsewhere, our Replit alternatives guide compares the options.

Under the hood

The migration runtime is the same open-source engine behind our Lovable Cloud to Supabase Exporter⁠: native Postgres tools doing what they've done reliably for years, wrapped so you don't have to think about table order or auth tables.

Get started

Open the Replit to Supabase Exporter⁠, sign in with Google or email, paste your production connection string, and run the preflight. You'll see exactly what you have before anything moves. The ZIP backup is always a safe first step.

If the exporter saves you a headache (or a database), tell us on X⁠ or r/dreamlitai⁠. If you'd like the verification report to check more than row counts, we're collecting ideas there too.

Where Dreamlit fits

Once the Replit migration is complete and your data is in your own Supabase project, Dreamlit can connect to it. Add Dreamlit to your AI agent and ask for a welcome email or trial reminder. It builds the workflow from your tables for you to preview with real user data before publishing.

Start a 7-day free trial⁠ or connect your agent.


Frequently asked questions

How do I export my Replit database?

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

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. You don't need a Supabase account for this.

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 switch over.

Do I need Agent credits to export my data?

No. The tool talks directly to your production database over its connection string. The Replit Agent never runs, 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 unchanged. 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 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.

Why can't the exporter reach my development database?

Development databases on Replit's current infrastructure are only reachable from inside your Replit app. Connect your production database instead. Published apps that use a database get a separate production database, and its connection string is in the production database settings.

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.

About the Author

Andrew Kim
Andrew Kim

Co-Founder & CTO

Andrew is Co-Founder and CTO of Dreamlit AI, which runs user activation for software companies. He previously built partner integrations at Netflix and led engineering at fintech startup Bonside. Full bio →

Other articles

Andrew Kim
Andrew Kim
Jul 29, 2026Comparisons

5 Best Replit Alternatives in 2026 + Pricing Explained

The 5 best Replit alternatives in 2026 compared on price and data ownership, plus a guide to Replit pricing: credits, Free Mode, and effort-based billing.

Andrew Kim
Andrew Kim
Mar 25, 2026Company

Lovable Cloud to Supabase: Why We Built a Free Exporter

Move Lovable Cloud to your own Supabase: our free, open-source exporter copies your tables, users with passwords intact, and storage files. Then keep building.