Back up and restore
Choose recovery arrangements for your installation. Database backups, uploaded media and service configuration cover different parts of recovery.
Choose backup and recovery arrangements that suit your installation and the records you want to retain.
Database and media are separate
Supabase's available database backups and recovery options depend on your plan. Database backups include Storage metadata, but not the uploaded file bytes. Retained upload originals or separate media copies can be part of your chosen recovery arrangements.
See Supabase's database backup options (opens in a new tab), Storage downloads (opens in a new tab), and logical backup and restore instructions (opens in a new tab).
Restoring or moving an installation
Keep the Fieldbook source version and service configuration available with any recovery set. A restored database must match its application version. Hosting credentials, Google callbacks, optional MCP connections and the cleanup destination must point to the intended installation.
Restoring an earlier database can lose later content, accounts and progress. Uploaded media needs its file bytes and matching references. Copied background jobs can still call their saved destinations, so check those destinations before activating a restored project.
Fieldbook does not require an isolated restore or a second hosted project before installation or an ordinary update. You choose whether a rehearsal is useful for a particular recovery or database change.