Practical guide
How to move a Lovable Cloud app to your own Supabase project
Supabase documents that there is no automated transfer of a Supabase project from Lovable Cloud into your own Supabase account. The practical path is to clone the backend state into a new project and reconnect the application deliberately.
Do not create the new database and point the frontend at it before reconciling Auth, Row Level Security, storage, functions, secrets, and callbacks. A database-only move can leave the application partially functional or insecure.
- 01
Create the target Supabase project
Create the project under the account and organization that should own production, and record the target project reference and environment boundaries.
- 02
Inventory the Lovable backend
Capture schemas, tables, extensions, RLS policies, Auth configuration, users, identities, storage buckets, Edge Functions, secrets, webhooks, and scheduled behavior.
- 03
Clone database schema and records
Use supported database backup or PostgreSQL export/import methods, then reconcile table counts, constraints, relationships, extensions, and representative queries.
- 04
Migrate Supabase Auth deliberately
Move the Auth schema where appropriate, including users and compatible password hashes. Plan for JWT/signing-key differences and whether existing sessions must re-authenticate.
- 05
Rebuild storage and functions
Copy file objects and bucket policy, deploy functions to the target, recreate required secrets, and verify service-to-service permissions.
- 06
Recreate authorization policy
Verify RLS, grants, roles, tenant isolation, ownership rules, and admin paths against the target project rather than assuming they moved correctly.
- 07
Reconnect the Lovable application
Update project URLs and public/secret keys in the correct environments, then update OAuth callbacks, webhooks, allowed origins, and integrations.
- 08
Stage, reconcile, and cut over
Test login, data reads/writes, uploads, functions, realtime behavior, integrations, and denied access paths before switching production traffic.
Use evidence, not assumptions.
BeyondCode Deploy tracks runtime portability and deep application-state migration separately. A route does not become a production pass because the UI loads or the container builds.
Primary references