Documentation
Documentation
Everything needed to migrate a Lovable Cloud project to a Supabase project you own — from connecting both databases to validating the result.
Getting started
Migrating
- Connect the sourcePoint SupaMigrate at your Lovable Cloud project. Where to find the project ref and keys, why the connection uses the IPv4 pooler, and how to verify read-only access.Read
- Connect the destinationCreate an empty Supabase project, find its database password and service_role key, and connect it as the migration target — credentials stay in your browser.Read
- Migrate the schemaReplay your Lovable Cloud schema onto your own Supabase project in DDL dependency order, gap-fill what replay misses, and resolve the common failures.Read
- Migrate the dataCopy table rows from the source to your own Supabase project using FK-ordered batched inserts, ON CONFLICT DO NOTHING, and a sequence resync at the end.Read
- Migrate auth usersMove Supabase auth users to your own project with UUIDs and bcrypt password hashes preserved, so nobody has to reset their password after the migration.Read
- Migrate storageCopy Supabase Storage buckets then objects file by file. Idempotent bucket creation, signed-URL downloads, and re-upload to your own project.Read
After migration
- Validate the migrationRun end-to-end checks on your destination Supabase project after migration: row counts, a sample API read, an auth check, storage, and manual follow-ups.Read
- TroubleshootingA triage guide for failed Lovable-to-Supabase migrations: route connection, schema, and data errors to the exact fix and decode any Postgres error string.Read