How is this different from your /magento-upgrade-cost-calculator?

Different scope, different decision.

• /magento-upgrade-cost-calculator, projects a Magento version upgrade (e.g. 2.4.6 → 2.4.9). Your theme stays whatever it is (Luma or already-Hyvä). Inputs: current version, target version, SKU count, custom modules, extensions, B2B, multi-store, custom checkout, ERP. Output: cost + timeline for the upgrade itself.
• /hyva-migration-cost-calculator (this page), projects a Luma → Hyvä theme migration. Your Magento version stays whatever it is (2.4.6+). Inputs: Luma complexity, custom modules, extensions, PDP complexity, checkout complexity. Output: cost + timeline + sprint plan + risk factors + gantt for the Hyvä migration.

The two projects are independent but often run sequentially:

1. If you’re on 2.4.4 or older: upgrade to 2.4.6+ first (use the upgrade calculator), then migrate to Hyvä (use this calculator).
2. If you’re on 2.4.6+: jump straight to the Hyvä migration (use this calculator).
3. If you want to combine both: the combined project is roughly 10-15% cheaper than running them sequentially but adds 4-6 calendar weeks. Worth it if both are already on your roadmap.

Some clients run both calculators and send me a combined-project enquiry, I quote a single fixed price covering the upgrade + Hyvä migration as one engagement.