Lovable deletes Test databases on December 1, 2026: what to check this week
If you built on Lovable's built-in backend with the old Test and Live environments, one date still matters: on December 1, 2026, Lovable deletes detached Test databases for good. Until then, they can still be restored on
If you built on Lovable's built-in backend with the old Test and Live environments, one date still matters: on December 1, 2026, Lovable deletes detached Test databases for good. Until then, they can still be restored on request (Lovable docs).
Here is a short checklist to find out whether that affects you, and what to do before the date.
What already happened
- September 14: owners of affected projects got an email and a notice in the project.
- October 23: the Test/Live split was retired. Every project now runs on a single database. Test databases were detached, not deleted.
- December 1: detached Test databases are deleted and can no longer be restored.
The part that catches people: publishing never moved data. It carried the schema, RLS policies, bucket definitions and edge functions from Test to Live, but not rows, user accounts, storage files or auth settings. If your real data was only in Test, your published app has been running on an empty or incomplete database since October 23.
1. Check whether your app is missing data
Open the app as a real user and look for:
- accounts that can't sign in (they were created in Test)
- empty lists or dashboards that used to have content
- images or files that return 404 (they were uploaded to Test storage)
Then compare row counts in the Database view against what you expect. If something is missing, it probably lives in the detached Test database.
2. Ask for a restore before December 1
Lovable says it can restore a detached Test database on request until December 1. Do this first, while it is still possible. After that date the data is gone, and their backups of affected projects are only kept for 30 days after detachment.
3. Export everything once it is back
Even if you plan to stay on Lovable Cloud, take your own copy:
- the full export (More → Database → Manage → Settings → Export project data, up to 15 GB)
- the files in each storage bucket, keeping the same paths
Merging Test data into Live needs care: users or rows that exist in both environments can collide on ids or emails. Decide which side wins for each table before importing anything.
4. If you want development and production again
Drafts replaced Test/Live, but a draft previews app changes. It does not give you a second database. Lovable's own answer to "Can I keep both databases?" is "Not within Lovable after October 23".
The supported way to get separate environments back is to connect your own Supabase project instead of the built-in backend. Then you can run one project for development and one for production, with migrations applied to both.
The move itself has a few traps (duplicate profile rows from the auth.users trigger, sequences starting at 1, storage paths, the one-time sign-in after the JWT secret changes). I wrote them up step by step in Moving a Lovable app from Lovable Cloud to your own Supabase, with a tested open-source toolkit: github.com/ricardonldev/lovable-cloud-to-supabase.
Summary
- Check the live app for missing users, rows and files.
- If anything is missing, ask Lovable to restore Test before December 1.
- Export your data and files and keep your own copy.
- If you need dev and prod databases, plan the move to your own Supabase.
If you would rather have it done for you, I offer the move (including separate development and production projects) as a fixed-price service on Fiverr.
Not affiliated with Lovable or Supabase. Written with AI assistance (Claude); dates and quotes are from Lovable's documentation as of November 22, 2026.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.