An app on Lovable's built-in backend keeps its database on Lovable's cloud. Export it, load it into a Supabase project of your own, and your users keep their passwords.
What you see
Your Supabase project isn't in your own Supabase dashboard, because Lovable created it on Lovable Cloud.
Why it happens
Lovable doesn't move a project to your own backend in one step: the data has to be exported and restored, and storage files, secrets and sign-in settings set up again.
How to fix it
- In Lovable: More → Database → Manage → Settings → Export data, then Export on the Database card. Download it from More → Storage when Lovable emails you, with any files your app keeps there.
- Create a Supabase project of your own (Launchpad's wizard does it when you turn on Database with Supabase) and deploy.
- Load the export:
launchpad db restore <the export file>. The app's tables, policies and user accounts come across, so people keep their passwords. - Upload the storage files, and set up secrets and sign-in providers in the new project.
Or ask your AI tool to fix it
Paste this into Lovable, Bolt, v0, Replit or Cursor:
This app is moving from Lovable Cloud to my own Supabase project. Point the Supabase client at environment variables (VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY) instead of the values written into the code, and list every edge function and secret the app uses so I can set them up in the new project.
The full page, with the request ready to copy, is at launchpad.axonscape.com/fix/move-off-lovable-cloud. I work on Launchpad by Axonscape, which runs a free launch check for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.
Top comments (0)