Introduction

SupaMigrate moves a Lovable Cloud project to a Supabase project you own — schema, data, auth users, and storage — without you writing migration scripts. Your source project is only ever read; nothing is modified on it.

What gets migrated

• Schema — tables, columns, constraints, indexes, sequences, enums, functions, triggers, views, and RLS policies. Migration files are replayed, and objects created ad-hoc in the SQL editor are reconstructed by introspection ("gap-fill").
• Data — every row, inserted in foreign-key order with sequences resynced afterwards. Large tables are batched and the step is resumable.
• Auth — users are inserted into auth.users with their UUIDs and bcrypt password hashes preserved, so people don't have to reset their passwords.
• Storage — buckets and their objects are transferred file by file.

What you need

• The destination Supabase project (create a free one at supabase.com).
• The destination database password and service_role key.
• A few minutes of an open browser tab — heavy steps run in the browser and Edge Functions, so the tab must stay open for the duration.

What SupaMigrate does not do

It doesn't modify your source project, it doesn't store your credentials server-side, and it doesn't move things it can't verify. When a step can't be completed safely, it stops and tells you why rather than guessing.

Next: the quickstart.