Export Lovable Cloud Database Without pg_dump
Four ways to get your data out without touching the command line. No forced password resets. No PostgreSQL tools required.
Why pg_dump Doesn't Work for Most Teams
Historically, pg_dump was the only documented way to export a full Lovable Cloud database. Here's why it fails:
- CLI barrier: Non-technical teammates cannot run command-line tools
- Tool installation: Requires PostgreSQL client installed locally
- Performance impact: pg_dump backups can slow down your live database
- Password resets forced: Users lost login access after migration (now solved)
In July 2026, Lovable released new export options. This guide covers all working methods, ranked by ease and completeness.
The 4 Export Methods
From official UI export to community tools, here are your real options.
Choose Your App
Select an app to get started.
Official Lovable Export (New)
UI button in Cloud > Advanced settings. One export per 24 hours, up to 5GB. Includes schema, data, user password hashes, RLS policies, functions, and triggers. Password hashes mean users keep their login without reset.
CSV Table-by-Table Export
Manual export via Lovable UI: click each table, click 'Export CSV'. No CLI required. Includes data only (no schema). Tedious but visual, no technical barrier.
Dreamlit Exporter (Community Tool)
Open-source tool (37 GitHub stars). Handles password hashes without forcing resets. Uses temporary edge functions to securely migrate tables, users, and auth. Hosted web interface or CLI available.
AI-Assisted Edge Functions
Deploy custom edge functions in Lovable that query tables and return JSON or CSV. Works with Claude or Lovable AI chat. No external tool needed. Requires technical setup.
Export Methods Compared
How to pick the right method for your team.
CSV export is slowest (one table at a time). Official export is fastest for most teams (one-click, includes schema). Dreamlit is best for large or complex schemas.
What Lovable Export Actually Covers
Official Lovable Cloud export (July 2026) includes:
- Schema: Tables, columns, data types, constraints
- Data: All rows in all tables
- User password hashes: Users stay logged in after migration (no password reset required)
- RLS policies: Row-level security rules preserved
- Functions: PostgreSQL functions/stored procedures
- Triggers: Automated database triggers
Does NOT include:
- Storage files (S3 bucket contents) — migrate separately
- Edge function code — export code via GitHub instead
- Secrets (.env variables) — manage separately in new platform
This design is intentional: data portability yes, but code and secrets stay where you control them.
One export per 24 hours from Lovable
Official export limit. Use Dreamlit or CSV if you need multiple exports or handle larger datasets incrementally.
Why Deploy on Ship (via Opsily)?
After export, you need a home. Ship offers the infrastructure Lovable doesn't: ownership, predictable costs, and control.
Flat-rate pricing, not credits
Lovable charges by usage (unpredictable). Ship via Opsily costs the same every month. No surprise bills. Scale without renegotiating.
Your data, your infrastructure
Ship runs on Opsily servers (EU or US). No vendor lock-in. You own the code, the data, and the backups. Export anytime without negotiation.
Built for TypeScript teams
Ship is a TypeScript SaaS boilerplate (430 GitHub stars, actively maintained). Same tech stack: React, TanStack Start, Hono, PostgreSQL. Familiar patterns, no rewrite needed.
Built for teams who need reliability
From Export to Running App: The Steps
- Export from Lovable: Use official export, CSV, Dreamlit, or edge functions (choose based on table above).
- Prepare SQL: If using CSV, write CREATE TABLE statements. If using official export, you have the full dump.
- Deploy Ship instance: Use Opsily dashboard to spin up Ship (TypeScript boilerplate with PostgreSQL).
- Restore database: Run psql < dump.sql or use Opsily's restore tool to load your exported data.
- Update connection strings: Point your Ship app to the new database URL.
- Test auth: Verify users can log in (password hashes migrate transparently with official export).
- Migrate storage: Copy S3 bucket contents to your new Ship instance (separate from database export).
- Deploy code: Push your Lovable-exported code to Ship (GitHub sync works end-to-end).
Total time: 30 minutes to 2 hours depending on database size and your setup experience.
Ship Hosting Plans
Simple, transparent pricing. All plans include automatic backups, GDPR-compliant hosting, and one-click export.
Loading pricing...
Data Safety & Compliance
Ship on Opsily is built for teams that cannot compromise on data ownership or compliance.
GDPR Compliant
Your data lives in EU data centers. Choose Germany or Ireland. Full GDPR audit trail.
Daily Encrypted Backups
Automatic backups every 24 hours. Encrypted at rest and in transit. Restore point-in-time.
Your Data, Your Export
One-click export of everything (database, code, backups). No lock-in. Works with any PostgreSQL client.
24/7 Developer Support
Round-the-clock support for enterprise deployments and critical issues.
Frequently Asked Questions
Lovable added a one-click export button in Cloud > Advanced settings. The export includes your complete schema, all data, user password hashes (so users don't need password resets), RLS policies, functions, and triggers. You get one export per 24-hour window, with a 5GB file size limit. This replaces pg_dump as the recommended method for most teams because it requires no CLI and includes password hashes for seamless user login after migration.
Ready to Own Your Data?
Export from Lovable and deploy on Ship. Flat rates, full control, same tech stack. Start in minutes.