Luma to Hyvä migration for Magento and Adobe Commerce.
The fastest storefront Magento has ever had, without a replatform, and with the shop open throughout.
We replace the Luma frontend of a Magento Open Source, Adobe Commerce or Mage-OS store with Hyvä, keeping the backend, catalogue, customers, orders, integrations and URLs where they are. Hyvä is the best thing to happen to Magento storefronts: faster for shoppers, simpler to build on and cheaper to change. From a Hyvä Silver Partner working with it since 2020.
Before and after: what the browser has to doillustration
LumaHyvä
JavaScript loaded before the page can be used
Requests to first render
CSS shipped
Time until the page responds to a tap
Same Magento, same URLs, same adminbars are illustrative
Same Magento, same URLs, same admin
For
Magento stores on Luma that are slow on a phone and costly to change
What it is
A new Hyvä frontend on the same Magento, catalogue, admin and URLs
Price
A written estimate once we have examined the store; the Hyvä Theme is free
First step
The free health check tells you whether you use Luma or Hyvä
Is your Luma store doing this?
What merchants say before they move to Hyvä.
“
Most of our traffic is on phones, and the store feels slow on every one of them.
What it usually means
Luma loads hundreds of script and style files before a page can be used. Hyvä loads a handful, which is where the speed comes from.
“
A small change to a product page takes our developers days.
What it usually means
Luma's parts are tangled together, so a small change disturbs a lot. Hyvä's Tailwind and Alpine.js components are simple and independent, so changes cost less.
“
We were told the only way to get a fast store is to leave Magento.
What it usually means
Not if the backend is doing its job. Hyvä changes the storefront and leaves the platform, admin and integrations alone.
Luma against Hyvä, point by point.
Luma was designed in 2015, before phones were most of the traffic. Hyvä was designed in 2020 to replace it, and it shows on every measure that matters to a shopper or a merchant.
MeasureLuma
Built on RequireJS, Knockout.js, jQuery and LESS, a stack from 2015 Alpine.js and Tailwind CSS, a modern and tiny stack
Before a page can be used Hundreds of script and style files to download and execute A handful of small files
On a phone Slow to appear and slow to respond to a tap Appears quickly and responds at once
Core Web Vitals A constant struggle, even after expensive optimisation Passing is the normal result of a well-built theme
Cost of a change High: parts are tangled, so small changes take days Low: simple, independent components
Developers Fewer each year want to work on it The stack most Magento developers now choose
Checkout Magento's heavy default checkout Hyvä Checkout: fewer steps, far less code
Where it is heading Maintained by Adobe, no longer developed Updated continuously, free and open source
35%
of Magento stores pass Google's Core Web Vitals on a phone. Most of them still use Luma.
Six parts, each in the written plan, each done by the engineers who will deploy it.
01
An audit of the frontend you have
Every module, custom Luma change and template listed with what will happen to it. The estimate is built on it.
02
Design carried over or redrawn
Your design rebuilt faithfully as Hyvä components, or a new design if this is the moment.
03
Extension compatibility, settled
Compatibility modules fitted, written by us where none exist, or a replacement recommended.
04
A checkout decision
Keep Magento's checkout through Hyvä's compatibility layer for now, or fit Hyvä Checkout together.
05
Search standing protected
URLs unchanged; titles, structured data and canonicals checked page type by page type.
06
A deployment that does not close the shop
Built on staging, switched at a quiet hour, with Luma kept ready to switch back to.
The same store, with and without us.
Without us
A Luma store that waits on JavaScript on every phone
Each change slowed by RequireJS and Knockout.js
A replatform proposed to fix a frontend problem
Extension frontends discovered broken after launch
Rankings risked by a launch nobody checked
A launch weekend with the shop closed
With Refined Commerce
A Hyvä frontend built on Tailwind CSS and Alpine.js
The same Magento, admin, catalogue and URLs
Every module accounted for before you commit
Compatibility modules fitted or written by us
SEO parity checked page type by page type before the deployment
A theme switch at a quiet hour, with Luma ready to switch back
How we carry out a migration.
Planned in writing, built where you can see it, and switched at a quiet hour.
1
Step 1: The free health check
Send us the store address. A senior engineer reads its release, support status, PHP, headers, hosting and any sign of a hijack.
Within two working days
Access we need
None. Publicly served pages only; nothing is tested.
What you receive
One page by email, with no obligation.
2
Step 2: We read the store and write the plan
Release, PHP, extensions, custom code, templates and traffic shape.
First findings within two working days
Access we need
Read access to the repository, an admin account and the server.
What you receive
What happens to every module, the design approach and an estimate, in writing.
3
Step 3: Design: keep, refresh or redraw
Agreed page by page before any component is built. A redesign is signed off as designs first.
Before the build starts
What you receive
Signed-off page designs, or a confirmed rebuild of the current design.
4
Step 4: Build and test on staging
Theme, components and compatibility modules built on a copy of your store with your real catalogue, then checkout, payment, search, every device size, accessibility and SEO parity tested.
Most of the project
Access we need
A staging copy of the store.
What you receive
A staging address to review, and written progress updates.
5
Step 5: Deploy at a quiet hour, Luma kept ready
The theme switched live with a tested way back. Errors, Core Web Vitals and Search Console monitored in the days after.
A quiet hour agreed with you
Access we need
Deployment access to the live store.
What you receive
A written note of what changed, and the first field data once it arrives.
What changes, and what stays exactly as it is.
A Hyvä migration touches one layer of the store. Knowing which layer is most of the reassurance merchants need.
Priced as a project: a written estimate once we have examined the store.
How you pay
Usually spread across the length of the project.
Our rate
£80 an hour plus VAT, the same for every merchant.
Never charged
Account management, or the first look at your store.
Priced as a project; the Hyvä Theme itself is free.
Hyvä made its theme free and open source in November 2025, so what you pay for is the work: the number of templates, custom Luma changes and third-party modules decide it. We examine the store first and then give you a written plan and estimate. Hyvä Checkout and Hyvä Commerce are optional paid products from Hyvä, shown separately where you want them.
Every module accounted for before you commit
Shop open throughout; Luma kept ready to switch back to
Payment usually spread across the project
What happens first
1We confirm the store uses Luma and read its theme structure and overrides.
2Each frontend module is checked against Hyvä's compatibility library.
3You get a written note of the modules that need work, before the full plan.
Design and Hyvä build for a British dance-shoe maker selling worldwide: the main content loads in 1.3 seconds on a phone for real customers.
Passes Core Web Vitals on mobile
LCP1.3 s
INP112 ms
CLS0.01
Core Web Vitals, real-user data (Chrome UX Report), mobile, 28 days to 31st October 2026. Marks show Google's thresholds.
Read the case study
After having a number of bad experiences with 3rd party developers for Magento we decided to go with Rowan for our last site redesign and upgrade. This has turned out to be a very good decision as Rowan has proven to be prompt, professional, efficient and very good at what he does! …
We adopted Hyvä when it launched and have built on it ever since. It is now the only frontend we build new Magento stores on.
Silver
Hyvä Silver Partner
Recognised by Hyvä for the stores we have delivered, with direct access to Hyvä's own team when a project needs it.
1.1s
Fast for real customers, not only in a test
The main content of a Hyvä store on our case pages loads in 1.1 seconds on a phone, measured by Google on real visits.
Questions merchants ask about this.
Is a Luma to Hyvä migration a replatform?
No. Hyvä replaces the frontend layer of Magento and nothing else. Your release, admin, catalogue, customer accounts, order history, integrations, hosting and URLs stay where they are, and your team logs into the same admin the day after the deployment. That is the point of Hyvä: a fast storefront without the cost and risk of moving platform.
Will our extensions work with Hyvä?
The backend parts of every extension keep working, because the backend does not change. Frontend parts need a Hyvä compatibility module: many vendors ship one, Hyvä maintains a library for common modules, and where neither exists we write one or recommend a replacement. Every module is listed in the plan before we estimate.
Will we lose search rankings?
The URLs do not change, so there is nothing to redirect. We check titles, meta descriptions, headings, structured data and canonicals on the Hyvä pages against the Luma pages before the deployment, and monitor Search Console afterwards. A faster store usually helps rankings rather than harming them.
Will the store pass Core Web Vitals afterwards?
Hyvä gives a store by far its best chance. Only 35% of Magento stores pass Core Web Vitals on mobile, according to the HTTP Archive Web Almanac, and most of those stores still use Luma; four Hyvä stores on our case pages load their main content in 1.1 to 1.5 seconds on real phones. Google measures the result from real visits, so we measure yours before and after and show you both. Hosting, images and third-party scripts matter too, and the plan covers them.
Can we keep our current design?
Yes. The Luma design is rebuilt in Hyvä component by component, usually with small improvements a rebuild makes cheap. Or you can redesign. A straight rebuild is the smaller job.
How long does it take?
A store with a standard design and a handful of well-maintained extensions can be moved in a few weeks; one with years of custom Luma work and thirty modules takes longer. The written plan gives you dates before you commit, and the shop stays open throughout.
What does a Luma to Hyvä migration cost?
The Hyvä Theme itself is free and open source, so the cost is the work: the number of templates, custom Luma changes and third-party modules decide it. We examine the store and give you a written plan and estimate before anything starts, with payment usually spread across the project.
Is Hyvä free?
The Hyvä Theme is. Hyvä made it free and open source in November 2025. Hyvä Checkout, Hyvä Commerce, Hyvä UI and Hyvä Enterprise are optional paid products, licensed from Hyvä.
Is Luma still supported by Adobe?
Luma still ships with Magento and receives security fixes, but it is built on RequireJS, Knockout.js and jQuery, a stack from 2015 that Adobe no longer develops in any meaningful way. Most new Magento storefronts are now built on Hyvä, and most extension vendors support it.
Does Hyvä work with Adobe Commerce and B2B?
Yes. Hyvä works on Magento Open Source, Adobe Commerce and Mage-OS. Adobe Commerce features such as B2B company accounts, shared catalogues and staging are supported through Hyvä Enterprise.
Find out whether your store uses Luma or Hyvä, and what else the public pages say.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
Magento Open Source, Adobe Commerce and Mage-OS stores
No login, no access, no obligation
Written by a person, not a scanner
Free store health checkOne page, by email
What you receive
Example reportMagento Security and Upgrade Health Check
example-store.co.ukNeeds attention
Platform
Magento Open Source 2.4.4-p3
Adobe support
ended 12th April 2025
PHP
8.1, end of life 31st Dec 2025
Frontend
Luma
Security headers
2 of 6 present
Hijack indicators
none found
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.