No way to get your database out of Lovable Cloud

You decide to move. You can export the code. Historically you could not extract the data, and no documentation described a way.

Lovable Cloud is a managed layer over Supabase rather than a Supabase project you hold credentials to. Without connection credentials there was no pg_dump and no standard export, so the only routes out were the application's own APIs, CSV-per-table from the Cloud UI, or printing the connection string from inside an edge function - a workaround the community openly called a backdoor. The hardest part was never the table data: it was auth.users, because moving accounts without the original password hashes forces a password reset on every user.

Use Lovable's official export, which now exists (see resolvedNote). If you are on an older project or the official path does not cover your case, the community routes are: (a) Lovable's MCP server to query the Cloud database directly including auth.users, (b) per-table CSV export from the Cloud database UI, then import into a Supabase project you own, (c) open-source exporters such as dreamlit-ai/lovable-cloud-to-supabase-exporter. Whichever route you take, audit RLS on the target immediately after import and before sending production traffic - RLS state is per-table and does not reliably survive a dump/restore, so a migration can silently land you in the supabase-row-level-security-not-enabled failure. Then test with two real accounts, not one.