Hyvä theme migration explained for merchants: what actually changes, what stays, how long it takes, what it costs, and how to avoid the common mistakes that slow stores down even on Hyvä.
Moving from Luma to Hyvä involves rebuilding your Magento storefront using a modern frontend stack, but your backend, catalog, orders, and integrations remain the same. Most migrations take 4 to 16 weeks, depending on the complexity of your store. Since November 2025, Hyvä Theme is free and open source. There’s also Hyvä Commerce, which offers a modern admin panel and an improved CMS with features like image editing, media optimization, and real-time storefront previews. You can see changes instantly and easily jump to the editor by clicking any part of the preview. Keep in mind that while Hyvä provides a strong performance foundation, it is not a magic fix. Your store can still be slow if you add too many unoptimized third-party scripts, large images, or poorly built extensions. The theme removes technical limits, but your choices still affect performance.
What “Migrating to Hyvä” Actually Means
Moving from default Magento Luma to Hyvä isn’t a simple switch like with Shopify themes, where you just pick a new one and activate it. Luma and Hyvä use different technology stacks, so migrating means building a new frontend on Hyvä while your Magento backend stays the same. (Yes, Shopify does make theme switching easier, but it comes with its own tradeoffs, like less control over backend logic, less flexibility for complex B2B scenarios, and platform lock-in. Check the full comparison in Magento vs Shopify.)
What changes: the storefront is everything your customers see and interact with. The product pages, category listings, navigation, CMS blocks, and (optionally) the checkout.
What doesn’t change: the admin panel (in case of migration to Hyva Commerce your admin panel will also change, for a better one 😁), your catalog structure, customer accounts, order history, ERP connections, payment gateways, shipping integrations, and URL structure. All of it stays in place.
So zero disruption to backend operations. There’s no data migration, no replatforming risk, and no downtime for your business processes. Your team continues to manage orders and inventory in the same Magento admin while the new frontend is being built in a staging environment.
Behind the scenes, Hyvä swaps out Magento’s old frontend libraries like RequireJS, KnockoutJS, jQuery, and LESS for a modern, lightweight stack. It uses Alpine.js for interactivity and Tailwind CSS for styling. This change in architecture is what leads to such a big performance boost, and it’s also why you can’t just move Luma code into Hyvä. Every custom frontend component needs to be rebuilt for the new stack, but this is often faster and less expensive than trying to maintain and optimize your existing Luma setup.
Why Stores Migrate from Luma to Hyvä
If you’re reading this, you likely already experienced issues with your Magento frontend. The real question is whether investing in Hyvä makes sense. Here are the business problems that lead merchants to make the switch, supported by real data rather than marketing claims.
Performance That Costs You Revenue
Luma’s frontend loads over 200 JS/CSS resources on every page, totaling roughly 1.5 MB of uncompressed assets. Hyvä loads just two resources at approximately 0.2 MB. That’s a 98% reduction in page requests and an 86% reduction in page weight.
We tested this ourselves. On identical DigitalOcean droplets with identical Magento installations: one running Luma, one running Hyvä - the product page weighed 0.9 MB on Luma and 0.15 MB on Hyvä. On modern mid-range smartphones (the devices most of your customers actually use), the gap widened further: pages that took several seconds to become interactive on Luma loaded in under one second on Hyvä. It’s fundamentally different from the user experience.
Core Web Vitals You Struggle to Pass on Luma
Google’s Core Web Vitals (CWV) — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — directly affect your search engine rankings. Over 66% of Hyvä-powered stores pass CWV, compared to roughly 44% on Luma. That gap isn’t because Luma merchants aren’t trying, it’s because Luma’s architecture makes passing CWV structurally difficult.
Hyvä resolves all three CWV signals at the architecture level. LCP improves because above-the-fold content renders before heavy scripts execute. INP improves because there’s minimal JavaScript overhead, so the browser responds to taps and clicks faster. CLS improves because there’s no KnockoutJS rebinding the DOM after initial load, so the layout stays stable from the first paint.
Still, some of Hyvä stores do not pass CWV. This is not a problem with Hyvä itself. The issue comes from merchants adding too many unoptimized third-party marketing scripts, chat widgets, heatmaps, A/B testing tools, and poorly built extensions. Hyvä gives you the best possible starting point, but it cannot make up for dozens of external scripts using up browser resources. You still need to build your store carefully even on Hyvä.
If you’ve already optimized your server, CDN, and images but still can’t pass CWV, then the frontend is the bottleneck.
Development Costs That Keep Climbing
Luma’s complexity not only slows down your store, it also slows down your development team. Every change means dealing with RequireJS dependency chains, debugging Knockout data bindings. In simple language, it costs more time and money.
Agencies consistently report that Hyvä reduces frontend development time by 30–50% compared to Luma. From our own experience, this holds true: our Magento extension store, which was a relatively simple project, was built with the first edition of Hyvä (just after the Hyva launch) in about a month (~200 hours), including the development of a custom Stripe payment integration. On Luma, the same scope would have taken considerably longer.
For complex projects, the savings add up. Grasscity, a large multi-store Magento project with thousands of SKUs and complex integrations, took five months to complete on Hyvä. That is quick for a project of this size. Lower development time also means lower ongoing maintenance costs. When your frontend is simpler, every new feature, bug fix, and Magento upgrade takes less time and causes fewer issues.
Beyond Frontend Speed: Hyvä Commerce as a Platform Upgrade
Since its general availability in July 2025, **Hyvä Commerce**has expanded the case for migration beyond pure frontend performance. Priced at €3,000/year with no restrictions on GMV, traffic, or number of storefronts, Hyvä Commerce is a full product suite built on top of Magento Open Source that includes the Theme, Checkout, UI components, CMS and a growing set of merchant-focused tools. Close to 300 merchants adopted it within six months of launch, and the number keeps growing.
Hyvä CMS is one of the most compelling features for marketing teams. It replaces Magento’s basic content management with a modern editor, allowing you to open an element in the editor with just a click in the preview. Yes, so simple. We waited it so long as well as real-time storefront preview (LiveView), content scheduling, version control, translation support, and drag-and-drop components. You can see exactly how your page will look on the live store while you’re editing it, no more “save, flush cache, reload, check.” Existing Page Builder content can be migrated into Hyvä CMS at your own pace.
Hyvä Admin Theme and Dashboard update the Magento backend with a cleaner interface, customizable widget-based dashboard, per-user layout control, and developer APIs for custom widgets. This makes daily work in the admin panel faster and less frustrating, especially for non-technical team members who manage the catalog and orders.
Hyvä Image Editor and Media Optimization let your team crop, resize, and apply filters to images directly within Magento, so no more external tools. The media optimization includes automatic WebP conversion and CLI-based bulk processing, which directly impacts storefront page weight and LCP scores.
Hyva AI Translations - AI-Powered Multilingual Content for Magento.
Hyvä POS - Coming Soon
For Magento Open Source stores, Hyvä Commerce fills a gap left by Adobe, which now focuses its investment on enterprise-level Adobe Commerce and AEM. Hyvä Commerce offers a clear roadmap for features and improvements that the core platform no longer provides for small and mid-sized businesses.
Most of those features are common for Shopify, but it’s a breakthrough for Magento.
Is Your Store Ready for Hyvä? What to Evaluate First
Before scoping a Hyvä migration project, there are four questions you should answer. Each one affects timeline, budget, and the overall approach.
What Magento Version Are You On?
Hyvä requires Magento 2.4 or higher. If you’re on an older 2.x version, a Magento upgrade needs to happen first, or can be combined with the Hyvä migration into a single project.
If you’re still on Magento 1, this isn’t a theme migration at all, it’s a full replatform. Magento 1 support ended in June 2020, and moving to Magento 2 + Hyvä is a significantly larger project with its own planning requirements. We’ve covered the Magento 1 migration path separately.
Do You Need a Redesign or a Performance Upgrade?
There are two paths: replicate your current design on Hyvä, or redesign at the same time.
If your current UX works and the goal is purely a performance upgrade, your agency can rebuild the same design on Hyvä. This is faster, cheaper, and lower risk because you’re eliminating one major variable (design decisions) from the project scope.
If you’ve been planning a redesign anyway, Hyvä migration is the ideal time to do it. You’re rebuilding the frontend regardless, adding a UX refresh on top of that doesn’t double the effort.
Either way, Hyvä’s UI component library speeds up the process significantly. Hyvä UI provides production-ready, fully functional storefront blocks, mega menus, product sliders, accordions, category filters, breadcrumbs, headers, footers, galleries, and more. All that comes with the expected interactions and Magento logic already wired in. They’re not just styling templates; they’re working components you can adapt to your brand. Hyva constantly extend the library with new components. We built a Hyvä UI Components demo store where you can click through and see these blocks in action.
Which Third-Party Extensions Do You Use?
This is typically the single biggest variable in a Hyvä migration project. The ecosystem has matured significantly: over 1,200 extensions are now compatible with Hyvä, and major extension vendors like Amasty, Mageworx, MagePlaza, and Mirasvit have been actively releasing Hyvä compatibility modules.
However, stores with niche or custom-built extensions need an extension compatibility audit before you can accurately plan the project. Extensions with storefront-facing components, such as product page widgets, category filters, or popup modals, need a Hyvä-compatible version. If the extension vendor has not released one, your development team will need to build it. The extension’s backend logic and admin configuration stay the same; only the customer-facing output is rebuilt for Alpine.js and Tailwind CSS instead of jQuery and Knockout.
This compatibility work is often the biggest cost factor in the project. Taking inventory of your extensions early helps prevent surprises during the build.
How Customized Is Your Checkout?
Hyvä doesn’t replace the checkout by default. When you migrate to Hyvä, Magento’s standard Luma-based checkout continues to work via a built-in fallback mechanism. This means the checkout still functions, but it’s often the last slow page on an otherwise fast site.
You have three options:
Keep the Luma checkout fallback. Simplest approach, zero additional development. But your customers will experience a noticeable speed drop at the most critical conversion step. If your current checkout is heavily customized and you’re not ready to invest in rebuilding it, this buys you time.
Adopt Hyvä Checkout. Built on Magewire, it loads 13× faster than the default Magento checkout on mobile. It supports the most common payment providers (Stripe, Mollie, PayPal, Adyen, Braintree) and shipping integrations out of the box. Available standalone for €1,000 or included in the Hyvä Commerce subscription.
Build a custom React-based checkout. For stores that need full control over the checkout experience, Hyvä React Checkout provides a flexible foundation. We developed a free open-source Stripe Payment method for Hyvä React Checkout.
Hyvä Theme, Hyvä Commerce or Hyvä Enterprise. Which Do You Need?
The Hyvä ecosystem has expanded beyond a single theme. Understanding which products fit your situation helps you budget accurately.
Hyvä Theme - free, open source. The frontend foundation. Since November 2025, Hyvä Theme is fully open source: no license fees, unlimited domains and store views, free updates. Community support via Slack. Up to 5 free access keys per individual, 50 per agency partner. This is where every Hyvä project starts.
Hyvä UI - €250 one-off per project. The pre-built component library. Mega menus, product sliders, layered navigation, cookie notices, headers, footers, galleries, and more. Comes with a Figma design system for designer-developer alignment. Worth it for any project where you want to move faster than building every component from scratch. See it live: Hyvä UI Components demo store.
Hyvä Checkout - €1,000 one-time. 13× faster load on mobile compared to default Magento checkout. Includes 12 months of support and updates; then €250/year for ongoing support, or €1,000 for a 5-year block. Supports major payment providers and shipping integrations.
Hyvä Commerce - €3,000/year. The full suite for Magento Open Source. Bundles Theme + UI + Checkout + CMS with LiveView + Admin Theme & Dashboard + Image Editor + Media Optimization. No restrictions on GMV, traffic, storefronts, or users. Premium support from the Hyvä team included. Existing Theme or Checkout license holders can trade in their investment as credit toward the first year. If you’re on Magento Open Source and plan to use Checkout + UI + CMS, the Commerce subscription is typically better value than buying everything separately.
Hyvä Enterprise - €2,500/year. Adds support for Adobe Commerce-specific features: B2B suite (company accounts, custom catalogs, negotiated pricing), Gift Cards, Rewards and Loyalty Points, Content Staging and Preview, Adobe Sensei (Live Search, Product Recommendations). Required in addition to a Hyvä Theme (free) or Commerce license if you run Adobe Commerce with these features.
If you have Adobe Commerce, you can use Hyvä Commerce, which is fully compatible as it's built on the Magento 2 codebase. Hyvä Commerce enhances your setup with better performance and CMS functionality. However, to access advanced features like the B2B Suite, Gift Cards, or Rewards and Loyalty Points, you will need to purchase Hyvä Enterprise alongside Hyvä Commerce.
The Migration Process: What to Expect
Here's what a Hyvä migration looks like from the merchant's side — what happens at each stage and what decisions you need to make.
Step 1: Store Audit and Compatibility Check
Your development team reviews your current Magento installation: which extensions are installed, what frontend customizations exist, how the checkout is configured, and what the current performance baseline looks like. The output is a compatibility report with a clear scope definition.
Your role: provide admin access, share which features and extensions are business-critical, flag any upcoming campaigns or peak traffic periods that affect timing.
A Magento performance audit at this stage gives you a documented baseline to measure the migration's impact against.
Step 2: Licensing
Hyvä Theme is free. Decide whether you need Hyvä UI (€250), Hyvä Checkout (€1,000), or the full Hyvä Commerce subscription (€3,000/year) based on the project scope defined in Step 1.
Your role: register at hyva.io, purchase the appropriate license(s).
Step 3: Design Decisions
Two paths: replicate your existing design on Hyvä, or use the migration as an opportunity for a UX refresh. Most stores find that a targeted redesign — keeping the overall brand and UX patterns but improving specific flows — offers the best balance of investment and impact.
Your role: approve the design direction and provide brand assets.
Step 4: Frontend Build
Your development team builds the new storefront on Hyvä. CMS pages and blocks are adapted to work with Hyvä's template system. If you're using Hyvä UI components, many common storefront blocks start from pre-built, functional foundations rather than from scratch.
Your role: review staging builds regularly, test user flows, flag issues early.
Step 5: Extension Compatibility Work
Extensions with existing Hyvä compatibility modules get those installed and configured. Extensions without them need their storefront-facing output built for the Hyvä stack. The backend functionality and admin configuration of every extension remains unchanged.
Your role: prioritize which extensions are must-haves for launch versus nice-to-haves that can follow.
Step 6: Checkout Configuration
Based on the decision from your readiness evaluation: implement Luma fallback checkout (simplest), configure Hyvä Checkout with your payment and shipping providers, or build a custom React-based checkout. If you choose Hyvä Checkout, your team will configure payment provider integrations (Stripe, Mollie, PayPal, Adyen) and shipping method support.
Your role: confirm which payment methods and shipping options must be supported at launch.
Step 7: QA and Performance Validation
Cross-device and cross-browser testing. Core Web Vitals validation using real device testing and lab tools (WebPageTest, Lighthouse). Full user journey testing: browse → search → product page → add to cart → checkout → order confirmation. Regression testing of all critical business flows.
Your role: user acceptance testing (UAT) sign-off. Test with your team as if you're a customer.
Step 8: Go Live and Monitor
Staged rollout. Monitor CWV in Google Search Console post-launch. Verify that search engine indexing and rankings remain stable. Track real-user performance data. Fine-tune — there are quick performance optimizations like enabling Speculation Rules and x-defer that take just a few clicks to activate in Hyvä's admin panel.
Your role: final go-live approval.
Timeline and Cost: What to Budget For
Timelines vary significantly based on store complexity, and any agency that quotes a fixed number without auditing your store first is guessing. Here are realistic ranges based on our project experience:
Simple store - standard catalog, minimal custom extensions, no custom checkout: 4–6 weeks. This is a relatively straightforward frontend build.
Mid-complexity store - B2B features, custom catalog logic, 10–20 third-party extensions, multi-language: 6–14 weeks. Extension compatibility work and checkout configuration add the most time here.
Complex/enterprise store - heavily customized checkout, many integrations, multi-store setup, large catalog with custom product types: 10–16 weeks. Projects like Grasscity with thousands of SKUs, multi-store architecture, and deep third-party integrations took approximately five months. Note that Hyvä’s ecosystem was less mature in 2022; the same scope today would likely take less time thanks to the larger library of compatible extensions and UI components.
The main cost drivers: number of integrations, checkout complexity (fallback vs. Hyvä Checkout vs. custom), whether you’re redesigning or replicating the current design, and the number of store views and languages.
What you’re not paying for: Hyvä Theme itself is free. The Hyvä product costs are transparent: €250 for UI components, €1,000 for Checkout, or €3,000/year for the full Commerce suite. The rest of the investment goes into development labor and your agency’s expertise.
What Happens to SEO During Migration?
This is one of the most common concerns merchants raise, and the answer is reassuring: a Hyvä migration is one of the lower-risk frontend changes you can make from an SEO perspective.
URLs don't change. Your URL structure is controlled by Magento's backend routing, which stays untouched. Every product, category, and CMS page keeps its existing URL.
Structured data transfers. Your meta titles, descriptions, schema markup, and Open Graph tags are implemented in the new Hyvä templates. If you take the opportunity to add FAQ schema, HowTo schema, or improve your structured data during the migration, it's a net SEO positive.
CWV improvement helps rankings. Google uses Core Web Vitals as a ranking signal. Passing CWV where you previously failed typically improves your organic visibility, not harms it.
No 301 redirects needed for a pure Hyvä migration (no redesign that changes URL structure). If you're combining the migration with a site restructure that does change URLs, plan your 301 redirect map carefully.
Post-launch monitoring is essential. Watch Google Search Console for any crawl errors, indexing issues, or ranking fluctuations in the first 2–4 weeks after go-live. Minor issues are normal during any frontend change and are typically resolved quickly.
FAQ
No. Hyvä replaces only the frontend layer — the storefront that customers see. Your Magento admin panel, catalog, customer data, order management, ERP connections, payment gateways, and all backend integrations remain completely unchanged.
Yes. Since November 2025, Hyvä Theme is open source and free to use with unlimited domains and store views. Hyvä UI (€250), Hyvä Checkout (€1,000), Hyvä Commerce (€3,000/year), and Hyvä Enterprise (€2,500/year) are separate paid products that add functionality on top of the free theme.
Hyvä Commerce is a product suite for Magento Open Source (it works with Adobe Commerce as well) that bundles Theme, UI, Checkout, CMS with LiveView, Admin Dashboard, Image Editor, and Media Optimization for €3,000/year. If you plan to use multiple Hyvä products, the Commerce subscription typically offers better value than purchasing them separately. It's not required, you can start with just the free theme and add products as needed.
Yes. Your agency can replicate your current design on Hyvä for a purely performance-focused migration. Many stores also use the migration as an opportunity for a UX refresh.
By default, your existing Luma checkout continues to work via Hyvä's built-in fallback. You can also adopt Hyvä Checkout (€1,000 or included in Commerce) for significantly faster performance, or build a custom React-based checkout for full control.
Over 1,200 Magento extensions are now compatible with Hyvä. Extensions that have storefront-facing components not yet adapted for Hyvä will need their customer-facing output built for the new stack. An extension audit before starting the project identifies exactly which extensions need attention and how much effort each requires.
Typically 4–6 weeks for a simple store, 6–10 weeks for mid-complexity, and 10–16 weeks for complex enterprise stores. The main variable is the number of extensions requiring compatibility work and whether you're combining the migration with a redesign.
In most cases, positively. URLs remain unchanged, and the CWV improvement from Hyvä typically helps organic visibility. Monitor Google Search Console for the first 2–4 weeks post-launch to catch and resolve any minor issues quickly.
Yes, Hyva Commerce is fully compatible with Adobe Commerce but to access advanced features like the B2B Suite, Gift Cards, or Rewards and Loyalty Points, you will need to purchase Hyvä Enterprise alongside Hyvä Commerce.
About the author
Olena Kulbych
CMO
With 12+ years at Eltrino, Olena bridges tech teams and business leaders, sharing Magento, Hyvä, Shopify, performance, and AI insights rooted in real-world eCommerce.
