Free Lovable Cloud to Supabase Exporter

Lovable has documentation for moving to your own Supabase, but the process is rough:

• Every user needs to reset their password. If you have real users, that's a non-starter.
• You're exporting and importing table data via CSV, one table at a time, in the right dependency order.
• Storage files need to be downloaded and re-uploaded individually.
• Miss a step or get the order wrong, and you're starting over.

This tool handles all of it. Tables, users, and storage move to your Supabase backend without password resets or manual work.

Use this free, open-source exporter. Deploy a temporary edge function to your Lovable Cloud project, point it at an empty Supabase project, and the exporter copies your tables, users, and storage files in a single pass. Small projects often finish in a few minutes; larger databases or storage-heavy projects take longer.

No. The exporter migrates user accounts with their password hashes intact, so existing users do not need to reset their passwords or re-verify their email addresses.

They may need to log in again after you cut over to the new Supabase project. The important part is that password hashes and auth records are preserved, so users can keep using their existing credentials without a forced password reset or email re-verification.

It moves your database tables, user accounts (with passwords intact), and storage files into your own Supabase project. Row-level security policies on tables come across automatically.

Yes. The exporter is non-destructive — it reads from Lovable Cloud and writes into a new Supabase project, so your original data stays intact until you choose to retire it. You can keep both running side by side while you cut over.

Lovable Cloud is a managed backend that Lovable provisions for you — convenient for prototyping but billed per usage and tied to Lovable. Connecting your own Supabase project means you own the database, storage, and secrets directly, which can lower ongoing cost and lets you connect external tools like Dreamlit, Claude Code, or Cursor.

Small projects often finish in a few minutes. Time scales with the size of your database and storage, so large databases or media-heavy projects can take much longer. If storage copy fails after the database clone succeeds, you can retry storage without rerunning the database clone.

Storage files are copied bucket-by-bucket into your new Supabase project, and public/private bucket configuration carries over. Row-level security policies on database tables come across automatically. Bucket-level policies configured in the Lovable Cloud UI need to be re-applied in Supabase Studio after the migration.

Yes. The tool is open source and ships with both a CLI and a self-hosted web UI. When you run it locally, your Lovable Cloud and Supabase credentials stay on your machine, and migration data only passes through your local runtime.

You have three: stay on Lovable Cloud and optimize (cache more, reduce AI message usage); move only the backend to your own Supabase project (this tool handles the data move while you keep building in Lovable); or leave Lovable entirely for a tool like Claude Code or Cursor. The exporter is the fastest path to either of the last two without losing users or data.

Yes. Once your data is in your own Supabase project, you can connect that project to a new Lovable app and keep building on top of infrastructure you control.

Lovable Cloud is great for prototyping, but you may outgrow it as costs rise or as you need direct ownership of your database, storage, and secrets. Moving to your own Supabase also makes it easier to connect external services like Dreamlit or your own tooling, without being tied to a single platform. You can still keep building in Lovable if you want.

• API keys, secrets, or third-party service credentials.
• Login provider settings like OAuth config or redirect URLs.
• App deployment, DNS, hosting, or the broader app setup.

Dreamlit lets you add professional, branded emails to your app built on Supabase. Connect your database, describe what you want in plain English, and the Workflow Agent builds the entire workflow for you: triggers, templates, and delivery.

You'll need to remove the Custom Email implementation from your Lovable Cloud project and replace it with another email solution (such as Dreamlit or Resend). There's currently no documented way to use Lovable Custom Email on your own infrastructure.

You'll deploy a temporary edge function to your Lovable Cloud project. The exporter uses it to read your tables, users, and storage files, then writes everything into your own Supabase project. Once it's done, you can remove the edge function.

Completely free, no strings attached. Many of our customers at Dreamlit were stuck on Lovable Cloud and wanted to use Dreamlit but couldn't because they didn't have direct access to their database. We started helping them one by one and decided to turn it into a tool so anyone can take control of their data.

The current flow is built around Lovable Cloud, but let us know which other platforms you want next. Hit us up on X or on r/dreamlitai.

Fully open source under the MIT license. You can inspect the code, run the CLI yourself, or self-host the entire tool from GitHub.

Hosted transfer jobs are processed transiently by Dreamlit's exporter runtime, and migration data is not kept after the job. You can always self host the tool or run the commands yourself if you do not want credentials or data to pass through Dreamlit infrastructure.

We're here to help. Use the chat widget in the bottom right to reach us directly, or send an email to [email protected]. We'll help you through it.