Data Retention
Record counts, custom fields and important values that should survive the upgrade.
Know what changed before go-live. We compare critical business data and workflows before and after an Odoo upgrade, then give you a clear report of what passed and what needs review.
Simple comparisons turn silent migration problems into findings your technical and business teams can review.
| Check | Before | After | Result |
|---|---|---|---|
| Employees with custom grade data | 1,482 | 0 | Review |
| Confirmed orders missing a warehouse | 0 | 281 | Review |
| Posted invoice total | 48.2M | 48.2M | Passed |
The checks are selected around the workflows and data that matter to your business.
Record counts, custom fields and important values that should survive the upgrade.
Orders, customers, warehouses, products and other links that must remain connected.
Accounting, sales and inventory totals compared using rules agreed for your project.
Unexpected changes to confirmed, posted, completed, cancelled or archived records.
No black box. The checks and expected outcomes are agreed before validation begins.
We identify the business data, totals and relationships that are critical to your migration.
Agreed checks run against controlled copies of the source and upgraded databases.
You receive a concise report showing passed checks and differences requiring investigation.
The goal is not another technical log. It is shared evidence for the implementation team, project owner and customer before the production decision.
Validation can run in a customer or agency-controlled environment using read-only access where practical. Access, hosting and data-handling responsibilities are documented before work begins.
Short answers for teams preparing an Odoo version upgrade.
It is a before-and-after comparison of agreed business data and rules. The review helps find missing values, changed totals, broken relationships and unexpected workflow changes before production go-live.
Checks can cover custom fields, record counts, sales orders, warehouse relationships, accounting totals, inventory totals, taxes, workflow states and other project-specific business rules.
Validation can be performed in a controlled customer or agency environment using read-only access where practical. The access model is agreed during scoping.
Tell us the source version, target version and modules involved. We will help define the business checks that should pass before go-live.