Skip to main content
iVentureTeam
Hosting & DevOps

Odoo.sh Staging Branch Deleted? Retention, Backups and Upgrade Tests

Why Odoo.sh deletes staging databases after one month, how long dev and production builds last, what to back up, and how to plan upgrade tests around it.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 18, 202612 min read4 views
Odoo.sh Staging Branch Deleted? Retention, Backups and Upgrade Tests cover

Many teams found out about the new rule from a banner that says their staging build will be deleted on a set date. Our Odoo ERP support team sees the same question every week: what is lost, what is kept, and how to plan testing around it.

Related service: DevOps and hosting services — Odoo.sh, self-hosting and CI/CD run by people who do it daily.

This guide is for Odoo.sh project owners, IT leads and partners who run UAT or upgrade tests on staging. It does not repeat how neutralization works; for that, read our Odoo staging environment checklist.

What happens when an Odoo.sh staging branch is deleted?

When people say an Odoo.sh staging branch was deleted, it is almost always the staging database that was removed, not the branch. Your Git branch, commits and branch settings remain, and a rebuild creates a new database.

The Odoo.sh branches documentation is short and clear: "Databases created for staging branches are automatically deleted after one month. To use the branch again, you must rebuild it."

So three things disappear with the database:

  • Records you created in staging: test orders, invoices, products and contacts.
  • Configuration done by hand: settings, views, automation rules or Studio changes you made only in the staging database.
  • The filestore of that copy: attachments uploaded during testing.

What stays is everything in Git: your custom modules, the branch history and the stage of the branch. The same docs warn that a branch deleted from the repository itself cannot be retrieved "unless a backup exists", so treat a Git delete as a separate, bigger risk.

How long do Odoo.sh staging, development and production databases last?

Odoo.sh retention: How long each database lasts

Production databases stay as long as the project is active, staging databases last one month, and development databases last about three days. Each stage also gets a different backup policy, which matters more than most teams expect.

StageHow long the database lastsAutomatic backupManual backup
ProductionFor the life of the projectYes, up to 3 monthsYes, kept 3 days
StagingDeleted after one monthNoYes, kept 3 days
DevelopmentAbout three days, may be removed without noticeNoNot possible
Trial projectProduction and staging set back to development after 30 daysDepends on stageDepends on stage

Development builds are the most fragile. Odoo says they "can be automatically garbage-collected to make room for new databases without prior notice". Never do work there that you cannot redo from code.

The trial rule is older and separate. On trial projects, Odoo moves the production branch and all staging branches back to the development stage after 30 days, which then makes them follow the shorter development lifetime.

What changed: from three months to 30 days on Odoo.sh staging

Older Odoo.sh documentation kept the latest staging database alive and valid for three months; the current documentation cuts that to one month. The change caught many teams in the middle of long UAT cycles.

The Odoo 16.0 version of the same page said the latest staging database "will be kept alive indefinitely" and would be valid for 3 months before a rebuild was expected. The 17.0, 18.0, 19.0 and 20.0 pages now all say one month.

On the Odoo forum, an Odoo staff member confirmed that all staging branches will now expire in 30 days unless rebuilt. The user who asked had never seen an expiry date on staging in years of using Odoo.sh.

The same staff answer carries an October 2026 update: Odoo plans to extend staging branches created from the Upgrade feature to 90 days, to give more time for upgrade testing. Treat that as a plan until your own staging banner shows the new date.

A paid extra staging branch does not change any of this. In a second forum thread, an Odoo.sh customer who bought a staging branch still saw the temporary environment banner, and the answers confirmed it is expected behavior.

Are Odoo.sh staging databases backed up?

No, Odoo.sh does not back up staging databases automatically; you can take manual backups, but each one is kept for only three days. Production is the only stage with a real backup history.

According to the backups section of the docs, production is backed up daily, with seven daily, four weekly and three monthly backups kept. Each backup holds the database dump, the filestore, logs and sessions. The production server keeps one month; dedicated backup servers hold the monthly copies.

For staging, the rules are tighter:

  • Manual only: you start a staging backup yourself from the Backups tab.
  • Three days: manual backups of production or staging "remain available for three days".
  • Five a day: there is a limit of five manual backups per day.
  • Download to keep: if you need a staging copy for longer, download the dump and store it yourself.

You can also restore a production backup into a staging branch. That is the normal way to test a fix on real data, or to recover records someone deleted by mistake in production, without touching production.

What should you back up before a staging database expires?

