Stage 5 of 6 · Move the data

Stage 5: move the data to a Supabase project you own

Your database, logins, files and server code end up in a Supabase project you own, and changes go live from your GitHub instead of through Lovable's chat. This is the only stage that can lose data, so it follows a fixed order.

You are here when

You need your own database: to open it yourself, to hand it to someone who needs it, because a client or an investor requires it, or because you want to leave Lovable completely. If your database is already your own Supabase project, this stage is shorter: it hands the job of putting changes live to Supabase’s GitHub integration (Supabase docs).

What usually goes wrong at this stage

What it costs: about an hour when the database is already yours; half a day or more to leave Lovable Cloud, with a pause on changes to your data during the switch. Supabase’s free plan pauses projects after a week of low activity and has no managed daily backups, so an app with real users belongs on a paid plan (Supabase docs, Supabase docs).

What this stage gets you

A database you can open yourself, in your own account, with your own backups; database changes and server functions that go live from your GitHub; and no part of the app that only Lovable can reach. You can still use the Lovable editor afterwards by connecting it to your new project (Lovable docs).

When to move on

When someone else starts working on the app: stage 6.

Short answers for this stage

The full stage, step by step with the agent prompts, is in the paid guide that comes with the kit.

Not sure which stage your app is in?

The free check asks five questions about your app and gives you the path, what usually breaks on it, and what it costs. It asks; it does not look at your app. About a minute, no email.

If you would rather have your AI agent do the work with you, the kit is $19, one payment: the full guide, an agent skill that runs each stage, guardrails and checks.