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.
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 fromsupabase/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.Storage
Buckets created in migrations or used in code, and the storage policies that guard them.Edge functions
Every function insupabase/functions, the secrets each one reads, functions that skip JWT checks, and calls to Lovable's AI gateway.Three things that break after a migration
We see these in most Lovable Cloud projects. None of them show up until a user hits them.
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. Real users need a custom SMTP provider before launch.
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?
Not if you copy the auth schema (auth.users and auth.identities) with the password hashes. Users who signed in with Google through Lovable need your own Google OAuth client set up first, then they sign in as before.
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.
Rather talk it through? Book a free 1:1 call.