away from lovableWhere it is
In your project: More → Cloud → Overview → Advanced settings → Export project data, then Export data, and Export in the Database card. Lovable emails you a download link when it is ready, and also saves the export to your project’s Cloud storage, where you can download it from More → Cloud → Storage (Lovable docs).
Limits: databases up to 15 GB, an export file of at most 5 GB, and one export every 24 hours (Lovable docs). It is a copy of the moment you click Export; anything written after that is not in it.
What is in it
- Every table, with its structure and its data. “The export contains your full database, both structure and data” (Lovable docs).
- Your users’ accounts and their password hashes, the scrambled form in which passwords are stored. Lovable’s docs: “If you restore the export into a Supabase project, your users keep their passwords” (Lovable docs). Supabase’s own docs say the same about moving users and their hashed passwords between projects (Supabase docs).
What is not in it
| Not in the export | Where it is instead |
|---|---|
| Files people uploaded | More → Cloud → Storage, downloaded separately (Lovable docs) |
| Edge function code | Your GitHub repository, under supabase/functions/, once GitHub is connected (Lovable docs) |
| Your project’s secrets (API keys for payments, email, AI) | Nowhere you can copy them from: Lovable’s secrets are write-only and their values are never shown again (Lovable docs). You get fresh values from each provider and enter them in the new project |
| Sign-in provider settings and the project’s API keys | Set up again in the new project; they are not part of the database (Lovable docs) |
Lovable’s docs sum it up: “You must reconfigure authentication, secrets, environment variables, and any external services in the destination platform”, and there is no one-click transfer from Lovable Cloud to Supabase (Lovable docs).
What your users notice
With the password hashes restored, users keep their passwords. Anyone who is signed in when you switch has to sign in once more (Lovable docs): each Supabase project signs its logins with its own secret, and existing logins stop working in a project with a different one (Supabase docs).
Test before you promise anything. Lovable’s docs end the same way: “After restoring, test that sign-in works” (Lovable docs). Sign up a test account with a password you write down before you export, and after the restore sign in with it, and with every other sign-in method your app offers. If your app sends login or password-reset emails, set up your own email sending in the new project: Supabase’s built-in sender is limited to 2 messages an hour (Supabase docs).
The button that deletes the export
Remove Lovable Cloud “permanently deletes your Cloud instance and cannot be undone”, and “You can’t download exports after you remove Cloud” (Lovable docs). So download the export and the files first and keep them somewhere safe. The export holds every user’s personal data, so keep it out of chats and shared folders.
The order that loses nothing: export, download the files, restore into a Supabase project you created, compare row counts table by table, test the logins, switch the app over, and only then remove Lovable Cloud.
If you want to keep using the Lovable editor
After Cloud is removed, More → Cloud offers Already have a Supabase project? Connect it here; the link only appears on projects that don’t have a backend (Lovable docs). Lovable supports managed Supabase and self-hosted Supabase as destinations for a Cloud backend (Lovable docs).
Not ready to leave?
Pause Cloud, in the same Advanced settings, stops the backend (database, logins, storage and edge functions) until you resume it. Storage keeps using credits, and while it is paused your published app can’t read or write data (Lovable docs). It suits a project nobody is using.
You may not need to move the data at all. Your code can go to GitHub, and the hosting to Vercel, while the data stays on Lovable Cloud. See the six stages, or take the free check to see which one your app is in.
Where this fits
This is part of stage 5, move the data. Other short answers: