Migrating from Luma to Hyvä: What We Learned After 15 Projects

Hyvä theme has become the de-facto standard for new Magento frontends. After migrating 15 stores from Luma to Hyvä, we've built a reliable playbook. The performance gains are consistent — PageSpeed scores jump from the 30-50 range to 85-98 — but the migration requires careful planning, especially around third-party extensions.

The Compatibility Challenge

Hyvä replaces Luma's RequireJS/KnockoutJS stack with Alpine.js and Tailwind CSS. This means every frontend extension that adds KnockoutJS widgets or RequireJS modules needs a Hyvä-compatible version. Check the official Hyvä compatibility list before starting. For incompatible extensions, you have three options: find a Hyvä-compatible alternative, pay for the vendor's Hyvä module, or rebuild the frontend functionality yourself.

Migration Phases

1. 1Extension audit: List all frontend extensions and check Hyvä compatibility
2. 2Page-by-page migration: Start with static pages (CMS), move to catalog, then checkout
3. 3Custom component rebuild: Rebuild any Luma-specific JavaScript widgets in Alpine.js
4. 4QA and regression testing: Full checkout flow, search, account pages, custom features
5. 5Performance validation: Confirm PageSpeed improvements meet targets before launch

Timeline Expectations

A standard Magento store with 5-10 extensions takes 6-10 weeks for a Hyvä migration. Add 2-4 weeks for each complex custom extension that needs a rebuild. Stores with heavy checkout customization or complex B2B functionality can take 16-20 weeks. Don't underestimate extension work — it's consistently where projects run over schedule.

Performance Results Across 15 Projects

Mobile PageSpeed: average before 38, average after 91. Desktop PageSpeed: average before 67, average after 97. TTFB improvement: 22% average. These numbers are consistent because Hyvä's architecture fundamentally removes the JavaScript bottleneck — you're not polishing a slow engine, you're replacing it.