Counts and duplicates
Agreed categories are counted, and accidental duplication is investigated before records are presented for review.
A migrated total is only as credible as the checks behind it. Wedoo makes validation and reconciliation an explicit stage before cutover.
The evidence required depends on scope, but these are the checks that make a migration reviewable rather than a black-box assertion.
Agreed categories are counted, and accidental duplication is investigated before records are presented for review.
Spot checks and exception review test whether source fields reached the right Odoo structure.
The agreed financial position and source-to-target references support a clear route for investigation.
You should not have to wait until after go-live to discover a mapping or reconciliation issue. The goal is to understand and resolve exceptions while the current system is still available.
Counts are compared across the agreed data categories so missing or duplicate records are visible.
Checks confirm values landed in the intended Odoo fields and structures, not just somewhere in the database.
Balances, debtors, creditors and opening positions are reviewed against the agreed source position.
Data that cannot be translated cleanly is surfaced for a human decision instead of silently guessed or omitted.
Validation is one part of the wider platform: scope, staging, security and controlled cutover matter too.
It is investigated in staging before a cutover is agreed. The purpose of the validation stage is to resolve or consciously address the exceptions rather than discover them after go-live.
Duplicate detection is a distinct part of validation for the agreed record categories, alongside count, mapping and reconciliation checks.
Yes. The prepared Odoo environment is reviewed before operational use moves to the live system.
Use the real demo route to understand the experience, then talk to Wedoo about the evidence that matters for your particular source system and scope.