Hyvä Migration: from Luma to Hyvä

Fundamentals

What a Hyvä migration actually changes

The short version

Hyvä replaces the Luma frontend, not your Magento installation.
Hyvä Theme has been open source and free since November 2025; Hyvä Checkout, Hyvä UI and the Hyvä Commerce and Hyvä Enterprise bundles still need a licence.
The effort sits in your extensions. That is why the engagement starts with a paid audit and only then gets a fixed price.
Delivered: two Hyvä stores end to end (gastrostars.shop, lestrouvaillesdelsa.fr) plus the Hyvä Checkout in an international enterprise project.

The store stays, the frontend is replaced: Magento 2 or Adobe Commerce, the catalogue, orders, customer accounts and the admin all stay where they are. What gets swapped is the storefront, not the platform.
The Luma frontend stack goes away: Hyvä replaces Knockout, RequireJS, the UI components and LESS with Alpine.js and Tailwind CSS. What stays are the Magento tools: layout XML, blocks, view models and phtml. That is also exactly why Luma templates cannot simply be copied across.
Extensions with their own frontend need a decision: Extensions that only work in the backend keep running unchanged. For extensions with their own Luma frontend there are three routes: a compatibility module from the publicly tracked Hyvä register, a rebuild in Hyvä, or dropping it. Which of your extensions falls into which group is the main outcome of the audit.
The checkout is a product of its own: Hyvä Checkout sits next to the theme: server-rendered on Magewire and switchable per store view, so it can be rolled out gradually. The work sits in payment methods, tax logic and shipping integration. I built it for GastroStars and own it in the enterprise project with Adyen, RatePay and Avalara.
The theme is free, the add-ons are not: Since November 2025 Hyvä Theme is open source and free. Hyvä Checkout, Hyvä UI, Hyvä Commerce and Hyvä Enterprise still require a licence — licensed per Magento installation, with unlimited domains and store views. The licence runs directly through hyva.io and is not buried in my fixed price.
What has to be true on your side: Per Hyvä's own documentation, Hyvä requires Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7 or 2.4.7-p1 and up, plus PHP 8.1 to 8.4. If your store sits below that, the version upgrade belongs in the plan — and in the price.

Services

Hyvä migration services

Theme analysis: Which Luma templates are overridden, which extensions ship their own frontend, and which of those already have a compatibility module.
Hyvä theme development: Alpine.js and Tailwind CSS under your own vendor namespace. For Les Trouvailles d'Elsa that meant two brand themes in a single installation.
Hyvä Checkout: Payment methods, tax logic and shipping — from Stripe and MondialRelay through to Adyen, RatePay and Avalara across several tax jurisdictions.
Carrying over customizations: Custom modules for category, navigation, header and footer rebuilt on Hyvä, as done for the two French brand stores.
Surrounding systems and search: Smile Elasticsuite, Snowdog Menu, ERP and PIM integrations (SAP, eggheads), supplier importers, newsletter and feed connections.
Quality assurance: Playwright end-to-end tests across several viewports, CI on GitHub Actions, Sentry for whatever surfaces after go-live — that is how GastroStars runs.

How I work: A paid audit of your existing theme first, then a fixed price for the migration. No open-ended hourly billing. Professional indemnity insurance via exali.com, invoiced from the EU.

Process

How a Hyvä migration runs

01

Paid audit

I go through theme, extensions and checkout and measure the store as it stands. The output is the list of what gets carried over, rebuilt or dropped.
02

Migration plan and fixed price

The audit becomes the plan, the plan becomes the fixed price. Only at that point is the migration decided.
03

Implementation

Theme, checkout and components under your own namespace, so your customizations survive updates. Local development on DDEV, every change through Git.
04

Testing and go-live

Playwright tests across several viewports, a measurement against the audit baseline, then go-live. Anything that breaks afterwards reaches me through Sentry.

These four steps are fixed; you get the timeframe with the audit.

References

Hyvä in practice

Two of these stores you can open yourself. The third stays anonymous at the client's request.

International heritage brand · on the project since 01/2019

Consumer goods, anonymized at the client's request

Moved the frontend from Vue Storefront to Hyvä Commerce while the business kept selling: eight store views across five countries, three languages, Adobe Commerce on Cloud with Fastly. I own the Hyvä Checkout with Adyen, RatePay and Avalara across several tax jurisdictions. Joined in 2019 as a senior developer through an agency, since 2025 as full-stack architect and lead of two developers.

Les Trouvailles d'Elsa · 03/2023–07/2023

lestrouvaillesdelsa.fr — retail, France

Migration from Luma to Hyvä for two brands in one Magento installation, delivered end to end from concept to go-live: two themes under my own vendor namespace, Hyvä Checkout, Stripe, MondialRelay including pickup-point selection, GeoIP country redirection and the French market requirements.

GastroStars · since 11/2025

gastrostars.shop — B2B wholesale for restaurant equipment

Built on Hyvä from scratch rather than migrated: a Shopify store moved entirely to Magento 2 Open Source, Hyvä theme with its own override and Hyvä Checkout, no Luma left. Plus eleven custom supplier importers with stock orchestration, Smile Elasticsuite, Snowdog Menu, Sentry, Playwright and CI on GitHub Actions — all of it delivered end to end.

