I’m about to start a Hyvä migration — what do I do with this report?

Three steps:

1. Lock all Unknowns via 2-hour spikes — never start a migration with unknowns in scope.
2. Quote every Partial with a fixed-price port budget (use the per-extension hours estimate × your dev rate).
3. Plan replacements for every Blocker — spec the swap-out (e.g. Hyvä Checkout for OSC) before the migration kicks off.

Add the totals and you’ve got a realistic Hyvä migration scope before you sign anything. Most surprise-rework on Hyvä projects comes from skipping this audit and discovering Partials / Blockers mid-build.