Back up anything that exists only in the staging database: manual configuration, test evidence and the exact data state you signed off. Code is already safe in Git, so focus on what Git does not hold.

  1. Write configuration into modules. Odoo's docs recommend recording staging changes step by step or writing them into the branch's modules as XML data files, so the next build has them.
  2. Export test evidence. Save screenshots, exported reports and the list of passed and failed test cases outside Odoo.sh.
  3. Download a dump at sign-off. When business users approve a UAT round, download that staging dump so you can show what was tested.
  4. Keep a data recipe. Note which test customers, products and orders you created, so you can recreate them quickly after a rebuild.
  5. Copy integration settings. Record sandbox API keys and webhook URLs you set in staging, since neutralization and rebuilds reset them.
  6. Check the date. Read the deletion date on the staging banner at the start of each test round and put it in the project plan.

If storage is your worry, note that staging instances and backups count toward your Odoo.sh disk total. Our guide on Odoo.sh storage full shows how to see what uses space and what to clean up.

Rebuild or update: how Odoo.sh staging builds behave on new commits

By default, a new commit on an Odoo.sh staging branch updates the existing build, while a rebuild always starts again from a fresh copy of production. Knowing which one you are triggering decides whether your manual setup survives.

The branch settings explain the default: a development branch creates a new build on each commit, while "a staging branch updates the previous build". You can switch a staging branch to New build, and then every push creates a fresh production copy.

The Odoo.sh builds documentation adds the key warning. Configuration you make in a staging database and do not apply in production "will not be present in the next build of the same staging branch".

Merging staging into production moves only code. Odoo states that changes made in the staging database are not passed to production, so anything configured by hand must be redone in production or shipped as module data.

How do you plan Odoo.sh upgrade testing around the 30-day limit?

Plan upgrade testing in short cycles that each fit inside the staging window, and make every cycle start from a rebuild you can repeat. A long, single UAT on one staging database is the plan that breaks.

The Odoo upgrade documentation explains the Odoo.sh flow. The latest daily production backup goes to the upgrade platform, and the upgraded copy lands on a staging branch in a special mode. Each push restores the upgraded backup and updates all custom modules.

That design helps you: every commit gives a clean upgraded database. It also means hand-made test data does not survive a push. Here is the plan we use:

  1. Week 0, prepare: make custom modules installable on the target version and list the business flows to test.
  2. Cycle 1, technical test: request the upgraded staging database, read `~/logs/upgrade.log`, fix module errors and push.
  3. Cycle 2, key users: run the main flows end to end, from purchase to invoice to report, and log every defect.
  4. Cycle 3, sign-off: fresh rebuild, re-run the failed cases, download the dump, and get written approval.
  5. Production upgrade: schedule it soon after sign-off, because the upgraded copy ages as production keeps changing.

For the checks to run in each cycle, use our Odoo upgrade verification guide and the scenario list in our Odoo UAT guide for Odoo 19 and 20.

To size the work before you book test dates, try the Odoo migration cost calculator. It gives a range based on version gap, apps and custom modules.

What do Odoo.sh staging environments cost?

On 18 November 2026, the Odoo.sh pricing calculator listed staging environments at US$14.40 each per month on annual billing, from 0 up to 20 per project. Storage for staging copies is billed with the rest of your disk.

The Odoo.sh pricing page showed these hosting items in USD on its default annual view:

Odoo.sh itemPrice shownNote
WorkerUS$57.60 per worker per month1 to 16 on shared hosting
StorageUS$0.20 per GB per month1 to 512 GB on shared hosting
Staging environmentUS$14.40 per environment per month0 to 20 per project
Dedicated hostingUS$480.00 per monthNeeded above 16 workers or 512 GB

Odoo's tooltip says storage is "the total disk space, including the size of the production and staging instances" plus 3 backups in different datacenters. The hosting price does not include the Enterprise license, so add your Custom plan users on top.

More staging branches let you run parallel tests, for example one for an upgrade and one for a new feature. They do not make any staging database permanent. For a full hosting comparison, see Odoo Online vs Odoo.sh vs on-premise.

Which teams feel the Odoo.sh staging limit most?

