The Hyvä theme is now open source and free, under the OSL and AFL licences. There is one condition worth knowing: you need a customer account to obtain a licence key, and an account covers a limited number of keys. The licence cost had been the main reason merchants hesitated, and with it gone the advice across the Magento world converged on one word: migrate.
The technical case is genuinely strong. The default Luma theme leans on a large JavaScript stack, and Hyvä deliberately does not. On a mid range phone that difference is not marginal, and it shows up most clearly in exactly the metric that has become hardest to pass. How much you personally gain depends on your store, which is why the number that matters is yours and not one from a case study.
But a lighter frontend only fixes problems that live in the frontend. If your store is slow because its cache is misconfigured or a single extension runs a heavy query on every page load, a new theme will not save you. You will have spent a five figure budget and still be slow, and now you also have a migration to maintain.
The question that decides it
There is one measurement that separates the two situations, and it is not a score out of a hundred. It is time to first byte: how long the server takes to send the first byte of the page.
If your time to first byte is poor, the browser has not even started rendering yet. Everything the theme does happens after that point. Replacing the theme changes nothing about the part that is slow. Fix the backend first, then look again.
If your time to first byte is healthy and the page still feels sluggish, particularly when people interact with it, then the weight is in the browser and a lighter frontend is addressing the real problem.
What drives the cost
Migration quotes vary enormously, and it is not because some agencies are greedy. Three things drive the number, and you can estimate your own position on each before you talk to anyone.
| Factor | Cheap end | Expensive end |
|---|---|---|
| Extensions | A handful, mostly with Hyvä-compatible versions available | Dozens, several with custom frontend work that has to be rebuilt |
| Theme customisation | Close to stock Luma with styling changes | Years of accumulated template overrides nobody has documented |
| B2B functionality | None | Company accounts, quotes, shared catalogues, custom pricing |
The extension inventory is the single most useful thing you can prepare. Not what is installed, but what you actually use. In most stores those two lists differ substantially, and every extension you can drop is one you do not pay to rebuild.
When we tell people not to migrate
- When the bottleneck is on the server. Covered above, and it is the most common case we see.
- When a replatform is already on the table. If you are seriously considering moving off Magento in the next year, a frontend rebuild first is money you will not get back.
- When the store is already fast. Some Luma stores perform perfectly well because someone did the unglamorous work properly. If yours is one of them, keep your budget.
- When there is no capacity to test it. A migration touches every template. If nobody on your side has time to check the checkout, the search and the account pages before launch, that is a reason to postpone rather than to rush.
What migration does not change
Worth being clear, because it is a common worry: Hyvä is a Magento theme, not a different platform. Your catalogue, your orders, your customers, your admin and your integrations all stay exactly where they are. That is a meaningful difference from a headless rebuild, which replaces the entire frontend architecture and typically takes twice as long.
It also means the decision is reversible in a way a replatform is not. That lowers the risk considerably, and it is a fair argument in favour once the measurement supports it.
A sensible order
- Measure time to first byte and Core Web Vitals per page type, in field data.
- Fix anything obviously wrong on the server side, because it is cheap and it changes the second measurement.
- Measure again. This is the number the migration decision should be based on.
- Inventory your extensions and separate what you use from what is installed.
- Only now get quotes, and give every party the same inventory so the numbers are comparable.
That sequence costs you a few weeks. It routinely saves people from spending a large budget on the wrong project, which is a trade worth making.