The data is one JSON file with every row of every table the app uses (clients, quotes, builds, products, suppliers, calendar, employees, timesheets, stock, checklists, meetings, JAP imports, the partner project and the rest), read fresh from Supabase when you press the button. Before it starts, the database is asked which tables it has, so a table added later is included too. Workshop docs, tracking, ordering, payments and materials ride inside each build's consultation_snapshot.
The files (photos, documents, drawings, invoices) are kept in Supabase file storage, not in the tables, so they are a separate download: zip files of about 200 MB each, plus a list of every file.
Each result below says exactly what was saved and names anything that could not be.
1. Download the data
Save the file somewhere safe (Dropbox, iCloud or an external drive). If Supabase ever goes wrong, this is the restore source. Recommended: weekly, and before any big change.
2. Download the files
Every file in storage, downloaded a few at a time and packed into zip files of about 200 MB each, with a manifest: a list of every file, its folder in storage, its size and which zip it is in. It can take a few minutes; keep this page open until it says it is done. Your browser may ask once whether this page may download several files: allow it.
Two-layer backup strategy
You're on Supabase Pro as of 2026-05-17, which means:
Layer 1 (automatic): Supabase takes a full daily backup of the database, retained for 7 rolling days. If a save ever corrupts data you can roll back from Supabase dashboard → Backups. Those backups hold the tables, not the uploaded files.
Layer 2 (manual, this page): the two downloads above write the data and the files to your machine. Run them before any big change or once a week, and keep them in Dropbox or iCloud so you also have a copy outside Supabase. The files download is the only copy of the files outside Supabase.
The two layers protect against different failure modes. Supabase backups protect against bad saves and accidental deletes. The downloads protect against Supabase itself being unreachable, or against a billing lapse.