Free tool

Lovable Cloud to Supabase migration checker

Paste the GitHub repo your Lovable project syncs to. You get a checklist of everything that has to move to your own Supabase project, and the parts that quietly break if you miss them.

Updated October 2026 for Lovable Cloud's Export, Pause and Remove options. Private repo? Use the cost check, which connects to GitHub.

Runs in your browser: your code goes from GitHub to this page and nowhere else. Public repos only. Private repo? Book a free call and we run it with you.

What it checks

Database

Tables, row level security and policies, functions, triggers, enums, views, extensions, Realtime tables and pg_cron jobs, read from supabase/migrations and the generated types.

Auth

Email and password, magic links, OAuth providers, the new-user trigger and redirect URLs, plus Google sign-in that runs through Lovable's own OAuth app and emails sent through Lovable's built-in email queue.

Storage

Buckets created in migrations or used in code, the storage policies that guard them, and file URLs saved with the old project's address.

Edge functions

Every function in supabase/functions, the secrets each one reads, functions that skip JWT checks, and calls to Lovable's AI gateway.

What breaks after a migration

None of these show up in a quick test. They show up when a real user hits them, usually after the Cloud project is gone.

Google sign-in stops working

Lovable apps often sign in with lovable.auth.signInWithOAuth, which uses Lovable's Google app, not yours. On your own Supabase you need your own Google OAuth client and supabase.auth.signInWithOAuth.

AI features go quiet

Edge functions that use LOVABLE_API_KEY call Lovable's AI gateway, which only works inside Lovable Cloud. They need your own OpenAI or Gemini key.

Signup and reset emails never arrive

Supabase's built-in email only sends to your own team and is heavily rate-limited, so auth emails need custom SMTP. Apps using Lovable's built-in email queue also need it rewired to your own provider, or app emails stop without an error.

Images and files disappear

Apps often save full file URLs with the Cloud project's address in the database. They keep loading until Cloud is removed, then every cover, avatar and upload 404s. They have to be rewritten as part of the move.

Private data becomes readable

A new Supabase project grants the public roles access to restored tables and functions by default, and the dump doesn't take that back. Restore without checking grants and data that was private on Cloud can be readable with the public key.

The live site still talks to the old backend

After Remove Cloud, the published app points at the deleted project until you connect the new one and republish. Connecting a Supabase organization also needs Admin on the Lovable workspace, which is easy to discover too late.

Want the full picture first? Read Lovable Cloud vs Supabase.

Questions

Does the checker see my data or my keys?

No. It reads the code in your GitHub repo (migrations, edge functions and app code) inside your browser. It never connects to your database, never reads your .env file and sends nothing to us.

Why does it need the GitHub repo and not my Lovable project?

Lovable syncs your project to GitHub, including the supabase/migrations and supabase/functions folders. That is the only place the full backend definition is readable from outside Lovable.

How accurate is it?

It reads what is in the repo. If a table or policy was changed directly in the Cloud database and never written to a migration, the checker cannot see it. Before you migrate, compare with a schema dump of the Cloud database.

Will my users have to sign up again?

No. Lovable Cloud's export includes auth.users and auth.identities with the password hashes, so restored users keep their password. Users who signed in with Google through Lovable need your own Google OAuth client set up first (and published, not left in Testing mode), then they sign in to the same account as before.

Lovable Cloud has an Export button now. Isn't that the whole migration?

It's the first step. The export is a database dump (up to 5 GB, once every 24 hours). It leaves out storage files, edge function code and secret values, and a fresh Supabase project already has its own system schemas, so the dump has to be restored selectively. After that come the parts that break quietly: grants, stored file URLs, Google sign-in, emails and the cutover in Lovable itself.

My repo is private. Can I still use it?

The browser version only reads public repos, because it uses GitHub without a login. Book a free call and we will run it on your private repo with you.

Want it done for you?

We move Lovable Cloud projects to your own Supabase for a fixed price: data, users, files, functions and secrets.