What a VersionBridge upgrade assessment looks like
This is the real, unedited output the engine produces — the same report you get for your own module, straight from a free scan. It is built to send to a client as your quote. No email gate: just read it.
What’s in it
Executive summary
Headline effort (with an optimistic–pessimistic band), complexity rating, and total findings — the number you put in front of a client, defensible because every figure traces to a specific change.
Cost & timeline
Your delivery cost from the effort estimate, at your own rate, plus an indicative timeline — so a fixed-price quote stops being a guess.
Findings by module
Every breaking change, grouped by module and ranked by severity: what breaks, where (file and line), and how the fix typically looks.
Verification
Whether the module was loaded on a real Odoo server of the target version, and the confidence level — observed compatibility, not a prediction.
How to read it
Start at the executive summary — the effort band and complexity rating are what you put in a proposal. The range matters: the optimistic figure assumes clean, well-structured code, the pessimistic one leaves room for surprises, and the “likely” number is what to quote. Because every finding below is tied to a specific Odoo change, you can defend the estimate line by line if a client pushes back.
Then scan the findings by module. Blocking issues stop the module loading on the new version — those set the floor on your timeline. Preventive issues load fine today but carry risk: silently changed behaviour, deprecations, or data hazards you’d rather catch now than in production. The verification section tells you whether the module was actually loaded on a real Odoo server of the target version, so “fixable” isn’t a guess. This sample is illustrative data; your own report is generated from your real module.
Generate this for your module — free
Upload a custom Odoo module and get your own assessment in minutes. Scanning is always free and needs no card.