A year ago this month, Hyvä Theme became free. On 10 November 2025 it went fully open source, and the licence fee of roughly £850 that used to come with every store disappeared.
So why do Hyvä migration quotes still range so widely? Because the licence was never the expensive part. Nearly all the cost of a Hyvä project is the work of moving your store onto it: your extensions, your design, your integrations, your customisations.
That’s also why a single headline price is useless. Two Magento stores of the same size can need very different amounts of work. In this article we’ll walk through what actually drives the cost, so you can see roughly where your store sits before you speak to anyone.
- The Hyvä Theme licence is free. Hyvä UI, Checkout, Enterprise and Commerce are still paid.
- Extension compatibility is usually the biggest unknown, and the main reason quotes differ.
- An extension audit before you request quotes is the fastest way to get a reliable number.
What’s Actually Free, and What Isn’t
The core Hyvä Theme is free under the same open-source licences as Magento Open Source (OSL 3.0 and AFL 3.0). The rest of the Hyvä product range is still commercial.
| Product | What it does | Licence |
|---|---|---|
| Hyvä Theme | The core frontend that replaces Luma | Free, open source |
| Hyvä UI | Library of prebuilt UI components | Paid, around £215 per store |
| Hyvä Checkout | Replacement for the default Magento checkout | Paid |
| Hyvä Enterprise | Adobe Commerce compatibility, including the B2B suite | Paid, annual |
| Hyvä Commerce | Bundle of Theme, UI, Checkout and other tools | Paid, annual |
If you run Magento Open Source and keep your existing checkout, your licence cost can genuinely be zero. If you run Adobe Commerce, budget for Hyvä Enterprise on top of the build. Check current pricing on hyva.io before you plan, as it has changed more than once.
Either way, the licence is now the smallest line on the bill.
The Six Things That Set the Price
Project scope
Hyvä replaces the frontend only. Your catalogue, orders, customers and admin stay exactly as they are. The first question is whether you are doing a straight theme swap, or using the migration as the moment to fix other things too. A like-for-like rebuild is the cheapest route. Adding new features, a platform upgrade or a checkout change all widen the scope.
If your store is on an older Magento version, that matters too. Hyvä needs Magento 2.4.4 or later, so an outdated store may need upgrading first.
Some projects are bigger still. For Hedges Direct, we first replatformed the store from SellerDeck to Magento, then rebuilt the frontend on Hyvä as a second phase. Splitting the work into phases kept each stage manageable and spread the investment over time.
Extension compatibility
This is usually the biggest unknown, and the reason quotes vary so much. Every extension that touches the frontend has to work with Hyvä. Each one falls into one of three groups:
A store with 15 extensions and one with 60 are very different projects, even if they look similar from the outside. An extension audit before you get quotes is the single best way to narrow the range.
Design requirements
You have three options, and they cost very different amounts:
Many merchants choose the third route because they were planning a redesign anyway. Doing both at once is usually cheaper than doing them a year apart.
Custom functionality and integrations
Custom features built for Luma, such as product configurators, bespoke account areas or B2B quoting, need rebuilding with Hyvä’s lighter stack (Tailwind CSS and Alpine.js). Integrations with your ERP, PIM or search are usually backend-only and carry over, but anything they display on the storefront needs checking.
Testing and QA
A Hyvä migration changes every page your customers see. Proper testing covers checkout and payment flows, every extension’s frontend, mobile and tablet layouts, accessibility, analytics and tracking tags, and Core Web Vitals. Underfunded testing is the most common reason a migration goes live with problems, so treat it as a real line item, not a buffer.
Hosting and infrastructure
Hyvä makes the frontend lighter, but the speed gains only show up fully on hosting that is set up properly, with caching and search tuned correctly. If your hosting is already struggling, budget to fix that alongside the migration. Otherwise you risk paying for a faster frontend that still loads slowly.
Where Does Your Store Sit?
Most stores fit roughly into one of three profiles. Find the closest match to see which cost drivers will matter most for you.
| Straightforward | Typical mid-market | Complex | |
|---|---|---|---|
| Extensions | Under 20, mostly well-known vendors | 20–50, a mix of mainstream and niche | 50+, including custom or abandoned ones |
| Design | Hyvä default with branding | Recreate current design | Full redesign during migration |
| Custom features | Few or none | Some, e.g. configurators or custom account pages | Heavy: B2B, multi-store, bespoke journeys |
| Platform | Magento Open Source, recent version | Open Source or Adobe Commerce | Adobe Commerce, often with B2B |
| Main cost driver | Design and testing | Extension compatibility | Custom rebuilds and testing |
| Typical timeline | 4 weeks | 6 weeks | 8–10 weeks |
A “straightforward” store with one awkward extension can move up a band quickly. That’s why the audit matters more than the profile.
After Launch: What It Costs to Run
The build is a one-off. Running costs are where Hyvä often saves money over time.
- Simpler frontend maintenance. Hyvä’s stack is much smaller than Luma’s, so frontend changes and bug fixes usually take less developer time.
- Magento and extension updates. These continue as before, and each one needs a quick Hyvä compatibility check. On ITQ’s Magento support plans, patches and upgrades are included at no extra cost, so this line stays predictable.
- Paid Hyvä products. Annual licences for Hyvä Enterprise or Hyvä Commerce, if you use them.
- Performance monitoring. Core Web Vitals can drift as new features and tracking scripts are added. A light, regular review keeps the gains you paid for.
When you compare quotes, ask each agency what ongoing support looks like after go-live, not just what the build costs.
What You Get Back
Cost only makes sense next to return.
Hedges Direct
One of the UK’s leading hedge and plant retailers, now on a Hyvä-powered Magento store with sub-second mobile load times.
Those gains came from Hyvä working alongside UX improvements and ongoing optimisation, not the theme alone. That’s the point: Hyvä gives you a faster, cheaper-to-change foundation, and the return comes from what you build on it.
How to Get a Real Number
The fastest way to turn a vague range into a reliable figure is to remove the biggest unknown first. For most stores, that’s the extensions.
Our free site audit does exactly that. Within two working days, we review your platform, extensions, performance and checkout, and give you a prioritised, costed list of findings. You’ll know which extensions are Hyvä-ready, which need work, whether your hosting is holding you back, and which profile your store really fits.
Find out what your Hyvä migration will cost
Get a free site audit, delivered in two working days. Or book a free 45-minute ecommerce clinic and talk it through with our team.
