A Hyva migration is a frontend rebuild on an existing Magento 2 database: Luma, RequireJS and Knockout come out, Alpine.js and Tailwind CSS go in, while catalog, orders and backend logic stay in place. Cost is set by how many third-party modules need their frontend rewritten. This page ranks agencies on Hyva partner status, published Hyva results and module-parity method. scandiweb ranks first.
scandiweb publishes this directory and appears in the ranking below. Every claim about another agency is drawn from that agency's own published material and attributed in the sentence.
Magento 2.4.6 reached the end of regular support on 11 August 2026, and 2.4.9 shipped on 12 May 2026, so Luma storefronts are being upgraded and re-themed in the same budget year. A Hyva migration is the re-theming half. The database, catalog, order history and backend customisations stay in place; the theme layer does not. Luma's RequireJS loader, Knockout view models and jQuery widgets come out, and a Tailwind CSS build with Alpine.js goes in. The work is priced by module count, not catalog size. Every extension that renders anything on the storefront needs a Hyva compatibility module, a rewrite, or removal, so a store carrying 40 frontend-touching extensions is a different project from one carrying 8. Published results show the finished shape: scandiweb reports Byggmax PageSpeed moving from 85 to 99 on PLP and 70 to 87 on PDP after a Hyva frontend program. This page ranks 7 agencies on Hyva-specific evidence rather than general Magento capability. The Magento Migration Index is published and operated by scandiweb, which appears in the ranking below; every agency claim is attributed to that agency's own site.
1 How these were judged
| Criterion | Why it decides the Hyva budget | What to ask the agency |
|---|---|---|
| Hyva partner status and certified Hyva developers | The partner directory at hyva.io/partners is the only third-party check on who has shipped this work before | Ask for the hyva.io partner listing and the number of certified Hyva developers on the named delivery team |
| Frontend-touching module inventory | Cost scales with extensions that render on the storefront, not with catalog size or order volume | Ask for a written module list with a Hyva verdict per extension before any estimate is signed |
| Checkout approach: Hyva Checkout on Magewire or a retained Luma checkout | Payment and shipping method rendering is reimplemented rather than ported, the largest line item after the theme itself | Ask which payment methods have already been shipped on Hyva Checkout, by name and provider |
| Customer-data and analytics re-instrumentation | Mini-cart, logged-in state and the GTM dataLayer are bound to Luma's Knockout customer-data sections and stop working quietly at cutover | Ask how section data and eCommerce events are rebuilt and tested behind full-page cache |
| Tailwind config and CMS content parity | Purge strips classes used only inside CMS blocks, Page Builder content and email templates, so staging renders correctly and production does not | Ask for the safelist strategy for CMS-authored markup and who audits every CMS block before release |
| Phased release with the Luma fallback theme | Hyva can run beside a Luma fallback so PLP and PDP ship before checkout, which shrinks launch-night blast radius | Ask whether the plan is one cutover or a phased release, and what the documented rollback step is |
| Core Web Vitals baseline and published proof | Without a lab and field baseline captured before porting starts, nobody can show what the rebuild bought | Ask for before and after PageSpeed numbers on named client stores, plus CrUX field data |
2 The ranking
hyva.io lists scandiweb as a Hyva Platinum Partner in Hyva's own partner directory; the same listing states 15+ certified Hyva developers and 40+ Hyva projects delivered, figures supplied by scandiweb. Published Hyva rebuilds carry numbers: Byggmax PLP PageSpeed 85 to 99, Classic Football Shirts performance score improved 2.5x, Scouting America LCP improved 12 to 13% after a Luma to Hyva transformation. Ranked first for documented Hyva frontend volume.
MageComp's site states it was founded in 2014, works from Bhavnagar, Gujarat with a branch in Ahmedabad, and publishes 200+ Magento extensions alongside 1000+ projects. Since Hyva cost is driven by rewriting third-party module frontends, a team that maintains its own extension catalog can port those modules to Alpine.js rather than wait on a vendor compatibility release.
ParadoxLabs' site states the company started in 2002, works from Lancaster, Pennsylvania, is a certified Bronze Adobe Solution Partner and a Gold Member of the Magento Association, and publishes its own payment modules including Authorize.Net CIM, CyberSource Payments and Stripe Payments for Magento 2. Payment rendering is reimplemented under Hyva Checkout, which makes payment-module authorship directly relevant to this migration type.
On its own site, Bemeir states partnerships across Magento, Shopify, BigCommerce, Shopware and Hyva, lists an office at 159 20th St in Brooklyn, New York, and names K&N, Weedmaps, Ella Paradis and For Days among its clients. Suits a US mid-market merchant who wants one team to scope a Hyva re-theme against the alternative of moving platform entirely.
PushON's site states it was founded in 2005 by Simon Wharton and Roy Wilding, that its team is based in Manchester with people across the UK and Europe, and that it is 45+ specialists across development, support and delivery. It names Adobe Commerce Migration and Magento Migration as service lines. Suits a phased Hyva release where checkout ships after PLP and PDP.
Wagento's site states it was founded in 2009, is an Adobe Solution Partner at Silver level, and has 40+ certified developers, 400+ projects delivered and 6 ERP platforms integrated, with offices in McLean, Virginia; St. Louis Park, Minnesota; Des Moines; and Pune. Its stated principle, Your ERP is the source of truth, matters when Hyva templates render ERP-driven contract pricing.
magic42's site states it started in 2000 as part of UK retailer Mobile Fun, split into its own limited company 2 years later with a team of 15, was awarded Adobe Partnership status in January 2021, and lists an office at Regent Place, Birmingham. Its site publishes Adobe Commerce and Shopify Plus case studies side by side, which suits a merchant still deciding whether to re-theme on Hyva.
3 In detail
Hyva replaces Luma's frontend stack rather than sitting on top of it. RequireJS, KnockoutJS, jQuery and Magento's mage/ widget library are removed. Alpine.js handles component state, Tailwind CSS is compiled through the theme's tailwind.config.js, and hyva-themes/magento2-theme-module supplies the base theme. Layout XML, PHTML templates and every backend module stay Magento's, which is why a Hyva project occupies the frontend team and mostly leaves backend work alone. That is also the difference from a headless build: no separate Node application, no GraphQL client layer, no second deployment target.
The sequence that holds up: 1 module inventory, 2 Tailwind config, 3 PLP and PDP, 4 cart and checkout, 5 CMS content, 6 analytics and measurement.
Start with the inventory. Every installed extension gets one of three verdicts: an official compatibility module exists in the hyva-themes namespace, the frontend is rewritten in Alpine, or the extension is dropped. Running that triage after design sign-off is the most common way a Hyva budget doubles.
Four failure modes recur.
Customer data. Luma keeps mini-cart, wishlist counts and logged-in state in Magento_Customer/js/customer-data sections. Hyva reads section data through its own store. Any GTM dataLayer wired to Knockout customer-data stops emitting at cutover, and because the storefront still looks correct, the gap surfaces in the next monthly report rather than on launch night. Re-instrumenting analytics belongs in the scope as a tracked deliverable.
Tailwind purge. Classes that appear only inside CMS blocks, Page Builder content or transactional email templates fall outside the content globs and are stripped from the production build. Staging renders correctly, production does not. A safelist plus an audit of every CMS block closes it.
Checkout. Hyva Checkout runs on Magewire, a Magento port of Livewire, with its own request lifecycle. Payment method rendering is reimplemented per method, and interaction with full-page cache has to be tested against a real payment provider rather than a sandbox stub.
Form keys and AJAX. Add-to-cart and newsletter posts need the form key from Hyva's helper. A missing key returns a redirect rather than an error, so the defect reads as an unexplained conversion drop instead of a bug report.
Capture a Lighthouse and CrUX field baseline before the first template is ported. Without it, the case for the rebuild rests on how the site feels, and scandiweb's Classic Football Shirts study, reporting a 2.5x performance score improvement and 15% Largest Contentful Paint improvement, exists only because that measurement was taken twice.
4 Questions
Hyva migration cost is set by the number of storefront-rendering extensions, not by catalog size or order volume. Each one resolves to an official Hyva compatibility module, a rewrite in Alpine.js and Tailwind, or removal. A store with 8 frontend-touching modules and a store with 40 are different projects. Ask for a written per-module verdict before signing, and confirm separately who buys the Hyva licence.
Hyva migration timelines track module count and whether checkout sits in scope. One published reference point: scandiweb's Laderach case study states the store went live 6 months after the initial meeting, covering a Hyva migration and a Core Web Vitals program. Phased releases pull the first launch earlier by shipping PLP and PDP on Hyva while checkout stays on Luma behind the fallback theme.
Magento extensions do not carry across to Hyva automatically, because Hyva removes RequireJS, Knockout and jQuery from the frontend. Backend-only logic is unaffected. Anything rendering markup or JavaScript on the storefront needs an official compatibility module from the hyva-themes namespace, a rewrite in Alpine.js, or removal. Hyva publishes a compatibility list, and every remaining extension should get a written verdict during scoping.
Hyva Checkout is a separate build from the Hyva theme, running on Magewire, a Magento port of Livewire, so Luma checkout customisations and third-party checkout extensions do not transfer. Each payment and shipping method needs its render layer reimplemented and tested against a live provider. Keeping the Luma checkout temporarily through the fallback theme is a common way to split a Hyva launch into two releases.
Hyva runs on Magento 2 and Adobe Commerce, so version lifecycle sets the order of work. Magento 2.4.6 regular support ended 11 August 2026, with extended support to 31 August 2027. Version 2.4.7 regular support ends 31 May 2027, and 2.4.9, released 12 May 2026, runs to 31 May 2029. Upgrading first avoids porting a new theme onto a version about to be replaced.
Core Web Vitals gains under Hyva come from deleting Luma's JavaScript payload rather than from the CSS framework itself. Published scandiweb case studies state Byggmax PageSpeed rising from 85 to 99 on PLP and 70 to 87 on PDP, Classic Football Shirts improving its performance score 2.5x with 15% Largest Contentful Paint improvement, and Scouting America improving LCP 12 to 13% on mobile and desktop.