Fixes · Data, email and payments

Move your data off Lovable Cloud to your own Supabase

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.

Most common in apps built with Lovable.

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, and let it make the change.

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.

Don't change what the app does.
Never put a secret key or password in the code: read it from an environment variable.
If a step has to be done outside the code, like revoking a key in a provider's dashboard, list it for me at the end instead of skipping it.

How Launchpad helps

launchpad db restore loads Lovable Cloud's export into your new project in one transaction, users and their passwords included.

Check your app for this, free Join the waitlist