How to Export Your Data from Lovable Cloud

Lovable Cloud gives every project a database, auth, storage and edge functions, built on Supabase’s open-source foundation. Since July 2026 it also has an official way out: Export project data. This guide covers what that export does, and everything it doesn’t.

This is Step 4 of the full Lovable migration guide.

What the export includes

Find it in Cloud → Overview → Advanced settings → Export project data. The backup contains:

• Your database schema and all data
• Security policies (row-level security)
• Auth users, including password hashes, so users keep their passwords

The backup file appears in a new storage bucket in your project, ready to download.

Limits

Limit	Value
Maximum export size	5 GB
Frequency	One export every 24 hours
Larger databases	Through Lovable support

Because of the 24-hour limit, plan your test migration and your final export on different days.

What the export leaves out

Asset	How to move it
Storage files	Download from each bucket, upload to your storage, rewrite URLs
Edge function code	Already in your GitHub repo; redeploy it on the target
Secret values	Re-issue from each provider and enter them on the target
Scheduled jobs	Recreate them on the target
OAuth provider apps	Re-create Google, GitHub or Apple sign-in apps on your accounts

Restoring into your own Supabase

Create a new Supabase project in the region you want, then restore the backup with pg_restore or the Supabase CLI. Check that:

• Every table exists with the right row count
• RLS is enabled on every table that holds user data, with the policies you expect
• Users can sign in with their existing passwords
• Foreign keys and indexes came across

Restoring into your own Postgres

For a fully self-hosted stack, restore the data into PostgreSQL and move auth users into your auth system. If it can verify the same password hash format, users keep their passwords; otherwise, plan a reset or magic-link email.

Before you switch off Lovable Cloud

Lovable Cloud offers Pause and Remove. Pause first. Remove permanently deletes the Cloud instance and can’t be undone, so only remove it after a few weeks on the new stack, with your own backups tested.

Prove nothing went missing

Check	How
Row counts	Every table, source vs. target
RLS	Query each table as an anonymous user; expect nothing back
Files	Count objects per bucket, open a sample
Sign-in	Test email and every OAuth provider
Functions	Call each edge function with a test request