Teams with long approval cycles, heavy integrations or seasonal peaks feel the one-month staging limit most. The fix is the same in each case: shorter test rounds and setups you can rebuild from code.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
ManufacturingLong BOM and routing sign-off by several managersTest in short rounds, keep BOM test data as import filesScript test data so a rebuild takes minutes
eCommerce and retailPayment and carrier connectors reset in each copyNote sandbox settings, rerun checkout tests each roundKeep a connector setup checklist per staging branch
Finance and accountingAuditors want proof of what was testedDownload a dump and reports at each sign-offStore sign-off evidence outside Odoo.sh
Regulated sectorsChange approval can take longer than a monthSplit approval into stages that each fit the windowPlan test cycles against the staging date
Multi-company groupsEach company needs its own test passOne staging branch per test streamSize staging branches and storage with you

How iVentureTeam helps with Odoo.sh staging and upgrade testing

Testing an upgrade? Size it first

We set up Odoo.sh projects so that a deleted staging database is a routine rebuild, not a lost month of testing. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Staging as code: we move hand-made staging configuration into module data, so every rebuild starts ready to test.
  • Upgrade test plans: our Odoo upgrade services run upgrade cycles timed to the staging window, with defect logs and sign-off.
  • Backup routine: a written routine for manual staging dumps at sign-off and production backups before risky merges.
  • Branch and storage sizing: our DevOps services size staging branches, workers and storage for your test load.
  • Recovery help: if a staging database is already gone, we rebuild it and recreate the test state from your notes and code.

Odoo.sh upgrade testing case study: EvoLogics

This case is a three-version Odoo Enterprise migration with careful testing before cutover; the case page does not state that it ran on Odoo.sh or under the current staging rule. We include it because the test-then-cutover approach is the same one this guide recommends.

EvoLogics, a subsea technology company in Germany, ran Odoo 12 Enterprise with significant custom workflow code. It needed to move to Odoo 15 Enterprise without meaningful ERP downtime, as orders and projects kept running.

We audited the system first, then migrated the database and the custom code in parallel. End-to-end testing on the migrated database checked data accuracy and workflow behavior before anyone touched production.

The migration took 12 weeks, and cutover downtime at go-live was under one day. On Odoo.sh today, a project like this would need its testing split into rounds that each fit the staging window. Read the EvoLogics Odoo 12 to 15 migration case study.

The bottom line on Odoo.sh staging branch retention

Treat every Odoo.sh staging database as temporary: keep configuration in code, back up at sign-off, and plan tests in rounds shorter than one month. Production is the only stage with a backup history you can rely on.

The rule is not a bug, and paying for more staging branches does not lift it. Teams that plan for it lose very little when a staging database expires. Teams that run long UAT on one copy lose weeks.

Ready to plan your next Odoo.sh upgrade test?

Plan my Odoo.sh tests

Get a staging and upgrade test plan that fits the one-month window. Plan your Odoo.sh upgrade test cycles with us, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

Why was my Odoo.sh staging branch deleted?

+

Most likely only its database was deleted. Odoo.sh removes staging databases automatically one month after they are created. The branch and its code stay in Git, and a rebuild creates a fresh copy of production.

How long does an Odoo.sh staging database last?

+

One month, according to the current Odoo.sh documentation. Older docs allowed three months. Odoo has said it plans to extend staging branches created from the Upgrade feature to 90 days.

Can I stop Odoo.sh from deleting a staging database?

+

No setting keeps a staging database forever. You can rebuild the branch, take manual backups before the date, and keep configuration in your modules so a rebuild is quick.

Are Odoo.sh staging databases backed up automatically?

+

No. Only production gets automatic backups. You can take manual backups of staging, up to five a day, and each is kept for three days, so download any copy you need to keep longer.

How long do Odoo.sh development builds last?

+

Development databases are meant to last about three days. Odoo says they can be garbage-collected without notice, and manual backups of development builds are not possible.

What is lost when an Odoo.sh staging database is deleted?

+

Test records, attachments and any configuration you made only in that database. Code, commits and branch settings stay in Git, so changes written into modules come back on the next build.

Does paying for more staging branches make them permanent?

+

No. Extra staging branches let you run more tests in parallel, but each staging database is still a temporary, neutralized copy of production that follows the same deletion rule.

How do I test an Odoo upgrade on Odoo.sh?

+

Use the Upgrade tab on a staging branch. Odoo sends the latest production backup to the upgrade platform and restores the upgraded copy on staging, refreshing it and updating custom modules on each commit.

Does merging staging into production copy my staging data?

+

No. Merging moves only code. Records and configuration made in the staging database stay there, so redo them in production or ship them as module data.

Free Odoo upgrade plan

Planning an Odoo upgrade?

Tell us your version, edition and custom modules. We check what breaks, what it costs to fix and the safest path, before any work begins.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.