Ordered by how much each one moves the estimate. Where a factor is weighted in our scoring engine, the bar shows its actual weight.
Biggest factor
Every custom module needs to be read and reviewed against the target version's API, not just re-installed. This is consistently the single biggest driver of effort — more so than the version gap itself.
Second
More versions means more accumulated schema and API drift to account for — real, but generally scales in a predictable, linear way rather than compounding out of control.
Third
Studio changes are structured data rather than code, so they migrate differently than custom modules — but heavy Studio usage still adds real, distinct review and testing work.
Smaller
Larger databases need more migration testing and tuning to keep the cutover window reasonable — a smaller factor on its own, but it compounds with the other complexity factors above.
Wildcard
Staying on Community for a version upgrade is often the more expensive path, not the cheaper one — there's no managed upgrade service to absorb version-by-version changes, so custom scripts do that work instead.
Before you ask us
The three that come up on every pricing call. Answered here so you don't have to book one to get them.
Something specific to your setup?Ask a human — no form gate. ›