Odoo.sh Staging Is Getting A Timer: What You Need To Know
Odoo is doing some digital spring cleaning. To keep their servers fast, they are now putting a 30-day limit on staging databases. It’s their way of clearing out old test environments, but it means we need to stay sharp if you are working on a longer project.
The staging safety net
Just a quick reminder: your staging environment is that "safe" copy of your live data. It is where we test new workflows or prep for a big move to Odoo 19 without any risk to your actual business. It is basically your playground for being brave with new ideas and we use it a lot!
What happens on May 31?
From May 31, 2026, Odoo will automatically delete any staging database older than 30 days. Your code on GitHub is safe, but the test data itself will go "poof" if the timer runs out. If you are in the middle of a big upgrade that takes longer than a month, we don't want you losing your progress.
How to keep the lights on
If you need your staging environment for longer than a month, you can reset the clock yourself. You’ll need to download a full backup from your Odoo.sh dashboard, refresh the branch, and restore it to start a new 30-day window.
If that sounds like a technical headache you’d rather avoid—don't worry. You can just send us an email to open a ticket, and we will handle the heavy lifting for you.
Better yet, let us handle the clock
Honestly, you have a business to run and probably didn't sign up for Odoo to spend your time managing database expirations.
This is exactly why we have our Care Plan. For our Care Plan family, this is all handled behind the scenes. We keep an eye on the dates and manage the rotations so your work is never interrupted. If you aren't on a plan yet, now is a great time to join so you can focus on the fun stuff while we handle the chores. Reach out if you want to check your current setup!