When the switch pays off
Many shops still run on the classic Luma theme and wonder whether a switch pays off. This guide shows what you gain, where the limits lie, how extension compatibility decides and how to move from Luma to Hyvä without risking revenue.
Table of contents
- 1. Starting point: why shops move from Luma to Hyvä
- 2. What you gain when you move from Luma to Hyvä
- 3. The limits: when the switch does not make sense
- 4. Compatibility: the key to the decision
- 5. Process: how to proceed when you move from Luma to Hyvä
- 6. Checklist: seven points before you move from Luma to Hyvä
- 7. Common misconceptions when you move from Luma to Hyvä
- 8. How we accompany the switch from Luma to Hyvä
- 9. Summary
- 10. FAQ
1. Starting point: why shops move from Luma to Hyvä
Luma is the standard theme that comes with Magento 2. It is widespread but technically heavy: it loads a lot of JavaScript and rests on older techniques that make the frontend heavy and slow. Hyvä is an alternative theme that relies on Tailwind CSS and Alpine.js and gets by with much less code.
The most common reason to move from Luma to Hyvä is speed. Leaner pages load faster, especially on mobile devices, and that affects usability, abandonment and visibility. The second reason is maintainability: a lean frontend is easier to adjust and develop further.
Whether the switch pays off for you depends on your shop. This guide helps with the decision. An overview of the theme is also on the page about Hyvä.
2. What you gain when you move from Luma to Hyvä
The advantages of a switch can be divided into four areas. The table shows them compared with the classic setup.
| Area | Luma | Hyvä |
|---|---|---|
| Load time | Lots of JavaScript, heavy build | Far fewer scripts, lean build |
| Customization | Complex structure, adjustments laborious | Simpler system with Tailwind CSS and Alpine.js |
| Maintenance | Many dependencies, updates demanding | Fewer dependencies, easier to oversee |
| Mobile use | Often sluggish on mobile devices | Designed for fast mobile use |
| Extensions | Standard modules work directly | Modules need Hyvä compatibility |
The last row is the most important point when you want to move from Luma to Hyvä: extensions built for Luma do not simply run in Hyvä. There are compatibility modules for many common extensions, while for others the frontend has to be rebuilt.
3. The limits: when the switch does not make sense
Not every shop benefits equally. If your shop uses many extensions with their own interface that have no Hyvä compatibility, the effort grows. This applies especially to heavily customized page areas, configurators and checkout extensions.
With a very small budget or a short remaining life of the shop, the switch may not pay off either. Whoever intends to replace the shop in a year anyway saves the investment. And if the shop is fast today but runs an old Magento without security updates, the version update takes priority first. See the guide Magento upgrade costs.
Honestly, there is no standard case. Whoever asks whether to go from Luma to Hyvä should check the extensions first and only then decide.
4. Compatibility: the key to the decision
Before you move from Luma to Hyvä, list all extensions that produce visible interfaces. These include sliders, filters, product configurators, reviews, payment and shipping selection, wish lists and cookie notices. For each extension three questions arise: is there a Hyvä compatibility from the vendor or from the community? Is a small adjustment enough? Or is a replacement needed?
Extensions without an interface, such as integrations in the background or reports in the admin, are usually uncritical because Hyvä changes only the frontend. The result is a list with three groups: uncritical, to adjust, to replace. This list determines effort and cost.
More on costs is in the guide Hyvä costs. The switch is a frontend project, not a rebuild of the entire shop. Data, orders and configuration are preserved.
Also ask about the price of Hyvä compatibility for extensions. Some vendors deliver it free of charge, others charge a fee, and for some modules there are community solutions. These items belong in the calculation so that no surprise arises at the end.
5. Process: how to proceed when you move from Luma to Hyvä
A switch runs in five steps. First the analysis with the list of extensions and their Hyvä status. Then the concept: keep the design or redesign, which functions must stay, which can be dropped.
In the third step the theme is built on a test environment and filled with your content. In the fourth step testing follows: categories, product pages, cart, checkout, customer account, emails and mobile view. The fifth step is go-live with backup and fallback plan, followed by short aftercare.
During the changeover the live shop stays unchanged. Only when the test environment is approved does the theme switch. The time until go-live depends on scope; the analysis gives guidance.
The biggest risk of the switch lies in checkout and payment methods. An error there costs revenue directly. Limit it by testing the checkout thoroughly on a test environment and carrying out the changeover at a time of low traffic.
Check payment methods and legal texts after the switch
After a theme change, mandatory information, legal texts, cookie notice and payment methods must still be displayed correctly. Check these points before go-live. Take advice on legal questions in individual cases.
The second risk is unclear scope. If it is not defined which functions are carried over, the project grows gradually. Define the scope in writing and introduce change requests through a clear procedure.
6. Checklist: seven points before you move from Luma to Hyvä
Seven points before the switch
- ✓List all extensions with a visible interface.
- ✓Check for each: Hyvä compatibility available, to adjust or to replace.
- ✓Check whether payment and checkout extensions run with Hyvä.
- ✓Decide whether the design is kept or redesigned.
- ✓Provide a test system with current data.
- ✓Record the most important flows as a test list.
- ✓Agree a backup and a fallback plan for go-live.
With this list you avoid nasty surprises in checkout, the most sensitive spot of the shop. Plan especially much testing time there.
7. Common misconceptions when you move from Luma to Hyvä
The first misconception: Hyvä makes every shop fast automatically. The theme removes one big cause but does not replace clean infrastructure. More on the other causes in the guide Magento shop too slow. The second misconception: the switch is a rebuild. Data and configuration stay, only the frontend is rebuilt.
The third misconception: all extensions keep working. That is true only for modules without an interface. Whoever wants to move from Luma to Hyvä should therefore check the list of extensions first and not the look.
8. How we accompany the switch from Luma to Hyvä
We are a web agency in which fixed freelancers work together, all remotely from home offices. If you want to move from Luma to Hyvä, we start with an analysis of your extensions and then state scope and effort in writing. The hourly rate is 30 euros net, see the pricing page.
After go-live we take over maintenance if you wish. This article is general orientation and not legal advice. For a first assessment please use our contact page.
9. Summary
Moving from Luma to Hyvä pays off above all when you want a faster, maintainable frontend. What decides is the compatibility of extensions with a visible interface.
Luma to Hyvä, the key points at a glance
Gain
Faster, leaner frontend, easier adjustment and maintenance
Limit
Many extensions without Hyvä compatibility raise the effort
Key
List of extensions: uncritical, to adjust, to replace
Safeguards
Test environment, checkout tests, backup and fallback plan
Note: This article offers general information and does not replace legal advice in individual cases.