Quickstart

This is the shortest path from a Lovable Cloud project to a Supabase project you own. Set aside a few minutes and keep the browser tab open the whole time.

1. Create the destination project

In the Supabase dashboard, create a new project. Note its database password and, under Settings → API, its service_role key. Keep both private — SupaMigrate uses them in your browser only and never stores them.

2. Connect source and destination

Paste your source (Lovable Cloud) and destination credentials. SupaMigrate connects to both through the connection pooler so it works even from IPv4-only environments.

3. Analyze

SupaMigrate introspects the source: it counts tables, rows, users, and buckets, and builds a dependency graph. Nothing is written yet — this step is read-only and produces the plan.

4. Migrate

The steps run in dependency order:

schema → data → auth → storage → validate

• Schema replays your migrations and gap-fills anything created in the SQL editor.
• Data inserts rows in foreign-key order, then resyncs sequences.
• Auth inserts users with their UUIDs and password hashes intact.
• Storage copies each file into the matching bucket.

Each step is idempotent, so if one fails you can safely retry it.

5. Validate

SupaMigrate runs end-to-end checks on the destination — row counts, a sample API read, an auth check, and a storage read — and produces a report with anything you still need to do by hand (rotating secrets, re-adding OAuth providers, redeploying Edge Functions).

If a step raises a Postgres error, the error reference explains what it means and how to fix it.