E-commerce

Migrating from Luma to Hyvä: How It Works and What Changes

How to migrate a Magento 2 store from Luma to Hyvä: audit, extensions, checkout, testing and go-live. What changes and where the risks are.

Area
E-commerce
Published
November 16, 2026
Reading time
5 minutes

In this guide

What you will find

Migrating from Luma to Hyvä means replacing the frontend of a Magento 2 store while keeping the backend as it is: you install the Hyvä theme, rewrite the custom templates and make compatible the extensions that touch the visible side. Data, business rules and integrations do not move. The work concentrates on theme, extensions and checkout, and that is what drives the timeline and cost of a Hyvä migration.

What changes when moving from Luma to Hyvä

Luma builds the interface with jQuery, KnockoutJS and RequireJS. Hyvä rebuilds it with Alpine.js and Tailwind CSS. In practice:

  • Templates. The custom PHTML files of the old theme are not reused as they are: they have to be rewritten with Tailwind classes and Alpine components.
  • JavaScript. Logic written in Knockout or RequireJS has to be converted to Alpine.js, or removed if it is no longer needed.
  • Extensions. Those that produce frontend output need a compatibility module.
  • Style build. Tailwind is compiled in development: the documentation requires Node.js 20 or higher and advises against building on production.

Catalogue, customers, orders, promotions, administration and integrations with ERP, PIM and marketplaces stay unchanged.

The stages of a Hyvä migration

1. Audit of the existing store

It starts with an inventory: installed extensions, customised theme components, the pages that generate the most revenue, the checkout in use and current Core Web Vitals values. The audit separates what is carried over as is from what must be rewritten and what can be dropped. It is also the moment to fix the scope: a migration that tries to redo everything at once risks never finishing.

2. Extension compatibility

For each frontend extension you check whether a compatibility module exists. According to the official documentation, modules based on Luma or Blank require a compatibility module to work with Hyvä, and Hyvä keeps a public tracker of the existing ones. Where one is missing, there are three paths: find an alternative that is already compatible, have one developed, or give up the feature. Extensions that only work in the admin usually need no compatibility module.

3. Installing and building the theme

Hyvä installs with Composer, with a free licence key from the vendor's site, and requires minimum Magento and PHP versions that you should verify before starting. Then you create a child theme with the brand customisations: header, category and product pages, search and filter components, cart.

4. The checkout

The checkout deserves a separate decision. The options are: use Hyvä Checkout, keep the existing checkout with a compatibility module, or keep a Luma-based version for a while using the Luma fallback, the module designed to let individual pages stay on Luma while the rest of the site runs on Hyvä. It is mainly useful for migrating gradually. What to choose depends on how customised the checkout is and on the connected payment methods.

5. Testing

You test the paths that bring revenue: search, filters, product page, cart, checkout with every payment and shipping method, customer area. It is better to write the acceptance tests in advance and have them run by the people who use the store every day; it is the same criterion we apply with tools such as EasyUAT.

6. Go-live and after

The release is scheduled in a low-traffic window, with a rollback plan and a monitoring period. After release you remeasure Core Web Vitals on the same pages as the audit and compare them with the initial values. For reference, Google considers LCP within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1 at the 75th percentile to be good.

Typical risks and how to reduce them

  • Extensions without a compatibility module. You find them in the audit, not halfway through the project.
  • Heavily modified Luma theme. The more custom code there is, the closer the rewrite gets to a brand-new frontend.
  • Checkout. It is not postponed: it is the part with the most dependencies.
  • SEO. URLs, structured data and template meta tags must stay equivalent: a frontend change must not change the address of indexed pages.

How long it takes and what it costs

There is no standard timeline: it depends on the number of extensions, the degree of customisation and the checkout. That is why we give no figures in an article: they are estimated after the audit. A store with many extensions and a custom checkout is a different project from a catalogue with few customisations.

An example of a project on Hyvä is the Semprefarmacia case study, a very large catalogue on Magento 2 with integrated microservices for payments, reviews, shipping, marketplaces and search. If you want to assess your own store, Ecommerce Factory starts exactly from an analysis of the existing project; after go-live the store can keep growing with DNA Evolution.

FAQ

Frequently asked questions

Can't find the answer? Write to us and we will get back to you.

Ask your question

Services

The services linked to the guide

  • Ecommerce Factory

    We design and build B2C and B2B online stores on Adobe Commerce (Magento) with Hyvä and on Shopify Plus: analysis, UX, development, integrations, go-live.

  • DNA Evolution

    A dedicated team keeps your online store or software evolving in continuous cycles: new features, integrations and optimisation, planned with a PM and PO.

See all services

The DNAFactory service lines that put into practice what this guide explains.

Guides

More guides

How e-commerce platforms, custom management software and AI work and how to choose, from the people who work on them every day.

Contact us

We are ready to hear about your project

Tell us about your online store or your idea. One of our experts will get back to you within 24 hours.

Request a quote Or write to us at [email protected]