Migrate from Lovable Cloud to Supabase
Leave Lovable Cloud without losing your data. Step-by-step guide to export, redeploy, and choose your hosting path.
Why Lovable users leave
Three reasons drive migration from Lovable Cloud:
Cost. Lovable's credit system looks like $25/month until you deploy. Real users report actual spend is 2-3 times the stated plan price. Credits burn faster than posted limits because they cover building, Cloud hosting, and AI features. The Pro plan mentions "500+ flexible credits" but doesn't price per action clearly. Monthly credit expiry adds pressure to spend or lose it.
Sovereignty. Lovable Cloud's hosting location is not explicitly documented. Teams needing GDPR compliance, EU data residency, or infrastructure ownership hit a wall. Supabase offers an EU region (Ireland). Self-hosted Supabase gives full jurisdiction control.
Control. Lovable Cloud is a managed layer on Supabase. If you want to own the infrastructure or move it elsewhere, you need to export and migrate. The fact that migration is possible but not automatic is the core frustration.
The good news: all three problems are solved by migrating to Supabase.
Is migration actually possible?
Yes. Lovable Cloud is built entirely on Supabase. No architectural mismatch exists.
Lovable's own documentation confirms: "There is no automatic migration between the built-in back end (Cloud) and your own Supabase project, in either direction." But no automatic does not mean impossible. Manual export works cleanly because both systems use PostgreSQL and identical function architecture.
Migration time: 15-20 minutes for database export and redeploy. No downtime required — you can build on Lovable Cloud while Supabase runs in parallel, then flip the switch when ready.
The unidirectional friction matters: migration from Supabase back to Lovable Cloud is not supported. This is the lock-in point. Migrating forward to Supabase is the escape route.
No automatic migration—but you're not locked in
Lovable's own docs confirm there's no automatic export path. Yet manual migration works cleanly. Cost, control, or GDPR: whatever your reason for leaving, the technical path is solid.
Step-by-step migration walkthrough
6 steps, 15-20 minutes of hands-on work. Test on staging first.
Sync your code to GitHub
Export your Lovable project to a GitHub repository. Lovable's built-in export syncs your React and backend code in a single push.
Create a Supabase project
Sign up for Supabase (free tier is fine for testing). Create a new project and note the project URL and API keys.
Export your database schema and data
Use pg_dump to export the Lovable Cloud database. This captures your PostgreSQL schema, tables, and data in a single SQL file.
Import into Supabase
Use psql or Supabase's SQL Editor to restore the dump. Your schema and data are now in Supabase.
Update environment variables
Replace Lovable's credentials with Supabase's. Change VITE_SUPABASE_URL and VITE_SUPABASE_KEY in your .env file.
Redeploy and test
Deploy your app pointing to Supabase. Test all flows: auth, database reads/writes, file uploads, real-time subscriptions.
What breaks during migration
Expect friction in three areas:
Storage buckets. Lovable Cloud stores files in managed buckets. Supabase Storage is a separate system. You must manually migrate files or re-upload. There's no bulk export tool—this is the longest step if you have large files.
OAuth providers. Google, GitHub, and other OAuth integrations store client IDs and secrets in Lovable. You'll need to re-enter these in Supabase. Create new OAuth apps in Google Cloud Console or GitHub if your Lovable setup used shared credentials.
Edge Functions routing. Lovable and Supabase both support edge functions, but path routing and deployment differ. Review your function URLs; they may have changed. Test all webhooks and background jobs.
Real-time subscriptions. If your app uses Supabase real-time subscriptions, be aware that Supabase Cloud has connection limits on the Pro plan (100 concurrent). If Lovable allowed unlimited, you may need the Team plan to scale.
None are showstoppers. They're admin tasks, not refactors.
Cost comparison: Lovable Cloud vs Supabase
| Plan | Price | Database | Best For | Real Cost |
|---|---|---|---|---|
| Lovable Pro | $25/mo stated | Managed, US | Indie makers | $50-75/mo actual (2-3x stated due to credit burn) |
| Supabase Cloud Pro | $25 base + usage | 8 GB included | Production apps | $25-100/mo (scales with traffic, predictable) |
| Supabase Self-Hosted | $0 SaaS | Unlimited | Full control | $0-500+/mo (infrastructure + ops cost) |
Key insight: Lovable's stated $25/mo hides variable credit costs. Supabase's $25 base is transparent; overages are itemized. Supabase Pro includes 8 GB of database storage and 100K monthly active users. Compute instances and egress are pay-as-you-go.
After migration: where to host?
Supabase Cloud (managed). $25 base + compute costs. Ops-free. EU region available. Best if you want predictable monthly costs and zero infrastructure management.
Supabase self-hosted. Free SaaS, but you run the servers. You pay for cloud infrastructure (VMs, storage, backups) and engineer time for setup, monitoring, patches. Makes sense if you're amortizing infrastructure across multiple products or have strict compliance needs.
Ship (managed Supabase hosting). Opsily's option for teams that want Supabase's independence without self-hosting ops burden. Flat-fee pricing, EU-based, zero lock-in. See related resources for details.
Ship: Managed Supabase After Migrating from Lovable Cloud
Once you've migrated off Lovable, you face a choice: stay on Supabase Cloud, self-host, or use managed hosting. Ship handles the ops side so you keep your independence.
Predictable pricing
Escape the credit-burn trap. Ship charges flat monthly fees, not per-action or per-build. Know your cost before the month starts. No surprise overage bills like Supabase Cloud or Lovable's variable credit system.
Zero lock-in
Your data stays yours. Ship runs open-source Supabase, not proprietary infrastructure. Export anytime. No vendor hooks. If you want to self-host later or switch hosting providers, you can—no refactoring needed.
Managed, not managed-cloud
We handle backups, patches, scaling, monitoring. You focus on code. Unlike self-hosted Supabase (where you own all ops), Ship gives you the convenience of managed hosting without tying you to a SaaS vendor.
Built for teams who need reliability
Frequently Asked Questions
Common questions about leaving Lovable Cloud for Supabase.
No. You can migrate in parallel. Keep your Lovable Cloud app live while building out Supabase in a staging environment. Export the database, import to Supabase, test, then flip the environment variable to point to Supabase. This approach keeps your live app running and gives you a rollback option if something breaks. Plan for 1-2 hours of staging work and 5 minutes of production cutover.
Ready to leave Lovable Cloud?
The migration is 15-20 minutes. The choice is yours: Supabase Cloud for managed simplicity, self-hosted Supabase for full control, or Ship for predictable costs without ops burden.