Moving to the Hyvä theme on Magento: what changes, how long it takes and how to plan it

What is the Hyvä theme for Magento?

Hyvä is a frontend theme for Magento 2, Adobe Commerce and Mage-OS. When you search for it, use “Hyvä theme” or “Hyvä Magento”, because the bare word mostly brings up a hydraulics company. Hyvä only changes what the shopper’s browser loads. Your admin, catalog, orders, customers, payment methods and ERP integrations stay where they are.

The default Luma theme is built on RequireJS, Knockout.js and jQuery, with LESS for styling. A typical Luma page loads many JavaScript files and a large stylesheet before it becomes fully usable. Hyvä drops that stack. It uses Alpine.js for interactive parts such as menus, galleries and the mini cart, and Tailwind CSS, which only ships the CSS classes your templates actually use.

Luma vs Hyvä theme at a glance

What the Hyvä theme changes for speed and Core Web Vitals

Less JavaScript means less work for the browser, especially on mid-range phones. That is where Hyvä helps most: Largest Contentful Paint and Interaction to Next Paint depend heavily on how much code runs before the page responds. Hyvä is not a magic switch, though. Large images, slow hosting, a badly configured full-page cache and heavy third-party scripts such as chat, review or tracking widgets can still pull scores down on a Hyvä store.

This is why MageBooster ties its Hyvä page score guarantee to clear conditions. Our Hyvä service promises a minimum Lighthouse Performance score of 89 on mobile for the home, category and product pages at launch, on a Hyvä-optimised server and with the images, videos and third-party scripts agreed in the project plan.

What Hyvä theme development changes for your costs

On Luma, even small frontend changes often mean working through layout XML, RequireJS configuration and Knockout templates. On Hyvä, most of that work becomes plain PHTML templates with Alpine.js and Tailwind classes. Developers who already know Tailwind and Alpine from other projects get productive faster, and later changes tend to take less time. The trade-off is the first project: every extension with frontend output has to be checked, and a custom Luma theme cannot be reused. It has to be rebuilt.

Hyvä theme licensing today

On 6 November 2025 Hyvä announced that its theme would become free and open source. Since 10 November 2025 the Hyvä theme is available on GitHub and through free Packagist Composer keys from the Hyvä Portal, under the same OSL 3.0 and AFL 3.0 dual license as Magento Open Source. The modules that support the theme were relicensed with it. The other products did not change:

• Hyvä theme: free and open source
• Hyvä UI, a library of ready-made components: a separate paid product, licensed per store
• Hyvä Checkout: a paid, commercial product
• Hyvä Commerce and Hyvä Enterprise: paid, commercial products

Check the current terms on hyva.io before you plan your budget, because product packaging can change. A free theme also does not make the project free: the real work is in extension compatibility, design and testing.

Extensions: the Hyvä compatibility check

Hyvä’s documentation is clear about this: modules built for the Luma or Blank theme need a compatibility module to work on a Hyvä storefront. A compatibility module re-implements only the parts of an extension’s frontend that do not work out of the box. Backend-only modules, such as most ERP connectors and product feeds, usually need nothing.

Hyvä keeps a public Compatibility Module Tracker that shows which modules already have one and what state it is in. Many extension vendors also ship Hyvä support themselves. For every remaining extension there are three options: port it, replace it with a Hyvä-ready alternative, or remove it if the store no longer needs it. In practice, this list decides much of the effort.

Hyvä Checkout or the default checkout?

The checkout is the hardest part of any Hyvä Magento move, because the default Magento checkout is built on Knockout.js. There are three common paths.

• Luma theme fallback: the checkout keeps running on Luma while the rest of the store runs on Hyvä. Hyvä’s documentation names the checkout as the most common use of the fallback. It is the quickest route, but those pages load the full Luma stack and must be styled the Luma way.
• Hyvä Checkout: a paid checkout built on Magewire, a PHP-driven component framework. It can be enabled per store view, so you can roll it out step by step, and it can also run on stores that still use Luma.
• Another checkout: for example a third-party one-page checkout with Hyvä support, or a checkout built for your store.

In MageBooster’s Hyvä projects you choose from checkout templates for Hyvä Checkout and IWD One Page Checkout, or our own 2-step, 3-step and one-page checkouts, each with a custom success page.

Steps of a Luma to Hyvä theme migration

1. Inventory: list every extension, custom module and frontend customisation, and check each one against the compatibility tracker.
2. Checkout decision: Luma fallback, Hyvä Checkout or another checkout.
3. Scope and plan: agree on what is ported, replaced or removed, the design approach and the acceptance criteria, including speed targets.
4. Build: set up the Hyvä child theme, apply your design, and rebuild the home, category, product, cart, account and content pages.
5. Integrate and test: compatibility modules, GA4 e-commerce tracking, payment and shipping methods, and every store view and language.
6. Launch and follow-up: go live, check Core Web Vitals and conversion data, and fix what real traffic reveals.

MageBooster runs this in four steps: project plan, scope and fixed quote, design and build, and launch and support.

How long does a move to the Hyvä theme take?

There is no honest single number. Hyvä does not publish a standard timeline, and the duration depends on a handful of factors:

• How many extensions have frontend output, and how many of them already have a compatibility module
• Whether you keep your current design or start a new one
• How custom your checkout is and which checkout path you choose
• The number of store views, languages and B2B features
• Custom features such as product configurators, quick order forms or complex layered navigation
• Your Magento version, because an old version may need an upgrade first

Our Hyvä service page puts it the same way: it depends on your extensions and how custom your checkout is, and your project plan comes with a timeline and a fixed quote.

When the Hyvä theme is not the right move

• Your Magento version is far behind and no longer supported. Upgrade first, because a new theme on an outdated core is not a good investment.
• Business-critical extensions have no Hyvä support and no realistic replacement, and porting them would cost more than you expect to gain.
• Your store is already fast on Luma and passes Core Web Vitals, so your budget may do more elsewhere.
• You plan to leave Magento in the near future.
• Your storefront is headless, for example PWA Studio or a custom frontend, so no Magento theme is used.

Planning your Hyvä Magento project with MageBooster

MageBooster builds Hyvä stores on Magento 2.4.9 and on Mage-OS for merchants in the UK, Germany, the Netherlands, Belgium, the US and Turkey, from our office in Istanbul. We start with your extensions and your checkout, then give you a plan with a timeline and a fixed quote before any build work begins.

See our Hyvä theme development service →

Read our step-by-step guide to installing the Hyvä theme →

Let us get in touch with you

Leave your details and your store address. We look at your store first and contact you within one business day, by phone, WhatsApp or email, whichever you prefer.