Need a Baseline First? The free Magento audit reads speed and Core Web Vitals from the storefront.

A Luma to Hyvä migration is done page by page. The first page takes the longest, about 2 months of development plus 1 week of QA and 1 to 2 weeks of user acceptance testing, because it includes the header, footer and mini cart that every later page reuses. In our estimate for a mid-size Adobe Commerce store, the first page came to 158 hours and the whole storefront (home, category, product and cart) to roughly 700 to 780 hours.

The Hyvä Theme licence itself is now free, so the budget goes to development hours, Hyvä-compatible extensions and, optionally, paid Hyvä products. Below: the steps, the order that works best, the hours per page type, current licence prices and the risks to plan for.

An example, not a quote: the timelines and hours in this article come from real estimates and they are rough. The actual numbers depend on how complex your site is and how much custom logic it already has.

What changes when you move from Luma to Hyvä?

Hyvä replaces Luma, the default Magento 2 theme, with a much lighter front end. Hyvä's own comparison puts a typical page at 5 requests instead of 230, which is 98% fewer, and at 0.4 MB instead of 3 MB uncompressed, which is 86% lighter. These are the vendor's numbers. Your result depends on your extensions and custom code, which is why we recommend measuring on one page before committing to the rest. Our Hyvä vs Luma comparison sets the two front ends side by side, category by category.

Why speed matters for revenue is documented outside Hyvä as well. Google's research behind the Web Vitals thresholds found that when a site meets them, visitors are 24% less likely to abandon a page before it loads. The Milliseconds Make Millions study, commissioned by Google and conducted by 55 and Deloitte, links a 0.1-second improvement in mobile load time to an 8.4% higher conversion rate on retail sites.

What should not change: analytics events, existing SEO work and accessibility. We treat all three as acceptance criteria for the migration, not as nice-to-haves.

How do you migrate from Luma to Hyvä, step by step?

1. Measure the baseline

Record Core Web Vitals for the home, category, product and cart pages on desktop and mobile in a monitoring tool such as DebugBear, so every later claim has a before and after. Our free Magento audit gives a first reading of speed and Core Web Vitals from the storefront.

2. Define what must not break

Write down the GA4 events, the SEO settings (titles, canonicals, structured data, redirects) and the accessibility level that the new theme has to keep.

3. Audit extensions and custom code

List every module that touches the storefront. Each one needs a Hyvä-compatible version or a rewrite, and some are separate paid licences. This audit is where our Hyvä theme development work starts, because the estimate follows from the list.

4. Get the licence and set up environments

Get the free licence key from a hyva.io account and install Hyvä on a development environment first. The paid Hyvä products are licensed per Magento installation, with unlimited store views and domains for the same business entity, and may also be used on non-production environments.

5. Build the pilot page with the shared layer

Header, footer, mini cart, quick search, account sidebar and store switcher are built once here and reused on every other page.

6. Check the pilot against the baseline

Pass or fail is decided on the Core Web Vitals you recorded in step 1, before any further stage is approved.

7. Migrate the remaining page types

Category, product and cart follow. From here the work is mostly content blocks, listing features and JavaScript that has to be rewritten for Hyvä.

8. Move CMS pages and monitor

Plan for about 4 to 5 hours per CMS page and around 4.5 hours for a repeatable page template, then keep the monitoring running after launch.

Which page should you migrate first?

The order is flexible: the product page, the home page or the category page can all go first. What matters is that whichever page goes first carries the one-off work of the header, footer and mini cart, and every page after that changes mostly content blocks. In one project we launched the product page alone first, and the pages still on Luma stayed untouched until later stages.

Pick the first page by business goal. The product page is closest to the purchase decision, so it is the usual choice when conversion is the priority. The home page is a smaller pilot with fewer moving parts, which suits teams that mainly want to prove the Core Web Vitals gain before spending more.

Hours per page type, from our estimate for a mid-size Adobe Commerce store with a custom catalog:

Page typeMain workHours
Home page (pilot, includes the shared layer)Header, footer, mini cart, quick search, add to cart, account sidebar, store switcher, custom content blocks158
Category pageLayered navigation, product listing, recently viewed, recommendations, out-of-stock alerts, plus a custom fitment finder244, of which 86 for the custom finder
Product pageRelated products, compatibility block, media, variations (bundle, configurable, downloadable), reviews, stock alerts, breadcrumbsAbout 290 to 310
Shopping cartCart items and sidebar; the markup is quick to adapt, the JavaScript has to be corrected for Hyvä83
CMS pagesPer page; about 4.5 hours for a repeatable template4 to 5 each

Together that is about 700 to 780 hours for the four page types, depending on how much of the custom finder work your store needs. Backend hours are heavy on the cart because most of the work there is JavaScript, not layout.

How long does a Luma to Hyvä migration take?

For the first page, plan about 11 to 12 weeks end to end in our estimate: 2 months of development, 1 week of QA and 1 to 2 weeks of user acceptance testing (UAT).

StageDevelopmentQAUAT
Home page pilot (with header, footer, mini cart)2 months1 week1 to 2 weeks
Category page2 months1 week1 to 2 weeks, longer when custom search or finder features are involved
Product page and cartScoped per stage from the hours above

