Lovable Cloud to Supabase: how to move your data and keep the app working

Quick verdict

Get an engineer for this one. A database export and restore with no undo.

How serious: High
Fix it yourself?: No, get an engineer
Typical cost: $300–$25,000 to move off the builder (prices)
Top rated for Lovable: Afterbuild Labs · 10.0/10

Lovable Cloud runs on Supabase, but the project is owned by Lovable, so there is no button to transfer it to your own Supabase account. You create a new Supabase project, export the database from Lovable, restore it, copy storage files, set secrets and sign-in providers again, and point the app at the new backend. Lovable's docs give the exact steps.

What you see, and what it usually means

What you see	What it usually means
Your database does not appear in your Supabase account.	The project uses Lovable Cloud, which Lovable owns and manages.
You need a service role key or a direct database URL and cannot get one.	Lovable Cloud does not expose them. Only a migration gives you that access.
You want to disconnect Lovable Cloud and connect your own Supabase.	Once enabled, Cloud cannot be switched to an external connection in place.
After a migration, nobody can sign in.	Providers and redirect URLs were not set up on the new project.

Why it happens

Lovable's built-in backend, called Lovable Cloud, uses Supabase's open-source foundation, but the Supabase project behind it is provisioned and managed by Lovable. Supabase's docs say these projects are not owned by your account, do not appear in your dashboard, do not expose service role keys or connection strings, and have no automated transfer path. Once Cloud is enabled, the project cannot be disconnected or switched to an external Supabase connection.

So moving is a copy, not a transfer. Git sync gives you the code and the migration files that define the schema, but never the data, the uploaded files, or the secrets. Each is a separate step, and sign-in providers, scheduled jobs and Edge Functions must be set up again on the new project. Lovable's external hosting guide documents all of it, including the export button and the restore warnings.

Check these first

OPS-01Critical

Database backups run automatically and a restore has been tested

Check what your database plan actually includes, then restore a backup into a test project once.

DATA-01Critical

Access rules are on for every table

In Supabase, open Table Editor: every table should show RLS enabled, with at least one policy. In Firebase, your rules should never say allow read, write: if true.

AUTH-01High

Sign-up confirmation and password reset work end to end

Use a real inbox. Check that the link arrives, points to your live domain, and works once.

OPS-04Medium

Secrets live in the host's environment settings

Keys belong in environment variables on the server, not in the repository or in front-end code.

OPS-02High

Testing and real users use separate databases

Experiments and AI agents should never run against production data.

CODE-01High

The code lives in a Git repository you own

Connect GitHub or export the project. If the builder account is lost, the product should not be.

Fix it yourself

Confirm what you have. Click the Cloud icon in the top bar of the editor. Menus for tables and users inside Lovable mean Lovable Cloud. A Supabase icon with your project name means you already own the backend.
Connect Git sync and create the destination: on supabase.com click New project, then apply the schema by running the files in supabase/migrations/ in the SQL editor in timestamp order, or with npx supabase link and npx supabase db push.
Export the data: More → Database → Manage → Settings → Export data, then Export on the Database card and Start export. Lovable emails you and the file appears under More → Storage. Exports are limited to one every 24 hours.
Restore with pg_restore into the new project. The file is a PostgreSQL custom-format backup, not SQL. Test on the new project first and do not add --clean without understanding that it drops the objects being restored.
In Supabase, open Authentication → Sign In / Providers and enable each provider, then update redirect URLs in Google or GitHub to the new project. Exported users keep their passwords, but everyone signs in again.
Download each bucket from More → Storage and upload to matching buckets in Supabase. Add every secret under Edge Function Secrets, because Lovable secrets are not exported, then run npx supabase functions deploy.
Set VITE_SUPABASE_URL, VITE_SUPABASE_PUBLISHABLE_KEY and VITE_SUPABASE_PROJECT_ID for a test deployment, verify sign-in, records and uploads, then in Lovable edit .env and supabase/config.toml with the new values. Do a final export with writes paused, because records written after the export are not included.

When to get a human engineer

This is the job most founders hand off, and it is in the move-off-the-builder band of $300 to $25,000. A small app with a few tables sits at the low end and takes a day or two. An app with real users, uploads, webhooks and Edge Functions needs a timed rehearsal, a pause window, and a check that one customer cannot read another's rows on the new project. Do not remove the Lovable database until the new backend is verified, because removal permanently deletes it, including exports saved to its storage.

Top-rated companies for Lovable apps

Ranked by our score: published prices, scope of work, AI tools named, timing and a low-risk first step. How we score.

1Afterbuild Labs10.0/10Best for: A check before launchFree first step · from $49
2Redlab10.0/10Best for: A full rescue by one team that keeps buildingFree first step · from $490
3Vibe Code Rescue (Lev Arakelyan)9.0/10Best for: A one-off check and a cleanupFrom $299

All 59 Lovable companies, ranked

Questions

How do I export my Lovable managed Supabase data?

In Lovable go to More → Database → Manage → Settings, click Export data, then Export on the Database card and Start export. You get an email when the custom-format backup file is ready to download from More → Storage.

Can I just connect my own Supabase to the existing Lovable project?

Not once Lovable Cloud is enabled. Supabase's docs say the project cannot be disconnected or switched. You create a new Supabase project, move the data, and change the project's .env and config.toml to point at it.

Will users have to reset their passwords after the move?

Lovable's guide says exported users keep their passwords because the hashes come with the export, but everyone must sign in again. If accounts cannot be restored, fall back to a password reset flow.

Sources: Lovable docs: Deploying and hosting outside Lovable (Supabase example); Lovable docs: Self-hosting and data portability; Lovable docs: Lovable Cloud (built-in backend); Supabase docs: Can't access Supabase project when using Lovable Cloud; Supabase docs: Identify Lovable Cloud or your own Supabase.