Where to work
Project → Branches → select a deployed environment → Backups sub-tab. Minimum role for most actions: DEVELOPER.
Create a manual backup
- Open the branch Backups tab.
- Click Backup.
- Wait until status is completed (also visible under Deployments activity).
The branch must already be provisioned (stackPath present).
- Choose a completed backup → Restore.
- Pick the target environment (production or staging).
- Confirm. This overwrites that environment’s database.
Important: Platform restore is database-only. Filestore on the target is not rolled back. For DB + filestore, use Import with a zip that includes filestore/.
- Blocked if the backup’s Odoo major version does not match the project.
- Target must already be provisioned.
- Prefer restoring to staging first.
Download / export
- Choose a backup → Download (export).
- Pick Exact or Neutralized dump.
- Optionally include filestore.
Neutralized dumps run Odoo’s neutralize flow (mail/outbound scrubbed) — better for sharing or loading into test databases.
Import a zip
- Backups → Import.
- Provide a zip containing
dump.sql and optionally filestore/.
- Small archives can upload in the browser; very large ones may need rsync/SSH as described in the dialog.
Import resets web.base.url / mail catchall style settings and deactivates custom mail servers. Production imports should be rare — prefer staging.
Safety tips
- Take a fresh backup before restore/import on production.
- Staging clones from production are neutralized; treat production restores carefully.
- See also automatic backups and cloud destination guides.