LOVABLE CLOUD TO YOUR OWN SUPABASE
Take full control of your data. We move your backend from Lovable Cloud to a Supabase project you own: data, users, files, functions and secrets. Fixed price from $150, and you keep building in Lovable.
Not sure what your project has? Run the free migration checker on your repo.
Lovable Cloud
Managed Supabase
Your Supabase
Full control
WHY MIGRATE?
Own your infrastructure. Scale on your terms. No vendor lock-in.
Full Control
Access your Supabase dashboard directly. Manage database extensions, connection pooling, backups, and configurations without restrictions.
Separate Bills
On Lovable Cloud your database, storage and traffic spend the same credits you build with, and the backend pauses if they run out. Supabase bills separately: a free tier, then $25/mo Pro.
Custom Configuration
Choose your own region, configure edge functions, set up custom domains, and integrate with your existing DevOps pipeline.
LOVABLE CLOUD VS YOUR OWN SUPABASE
Lovable Cloud is a Supabase project that Lovable runs for you. Moving doesn't change your database engine or your code. It changes who holds the keys and who sends the bill.
| Lovable Cloud | Your own Supabase | |
|---|---|---|
| Database | Postgres, run by Lovable | Postgres, in your Supabase account |
| Supabase dashboard | No | Yes: table editor, logs, auth settings |
| Connection string | No | Yes: pgAdmin, TablePlus, pg_dump |
| service_role key | No | Yes: n8n, Make, cron workers, scripts |
| Backups | Not in your control | Daily on Pro, point-in-time recovery as an add-on |
| Billing | Run credits from the same balance you build with (20 credit monthly Cloud grant, then general credits) | Supabase rate card, free tier then $25/mo Pro, separate from your Lovable plan |
| If the balance hits zero | Backend pauses: no logins, no data access, no export until it wakes | Your app keeps running. Building in Lovable stops, the backend does not |
| Team access | Only through Lovable | Invite developers to your Supabase org |
| Keep building in Lovable | Yes | Yes, same project, now connected to your Supabase |
- Database
- Lovable Cloud: Postgres, run by Lovable
- Your Supabase: Postgres, in your Supabase account
- Supabase dashboard
- Lovable Cloud: No
- Your Supabase: Yes: table editor, logs, auth settings
- Connection string
- Lovable Cloud: No
- Your Supabase: Yes: pgAdmin, TablePlus, pg_dump
- service_role key
- Lovable Cloud: No
- Your Supabase: Yes: n8n, Make, cron workers, scripts
- Backups
- Lovable Cloud: Not in your control
- Your Supabase: Daily on Pro, point-in-time recovery as an add-on
- Billing
- Lovable Cloud: Run credits from the same balance you build with (20 credit monthly Cloud grant, then general credits)
- Your Supabase: Supabase rate card, free tier then $25/mo Pro, separate from your Lovable plan
- If the balance hits zero
- Lovable Cloud: Backend pauses: no logins, no data access, no export until it wakes
- Your Supabase: Your app keeps running. Building in Lovable stops, the backend does not
- Team access
- Lovable Cloud: Only through Lovable
- Your Supabase: Invite developers to your Supabase org
- Keep building in Lovable
- Lovable Cloud: Yes
- Your Supabase: Yes, same project, now connected to your Supabase
Still validating your idea, with nobody else needing database access? Staying on Cloud is fine. Move when a developer needs access, you need backups you can restore, or you can't explain the bill. How the credits work now is in Lovable pricing: where the credits go. We wrote up the full comparison in Lovable Cloud vs Supabase: which should your app run on?
WHAT ACTUALLY MOVES (AND WHAT BREAKS)
Updated October 2026 for Lovable's native Cloud Export
Lovable added an official exit: Cloud → Overview → Advanced settings lets you export your project data and remove Lovable Cloud, then connect the same Lovable project to a Supabase project you own. The export is a database dump of up to 5 GB, and you can run it once every 24 hours. It includes your auth users with their password hashes, so people keep their passwords. The database part is the easy bit. The parts people trip over are the ones the export leaves behind.
Moves cleanly
- tableSchema, tables and all rows
- lockRLS policies, functions and triggers
- personAuth users, identities and password hashes
- codeEdge functions, with the right verify_jwt settings
- syncCron jobs and database extensions
Needs hands-on work (this is the part we do)
Storage files
The export carries the bucket records, not the files. They have to be downloaded and re-uploaded with their paths intact.
Stored file URLs
Image and file URLs saved in your tables still point at the old Lovable Cloud host. They keep working until you remove Cloud, then every one of them 404s.
Secrets
You get the names, never the values. API keys for Stripe, OpenAI, Resend and the rest need re-entering on the new project.
Google sign-in and auth settings
Lovable's managed Google login stops working once you leave Cloud. You need your own Google OAuth client, published "In production", plus redirect URLs, email templates and SMTP recreated by hand.
Access after the restore
A straight restore leaves the public anon role with more table and function access than it had on Cloud. We check and tighten it before anyone points the app at the new database.
Built-in emails
If your app sends email through Lovable's built-in queue, it goes quiet after the move until the queue is wired up again on your project.
The cutover
The published site keeps talking to the old backend until you republish, and the repo still names the old project. We switch everything in one sitting.
HOW THE MIGRATION WORKS
-
01
Quick call
We look at your project together: table count, storage, auth providers, edge functions. You leave with a fixed price. Book it here.
-
02
Give us access
Invite us to your Lovable project and your Supabase organization. Both take about two minutes, with screenshots.
-
03
Migrate and verify
Schema, data, files, functions and secrets go across. Then we check row counts table by table, sign in as a test user and open uploaded files before anything is switched.
-
04
Switch over, you own it
Your Lovable project points at your own Supabase. Dashboard, service role key, backups and billing are yours, and you keep building in Lovable as before.
From a client who moved off Lovable Cloud
Lovable is a great website builder but if you host your website on Lovable and your website scales you will spend hundreds or even thousands of dollars keeping up your website, and that's why I recommend (Lovable2Live.com) because this business will help you migrate your website off of Lovable onto your own Supabase and if you don't know Supabase is way cheaper to scale started at 1GB of storage/data for free so (Lovable2Live.com) will save you from spending hundreds of dollars
MIGRATION PRICING
Pricing based on the number of tables in your Supabase instance.
Small
1–5 tables
- check_circle Schema Migration
- check_circle Data Transfer
- check_circle RLS Policy Migration
- check_circle Connection String Update
Medium
6–15 tables
- check_circle Everything in Small
- check_circle Storage Bucket Migration
- check_circle Edge Function Migration
- check_circle Auth Provider Setup
Large
16+ tables
- check_circle Everything in Medium
- check_circle Complex Trigger Migration
- check_circle Performance Optimization
- check_circle Post-Migration Support
Lovable Cloud to Supabase: FAQ
Can I move my app off Lovable Cloud?
expand_more
Yes. Lovable has an official export under Cloud, Overview, Advanced settings, and afterwards the same Lovable project can be connected to a Supabase project you own. The export covers the database, including auth users. Storage files, stored file URLs, secrets, Google sign-in and the cutover need extra work, which is what we take care of.
Will my users have to reset their passwords?
expand_more
No. Lovable's native Cloud Export includes auth users with their password hashes, so after a correct restore everyone signs in with the password they already have. Users who signed in with Google need your own Google OAuth client set up, which we do as part of the move.
Isn't Lovable's Export the whole migration?
expand_more
It is the database part. It leaves out storage files, edge function code and secret values, and it does not fix file URLs saved with the old host, Google sign-in, the public role's access after a restore, or the published site still pointing at the old backend. Those are the steps that break apps, and they are the steps we handle.
What if my database is bigger than 5 GB?
expand_more
The built-in export stops at 5 GB. Mention the size when you book the call so we can plan the export path before anything is touched.
Can I keep building in Lovable after the migration?
expand_more
Yes. It is the same Lovable project, just connected to your own Supabase instead of Lovable Cloud. You keep prompting and shipping the way you do now.
Will my app go down during the move?
expand_more
The heavy lifting happens on the new project while your app keeps running. The switch itself is short, and we schedule it for your quietest hour.
Why move if Lovable Cloud already runs on Supabase?
expand_more
On Lovable Cloud you do not get the Supabase dashboard, the service role key or the database URL, and you cannot pick your plan, region or storage limits. With your own project you see everything, choose the plan that fits, and pay Supabase directly. Supabase has a free tier and paid plans start at $25 a month.
How is Lovable Cloud priced?
expand_more
Since June 2026, Lovable Cloud is billed in credits from the same balance you use to build. Every plan gets a 20 credit monthly Cloud grant (marked temporary by Lovable). After that, database server time, database storage, file storage, network traffic, compute and realtime all draw from your general credits. A bigger instance size uses more credits per hour, and stored files keep costing credits while a project is paused.
What happens to my app if my Lovable credits run out?
expand_more
The published site stays up, but AI features stop and the built-in backend pauses shortly after the balance reaches zero, so users cannot sign in or load data. Lovable says the data stays safe but cannot be accessed or exported until the services run again, and you may need to click Wake up after adding credits. On your own Supabase project, running out of Lovable credits only stops building.
What does it cost?
expand_more
A fixed price based on the number of tables: $150 for 1 to 5 tables, $350 for 6 to 15 (adds storage, edge functions and auth providers), and $600 for 16 or more (adds complex triggers, performance tuning and post-migration support).
What do you need from me?
expand_more
Editor access to your Lovable project and an invite to your Supabase organization. We have step-by-step guides for both.
Ready to Own Your Data?
Take full control of your Supabase instance. We handle the migration so you can focus on building.
Rather talk it through? Book a free 1:1 call.