Move your Magento store from Luma to Hyvä.
Hyvä Theme has been free and open source since November 2025, so a migration now costs the work, not a licence. A senior Magento and Hyvä engineer scopes it, quotes it at a fixed price and builds it on staging while your store keeps selling.
The free check tells you whether the store runs Luma or Hyvä and what a phone waits for today.
- 120 to 300 hours for a store with one design, 20 to 40 extensions and a standard checkout
- 6 to 12 weeks from compatibility audit to release
- Quote in two working days after the compatibility audit; the price is the price
- Built on staging in your repository; nothing changes on the live store until the release
Deep checkout customisation, several store views or a custom design system move a store up the range; the audit says where yours sits.
Get a Hyvä migration quoteThe frontend goes. The store stays.
- The frontend stack
RequireJS, KnockoutJS and jQuery go. Hyvä renders with Alpine.js and Tailwind CSS: a fraction of the JavaScript, pages that paint in under a second on a phone, and frontend work that takes hours instead of days.
- The theme, rebuilt
Your design is rebuilt on Hyvä components, not ported file by file. Header, navigation, category and product pages, cart, account: the same look where you want it, and a chance to fix what never worked.
- What stays
The backend, catalogue, orders, customers, admin, integrations and most extensions keep working as they are. The migration is a frontend project; the store does not move anywhere.
- Editors and marketing
Page Builder content and CMS blocks render on Hyvä; the editors keep their tools. Tracking tags, consent and the analytics layer are re-attached and tested, not assumed.
The audit before the quote.
Every extension that touches the frontend gets one of four verdicts. The list is the scope, and the scope is the price; no estimate is given before it exists.
- Hyvä version availableThe vendor ships a Hyvä build. Installed and tested.
- Compatibility module existsA community or vendor compatibility module from the Hyvä registry covers it. Installed, tested, sometimes adjusted.
- RewriteSmall frontend parts (a widget, a block, a form) rebuilt as Hyvä components. Hours in the quote.
- Replace or dropAbandoned extensions, duplicates, or ones whose job Hyvä already does. Often the cheapest line.
Three options for the checkout. I say which.
The native option: fast, same stack, and the one I recommend when your payment and shipping extensions have a Hyvä Checkout version. Licence terms are checked at quote time.
The Luma checkout can stay behind the Hyvä compatibility layer. Cheaper now, slower for the customer; fine as a first phase when checkout customisations are deep.
A third-party or custom checkout you already run can stay if it has a Hyvä build. I say which of the three fits your store in the compatibility audit, with the price of each.
Four phases, one release.
6 to 12 weeks for a typical store. Still on Magento 2.4.6 or older? The upgrade fits into the same project.
Get a Hyvä migration quote- Compatibility auditEvery extension that renders on the frontend is listed with its status: Hyvä version available, compatibility module exists, rewrite needed, or replace. Backend-only modules are unaffected. You get the list and the fixed quote.
- BuildTheme and components on staging, page type by page type, reviewed against the live store. Your team sees progress on the staging URL, not in a slide deck.
- Checkout and integrationsThe checkout option you chose, payment methods, shipping, tax, promotions, search, tracking, consent. Tested with real orders on staging.
- Release and the first monthGo-live in your window with a rollback plan; Core Web Vitals watched for the first weeks. Then the monthly plan keeps the store moving.
Is the Hyvä licence really free?
Yes. Hyvä Theme has been open source and free since November 2025. Hyvä Checkout and some paid compatibility modules are separate products; their terms are part of the quote.
How long does it take?
Most migrations run 6 to 12 weeks from compatibility audit to release, depending on the number of extensions and how custom the design is. A store with a simple theme and well-supported extensions is at the short end.
Can we keep our current design?
Yes, rebuilt on Hyvä components. Pixel-for-pixel is possible but rarely worth it; most stores take the migration as the moment to simplify.
Our extensions have no Hyvä version. Now what?
The audit says which ones: the Hyvä compatibility registry covers a large share of common extensions, a rewrite covers small ones, and a replacement is sometimes cheaper than either. No store has been stuck on this in my experience; the question is cost, and it is in the quote.
Upgrade and Hyvä at once?
If you are on 2.4.6 or older, yes: one staging environment, one round of testing, one release. See the Magento upgrade page for the dates.
See what is slowing your store down
Free, no call. Results by email within one working day.