Marked as helpful by the asker
Switching the connection is the easy part (disconnect, reconnect, pick the other project). The tables won't move with it though, they live in the tutorial project.
So:
- In the tutorial project, SQL editor: copy the schema. Easiest is to check if Lovable put migration files in
supabase/migrations/in your code, those can just be run in the new project in order. - Run them in the new project's SQL editor.
- Data: if it's test data, skip it. Otherwise export per table as CSV and import.
- Then switch the connection in Lovable, and check the app's env vars point to the new project.
- Auth settings (Site URL, providers) are per project, redo them.
Or the honest shortcut: if the tutorial project is otherwise empty, just rename it in Supabase and keep using it. Nothing forces you to move.
Oh I didn't realize I can just rename it. Did that. Easy renata_builds · edited
Best kind of migration is the one you don't do. mira_dev · edited