Magento Luma to Hyvä
migration guide.
A Hyvä migration replaces Magento's slow Luma frontend with a Tailwind and Alpine.js theme, keeping your backend. Here is what it involves, how long it takes, and the pitfalls, from a studio that ships Hyvä.
What a Hyvä migration actually is
It is a rebuild of the storefront layer, not a re-platform. Hyvä replaces Luma's RequireJS and Knockout stack with Tailwind and Alpine.js, shipping a fraction of the JavaScript. Your Magento 2 or Adobe Commerce backend, catalogue, orders and admin stay exactly as they are. You are changing how the store is rendered, not where it runs. See also Shopify Plus vs Magento Hyvä if you are still choosing a platform.
How long it takes and what drives the cost
Most migrations run 8 to 16 weeks, and the driver is the number of custom modules and the depth of the existing theme, not the size of the catalogue. A two-week audit produces the real number by inventorying every module and override. From there the work ships in two-week sprints with the site live the whole way through.
The migration, step by step
- Audit the module and theme inventory. List every third-party module, every custom module, and every Luma template override. Mark each for Hyvä compatibility: native Hyvä support, a Hyvä compatibility module exists, needs a frontend rewrite, or can be dropped. This inventory is the real scope of the migration.
- Install Hyvä and a child theme. Add the Hyvä theme and a project child theme. Configure Tailwind and the Hyvä build. Nothing on the storefront changes yet; this is the new frontend foundation alongside the existing Luma theme.
- Rebuild the storefront templates. Port layout by layout: header, footer, PDP, PLP, cart, checkout, CMS blocks. Hyvä uses Tailwind and Alpine.js instead of Luma's RequireJS/Knockout, so this is a rebuild of the frontend, not a restyle. Keep the same Magento backend, blocks and data.
- Port custom and third-party frontend. For each module flagged in step 1, install its Hyvä-compat package or rewrite its frontend as CSP-compliant Alpine.js. Payment, search, reviews and configurator modules are the usual ones that need attention.
- Performance and accessibility pass. Set a Core Web Vitals budget and hit it: image formats, lazy-loading, a measured JS budget, INP on PDP and cart. Hyvä makes strong mobile LCP achievable; the budget is what keeps it that way through launch.
- QA, then launch behind the existing site. Regression-test every journey, diff rendered output for content-heavy pages, and launch with the site online throughout. Migrate in two-week sprints rather than a big-bang cutover.
What to keep versus rebuild
Keep everything backend: modules' business logic, data models, integrations, admin. Rebuild everything frontend: templates, theme JavaScript, and any module UI that touched Luma. The trap is assuming a popular extension “just works” on Hyvä; its backend will, its frontend may need a compatibility package or an Alpine.js rewrite.
The pitfalls to plan for
- Third-party module frontends. Payment, search, reviews and configurators are the usual ones that need a Hyvä-compat package or a rewrite.
- Checkout. Decide early between the default Magento checkout on Hyvä and Hyvä Checkout; they are different scopes.
- Custom JavaScript. Bespoke RequireJS/Knockout widgets do not port; they are rewritten as CSP-compliant Alpine.js.
- Performance regression. Without a budget, third-party scripts creep back in and erase the Hyvä gain. Set the budget on day one.
FAQ
- What is a Magento Hyvä migration?
- A Hyvä migration replaces Magento's legacy Luma frontend (RequireJS, Knockout, heavy JavaScript) with the Hyvä theme, built on Tailwind and Alpine.js. The Magento 2 / Adobe Commerce backend stays the same; you are rebuilding the storefront layer for speed and maintainability, not re-platforming.
- How long does a Hyvä migration take?
- Typically 8 to 16 weeks, driven mostly by the number of custom modules and the depth of the existing theme, not by the catalogue size. A two-week audit sets the real number; then the work ships in two-week sprints with the site live throughout.
- Will a Hyvä migration improve Core Web Vitals?
- Yes, when built to a budget. Hyvä ships a fraction of the JavaScript Luma loads, which is why Hyvä stores reach mobile LCP and INP scores classic Magento themes struggle to hit. The gain comes from the rebuild plus a measured performance budget, not from the theme alone.
- Do all my extensions work with Hyvä?
- Backend logic is unaffected; the frontend of each extension is the question. Many popular modules ship Hyvä compatibility packages; the rest need their frontend rewritten as Alpine.js. The module inventory in step 1 tells you exactly which is which before any budget is committed.
Planning a Hyvä migration?
A two-week audit turns this into a real module inventory, a prioritised plan and a fixed scope for your store. The fee is credited against the build if you proceed.