ERP Rollback Plan for Odoo: Cut-Over Criteria, Backups and Go/No-Go

Most go-live plans cover launch day. Few say what happens if it fails. Our Odoo implementation services treat the ERP rollback plan as a signed deliverable, not a late slide.

Related service: Odoo implementation services — fixed-scope implementations with a named senior team.

This guide is for sponsors, finance leads and IT managers near an Odoo launch. It goes deeper than our Odoo implementation checklist, focusing on cutover, the go/no-go gate and fallback.

What is an ERP rollback plan for an Odoo go-live?

An ERP rollback plan for an Odoo go-live is the agreed procedure for stopping the launch and returning to the legacy system, or to the last good Odoo state, when go-live fails. It turns a panic decision into a planned one.

A useful plan answers five questions in writing:

• When: which measurable problems trigger a rollback, and which only trigger a fix.
• Who: one person who makes the call, plus who executes, who is consulted and who is told.
• How: the exact restore steps, in order, with the backup they use.
• How long: the window during which rollback is still possible, in our experience often 24 to 72 hours.
• What next: how data entered in Odoo after go-live is re-keyed or replayed in the old system.

Keep it short, test it, and make sure the decision owner has read it.

How is a rollback plan different from a go-live checklist or UAT?

UAT proves Odoo works, the go-live checklist proves you are ready to launch, and the rollback plan covers what you do if launch still goes wrong. You need all three, and each has a different owner.

If your UAT is not finished, stop here and read our guide to Odoo UAT scenarios, sign-off and defect triage. A rollback plan cannot rescue a system that was never tested.

What cut-over criteria must be met before Odoo go-live?

Odoo cut-over criteria are the entry conditions that must all be true before the switch starts; if one is missing, the default answer is to wait. Agree them early, so nobody argues about them on cutover eve.

• UAT signed off: every critical scenario passed, with no open blocking defects.
• Dress rehearsal done: a full trial cutover on a copy of production, timed step by step, that fits the downtime window.
• Backup restored: the latest backup of both systems restored to a test server and opened by a user.
• Legacy freeze agreed: a date and time after which no one posts in the old system.
• Opening data reconciled: trial balance, open receivables and payables and stock values tie out between systems.
• Integrations ready to pause: a switch for each connector, so orders and payments do not land in two places.
• People ready: key users trained, a war room staffed and support hours agreed for the first two weeks.

Our Odoo database migration guide explains how to load and verify balances, stock and open documents before you count them as ready.

How do Odoo backups work on Odoo Online, Odoo.sh and on-premise?

Each Odoo hosting option backs up and restores in its own way, so your rollback plan must name the exact backup and restore method for your platform. The table sums up what Odoo documents.

On Odoo Online, the database manager offers a Download Backup option and daily backups under the Cloud Hosting SLA. Very large databases may need Odoo Support for an alternative download, so test this weeks before go-live.

On Odoo.sh, the production branch keeps seven daily, four weekly and three monthly backups. Take a manual backup before cutover and after the data load.

On-premise, Odoo advises daily backups of databases and filestore copied to a remote server and warns the web database manager is not for production.

Use PostgreSQL tools instead: pg_dump makes consistent exports while the database is in use.

Not sure which hosting you will run on? Our comparison of Odoo Online vs Odoo.sh vs on-premise covers backup control alongside cost and customization.

How do you run the Odoo go/no-go meeting?

The Odoo go/no-go meeting is a short, scripted session where the sponsor checks each criterion as pass or fail and makes one recorded decision. It should take under an hour if the work is done.

1. Send the evidence a day ahead: UAT sign-off, rehearsal timings, reconciliation reports and the open defect list.
2. Read each criterion aloud: the owner answers pass or fail, with no "mostly done".
3. Review open risks: for each, confirm the workaround and who watches it on day one.
4. Confirm the rollback plan: the trigger list, the decision owner, the restore point and the closing time of the window.
5. Make the call: go, no-go, or go with named conditions, and write it down with the time.
6. Tell everyone: users, customers if needed, suppliers and the support team, within the hour.

A no-go is not a failure: a one-week delay costs far less than a rollback after live trading.

What triggers a rollback after Odoo go-live?

A rollback trigger is a measurable problem, agreed before go-live, that is serious enough to justify leaving Odoo; anything else is fixed forward. Set numbers, not feelings.

The thresholds below are illustrative. Set your own from your order volumes, margins and customer promises.

Also agree how many triggers firing together force a rollback. Two core flows failing at once usually does.

