How to Get Your Database Out of Lovable Cloud
Your guide to escaping credit-based billing and vendor lock-in. Safe extraction methods, what migrates and what doesn't, and the risks to avoid.
Why Extract Your Lovable Cloud Database?
You built something real in Lovable. Now you're staring at Lovable Cloud bills that climb with traffic, or you need EU data residency for GDPR. You want out.
Lovable Cloud locks your database into their managed Supabase instance. No direct access. No pg_dump credentials. One export per 24 hours, capped at 5 GB, delivered by email.
The good news: extraction is documented and possible.
The catch: one Lovable builder's production system went offline attempting manual methods. This page walks you through the safe path.
Three methods exist:
- Official export (Lovable UI): slowest, safest
- Dreamlit exporter (browser-based tool): fastest, no terminal required
- Manual pg_restore (CLI): most control, highest friction
Read through all three. Choose the one that matches your technical comfort.
The Official Lovable Cloud Export
Tested on real Lovable projects. Carol Monroe migrated 237 rows, 23 users, 40 files, and 5 edge functions without data loss.
Log into Lovable Cloud Console
Open your project's Cloud tab. Navigate to Overview → Advanced Settings.
Click Export Data
Lovable generates a .backup file (PostgreSQL binary format). Starts immediately.
Wait for Email
Export is async. For databases under 1 GB, expect 5-15 minutes. Over 1 GB, up to an hour.
Download the .backup File
Email contains a download link. File is your complete schema, data, RLS policies, and user password hashes.
Restore to Target Supabase
Use pg_restore with your target database connection string. Requires PostgreSQL CLI tools (v16+).
Verify Row Counts
Query both databases. Confirm row counts match every table. One mismatched table breaks the app.
Test User Login
Pick a test user. Password hashes migrated intact—login should work without reset.
Re-enter Secrets & OAuth
Export does NOT include API keys, OAuth tokens, or database connection strings. Must re-enter manually.
Three Ways to Extract Your Database
Compare effort, speed, and technical requirements for each method.
Dreamlit exporter tested on projects up to 412 tables. Official Lovable export is the documented baseline.
The Export Only Covers Half Your Database Layer
Your Lovable Cloud database export includes:
- Full PostgreSQL schema (tables, columns, constraints, indexes)
- All row data
- Row-level security (RLS) policies
- User email addresses and password hashes
- Real-time subscriptions config
Your export does NOT include:
- API keys and secrets (Database URL, anonymous key, JWT secret). These are stored in Lovable's vault, not in the database. You must find them in Lovable Cloud Settings and paste them into your new host.
- Scheduled background jobs. Lovable stores job definitions with URLs pointing back to Lovable. These must be recreated manually with new webhook URLs.
- File storage (uploaded photos, documents). Files live in Lovable Cloud Storage, separate from the database. You must download them manually (see Lovable Cloud console: Files tab) and re-upload to your new host's storage.
- OAuth provider credentials (Google login, GitHub login). Lovable stores these in the project settings. You must reconfigure each provider to point to your new domain.
Missing any one of these breaks the app. Users can't log in, scheduled tasks don't run, images don't load. The export is the easy part. The secrets checklist is where migrations fail.
Carol Monroe's tested migration included:
- 12 tables, 237 rows
- 23 users with password hashes
- 40 uploaded files
- 5 scheduled background jobs
- 2 OAuth providers (Google, GitHub)
Every item above required manual re-entry after the database export.
One Builder's Production System Went Down During Migration
Attempted a manual extraction method without completing the secrets checklist. Database restored but app was broken: broken OAuth, no scheduled jobs, files offline. Research shows this is the highest-risk phase of extraction.
If Extraction Isn't Your Answer
You don't have to extract at all. The reason you want to leave Lovable Cloud matters.
If you're paying too much: Lovable Cloud is credit-based. You pay per compute minute, storage GB, and API requests. $50–500/month is common. There's no way to predict costs until usage is live.
Alternative: Opsily Ship. Fixed monthly pricing (€20/month entry tier, scales to ~€50+ depending on server size). Germany-hosted (GDPR-compliant). No overage charges. You stay on the same Lovable-exported app but on predictable infrastructure.
If you need EU data residency: Lovable Cloud supports region selection (Americas, Europe, Asia Pacific) but data may transit through US infrastructure. EU GDPR customers can't guarantee local residency.
Alternative: Opsily Ship. Frankfurt data center. German data residency compliance. Full GDPR Article 44 transfer protection.
If you want root access: Lovable Cloud is fully managed. No SSH, no Docker export, no server access.
Alternative: Opsily Ship. Full root access. Git-integrated (GitHub push to deploy). SSH into your server. Export the Docker container and take it anywhere.
If you want to try a different backend: Keep your React/Vite frontend, swap out Supabase for a different database.
Alternative: External Supabase + your own frontend host (Vercel, Netlify). Most common escape path. Frontend and database separate. More moving parts to maintain.
How to Get Your Database Out of Lovable Cloud: Why Builders Choose Ship
Ship is built for founders who've already figured out their app works. Now they want infrastructure that gets out of the way.
Fixed monthly price, no credit surprises
Lovable Cloud bills by credit usage—traffic spikes become surprise invoices. Ship's €20/month entry tier is flat. All compute, storage, bandwidth included. No overage charges, no rate increases per user.
GDPR-compliant German hosting
All data in Frankfurt, Germany. No US infrastructure. EU Article 44 transfer restrictions built-in. Builders with European customers can guarantee data residency.
Full root access and Git-powered deploys
Push to GitHub, Ship deploys automatically. SSH access to your server. Export your entire Docker environment. No vendor lock-in—your app is portable.
Built for teams who need reliability
Frequently Asked Questions
Common questions about extraction, migration, and alternatives to Lovable Cloud.
The .backup file includes your PostgreSQL schema (tables, columns, indexes, constraints), all row data, RLS policies, and user password hashes. It does NOT include secrets, API keys, OAuth credentials, scheduled jobs, or uploaded files. Those must be re-entered manually after restore. This is why Carol Monroe's guide breaks the migration into 8 steps—the database export is only step 5.
Ready to Leave Lovable Cloud?
Whether you're escaping credit bills, chasing EU data residency, or just want predictable infrastructure: Ship makes the transition smooth.