How much does a Hyvä migration cost in 2026? The real numbers
TL;DR
A Hyvä migration costs £12,000–£35,000 for a typical Magento Luma store. Hyvä Commerce implementations (including Hyvä Checkout) sit in the £35,000–£90,000 range. The biggest cost driver is your paid extension count, not catalogue size.
We quote fixed price, fixed timeline after a 30-minute scoping call. Read on if you want to understand what the line items actually are, where merchants typically get blindsided, and how to cut cost without cutting corners.
What you're actually paying for
A Hyvä migration is a frontend rebuild. The Magento backend (admin, products, orders, customers, integrations) doesn't move. The work splits roughly like this:
| Phase | Share of budget | What it covers |
|---|---|---|
| Theme install + brand system | 10–15% | Hyvä theme package, Tailwind config matching your brand tokens, base typography + colour system |
| Page templates | 25–35% | PDP, PLP, search, cart, customer account, CMS blocks |
| Extension compatibility | 20–35% | One Hyvä-compat module per paid extension that doesn't ship its own |
| Performance tuning | 10–15% | Lighthouse mobile 90+ as exit criteria — usually LCP + JS-budget work |
| QA + UAT | 10% | Real orders end-to-end on staging, cross-browser, accessibility pass |
| Cutover + post-launch | 5% | Off-peak DNS flip, 72-hour monitoring, bug-fix sprint |
Notice that extension compatibility is the single biggest variable. Stores with 5–10 paid extensions can land at £12k–£18k. Stores with 25+ extensions, especially older or heavily customised ones, push into the £25k–£35k bracket on theme alone.
What drives the price up
In order of impact:
Paid extension count. Each extension without vendor-supplied Hyvä compat is £1,500–£8,000 of work depending on complexity. Display-only extensions (banners, badges, content blocks) sit at the low end. Checkout-touching extensions (payment, fraud, shipping rate calc) sit at the high end because they need integration testing across real orders.
Design fidelity. A migration that matches your existing Luma design 1:1 is cheaper than a migration that includes a brand refresh. If you're already redesigning, do it inside the Hyvä build — adding it later doubles the work.
B2B + Adobe Commerce features. Company accounts, shared catalogues, customer-specific pricing, negotiated quotes, requisition lists. Each of these is a separate Hyvä template surface. B2B Hyvä on Adobe Commerce typically adds 2–4 weeks vs an equivalent B2C build.
Customer-account section complexity. Out-of-the-box Magento customer account is several pages. If you've added subscriptions, gift cards, store credit, returns, wishlists, multi-address shipping, every one of those needs its own Hyvä template.
Custom checkout flow. Magento's default checkout already isn't fast on Luma. If you've customised it heavily — split checkout, B2B approvals, custom fields per shipping country — that's not migration work, that's a Hyvä Checkout build.
What drives the price down
- Vendor-supplied Hyvä compat modules. Check compat.hyva.io before the scoping call. Every extension on that list saves you £1.5k–£8k.
- Standardised Magento install. If you haven't customised the base Magento templates beyond the theme layer, the migration is mechanical. Heavy customisations to
app/code/local/*or core overrides add days. - Phased rollout. Phase 1 ship Hyvä Theme (storefront only). Phase 2 add Hyvä Checkout once theme is bedded in. Spreads the budget over two quarters and de-risks the cutover.
- Realistic design rebuild scope. If you accept the current design rebuilt-faithfully under Hyvä, you save 2–4 weeks of design + dev. Save the rebrand for next year.
Hyvä Commerce changes the maths
Hyvä Commerce bundles Hyvä Theme + Hyvä Checkout + Hyvä Admin + Hyvä Insights. Implementations sit at £35k–£90k, with the bigger range driven by:
- Hyvä Checkout integration complexity — every payment gateway, fraud-detection module, and shipping calculator needs re-templating
- Customer-account rebuild (Hyvä re-skins the whole account section, not just the storefront)
- Optional Hyvä Admin + Insights rollout
Don't pay for Hyvä Commerce if Hyvä Theme alone solves your problem. The single biggest win is the one-page Hyvä Checkout — which consistently lifts mobile completion rate by 8–15%. If your checkout conversion isn't your current bottleneck, the Theme-only spend is better.
Where merchants get blindsided
In rough order of "I see this every quarter":
"All our extensions are Hyvä-compatible already." Reality: check the version. Vendors ship Hyvä compat for current major versions only. If you're on an older extension version, you either upgrade the extension (often paid) or pay for a custom compat module.
"Migration is cheaper than a redesign, so let's just lift-and-shift." Reality: lifting Luma design directly into Hyvä gives you a faster site with the same UX problems you already had. Budget some design-system thinking even if it's not a full rebrand.
"We'll handle the checkout work in phase 2." Reality: if Hyvä Theme without Hyvä Checkout means your checkout page is still a Knockout island while the rest is Tailwind, the visual jarring + perf cliff at checkout costs conversion. Either do them together or commit to a Phase 2 date.
"Our hosting can handle it." Reality: Hyvä reduces frontend load dramatically, but if your Magento backend is undersized for product imports or order spikes, that doesn't change. Performance bottlenecks shift; they don't disappear.
"SEO will be fine as long as URLs don't change." Reality: URL preservation is the floor, not the ceiling. Structured data (Product, Offer, Breadcrumb, FAQPage), internal linking patterns, and Core Web Vitals all matter. A good Hyvä migration improves SEO; a sloppy one keeps it flat or hurts it.
The honest case for staying on Luma
Three scenarios where the migration doesn't pay back:
- Replatforming off Magento within 12 months. Don't pay for a Luma → Hyvä migration if Shopify Plus or BigCommerce is on the roadmap.
- Heavily customised Luma on low-traffic stores. If you've sunk £100k into bespoke Luma frontend and your monthly conversion lift from Hyvä would be 200 orders, the maths doesn't work.
- Magento version Hyvä doesn't support yet. Combining a Magento major upgrade with a Hyvä migration is high-risk. Sequence them: upgrade first, migrate second.
Otherwise, Hyvä is almost always the right call by 2026. The Core Web Vitals weighting compounds and the Luma frontend is the single biggest drag on Magento mobile performance.
What we charge, in plain numbers
For reference, this is the eTechFlow price band as of 2026:
- Small Luma store, 5–10 extensions, faithful design rebuild: £12,000–£18,000, 6–8 weeks.
- Medium B2C, 15–25 extensions, brand refresh, schema markup carry-over: £18,000–£35,000, 8–10 weeks.
- Hyvä Commerce (Theme + Checkout): £35,000–£60,000, 10–14 weeks.
- Hyvä Commerce + Admin + Insights, full suite: £60,000–£90,000, 12–16 weeks.
- Custom Hyvä-compat module per extension (not bundled): £1,500–£8,000 depending on complexity.
These are fixed-price quotes against your scope, not day rates. You get the number within 48 hours of a 30-minute scoping call. If it's wrong for your budget, you walk away with a useful scope doc + the full extension list — no fee.
Next steps
- See the full Hyvä migration service page for the timeline + deliverables
- Compare Hyvä vs Luma if you're still deciding whether to migrate
- Browse the Hyvä Theme glossary for the technical primer
- Book a scoping call to get a fixed-price quote against your specific extension list