Core Web Vitals you can pass
A Hyvä page ships a fraction of the JavaScript and CSS of the same page on Luma. Lighthouse scores in the 90s are the norm, not the goal. That shows up in Google’s ranking signals and in mobile conversion.
Hyvä migration · Lead Magento 2 developer · Adobe Commerce Expert certified
Luma to Hyvä migration.
Fixed price, one senior developer.
I replace your Luma frontend with Hyvä: the same Magento 2 backend, data and admin, with a storefront that loads in a fraction of the time and costs less to change afterwards. Scoped after a short audit, quoted as a fixed price, delivered weekly on a staging you can click through.
- Adobe Commerce Expert
- 20 years in e-commerce
- Hyvä & headless
- Toptal network since 2019
Why move from Luma to Hyvä
Luma was designed in 2015 around RequireJS, KnockoutJS and jQuery, and every page still carries that weight. Hyvä keeps your Magento and replaces only the storefront, with Tailwind CSS and Alpine.js.
Cheaper every month after
Hyvä’s stack is small and standard. Frontend changes that take days in Luma, with its layers of XML, Knockout templates and RequireJS, take hours. Every feature you add later costs less.
Not a replatform
Products, orders, customers, admin, integrations and extensions stay where they are. Hyvä is a theme migration with a clear boundary, so it can be scoped, fixed-priced and finished.
What the migration includes
The fixed quote covers everything below. Anything outside it is named in the quote before you sign, not discovered during the project.
- Audit of the current store Theme customisations, third-party extensions, custom modules, checkout, page types and the Core Web Vitals baseline. You get a written compatibility report together with the quote.
- Hyvä theme build Your brand in Tailwind: a faithful rebuild of the current design, or a new design from your designer’s files. All standard page types: home, category, product, search, cart, account, CMS.
- Extension compatibility Existing Hyvä compatibility modules where they exist, written by me where they do not, or a recommendation to replace an extension that is not worth carrying over.
- Checkout Hyvä Checkout, or your current checkout kept through Hyvä’s Luma fallback. Payment and shipping methods tested end to end with test transactions.
- Content and Page Builder CMS pages, blocks, widgets and Page Builder content rendered correctly in the new theme, and your marketing team shown how to keep editing it.
- SEO parity URLs, meta data, structured data, hreflang and sitemaps unchanged, verified before go-live, so the migration cannot cost you rankings.
- Performance measured Lighthouse and Core Web Vitals recorded before, on staging and after go-live, on the same pages and devices. Targets agreed in the quote.
- QA, go-live and 30 days of care Cross-browser and device testing, accessibility basics, a go-live checklist, a rollback plan, documentation, and fixes for anything that worked on Luma and does not on Hyvä, free for 30 days.
How the migration runs
-
Audit and compatibility report
I look at your theme, extensions and custom code and measure the current store. You get a written report, a fixed quote per phase and a timeline.
-
Theme and templates
The Hyvä theme is built on a staging copy of your store. From week two you click through real pages with your real products.
-
Extensions, checkout, content
Compatibility modules, checkout, CMS and Page Builder content, then full QA. Every week ships something you can review.
-
Go-live and 30 days of care
Switch at a quiet hour with a rollback ready. I watch Core Web Vitals and errors afterwards and fix what the migration broke, at no extra cost, for 30 days.
What it costs
Starting price below. The exact figure comes after the audit, fixed per phase, and it does not move unless you change the scope.
Fixed price
Luma to Hyvä migration
Audit, theme build, extension compatibility, checkout, content, SEO parity, QA, go-live and 30 days of post-launch fixes.
from €9,000
Get a migration quote →What moves the price
The number of custom page types and layouts, how many extensions have no Hyvä compatibility module yet, a custom or third-party checkout, B2B features such as company accounts and quotes, and several store views with different designs.
What is not included
The Hyvä licence itself, a one-off fee per production domain paid directly to Hyvä, and a Hyvä Checkout licence if you choose it. Both are listed with current prices in the quote. New features that did not exist on Luma are quoted separately.
Questions about Hyvä migrations
How long does a Luma to Hyvä migration take?
Typically 6 to 12 weeks from kick-off to go-live. A store with standard page types and well-supported extensions sits at the lower end; custom B2B flows, many store views or an unusual checkout push it up. The audit gives you the number for your store, and the first pages are on staging within two weeks.
Will my extensions work with Hyvä?
Most popular extensions already have Hyvä compatibility modules, from the vendor or from the Hyvä community. For the rest I write the compatibility module myself, or suggest a replacement when the extension is not worth carrying over. The compatibility report puts every extension in one of these three groups before you commit.
Do we need Hyvä Checkout?
No. Hyvä can keep your existing checkout, including most third-party one-step checkouts, through its Luma checkout fallback. Hyvä Checkout is faster and easier to customise, and I recommend it when checkout speed is part of your goal, but it is a separate licence and a separate decision.
What does Hyvä itself cost?
Hyvä is a commercially licensed theme: a one-off licence per production domain, paid directly to Hyvä, which also gives you access to their support channels and compatibility modules. It is not included in my price. The quote lists the current licence price, so there are no surprises.
Tell me about your Luma store
Send your store URL and a few lines about what you expect from Hyvä. I reply within one business day with next steps, or a straight answer if the migration is not the right move for you yet.