How to comot from Lovable Cloud go your own Supabase

Lovable Cloud or your own Supabase: which one you go use?

Lovable Cloud na Lovable built-in backend: database, authentication, storage, edge functions and AI, wey dem build on Supabase open-source foundation and you dey pay from your Lovable credits. To connect your own Supabase project mean say na you hold di account, di keys and di bill. None of dem wrong. Dem fit different stages.

Stay on Cloud while you still dey find out wetin di product be: na di fastest way to get backend at all. Move when you need something wey Cloud no dey give you, like direct database access for engineers, your own backups and point-in-time recovery, specific region for compliance, data processing agreement for your own name, or simply no vendor lock-in on di system of record.

Wetin Lovable Cloud export include, and wetin e dey leave?

Lovable advanced settings dey allow you export, pause or remove Cloud. As Lovable documentation talk, di export get your full database, both structure and data, and your users accounts with their password hashes. E no get files inside storage, Edge Function code or your project secrets, and you go need set up sign-in provider settings and API keys again for di new place. E dey work for databases wey dey use up to 15 GB of storage, di export file fit be at most 5 GB, and you fit request one export every 24 hours.

Two more controls matter during di move. To pause Cloud dey stop di database, authentication, storage and edge functions, so anything wey dey send email, collect payments or call AI go stop too, while dem go still bill storage. To remove Cloud dey delete di instance permanently and you no fit undo am. No remove anything until di new setup don run for production for some time.

How you go take move from Lovable Cloud to Supabase, step by step?

1. 01

   Create and secure di new project

   Create Supabase project inside your own organization, for di region wey you need, on plan wey get backups. On multi-factor authentication for everybody wey get dashboard access.

2. 02

   Export and import di database

   Export from Lovable advanced settings and restore di export inside di new Supabase project. From here keep di schema as versioned migrations, so you fit rebuild am from code.

3. 03

   Move wetin di export leave

   Copy storage buckets and files, redeploy Edge Functions from your code, and create new secrets and API keys. Take every old key as retired instead of copying am.

4. 04

   Connect Lovable to di new backend

   Lovable documentation describe how to connect your own Supabase project to fresh Lovable project. Do am, and agree how your team go continue to prompt there before di switch.

5. 05

   Connect authentication again

   Set up your sign-in providers (Google, email) again for di new project and test with real account. Lovable note say users wey dey signed in when you switch go need sign in again.

6. 06

   Check access rules again

   Run Supabase Security Advisor and di two-user test from our security checklist. Policies no dey always survive move without change.

7. 07

   Rehearse, then cut over

   Rehearse di whole move on copy, then switch production for quiet hour with written rollback plan. Keep Cloud paused, no remove am, until you sure.

My users go need reset their passwords?

No, if you restore Lovable export inside Supabase project: Lovable documentation talk say di export include users accounts and password hashes, so users go keep their passwords. Test am before cutover by signing in to di new project with account wey dey already. Wetin users go notice na say dem go need sign in again if dem dey signed in when you switch, and any social sign-in wey you forget to set up again.

Wetin dey usually break during Lovable Cloud migration?

• Files. Images and uploads go stay behind unless you move storage by yourself, and their URLs go change.
• Background work. Emails, payment handlers and AI calls dey live inside Edge Functions, wey di export no include.
• Webhooks. Stripe and other providers go still point to di old endpoints until you change dem, and their signing secrets go change with di new functions.
• Access rules. Policy wey refer to something wey only Cloud get fit fail closed (features go break) or open (data go leak).
• Lovable itself. Lovable documentation describe how to connect di new Supabase project to fresh Lovable project, so plan how your team go continue to prompt after di move.

You go do di migration by yourself or make engineers do am?

Small app wey no get payments, few files and small number of users na reasonable weekend project with di steps wey dey up. Di risk dey grow with live payments, plenty users and files, because mistake go show as lost uploads, double charges or data wey wrong people fit see. For those apps di move na engineering work with rehearsal and rollback plan. On our plans e dey part of di work, and after am we go run di new backend, with monitoring and emergency production support.