Moving from Lovable Cloud to your own Supabase project
Last reviewed 21 November 2026
Lovable’s built-in backend is the easy start. Some founders later want the database in their own Supabase account, for control, a developer, or an investor’s due diligence. It can be done, but nothing about it is automatic. Here’s what you gain, what you give up, and how the move works.
There’s no one-click move. You export the database from Lovable, restore it into your own Supabase project, and move uploaded files, backend functions, secrets and sign-in settings by hand. You also lose some conveniences that only work on the built-in backend, such as managed Google sign-in and in-editor tools. Plan it as a small project, and test before you switch.
Should you move?
Lovable Cloud is built on Supabase, and Lovable recommends choosing your backend early, because switching isn’t automatic in either direction. Moving to the built-in backend from Supabase isn’t supported at all. See Lovable’s backend guide.
| On your own Supabase you gain | You give up |
|---|---|
| The database in your own account and dashboard | Lovable’s in-editor database, users, storage, secrets, jobs and logs views |
| Direct access for developers and your own tools | Setting up sign-in from the Lovable chat, including managed Google sign-in |
| Your own Supabase plan and settings | Sign-in emails from your own domain, which need the built-in backend |
| A clearer path if you later leave Lovable | Lovable monitoring the backend for you |
What moves, and what doesn’t
- The database export includes the structure, data, user accounts and password hashes.
- It doesn’t include uploaded files, backend function code, secrets, sign-in provider settings or API keys, according to Lovable’s backup guide.
- App connectors and AI features run through Lovable only while the app uses the built-in backend. When you move, Lovable says to replace them with your own account for each provider, so plan and test each one before you switch.
- Scheduled jobs and email sending don’t carry over reliably, so set them up again.
The steps
- Export the database: More → Database → Manage → Settings → Export data. Lovable emails you when it’s ready. One export per 24 hours, and the database must be running.
- Download uploaded files from Storage, since they aren’t in the export.
- Create the Supabase project and turn on any extensions and webhooks the old database used, as Supabase advises.
- Restore the export with
pg_restorefrom PostgreSQL 16 or newer, with zstd support. Lovable warns that restoring everything over a fresh Supabase database can clash, so don’t just force it. - Deploy backend functions and set secrets with the Supabase command-line tool, as Lovable’s hosting guide lists.
- Set up sign-in providers again, and the Site URL and redirect addresses.
- Point the app at the new project by updating its Supabase settings, then test sign-up, sign-in, payments, emails and uploads.
Users keep their passwords, but everyone has to sign in again, because sessions are signed with the new project’s keys.
Don’t delete the old backend too soon
Removing Lovable’s built-in database permanently deletes the database, backups, user accounts and uploaded files, including any export saved in project storage. Download everything and run on the new project for a while before you remove anything.
When to get help
If the app has paying customers, plan the move with a developer and do it in a quiet hour, with a tested way back. See hiring a Lovable developer, or the wider guide to exporting your Lovable code.
Questions founders ask
Is Lovable Cloud the same as Supabase?
It’s built on Supabase’s open-source foundation, but it’s Lovable’s managed backend. You manage it inside Lovable rather than in a Supabase account of your own.
Can I move from my own Supabase back to Lovable Cloud?
Lovable says moving from Supabase into the built-in backend isn’t supported.
Will my users lose their accounts?
No, if the export is restored properly: it includes accounts and password hashes. They will need to sign in again.