AskVibeMarked as helpful by the asker
First find out which one you have. In your repo, open src/integrations/supabase/client.ts (or .env) and look at the URL.
- If you created a Supabase account and connected it to Lovable, you'll recognize that project in your supabase.com dashboard. Then nothing to migrate. Point your local
.envand Vercel env vars at the same URL + publishable key and you're done. Users, passwords, data all stay. - If you were on Lovable Cloud, the backend is managed for you and you don't own a supabase.com project. Then you need to move data + auth users to a Supabase project you own. Use Lovable's own export route where possible, and plan it: test on a copy first.
Either way, don't forget:
- Auth → URL Configuration: add your new Vercel domain to Site URL / Redirect URLs, or logins break after the switch.
- Edge functions and their secrets: they live in Supabase, not in your repo (unless
supabase/functions/is in the repo, then deploy them with the CLI). - Stop prompting in Lovable once you've switched, two tools writing the same repo gets messy.
It's my own project, I recognize it in the dashboard. Relief. Switched env vars on Vercel and it works. emeka · edited
Forgot the redirect URL at first, google login went to the lovable domain. Fixed now emeka · edited
Good checklist. Would add: grab the migrations with
supabase db pull so your schema is in git from now on. jb_supa · edited