The stages are delivered one after another, so migrating the whole storefront takes several months rather than weeks. The upside is that each stage ships on its own and can be checked against the baseline before the next one starts.

Treat these timings as a rough guide only. A store with many custom modules, complex catalog logic or heavy third-party integrations can take noticeably longer, and a simpler store can take less. The only reliable number comes from an estimate based on an audit of your own site.

How much does a Luma to Hyvä migration cost?

The cost has four parts: Hyvä licences, development hours, third-party extensions and CMS pages. The development hours are by far the largest.

Hyvä licences

As listed on the Hyvä Commerce and Hyvä Theme licence pages on 18 November 2026:

ProductPrice
Hyvä Theme (open source)Free, needs a free licence key
Hyvä UI€250 one-time
Hyvä Checkout€1,000 one-time, with one year of support and updates
Hyvä Commerce (Magento Open Source)€3,000 per year, or €15,000 for 5 years
Hyvä Enterprise (Adobe Commerce only)€7,500 for the first year, then €5,000 on renewal, or €27,500 for 5 years

The pages carry no date, and prices have moved before, so confirm them on hyva.io before you budget.

Development

Multiply the hours above by your agency's rate. Your own number moves with the number of custom features, not with the number of products.

Third-party extensions

Layered navigation, product labels, reviews and out-of-stock alerts all need Hyvä-compatible versions, and some are sold as separate licences. The home page pilot needs none, which is one more reason to start there. The category and product stages do.

CMS pages

About 4 to 5 hours per page, or around 4.5 hours for a repeatable template.

What does a page-by-page migration look like in the numbers?

On one of our projects only the product page was moved to Hyvä, and the home and category pages stayed on Luma. Monitoring in DebugBear shows the difference between the two on the same site:

PageThemePerformance score (desktop / mobile)Largest Contentful Paint (desktop / mobile)Page weight (desktop / mobile)
HomeLuma39 / 252.8 s / 12 s6.5 MB / 4.4 MB
CategoryLuma49 / 331.9 s / 6.1 s4.1 MB / 3.6 MB
ProductHyvä90 / 671.2 s / 3.6 s0.3 MB / 0.3 MB

These are different page types, so the table shows what a Hyvä page looks like next to the Luma pages around it, not a controlled before-and-after. The cleaner test is the same product page measured before and after the switch, which is why step 1 of the process is to record a baseline.

On a second project the home and product pages were already on Hyvä, and the category page was moved next, as the second-to-last stage before checkout. The monitoring after that stage:

PagePerformance score (desktop / mobile)Largest Contentful Paint (desktop / mobile)Page weight (desktop / mobile)
Category page 197 / 830.9 s / 1.8 s0.9 MB / 0.9 MB
Category page 298 / 840.8 s / 1.9 s0.8 MB / 0.8 MB

What are the risks of migrating Luma to Hyvä, and how do you roll back?

The main risk is that the pilot page does not improve Core Web Vitals enough. Agree in advance what happens then. There are two realistic options.

Keep the Hyvä page and stop

The store runs two themes side by side. That is still an improvement, but it means two overlapping front ends, and future work can cost more because every change has to account for both. Nobody can promise how later requests or platform changes will interact with that split.

Revert to the previous theme

Decide who pays for the rollback before the project starts.

Three further risks worth budgeting for

Extensions. A module without a Hyvä-compatible version has to be replaced, rebought or rewritten, and the full list often emerges only during the category and product stages.

JavaScript. Luma-era scripts do not carry over. On the cart page, most of the effort is in correcting them, not in the layout.

Regressions. GA4 events, SEO settings and accessibility must be re-tested after each stage, which is why QA and UAT time are in every estimate above.

Frequently asked questions

Can I migrate only one page to Hyvä?

Yes. The product, home or category page can go first. The first page carries the shared header, footer and mini cart, so it costs the most, and later pages mostly add content blocks. Treat the mixed state as temporary and plan the remaining stages.

Is Hyvä free now?

The Hyvä Theme is free and open source, with a free licence key. Hyvä UI, Checkout, Commerce and Enterprise are paid. The licence table in this article lists the prices as they stood on 18 November 2026, so check hyva.io for the current figures.

Will the migration hurt SEO or analytics?

It should not if both are written into the acceptance criteria. We keep the existing GA4 events and SEO settings and re-test them after every stage.

How do I know the migration worked?

Compare Core Web Vitals on the migrated page with the baseline you recorded before starting, in the same monitoring tool and on both desktop and mobile.

Do I need new extensions?

Often yes, for category and product features such as layered navigation, product labels, reviews and out-of-stock alerts. The home page pilot usually needs none.

Sources

  1. Hyvä. Hyvä: Where Good eCommerce Stores Begin
  2. Hyvä. Hyvä Theme: Free, Open Source Magento Frontend
  3. Hyvä. Hyvä Commerce: All-in-One Suite for Magento Open Source
  4. Chromium Blog. The Science Behind Web Vitals
  5. Deloitte. Milliseconds Make Millions