This is unfortunately an expected Odoo.sh behavior, not a misconfiguration on your project. Staging databases on Odoo.sh are automatically deleted after one month by design. They're meant as duplicates of production for testing features against real data, not as persistent environments, so Odoo treats them as disposable and does not back them up automatically. This is a relatively recent change, the staging lifetime was previously longer (90 days), and Odoo shortened it to one month.

What you've already done, taking a manual backup, is the right move. Odoo.sh does allow manual backups of staging databases. To restore: open your Odoo.sh project, go to the staging/dev branch, open the build, go to the Backups section, and use Restore to upload your dump. That recreates the database in that environment.

The backup-rebuild-restore loop is fine for occasionally extending a test, but if you need a UAT environment that just stays up, fighting the expiry every month is the a few cleaner options would be:

• Second Odoo.sh project with a production branch as your UAT. Production branches don't expire and are backed up. Costs another subscription, but it's fully native and no maintenance overhead.
• Self-hosted UAT instance (your own VPS/Cloud Server or on-prem). No expiry, no extra Odoo.sh cost, full control, at the cost of you owning the infrastructure and maintenance. This is the usual route when teams want a long-lived staging/UAT clone they control. You restore your production dump into it and refresh it on whatever cadence you want.
• Scripted rebuild + restore on Odoo.sh staging if you want to stay on-platform and don't mind the manual-ish cycle.

Hello, 

Yes, as long as you have created and downloaded a backup before the staging environment is deleted, you can restore it later.

A common approach is to create a new staging branch/environment in Odoo.sh and use the Restore Database option to upload the backup file. This will recreate the database with the data contained in the backup.

Before restoring, make sure the target environment is running a compatible Odoo version and that any required custom modules are available in the corresponding code branch.

Hope this works for you! If you need any help implementing this or want a more optimized approach, feel free to reach out for further discussion.

Regards,

Zehntech Technologies Inc.

santosh.sekwadia@zehntech.com

It is not possible to prevent the automatic deletion of a temporary staging database. If you need ongoing access to the data, the recommended approach is to keep regular backups and restore them to a permanent staging or development environment when required.

Hope it helps

You can reply like this:

Hello,

That warning is normal for Odoo.sh staging databases.

Staging databases are temporary, automatically deleted after some time, and are not automatically backed up. If you want to preserve the data, the correct step is to download/create a manual backup before the staging database expires.

To restore it later:

1. Keep the backup file safely on your local system.

2. Create/rebuild a new staging branch in Odoo.sh.

3. Go to the new branch in Odoo.sh.

4. Open the Backups tab.

5. Use Import Database and upload your backup.

6. Wait for the import to finish.

7. Open the restored database from the branch history/connect button.

Important: do not store important production data only in staging. If the data is important, move it to production or keep regular manual backups.

So yes, once the current staging database is deleted, you can restore your saved backup into a newly created staging environment using the import database option.

Odoo’s documentation confirms that staging/development databases are not automatically backed up, staging databases are automatically deleted after a period, and Odoo.sh supports importing database backups from the branch Backups tab. (odoo.com)