Why We Built a Free, Open-Source Lovable Cloud Exporter

Lovable is one of the best tools out there for going from idea to working app fast. We're fans. A lot of our Dreamlit users build on it.

But over the past few months, we kept hearing the same thing: "I need direct access to my database." Someone wants to connect Zapier, or set up email automations, or plug in analytics that talk directly to Postgres. They can't, because Lovable Cloud manages the Supabase instance for you. You don't get the keys.

The official path to fixing this is rough. You're exporting tables as CSV one at a time, re-uploading storage files individually, and asking every user to reset their password. If you have real users, that last part is basically a non-starter.

We kept walking people through this manually. Same messages, same gotchas, same "wait, what order do I import these tables in?" At some point we just said: we should build this.

We work with Supabase internals every day. We knew native Postgres tooling (pg_dump and psql) could handle the whole thing cleanly. So we built it and open sourced it.

Plug in your credentials, hit export

You point it at your Lovable Cloud project and a fresh Supabase project. One click. It moves everything: data tables, user accounts with auth intact (no password resets), and storage files. The whole thing runs through a temporary Cloudflare container that spins up just for your migration and gets destroyed after. Your credentials pass through an isolated environment that doesn't persist. Nothing is stored on our side.

Your data is now in a Supabase project you own.

You don't have to leave Lovable

Here's the part that surprises people.

Once your backend is in your own Supabase, you can bring it right back into a new Lovable project. Keep building the same way you always have. The only difference is your data lives in infrastructure you control.

That means direct database access for connecting tools like Zapier, Make, or Dreamlit. Portability if you ever want it. And if you decide to develop with Claude Code, Cursor, or something else, that door is open too. But it doesn't have to be. Plenty of people export their data and keep building happily in Lovable.

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

Under the hood

No custom migration format. No intermediary API. It's pg_dump to extract, psql to load. The way database engineers have been moving data between Postgres instances for years.

The exporter handles the parts that make Supabase-to-Supabase specifically tricky: auth tables, storage buckets, RLS policies, and the dependency ordering between tables. It wraps that complexity so you don't have to think about it.

Everything is open source. The hosted version runs the exact same code that's in the repo. Run it locally, read the source, fork it. We also recommend rotating any secrets you provide after the migration, just to be safe.

Why we open sourced it

We could have kept this as a Dreamlit feature. But the problem affects more people than just our users. Anyone on Lovable Cloud who wants to connect an external service needs their data in a Supabase instance they control.

We built Dreamlit around a simple idea: your database is the source of truth, and builders should own it and pick their tools. Open sourcing this exporter is that same idea, applied to a problem that needed solving.

Get started

Want convenience? Use the hosted exporter. No setup needed.

Want to run it yourself? The full source is on GitHub. CLI and web UI included.

After the export, the repo includes a guide walking through four paths forward: staying on Lovable with your own Supabase, developing locally while deploying through Lovable, hosting elsewhere, or going fully self-managed.

If you found this useful, give us a shout on X, r/dreamlitai, or drop a star on the GitHub repo.

Questions? We're happy to help.

---

Frequently asked questions

Can I still use Lovable after exporting my data?

Yes. Once your data is in your own Supabase, you can connect that Supabase project to a new Lovable project and keep building exactly the way you have been. The only difference is your data lives in infrastructure you control.

Does the exporter require users to reset their passwords?

No. The exporter migrates user accounts with auth intact, so your users don't need to reset passwords or re-verify their email addresses.

How does the Lovable Cloud exporter work under the hood?

It uses native Postgres tooling (pg_dump and psql) to move data between Supabase instances. The exporter handles auth tables, storage buckets, RLS policies, and table dependency ordering automatically.

Is the Lovable Cloud exporter free?

Yes. The tool is free and fully open source. You can use the hosted version on dreamlit.ai or run it locally from the GitHub repo.

What does the exporter move from Lovable Cloud?

It moves your data tables, user accounts (with authentication intact), and storage files to your own Supabase project.