Short answer
Export the database from Lovable (it includes your users and their password hashes) and restore it into your own Supabase project. Then move storage files, edge functions, secrets and sign-in settings by hand, and switch the app over. Anyone signed in at the switch signs in once more. Keep the built-in backend until the new project works, because removing it can’t be undone.
The move, in the order that loses nothing
01
There is no one-click move
“Lovable does not move a project from the built-in backend to your own Supabase project in one step.” Lovable docs, Lovable Cloud
Lovable runs its built-in backend, called Cloud in parts of the product, on Supabase’s open-source foundation, and documents a manual path to a Supabase project you own. It isn’t a trap: your code is yours and can sync to a GitHub repository you control. It is developer work, and the steps below are that path.
02
Export the database, users included
“It also includes your users' accounts and their password hashes” Lovable docs, Database backups
The export is a compressed PostgreSQL archive with the full structure and data, restored into the new project with pg_restore, not pasted into the SQL editor. Lovable allows one export every 24 hours and only while the database is running, so resume a paused project first.
03
Move what the export leaves out
“It does not include files in storage, edge function code, secrets, sign-in provider settings, or your project's API keys” Lovable docs, Database backups
Download the storage files and upload them to the new project. Deploy the edge functions from supabase/functions in your repository with the Supabase CLI. Enter the secrets again, set up the sign-in providers in the Supabase dashboard, and replace any Lovable connectors and AI calls with your own accounts, since Lovable doesn’t export those connections.
04
Switch the app over, then test sign-in
“Users who are signed in when you switch need to sign in again” Lovable docs, Database backups
Stop writes for a short window, take a final export and restore it, then point the app at the new project and deploy. Test sign-in, payments, uploads and every function before telling users. Anyone signed in signs in once more; their passwords still work.
05
Only then remove the built-in backend
“Removing the database deletes the database, its backups, your app's user accounts, and the files in storage, and cannot be undone.” Lovable docs, Pause or remove
Keep it running until the new project has served real traffic. Lovable says exports saved in its storage are deleted with it, so keep your copies somewhere else.
Checked against the vendor’s docs on : Lovable docs: Lovable Cloud (built-in backend), FAQ; Lovable docs: Database backups and export; Lovable docs: Pause or remove a database; Lovable docs: Supabase integration; Lovable docs: Deploying and hosting outside Lovable; Lovable docs: What you own and self-hosting; Supabase docs: Migrating auth users between projects.
Rather hand it over?
Start with a paid consultation to agree the plan, then get a written quote with a fixed price.
- $100 per 15 minutesPaid consultationGo through the app and the move with Simon and agree the plan.Book a consultation
- Written quoteDescribe the app, such as its tables, sign-in providers and connectors, and get a fixed price and timeline in writing; we reply by email, usually within one business day.Describe your project
Related: Lovable app rescue · Supabase RLS fixes