Your Lovable app keeps its database in Lovable Cloud. If you want it in a Supabase project you own, I move it and check it table by table, so nobody has to sign up again.

What moves:

The schema: tables, row level security, policies, functions and triggers.

Your data, table by table, and your users with their password hashes.

Storage buckets with their access rules, and the files in them.

The grants your app's API roles need, written explicitly. From 30 October 2026 Supabase stops adding them to new tables on its own.

What we do together, in writing: scheduled jobs (pg_cron) are recreated, sign-in providers are reconnected with your own keys, and the new keys go where your site runs. You switch the site over with my step-by-step notes, and Lovable Cloud stays as it is until you confirm everything works.

You get a count of every table, user and file on both sides. I need a Supabase project on your account with me invited as a member (never your database password). You start the export in Lovable (Cloud → Advanced settings → Export data) and send me the file; Lovable allows one export a day.

One app takes 1 to 2 days. From $350. Support after the move is $80 a month: backups, updates and a check of access rules after changes made in Lovable.

Our own test move: 30 tables, 77 of 77 bookings and an identical password hash on the new project. https://flowlab-dev.github.io/work/lovable-to-supabase/

Send me your Lovable project name and usually within a few hours I'll list what moves and what needs a manual step.