When does an Odoo rollback stop being possible?

An Odoo rollback gets harder with every live transaction, and it becomes impractical once documents have left your company through tax portals, banks and customers. That is why every plan needs a closing time for the rollback window.

Each of these events makes the way back more costly:

• E-invoices submitted: invoices cleared or reported to a tax authority cannot simply be deleted; they must be cancelled or credited under local rules.
• Payments sent: bank payment files and direct debits already processed must be matched again in the old system.
• Goods shipped: deliveries validated in Odoo must be re-keyed in the legacy system to keep stock right.

Upgrades have their own limit. After a production upgrade on Odoo Online it is impossible to revert. Odoo.sh reverts a failed upgrade itself, but after success, going back means restoring a backup.

As an industry estimate, most teams close the window 24 to 72 hours after go-live. After that, fixing forward is almost always safer than rolling back.

What are the Odoo fallback steps if you roll back?

Odoo fallback steps are the ordered actions that stop new entries in Odoo, restore the legacy system and recover the transactions made in between. Keep them in a runbook that anyone on the team could follow.

1. Announce the decision: the sponsor confirms the rollback in writing, with the time.
2. Freeze Odoo: stop users from posting, pause scheduled actions and switch off outgoing mail.
3. Pause integrations: stop webshop, marketplace, bank and carrier sync, and note the last record each one sent.
4. Export the live delta: list every invoice, order, payment, receipt and delivery created in Odoo since go-live.
5. Reopen the legacy system: lift the freeze, restore its last backup if anything changed, and check user access.
6. Re-key or import the delta: enter the Odoo transactions in the old system, finance documents first.
7. Reconnect integrations: point connectors back to the legacy system and check the first few records.
8. Reconcile: compare bank, receivables, payables and stock totals before the business trades normally again.
9. Keep Odoo as is: do not delete the live database; it holds the evidence for the root cause review.

Step four is where weak plans fail. Decide in the rehearsal which Odoo reports list what changed since go-live.

Should you roll back Odoo or fix forward?

Fix forward when the problem is narrow and has a workaround; roll back when core flows fail together and the fix needs days, not hours. The table helps the decision owner decide quickly.

Fixing forward still needs a plan. Our Odoo ERP support team can cover hypercare after launch.

Then review the go-live honestly in a 30/60/90 day post implementation review.

ERP rollback plan risks by industry

The riskiest part of an Odoo rollback depends on what flows out of your business fastest, so tune the triggers to your industry. A distributor fears shipments; a retailer fears tills.

How iVentureTeam helps build your ERP rollback plan

We write, rehearse and run the rollback plan as part of the Odoo go-live, so the way back is tested before you need it. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Cut-over criteria: a pass or fail list tied to your UAT, data and integrations.
• Backup and restore tests: restore points on Odoo Online, Odoo.sh or your own servers, opened and checked by a user.
• Dress rehearsal: a timed trial cutover on a copy of production, including a practice rollback.
• Go/no-go and war room: we prepare the evidence pack and staff the first days live.
• Migrations and upgrades: for version moves, our Odoo migration services include the same gate and fallback plan.

To size the work, start with our Odoo implementation cost calculator. Our published ranges run from $3k to $9k for small projects to $27k to $150k+ for large ones, depending on scope.

ERP cutover case study: EvoLogics

A German subsea technology company moved from Odoo 12 to Odoo 15 Enterprise with less than one day of cutover downtime. EvoLogics could not absorb meaningful ERP downtime because it had live orders and projects.

The instance carried significant custom workflow code, so a straight database upgrade would have broken it. We audited every custom module and business flow, then wrote a staged plan for database conversion, code migration, testing and cutover.

Custom code was ported to Odoo 15 and tested end to end on the migrated database before anyone touched production. Go-live ran with minimal downtime and post-migration support, inside a 12-week project.

Read the full EvoLogics Odoo 12 to 15 Enterprise migration case study.

The bottom line on an ERP rollback plan

A good ERP rollback plan is short, tested and owned by one person, and it closes within days of go-live. Its real value is the discipline it forces before cutover.

Set the cut-over criteria, test the restore on your hosting, run a scripted go/no-go and write down the fallback steps. If launch still goes wrong, you make one calm decision.

If a past launch already failed, our guide to failed ERP implementation recovery covers the restart options.

Ready to plan a safe Odoo go-live?

Get a tested cutover and rollback plan before you switch. Plan your Odoo cutover and rollback with us, call +91-90235-15208, or email business@iventureteam.com.