Free Lovable Cloud to Supabase Exporter | Dreamlit | Dreamlit AI

Free Lovable Cloud to Supabase Exporter

Lovable is great for building. As your app takes off, you'll want to host it wherever you like, bring your own infrastructure and AI, and own your data. Step one is moving to your own Supabase.

This free, open-source tool moves the data pieces for you: database tables, user accounts, and storage files.

Why this exists

Lovable's built-in export hands you a database backup file, which is real progress. It is still not a migration. To finish the move you need to:

This tool does the data move in one pass from your browser: database tables, users with passwords intact, and storage files, straight into your Supabase project. For the config that moves by hand, like auth settings, secrets, and scheduled jobs, it gives you step-by-step directions.

MOSSKKLM943+ people have used this exporter

“All 412 tables transferred successfully and all 125 users came across with their password hashes intact. No forced password resets for our users, which was a dealbreaker with the manual approach.”
— Mohamed

“I was able to finish the migration, and now I can build my native companion app off the same database and keep building in Lovable. I'm stoked! Even Lovable, ChatGPT, and Claude all said it was impossible.”
— Shane S.

“I've used your exporter and I just want to say what a fantastic tool, thank you!!!”
— Kieran K.

“Can I start with, this tool is absolutely amazing!”
— L.M.

“The tool has been extremely helpful. We just successfully migrated a client from Lovable Cloud to Supabase. This tool made it much simpler.”
— Agency founder

“Thanks a lot for the tool, I transferred the project to Supabase and the data is showing up there.”
— Arhaan

What you'll need

Step 1: Add the migrate helper edge function

First, create a small, temporary endpoint to export your Lovable Cloud data. We'll remove this endpoint after the export.

  1. Create an edge function

In your Lovable project, tell Lovable:

Create an empty edge function called migrate-helper

  1. Refresh the page to reload the latest code

Sometimes Lovable won't show the new edge function until you refresh the page.

  1. Copy and paste the helper function code

First, enter an access key below. Then copy and paste the generated edge function code into Cloud > Edge Functions > migrate-helper > View code, then hit Save in the upper right.

  1. Deploy the edge function

Tell Lovable:

Deploy the migrate-helper edge function with verify_jwt = false in supabase/config.toml.

  1. Enter your edge function URL

Get this from Cloud > Edge Functions > migrate-helper > Copy URL.

Step 2: Choose how to export

  1. Connect Supabase

Approve access so the exporter can set up and verify the destination project for you.

  1. Select project

Create a fresh Supabase project (recommended), or pick an empty project you already have and enter its database password.

Step 3: Run the export

Transfer directly into your Supabase project.

Before you can transfer, ensure:

Step 4: Transfer configs

Choose where you'll keep building next. The checklist below covers the code and config that still needs to move, including any app Edge Functions.

What's next?

Connect your new Supabase project to a fresh Lovable app and keep the same building flow you're used to.

Keep building in Lovable config checklist

These are the handoff tasks for the path you picked above.

Copy any app secrets from Lovable Cloud into Supabase Edge Functions > Secrets, and keep client-safe public values separate from server-only secrets.

The exporter does not deploy existing Edge Functions. Bring their source over with your app code if you have it, deploy them to the target Supabase project, and recreate their secrets.

Recreate any enabled auth provider settings in your new Supabase project so existing login methods keep working against the migrated backend.

AI features built with Lovable AI call Lovable's gateway, which stays behind after migration. Get an API key from Anthropic or OpenAI, ask your app to switch its AI calls to that provider, and store the key as an Edge Function secret.

Lovable Cloud's managed email does not come along, so auth and app emails stop sending after you cut over. Connect Dreamlit to your migrated Supabase project to keep branded auth and app emails working in a few clicks, or set up a provider like Resend or Postmark and update your email functions.

Scheduled jobs (cron) are saved with your old project's function URLs and keys baked in, so after migration they either break or keep calling the old backend. Recreate each job in your new Supabase project pointing at the new function URLs and keys, then remove the old ones.

In Lovable, create or open the app you want to keep building in and connect it to your migrated Supabase project.

Add only the third-party secrets your Lovable app still needs in Lovable Cloud > Secrets. Keep Supabase database, auth, and storage owned in Supabase.

Step 5: Cleanups

After the export completes, check off each item as you clean up the temporary access you created for the migration.

Tell Lovable to remove the temporary edge function you created for the export.

Open Project Settings > API Keys > Publishable Secret Keys and delete the key you pasted into Step 2.

In Supabase database settings, reset the postgres password you used in the connection string.

Exporter pricing

The exporter is free for every project

Free for every project, big or small. Pay only if you want expert help.

Every project

Free

Optional expert help

FAQs

Why does this project exist?

Lovable now has a built-in export button, and it is a real improvement. But it hands you a backup file, not a working migration:

This tool does the whole data move in your browser instead. Tables, users with passwords intact, and storage files land straight in your Supabase project, and a checklist walks you through the rest.

How do I move my Lovable Cloud database to Supabase?

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.

Is the exporter really free?

Yes. The exporter is free for every project size, including big databases and storage-heavy projects. The exporter is open source, so you can also run it on your own machine for free.

Can I get help with my migration?

Yes. Beyond free chat support, there are two ways to get extra help:

Does the exporter require users to reset their passwords?

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.

Will my users have to log in again after migration?

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.

What does the exporter move from Lovable Cloud?

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.

Does the exporter migrate Edge Functions?

No. Supabase Edge Functions are deployed code, not database or storage data. The exporter moves database tables, auth users, and storage files. Bring Edge Function source over with your app code if you have it, then deploy those functions and recreate their secrets in the target Supabase project.

Is migrating off Lovable Cloud reversible?

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.

What is the difference between Lovable Cloud and connecting your own Supabase?

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.

How long does a Lovable Cloud export take?

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.

Does the exporter copy storage files and bucket policies?

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.

Can I run the Lovable Cloud exporter without uploading my credentials to a third party?

Yes. The migration engine is open source and ships with a local CLI. When you run the CLI, your Lovable Cloud and Supabase credentials stay on your machine, and migration data only passes through your local runtime.

Lovable Cloud cost is climbing. What are my options?

You have three options: stay on Lovable Cloud and optimize it, move only the backend to your own Supabase project, or leave Lovable for a tool like Claude Code or Cursor. This exporter handles the data move for the last two options without losing users or data.

Can I keep using Lovable after exporting my 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.

Why move off Lovable Cloud?

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.

What does the exporter not cover?

What is Dreamlit?

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.

How do I migrate my email setup from Lovable Cloud Custom Emails?

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.

What is the exporter doing exactly?

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 that data into your own Supabase project. This helper is not a migration for existing app Edge Functions. Once the data migration is done, you can remove the helper.

Is the Lovable Cloud to Supabase Exporter free?

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.

Is there an equivalent exporter for Replit, Bolt, or other vibe coding platforms?

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.

Is the exporter open source?

The CLI, migration runtime, and helper code are open source under the MIT license. You can inspect the code or run the CLI yourself from GitHub.

Does Dreamlit store my data during the export?

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

Running into issues?

We're here to help. Use the chat widget in the bottom right to reach us directly, or send an email to support@dreamlit.ai. We'll help you through it.