Straight talk

What I promise

Measured on your store

During the audit I measure your store as it stands, so that after go-live you hold a real comparison. I have no recorded before/after figures from my previous Hyvä projects, so I do not quote a percentage up front.

A timeframe I hold myself to

After the audit you get a timeframe I can hold myself to. What decides the duration is the number of overridden templates and the extensions with their own frontend.

An honest recommendation

The audit shows whether a migration is worth it for your store right now. If not, I will say so. You keep the findings, with everything in them.

You talk to the person who builds it

No account manager, no handover chain. On larger projects I bring in experienced freelance colleagues; responsibility for the result stays with me. German and English, EU time zone, EU invoicing.

Qualifications

Official Hyvä Bronze Partner

Official Hyvä Bronze Partner — currently valid, listed in the partner directory on hyva.io
Two Hyvä stores delivered end to end, from concept to go-live, plus the Hyvä Checkout in an international enterprise project
Adobe Certified Expert — Adobe Commerce Developer (valid 01/2022–01/2024, expired)
Adobe Certified Expert — Adobe Commerce Cloud Developer (valid 10/2021–10/2023, expired)
B.Sc. Electrical Engineering and Information Technology, Technical University of Munich (2017)
In the Magento ecosystem since 2014, self-employed since 2022 as Maile IT

Badges on Credly.

FAQ

Frequently asked questions about Hyvä migration

Are you an official Hyvä partner?

Yes, an official Hyvä Bronze Partner, currently valid and listed in the partner directory on hyva.io. Bronze is the entry tier of the four-tier partner programme (Bronze, Silver, Gold, Platinum); the tiers follow active licences, certifications and the Core Web Vitals pass rate of the listed live projects.

What does a Hyvä migration cost?

Hyvä Theme itself has cost nothing since November 2025, it is open source. What you pay for is the development work and, if you need them, licences for Hyvä Checkout, Hyvä UI, Hyvä Commerce or Hyvä Enterprise — those run directly through Hyvä and are not part of my price. My side starts with a paid audit of the existing store, after which you get a fixed price for the migration.

How long does a Hyvä migration take?

The audit establishes that. The duration depends on how many templates are overridden in your Luma theme and how many extensions ship their own frontend. After the audit you get a schedule and a price I can hold myself to.

How much faster will my store get with Hyvä?

Measuring your own store shows it: during the audit I measure the current state, after go-live I measure against those baseline values. That gives you a real comparison instead of percentages from other people's stores.

Which Magento version do I need for Hyvä?

Per Hyvä's own documentation, Hyvä requires Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7 or 2.4.7-p1 and up, plus PHP 8.1 to 8.4. If your store sits below that, the version upgrade belongs in the migration plan and in the price.

What happens to my extensions and custom work?

Extensions that only work in the backend keep running unchanged. Extensions with their own Luma frontend need a decision: a compatibility module, a rebuild in Hyvä, or dropping it. Which of your extensions falls into which group is the main outcome of the audit.

Will my Google rankings survive the migration?

The migration swaps the frontend, not the content: URLs, categories, product copy and redirects stay in Magento where they are. My job is to carry meta data, heading structure and structured data over completely while the templates are rebuilt. I do not give a ranking guarantee — nobody can give one honestly.

Can we keep selling during the migration?

Yes. Per Hyvä's documentation, Hyvä Checkout can be enabled per store view, so a gradual rollout is built in. I did the frontend switch in the enterprise project while international selling continued, across eight store views in five countries.

Do you also migrate from frontends other than Luma?

Yes. Among other things I moved a frontend from Vue Storefront to Hyvä Commerce on an international multi-store shop with eight store views across five countries.

Hyvä or headless / PWA — which is right for us?

I have built both, and in one project I was part of the way back: there the frontend ran headless on Vue Storefront and was moved to Hyvä. The difference is mostly operational. Hyvä stays inside Magento's own templating with layout XML, blocks, view models and phtml; a headless setup brings a second application with its own deployment and its own operations. Which one is right for you is something I say after the audit, not before.

Do you take on the checkout as well?

Yes. Hyvä Checkout is a product of its own next to the theme. I built it for GastroStars and own it in the anonymized enterprise project with Adyen, RatePay and Avalara across several countries and tax jurisdictions.

Is Hyvä suitable for B2B stores?

Yes. GastroStars is a B2B wholesaler for restaurant and kitchen equipment and runs entirely on Hyvä, including Hyvä Checkout, eleven connected suppliers and stock orchestration across several sources.

Do you also build new stores directly on Hyvä, without a migration?

Yes. For GastroStars I built a Shopify store from scratch on Magento 2 Open Source with Hyvä, with no Luma involved.

Request a Hyvä migration.

Tell me briefly which theme you're running today. You get a personal reply from me within 24 hours.

Book a 30-minute call

or send me a message: WhatsApp or email

contact@maileit.com · German & English · EU time zone

Hyvä migration: from Luma to Hyvä