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.

Andrew Kim

To move from Lovable Cloud to your own Supabase project, you need to copy three things: your database tables, your users, and your storage files. Lovable doesn't offer a one-click migration, so we built a free, open-source Lovable Cloud to Supabase Exporter that copies all three, keeps your users' passwords working, and lets you keep building in Lovable afterward.
Why we built it
Lovable is one of the fastest ways to go from idea to working app. As those apps grow, we kept hearing the same request: "I need direct access to my database." People wanted to connect Zapier, analytics, or other tools that talk to Postgres directly. On Lovable Cloud they can't hand those tools a connection string, because Lovable runs the Supabase project for them.
When we started, the official route meant exporting tables as CSV one at a time and asking every user to reset their password. After walking enough people through it by hand, we built a tool on native Postgres tooling, which can do the whole move cleanly.
What about Lovable's built-in export?
Lovable has since added an Export project data button, and it's a real improvement. It exports your full database, including users' password hashes. But it's a backup file, not a migration:
- You restore it into your Supabase project yourself, with Postgres command-line tools.
- It only works for databases using up to 15 GB of storage. The export file can be at most 5 GB, you can request one every 24 hours, and the download link arrives by email.
- Storage files aren't included, so you download and re-upload them separately.
- Edge Function code, secrets, and sign-in provider settings still have to be moved by hand.
Lovable's own docs say there is no one-click migration from Cloud to your own Supabase. The exporter is the closest thing to one: it does the restore, the users, and the storage files in one run.
How the exporter works
- Add a temporary helper. Tell Lovable to create an empty edge function called
migrate-helper, then paste in the code the tool generates, protected by an access key only you know. The exporter uses this read-only endpoint to fetch your data, so you never hand over your Lovable login. - Choose a destination. Transfer into an empty Supabase project you own, or download everything as a ZIP backup.
- Run the export. Tables, users, and storage files copy across in one pass. Small projects often finish in a few minutes.
- Move your config. Pick how you'll keep building and follow the checklist for what the tool doesn't move: Edge Function code, secrets, and login provider settings.
- Clean up. Remove the
migrate-helperfunction and delete the temporary Supabase secret key you created for the transfer.
The hosted version runs each job in a temporary Cloudflare container that's destroyed afterward, and migration data isn't kept once the job finishes. If you'd rather nothing pass through our infrastructure, run the open-source CLI locally. Either way, rotate any secrets you used once the migration is done.
You don't have to leave Lovable
Once your backend is in your own Supabase, you can connect it to a new Lovable project and keep building with the same workflow. A few features need Lovable's built-in backend and don't carry over, such as the in-editor Database and Users views, sign-in setup through chat, and signed-in browser testing. You manage your data, users, and sign-in settings in the Supabase dashboard instead.
What changes is who holds the keys:
- On Lovable Cloud: Lovable manages the project. You can browse data and run SQL inside Lovable, but there's no connection string for outside tools, and billing runs through your Lovable credits.
- On your own Supabase: the same stack in an account you control. You get a real connection string, the Supabase dashboard, backup settings you manage, and any tool that speaks Postgres.
Because it's Supabase on both sides, your app's data model doesn't change. The repo's guide covers four paths: staying on Lovable with your own Supabase, developing locally while deploying through Lovable, hosting elsewhere, or going fully self-managed.
Under the hood
There's no custom migration format and no intermediary API: pg_dump extracts, pg_restore and psql load. The exporter handles the parts that make a Supabase-to-Supabase move tricky: auth tables, storage buckets, row-level security (RLS) policies, and the order tables must load in.
We open-sourced the CLI, migration runtime, and helper code under the MIT license because anyone on Lovable Cloud who wants to connect an outside service has this problem. Read the source, run it locally, or fork it.
Get started
- Want it done for you? Use the hosted Lovable Cloud to Supabase Exporter. Sign in with Google or email and follow the steps. It's free for every project size.
- Want to run it yourself? The CLI and migration runtime are on GitHub. You'll need Node.js 22 and Docker.
If you'd like hands-on help, the tool page also offers a paid expert migration review and a done-for-you migration.
Questions or feedback? Find us on X or r/dreamlitai, or star the GitHub repo if it saved you a weekend.
Where Dreamlit fits
After the export puts your data in your own Supabase project, Dreamlit can connect to it. Add Dreamlit to your AI agent and ask for onboarding or trial emails; it builds the workflows from your tables and previews them with real user data before you publish. Dreamlit doesn't connect to Lovable Cloud's managed database.
Start a 7-day free trial or connect your agent.
Frequently asked questions
How do I move from Lovable Cloud to my own Supabase project?
Lovable has no one-click migration. You can restore Lovable's built-in database export yourself with Postgres tools and move storage files separately, or use the free Lovable Cloud to Supabase Exporter, which copies your tables, users, and storage files straight into your Supabase project.
Does Lovable have a built-in export?
Yes. Lovable Cloud can export your full database, including users' password hashes, as a backup file. It works for databases using up to 15 GB of storage, the file can be up to 5 GB, you can request one export every 24 hours, and it doesn't include storage files, Edge Function code, or secrets.
Does the exporter require users to reset their passwords?
No. The exporter copies user accounts with their password hashes intact, so users keep their existing passwords. They may need to sign in again after you switch your app to the new project.
What does the exporter move, and what doesn't it move?
It moves your database tables, user accounts, and storage files. It doesn't move Edge Function code, API keys and secrets, login provider settings such as OAuth redirect URLs, or your hosting setup. The tool gives you a checklist for those.
Can I still use Lovable after exporting my data?
Yes. Connect your new Supabase project to a new Lovable project and keep building. You hold the keys to the backend, but a few features only work on Lovable Cloud, such as the in-editor backend views, sign-in setup through chat, and signed-in browser testing.
Is the Lovable Cloud to Supabase Exporter free?
Yes. The hosted tool on dreamlit.ai is free for every project size; you sign in with Google or email to run it. The CLI and migration runtime are open source under the MIT license, so you can also run them on your own machine.
What is the difference between Lovable Cloud and Supabase?
Lovable Cloud is a managed backend built on Supabase's open-source foundation, and Lovable runs it for you. Your own Supabase project is the same technology, but you manage the account, backups, and dashboard, and you can connect any tool that speaks Postgres.
About the Author

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

Lovable Email Setup: 4 Flows Your App Needs Before Launch
How to set up Lovable email: auth emails, app emails, email blasts, and recurring emails, using Lovable Cloud Emails, Resend, or your own Supabase project.

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.