The Frontend RecordMagento and Adobe Commerce front end migrations, scored on what each agency publishes Updated 23 September 2026

Hyvä migration agencies in 2026: moving a Magento store off Luma

Nine agencies are scored here out of 100. scandiweb ranks first on 78, because it holds the top Hyvä register tier alongside the highest published count of certified Hyvä developers on this page and the only named Adobe partner level in the set. Vendic and ParadoxLabs both score 75, and both publish better attributed evidence of a Luma to Hyvä migration than scandiweb does. elgentos scores 70. This lane behaves differently from most agency comparisons and the difference decides how it is scored: all eight agencies beside scandiweb publish measured performance for a named Hyvä build, so publishing a number separates nobody here. What separates them is finer. Seven of the eight name Luma as the theme the store moved off, and six publish the source theme and the figures together, which is what lets a number be attributed to the migration rather than to everything else that happened that quarter. ParadoxLabs names the measurement tool and the date on every figure it publishes, and ZERO-1 cites Chrome UX Report field data over a 28 day period in June 2026. Three agencies qualify their own numbers instead of leaving them to be read as generously as possible: Foundation Commerce states that its Todd Doors gains came from a hosting migration, elgentos publishes a null result on the one metric Hyvä did not move, and Emico writes that Hyvä was one of several causes. This page rewards that rather than penalising it. One check matters more than any of them and is easy to get wrong: Hyvä runs two directories. The page most buyers land on is Preferred Partners, a curated shortlist carrying only the top three tiers. The full agency register sits at a separate URL and publishes 460 listings across five tiers, 17 Platinum, 46 Gold, 102 Silver, 264 Bronze and 31 Partner. Every tier on this page is read from the full register.

1 The shortlist

Every agency on this page, in order

1
scandiweb Buyers who screen on register tier, certified developer counts and an Adobe level before anything technical is discussed 78 of 100.
2
Vendic Buyers who want a documented Luma to Hyvä speed jump, a published hourly rate and the tightest support response in the set 75 of 100.
3
ParadoxLabs Buyers who want every figure dated and sourced, a published rate card and a straight answer on when Hyvä is the wrong call 75 of 100.
4
elgentos Buyers who want the migration quoted in hours before anything is signed, and an agency that publishes what Hyvä did not fix 70 of 100.
5
ZERO-1 Buyers who want field data rather than lab scores, and a fixed price for the smallest possible first step 57 of 100.
6
Foundation Commerce Buyers who want the Luma problem diagnosed in writing, and a support contract priced before the first call 56 of 100.
7
Emico Buyers who care most about live field performance across several stores, and will ask about the migration separately 45 of 100.
8
Fluid Commerce Buyers who want the migration shown page by page and device by device in a single Lighthouse table 43 of 100.
9
JaJuMa Buyers who want the agency that writes Hyvä code, and will accept a timeline and a price being withheld until the call 37 of 100.

Nine agencies that move Magento and Adobe Commerce stores from the Luma theme to Hyvä, each scored out of 100 against the weighting in the next section. Read the scores for what they measure. This page scores what an agency publishes about its Hyvä migration work, not the quality of that work, so a low score means thin public disclosure rather than weak delivery. The top of the table is unusually tight and the reason is worth knowing before you read any of it: every agency here publishes measured performance for a named Hyvä build, which was not true of any other front end lane examined this year. Publishing a number is table stakes in this lane, so it cannot carry the weight it carries elsewhere, and the criteria are pitched at the finer distinctions instead. First place is three points clear, and the two agencies immediately below it both publish better attributed evidence of the migration itself than first place does. Every fact about an agency other than scandiweb was read from that agency's own website on 23 September 2026 and is attributed in the sentence, apart from Hyvä partner tiers and Hyvä's own documentation, which are read from Hyvä and named where they are used.

2 How these were judged

What separates a Hyvä migration practice from a Hyvä service page

CriterionWhat a pass looks likeWhat a fail looks likeWeight
Hyvä register position and published certified Hyvä developers24 for a Platinum listing in Hyvä's full agency register together with a published count of certified Hyvä developers in double figures. 20 for a Platinum listing with a published count. 16 for a Platinum listing with no count published. 13 for a Gold listing with a published count. 10 for a Gold listing with no count published. 6 for Silver, Bronze or Partner in the register. Hyvä certification is a proctored exam sat through Webassessor from 200 euro excluding VAT, so a published count is checkable rather than decorative.Not listed in the full register at all. A tier is read from the full register and never from the curated Preferred Partners page, which omits the two lowest tiers, and never from the agency's own claim. Only Hyvä certifications count here; Adobe and Magento certification counts are scored under delivery scale instead, so nothing is counted twice24
Performance evidence that belongs to the migration22 for figures published for a named client whose case names Luma as the source theme, with the measurement tool named and the date or window it was measured over stated. 18 for the same with the tool named and no measurement date. 15 for absolute before and after metric values on a named Luma case with no measurement tool named. 12 for a named Luma case publishing a relative improvement with no absolute metric value behind it. 10 for measured figures on a named Hyvä build where no case names the source theme. 5 where the only full metric set published for a named client is one the agency's own page attributes to a cause other than the theme migration.No measured figure attached to a named build, or a page whose headline promises measured gains and publishes none. A figure that cannot be tied to the theme swap is not evidence of the theme swap, however good the number is22
Delivery scale, Adobe partner tier and published certification counts18 for a published team size, a published certification count and an Adobe partner level named in current Adobe wording, all three. 13 for two of the three. 9 for one of the three alongside a published project, client or install count. 6 for one of the three on its own. 3 for Adobe Solution Partner status published with no level attached, or a named team roster with no headcount stated.Neither a team size, nor a certification count, nor any Adobe partner status published anywhere. Adobe's own directory earns nothing here, because the other eight agencies were not looked up in it and a test only one party sits for is not a test18
What the migration costs and breaks, published before the call16 for a figure a buyer can budget against, whether an hours range, a migration price or a full rate card, together with a specific account of what a Hyvä front end breaks that names the module classes or the JavaScript libraries involved. 12 for one of the two in specific terms and the other in general terms. 9 for a timeline and a general compatibility statement with no hours, price or rate card. 6 for an account of what breaks, or a timeline, or a price, but not two of the three.Neither cost nor breakage published on any reachable page. A compatibility promise with no named library, module class or hours behind it is marketing rather than scope16
Support terms published before you sign12 for a stated first response or patch turnaround time, with cover hours and a price. 9 for a stated response or patch turnaround time with cover hours and no price. 7 for a stated response or patch turnaround time alone. 5 for cover hours and a price with no response commitment. 3 for retainer pricing alone, or cover hours alone.Support sold with no number attached on any reachable page, including a support page that describes a process without committing to a time12
Honest causation, or what the agency says its own numbers do not prove8 for publishing a result that works against its own sales case, such as a metric Hyvä did not move, or a statement that a headline gain came from something other than the theme. 6 for naming the other causes alongside Hyvä where a gain was joint, publishing the full scope of work behind the figures, or publishing the conditions under which it says Hyvä is the wrong choice. 3 for a caveat that narrows what its figures prove, such as separating two builds or stating that a Hyvä build can still be built badly.Figures published with no qualification anywhere, or a page whose headline promises measured gains it does not publish. This criterion exists because three agencies here qualify their own numbers and are more trustworthy for it, and a scoring model that ignores that rewards the loudest page over the most careful one8

3 The ranking

Luma to Hyvä migration agencies in 2026

1

scandiweb

Buyers who screen on register tier, certified developer counts and an Adobe level before anything technical is discussed78 of 100

Hyvä's full agency register lists scandiweb five times, every one at Platinum, the top of five tiers and one of 17 listings there. The entry Hyvä publishes for it reads that scandiweb is a Hyvä Platinum Partner and one of the most experienced Hyvä agencies, with 15+ certified Hyvä developers and 40+ Hyvä projects delivered. That count is the scarcest credential in this comparison. Only two of the eight agencies below publish one at all, at four and at three, and Hyvä certification is a proctored exam sat through Webassessor from 200 euro excluding VAT, so the number is checkable rather than decorative. Its own Hyvä theme development page carries the Platinum tier and states that Satoshi for Hyvä is the first original theme built on top of the Hyvä frontend, which nobody else here claims for a theme of their own.

Performance evidence is where this page is hardest on everybody, and first place gives away more here than anywhere else. One scandiweb case names the theme the store moved off. Scouting America describes a migration from its old Luma based platform to a storefront built with Hyvä, calls the legacy Luma setup unoptimised for performance on mobile, and publishes Largest Contentful Paint improved by 12 to 13% on mobile and desktop alongside mobile revenue up 6.2% year on year, average order value up 27.3% and checkout starts up 23.9%. That is a relative improvement rather than an absolute before and after value, with no measurement tool named and no measurement date, which places it on the same rung as Foundation Commerce in sixth and takes 12 of 22. Six agencies below publish better attributed evidence of a Luma migration than this.

The larger body of figures is unattributed to any source theme, and there is a lot of it. The Hyvä case study roundup names Läderach, Airthings, JYSK, Byggmax and Nicokick, reporting Byggmax product listing pages improved from 85 to 99 and product pages from 70 to 87, and Nicokick's homepage PageSpeed score reaching 96 with 73% of all pages at or under 2.5 seconds for Largest Contentful Paint. The Läderach write-up adds 93 PageSpeed for the homepage and product page on desktop, 99 for the listing page, and Largest Contentful Paint of 1.8 seconds on desktop and 1.9 on mobile. Those are better numbers than most of this page carries and none of those cases says what the store was running before, so a reader cannot attribute them to a theme migration. This ranking scores attribution, not volume.

On causation it publishes the scope rather than the caveat, which earns the middle rung and not the top one. The Classic Football Shirts case study reports a PageSpeed performance score improved by 2.5 times with movement on First Input Delay, Interaction to Next Paint and Largest Contentful Paint, and introduces those results with the words after the Magento version upgrade and migration to Hyvä, listing an upgrade from Magento 2.4.0 to 2.4.4-p2 in the same scope. Scouting America does the same thing, publishing that the previous infrastructure was self hosted and the new storefront runs on ReadyMage, so the hosting changed too. A reader can therefore see the theme was not the only variable. The top mark on that criterion goes to an agency that published a metric Hyvä failed to move at all.

Cost and breakage is the second concession, and it is a clear one. The FAQ on the Hyvä page and on the Adobe Commerce and Magento 2 migration side of the practice answers the cost question with the statement that implementation cost varies depending on the store's specific requirements and desired customizations, the timeline question with a standard implementation in a few weeks, and compatibility with the statement that Hyvä themes are designed to be compatible with most Magento extensions. Satoshi carries a stated 6 to 8 weeks to market and the working with Hyvä guide sets out the build approach. None of that is an hours range, a rate card or a list of what a merchant has to re-implement, and three agencies below publish exactly those. This line scores 9 of 16.

What is unmatched here is the credential sheet and the delivery volume behind it. The Adobe Commerce development page names Adobe Commerce Gold Solution Partner, and Adobe's own Solution Partner Directory carries the same Gold listing, which corroborates the claim and earns nothing on this page because the other eight were not looked up in the directory. Behind it sit 894+ Adobe certifications, 600+ people working across 36 countries, 700+ clients, 2,100+ eCommerce projects, 23+ years of this work and a 95 NPS. Exactly one other agency here names an Adobe level at all. On support it states a first response within 24 hours, issues triaged by severity with showstoppers taken first, monitoring around the clock, 450+ active support clients and 9,000+ tickets handled, billed pay as you go with no fixed monthly fee and no published rate. Vendic in second place commits to a response within 60 minutes between 07:00 and 23:00 seven days a week, and ParadoxLabs in third publishes a patch turnaround, an emergency response time, cover hours and a full price list. Both take more on that line than this entry does.

2

Vendic

Buyers who want a documented Luma to Hyvä speed jump, a published hourly rate and the tightest support response in the set75 of 100

Hyvä's full register lists Vendic at Platinum under the Netherlands, and Vendic goes further on its own Hyvä page, calling itself the first Hyvä platinum partner in the world. It publishes four certified Hyvä developers by name, Kevin, Yevhen, Maxim and Olga, announced in June 2025 as having completed the Hyvä Certified Associate Developer exam. That is one of only two published certification counts among the eight and it is what puts Vendic second. Its Huissteden case carries the cleanest Luma attribution in the set: the award it won was for the largest speed jump from Luma to Hyvä, and the table is labelled Google Lighthouse mobile, before and after the 2025 Hyvä build. The figures are homepage 66 to 100, one category page 60 to 84, another 62 to 95, a product page 59 to 98 and a Juki product page 37 to 97, an average improvement of 74.6%, with RUMvision real visitor scores of 100 for Largest Contentful Paint, 100 for Cumulative Layout Shift, 99 for Interaction to Next Paint, 100 for First Contentful Paint and 95 for Time to First Byte. The tool is named and the build is dated, but no measurement date is attached to the run itself, which is the one thing separating it from the two agencies taking full marks on evidence. On scope it publishes four determinants a buyer can price against: Luma templates are not translated but rebuilt, so the more custom work in the current theme the more there is to rebuild; every third party module with frontend output needs a Hyvä compatible version, inventoried up front; Hyvä Checkout replaces the Luma checkout, with payment, shipping and B2B flows requiring testing; and the job runs from a few weeks to a few months, launched in phases with the old frontend kept as a fallback. Custom work is billed at 130 euro an hour and a code review at 480 euro. Support is the tightest published anywhere here: a 48 working hour service level on patches and vulnerabilities, a response within 60 minutes from 07:00 to 23:00 seven days a week under Vendic Protect, monitoring around the clock and two Magento and PHP upgrades a year, with no retainer price attached. It publishes 20+ Magento specialists against a roster showing 18 named people, 30+ Hyvä projects realized, and a PostNL Hyvä Checkout compatibility module released as open source without a repository URL. Two things it leaves unsettled: its own pages give both 2012 and 2013 as the year it went Magento only, and it publishes no Adobe partner status of any kind, because Adobe is not mentioned anywhere on the site.

3

ParadoxLabs

Buyers who want every figure dated and sourced, a published rate card and a straight answer on when Hyvä is the wrong call75 of 100

No agency on this page evidences a number as carefully as ParadoxLabs does, and that is why a team of eight finishes third. Its Half Time Beverage case lives at a URL ending luma-to-hyva and publishes a median page load moving from 6.5 seconds to 1.9 on the night of the Hyvä cutover, attributed to real user monitoring on 30 July 2023; page loads with good Largest Contentful Paint moving from 52% to 88% between July and August 2023, attributed to Chrome UX Report with a 75th percentile of 1.7 seconds; and organic traffic up 147% over the same window, attributed to analytics. Every figure carries its tool and its date, which nothing else here does consistently. The work is described just as precisely: a Tailwind based theme, Alpine.js interactivity, checkout preserved and custom catalog features reimplemented natively. A second case, Denver Wholesale Foods, reports mobile 75th percentile Largest Contentful Paint falling from 4.1 seconds to 1.4 and a launch in five months, citing Chrome UX Report field data from spring 2026. It publishes no Lighthouse score at all, deliberately, stating that it prefers field data to lab testing. Its engineering note on Hyvä migrations is the sharpest statement of breakage in this lane and the section below quotes it in full. It is also the only agency here that publishes when the answer should be no: deeply customized checkout ecosystems mid refactor, or stores leaving the platform inside 18 months, under the position that Luma is a liability and headless is usually over engineering for mid market. Pricing is the most complete published anywhere in this set: a fixed scope audit at 899 dollars, retainers at 2,700, 4,950 and from 9,000 dollars a month, hourly rates from 150 to 195 dollars, a patch turnaround of three, two or one day by tier, emergency response of two, two or one hour, cover weekdays 8am to 5pm Eastern, no lock in and 30 days notice. What holds it to third is credentials rather than craft. It publishes a team of eight, all named, 100% in house with no outsourcing, and no certification count, no Adobe partner status at any level by choice, and no certified Hyvä developer count. Its contribution record points at Mage-OS rather than Hyvä: Ryan Hoerr co-founded Mage-OS and remains a core maintainer, Melinda Humphrey sits on the Mage-OS board, the firm is a Gold Member of the Magento Association, and its Packagist organisation publishes 465k+ Composer installs. One discrepancy is worth raising on a call rather than treating as a problem: its own partners page carries a Hyvä Silver Partner badge while the full register lists it at Gold. It is scored at Gold, from the register, like everyone else.

4

elgentos

Buyers who want the migration quoted in hours before anything is signed, and an agency that publishes what Hyvä did not fix70 of 100

elgentos takes the top mark on honest causation and earns it with a paragraph most agencies would cut. Its Mijnheer Truckbanden case, titled from Luma to Hyvä with the same design, states that the shop it rebuilt ran on Magento with the standard Luma theme, and publishes the mobile Lighthouse score moving from 74 to 98 on the homepage and 79 to 91 on the category page, the homepage dropping from 38 MB to 0.36 MB and from 238 requests to 29, JavaScript blocking time falling from 21 to 28 milliseconds to zero, and accessibility at 100. Then it adds, in its own words, that fair is fair: the time the server needs to build a page has not changed, it was 368 milliseconds and it is 365 milliseconds, so the gain is not there. It also publishes what it deliberately left alone, saying the checkout was kept as it was and that one part of the shop therefore still carries the old JavaScript. Six of its eighteen cases name Luma as the source theme, and the case index is headed with the claim that every number on it was measured in production. Its migration scoping is the most specific in the lane and sits in the open before any conversation: keeping the current design means a retrofit at typically 200 to 400 hours, rebuilding on Hyvä UI components 300 to 500 hours, a fully custom design 400 to 700 hours, and Hyvä Checkout implementations between 50 and 200 hours. It states that a Hyvä migration touches more than the frontend, that extensions must be Hyvä compatible, that links to an ERP, PIM or WMS have to keep working, and that in practice the checkout usually travels in the same project so a merchant is not left halfway with two frontends. Maintenance is priced in three published bands from 1,500 to 7,000 euro a month depending on complexity, with feature development explicitly outside it, and no response time, patch turnaround or cover hours attached anywhere, which is what costs it most. It was founded in 2011, publishes a GitHub organisation, built Hyvä Checkout support for Paazl and Loqate itself, and gives away Hyvä Themes, The Book, a free e-book by Peter Jaap Blaakmeer. Adobe appears nowhere on the site as a partner at any level, and three of its own pages give three different team sizes: 22 people, 24 team members and 20+ employees.

5

ZERO-1

Buyers who want field data rather than lab scores, and a fixed price for the smallest possible first step57 of 100

ZERO-1 publishes the best evidenced single case on this page and almost nothing else a buyer can screen on, and the gap between those two facts is the whole entry. Its iBottles case states the previous theme as Luma and the build type as a Hyvä Retrofit, then publishes a passing Core Web Vitals assessment with Largest Contentful Paint at 1.2 seconds, Interaction to Next Paint at 138 milliseconds, Cumulative Layout Shift at 0, First Contentful Paint at 1.1 seconds and Time to First Byte at 0.8 seconds, attributed to real user data from the Chrome UX Report over a 28 day period in June 2026. A second case, BigK Products, publishes the same metric set with the same attribution, though that store came from WordPress and WooCommerce rather than Luma. Field data with the tool and the window stated is the top rung on evidence and ZERO-1 takes it. The rest of the site is where the score falls away. Its register tier is Platinum under both the United Kingdom and the United States and it publishes three certified Hyvä developers, which together carry most of its total. It publishes no team size, no certification count beyond those three and no Adobe partner status of any kind. There is no support page: the URL that should hold one serves unedited Magento sample data asking customers to allow 10 to 14 days for Luma to process a return, so nothing about response time, cover or escalation is published anywhere, and that line scores zero. On cost it is more concrete than most, stating it has implemented its most basic Retrofit project in as little as one week for 8,000 pounds, and that within 48 hours of one Hyvä launch Core Web Vitals good URLs began lifting from 19% to 85% in a little over two weeks. Its own accelerator, Miami, is published at 695 pounds a month. It also published original research, a survey of 37 websites split evenly between Hyvä and Luma using Google Search Console data, reporting 94% of Hyvä sites improving in organic results against 47% of Luma sites, with no clients named. The most useful sentence on its site is a caution about its own product, that Hyvä can still be butchered and it is solely down to the implementation. One page pulls the other way: a third case study is titled as delivering instant Core Web Vitals gains and publishes no Core Web Vitals data at all, which is why this page cites the two that do and not that one.

6

Foundation Commerce

Buyers who want the Luma problem diagnosed in writing, and a support contract priced before the first call56 of 100

Foundation Commerce is the clearest illustration of why this page separates a good number from an attributable one. Hyvä's directory blurb describes it as the first agency in the UK to launch a Magento and Hyvä project, and the register lists it at Platinum. Its Again Faster case is the one that names the source theme, stating that the existing website used the out of the box Luma theme and that this was quickly identified as one of the main problems, then reporting a 54% increase in conversion rate, a 64% increase in page speed and a 63% increase in checkout completion, with Core Web Vitals passed with flying colours and no figure behind that sentence. A relative improvement without an absolute metric value is the fourth rung, which is exactly where the agency in first place also lands. Its fullest metric set belongs to a different client, Todd Doors, with real user data at the 80th percentile giving Time to First Byte at 636 milliseconds, Interaction to Next Paint at 153 milliseconds, Largest Contentful Paint at 1,096 milliseconds, First Contentful Paint at 832 milliseconds and Cumulative Layout Shift at 0.038, alongside a product template moving from 5,689 milliseconds to 1,101. None of it is counted here as Luma to Hyvä evidence, because Foundation Commerce itself does not claim it is: the Hyvä storefront was already live, the word Luma appears on that page zero times, and the step change is attributed to a hosting migration. Publishing that rather than letting the numbers carry an implication is what takes the top mark on honest causation. On breakage it writes more than most: it states plainly that extension compatibility depends on whether the extensions in use are dependent on the Luma JavaScript libraries, that Luma delivers hundreds of CSS and JS files of which a large percentage are never used and is built on LESS, RequireJS and KnockoutJS, that it assesses and reviews every existing module and integration and implements Hyvä friendly alternatives where needed, and that this is not a one size fits all theme install. It publishes a Hyvä licence at 1,000 euro and conversion projects turned around in 8 to 12 weeks, though one of its own accelerator pages advertises both eight weeks and four weeks. Support runs from 1,200 pounds a month on a 12 month minimum with cover Monday to Friday 9am to 6pm UK time, monitoring around the clock, unlimited critical issue support, daily Sansec scanning and one major upgrade a year, and no response time is stated. Its Adobe wording is the bare Adobe Solution Partner with no level, no certified Hyvä developer count appears anywhere, and its team page lists 12 named people without stating a headcount.

7

Emico

Buyers who care most about live field performance across several stores, and will ask about the migration separately45 of 100

Emico publishes more real user performance data across more named clients than anyone here and never once names the theme those stores came from, which is why a Platinum agency with a genuine certification count finishes seventh. Its Tuinmeubelshop case publishes Largest Contentful Paint at 1.15 seconds, Cumulative Layout Shift at 0.00, Interaction to Next Paint at 118 milliseconds, First Contentful Paint at 1.21 seconds and Time to First Byte at 761 milliseconds, with a performance score of 97 out of 100 from RumVision explicitly described as based on real user data. Zitmaxx is published at 1.2 seconds, 112 milliseconds, 0, 1.1 seconds and 0.5 seconds on the same five metrics and called one of the best performing Magento 2 webshops worldwide. Girav is reported scoring between 96% and 99% on Core Web Vitals with conversion up 11% in a year and Hyvä Checkout named as playing a key role. Plutosport moved from average load times around 1.8 seconds to 800 milliseconds in the first month with Core Web Vitals improving by more than 30% on average, in a phased rollout published market by market. What it does with those figures is more careful than most: it writes that Zitmaxx got there through Hyvä among other things, its own Zitmaxx case attributes the result to a ground up rebuild involving Percona MySQL, lazy loading, Elastic and Hypernode, and the Plutosport gains are credited jointly to backend optimisation and Hyvä. Naming the other causes is worth six of the eight points on that criterion. Against that, no case names Luma as the source theme, so none of those figures can be tied to a theme swap by a reader, and the Platinum register tier carries no published certified Hyvä developer count behind it. It publishes three locations with full street addresses in Rhenen, Rotterdam and Nijmegen, a history beginning in 2009, 14 Magento certified specialists, and a team size its own pages give twice, as 45+ senior developers on one and 40+ Magento specialists on another. There is no Adobe partner status anywhere, no migration price, no hours, no timeline, and no page at all describing what a Hyvä migration breaks, which is the only zero on this page for that criterion. It did build the Hyvä compatibility module for Tweakwise. Its Hyvä page title tag reads Gold Partner in both languages while the body copy and the register both say Platinum, so the register settles it and it is scored at Platinum.

8

Fluid Commerce

Buyers who want the migration shown page by page and device by device in a single Lighthouse table43 of 100

One document earns Fluid Commerce most of its score. The Fletcher Stewart project lists its objective as migrating the Luma front end theme to Hyvä, states that the previous site used the Luma front end theme and that migration to Hyvä was a key part of the proposal, then publishes the only Lighthouse performance table in this lane broken out by page and by device. Homepage desktop 54 to 97 and mobile 34 to 80; category desktop 54 to 96 and mobile 29 to 93; product page desktop 49 to 99 and mobile 12 to 95. Speed Index follows the same breakdown, with the product page moving from 4.7 seconds to 1 on desktop and 15.1 seconds to 3.1 on mobile. Its Hyvä service page cross checks the headline independently, describing a mobile product page speed increase of nearly 700%, which is what 12 to 95 comes to. Commercial results over the first two months and a Hive Excellence Award are published alongside. The tool is named, the pages are named, the devices are named, and no measurement date is given, which is the gap between 18 and 22 on that criterion. Everything else is softer than the table. Timelines are published as typically two to six months, longer for complex projects. On breakage the wording runs the other way from every other agency here: it states that the vast majority of custom features work well with Hyvä and that it is rare for problems to occur that prohibit its use, with equivalent solutions or custom development provided where a third party extension is not compatible, and no library, module class or hours behind any of it. It publishes a genuinely useful licensing note, that the core theme became open source in November 2025 while Hyvä Commerce, Hyvä Checkout and Hyvä UI remain on a paid subscription, and confirms the existing site stays live while the Hyvä version is tested in staging. Its register tier is Gold and no certified Hyvä developer count is published. Its support page describes a retainer with an agreed number of hours a month, a dedicated account manager, monthly reporting, quarterly business reviews, Core Web Vitals monitoring and urgent tickets moved to the top of the queue, and attaches no response time, no cover hours and no price to any of it, which scores nothing. It is also the only agency on this page publishing no contribution to Hyvä of any kind: no module, no repository, no compatibility work. A second project labelled a Hyvä migration turns out on reading to describe a greenfield build for a company established in January 2025, with no source theme and no performance figures.

9

JaJuMa

Buyers who want the agency that writes Hyvä code, and will accept a timeline and a price being withheld until the call37 of 100

JaJuMa contributes more to Hyvä itself than anyone else on this page and publishes less that a buyer can screen on than almost anyone, and the score reflects the second rather than the first. On contribution it holds ground nobody else here claims: it states it was the very first Magento extension provider to offer official Hyvä compatibility, that it achieved status as a Core Contributor to the Hyvä theme itself by fixing bugs and adding features, that it ships seven extensions named for and dedicated to Hyvä including Awesome Hyvä, Hyvä Inline CSS, Hyvä Flags and Hyvä Translation, that a significant number of them are free and open source, and that it has built free compatibility modules for extensions made by other providers. It runs its own site on Hyvä using most of its own extensions. Its migration case is properly evidenced and properly scoped. The client is named, Rosemarie Schulz, the source theme is named as an outdated Luma based frontend that was failing its Core Web Vitals assessment on Cumulative Layout Shift, and the before and after table publishes Cumulative Layout Shift 0.3 to 0.0, Largest Contentful Paint 1.6 to 0.8 seconds, First Contentful Paint 1.3 to 0.7 and Time to First Byte 0.9 to 0.4. It publishes the full scope behind those numbers rather than letting the theme take credit for all of it: upgrading Magento, cleaning up, refreshing every extension, then rolling out Hyvä Theme and Hyvä Checkout, moving payment processing to Mollie and customising the frontend to preserve the store's familiar look. It adds, unusually, that it did not need Elasticsearch, Varnish or Redis to get there. No measurement tool is named on that table, which is what holds evidence to 15. Elsewhere the disclosure runs thin. It publishes no team size anywhere, no Adobe partner status at any level, and a Hyvä Certified Developers badge with no number on it, so the certification credential it genuinely has is not countable. Its register tier is Gold and it discloses its own tier history openly, Silver in 2024 and Gold in 2025, which is rarer than it sounds. On the two questions a buyer asks first it declines to answer: the timeline is published only as varying with store complexity, customisations and extension compatibility requirements, and no migration price appears anywhere, only extension prices from 149 to 349 euro. What it does publish about breakage is a single accurate sentence, that compatibility depends on whether an extension relies heavily on the JavaScript libraries such as jQuery and KnockoutJS that Hyvä removes.

4 Which one fits

Pick by situation, not by ranking

If this is youShortlistWhy
Your board wants a before and after number it can attribute to the theme swap and nothing elseParadoxLabs, then Vendic or Fluid CommerceParadoxLabs publishes a Luma to Hyvä case where every figure names its tool and its date, including page loads with good Largest Contentful Paint moving from 52% to 88% on Chrome UX Report between July and August 2023. Vendic publishes a Lighthouse table across five pages for a store the award citation describes as the largest speed jump from Luma to Hyvä. Fluid Commerce publishes the only Lighthouse breakdown by page and by device, with a product page moving from 12 to 95 on mobile.
Your store is heavy with third party extensions and you need the breakage priced before you commitelgentos, with ParadoxLabs as the second readelgentos publishes the work in hours before any conversation: a retrofit that keeps the design at typically 200 to 400 hours, a rebuild on Hyvä UI components at 300 to 500, a fully custom design at 400 to 700, and Hyvä Checkout at 50 to 200. ParadoxLabs publishes the clearest statement of what a Hyvä front end actually breaks, quoted in full further down this page, and asks for an integration inventory before quoting anything.
You want the smallest possible first step, on a fixed price, to see whether Hyvä is worth a bigger programmeZERO-1, with Foundation Commerce as the second callZERO-1 states it has delivered its most basic Retrofit project in as little as one week for 8,000 pounds, and publishes its own accelerator at 695 pounds a month. Foundation Commerce publishes the Hyvä licence at 1,000 euro and turns conversion projects around in 8 to 12 weeks. Ask both what falls outside the fixed scope, because ZERO-1 publishes no support terms at all and one of Foundation Commerce's own pages advertises two different minimum timelines.
You need a service level and an escalation path in the contract from day one, not after go liveParadoxLabs, then VendicParadoxLabs publishes a patch turnaround of three, two or one day by retainer tier, emergency response at two, two or one hour, cover weekdays 8am to 5pm Eastern, retainers from 2,700 to over 9,000 dollars a month and hourly rates from 150 to 195 dollars. Vendic commits to a response within 60 minutes from 07:00 to 23:00 seven days a week and a 48 working hour turnaround on patches and vulnerabilities. Four of the nine publish nothing usable on this at all.
Procurement screens partner tier and certification counts before any technical conversation happensscandiweb, then Vendic or ZERO-1scandiweb is listed at Platinum in Hyvä's full register with 15+ certified Hyvä developers and 40+ Hyvä projects published in that entry, alongside Adobe Commerce Gold Solution Partner and 894+ Adobe certifications. Vendic is Platinum with four certified Hyvä developers named individually, and ZERO-1 is Platinum with three. Nobody else on this page publishes a Hyvä certification count, and only one other agency names an Adobe level.
You want the people who write Hyvä code rather than the people who sell Hyvä projectsJaJuMa, with Emico and Foundation Commerce as second readsJaJuMa states it is a Core Contributor to the Hyvä theme, was the first Magento extension provider to offer official Hyvä compatibility, and ships seven Hyvä specific extensions, many of them free and open source. Emico built the Hyvä compatibility module for Tweakwise. Foundation Commerce made the Klaviyo, Klevu, Mageworx Layered Navigation and Mageplaza Instagram Feed extensions compatible and submitted them to the Hyvä compatibility library. Expect to trade disclosure for depth: JaJuMa publishes neither a timeline nor a price.

5 Evidence

Published work and primary sources behind the entries

ClientWhat was doneResultSource
Hyvä full agency registerHyvä's own complete register, and the source for every partner tier printed on this page460 listings across five tiers: 17 Platinum, 46 Gold, 102 Silver, 264 Bronze and 31 Partner, counted from the page's own elements on 23 September 2026. All nine agencies here were looked up in it. This is not the page most buyers find first, and reading the other one instead is the most common mistake in this laneSource
Hyvä Preferred PartnersThe curated shortlist that is frequently mistaken for the full registerCarries three tiers only, Platinum, Gold and Silver, with 11, 40 and 75 partner cards respectively, 126 in total. Bronze and Partner do not appear, so an agency holding either is absent from this page while correctly listed in the register. scandiweb's entry here reads that it is a Hyvä Platinum Partner and one of the most experienced Hyvä agencies, with 15+ certified Hyvä developers and 40+ Hyvä projects deliveredSource
Half Time BeverageLuma to Hyvä migration reported by ParadoxLabs, the best evidenced case in this laneMedian page load from 6.5 seconds to 1.9 on the night of the Hyvä cutover, attributed to real user monitoring on 30 July 2023. Page loads with good Largest Contentful Paint from 52% to 88% between July and August 2023 on Chrome UX Report, 75th percentile 1.7 seconds. Organic traffic up 147% over the same window, attributed to analytics. Every figure carries its tool and its dateSource
iBottlesHyvä Retrofit from Luma reported by ZERO-1, on field data rather than lab scoresPrevious theme stated as Luma. Passed, with Largest Contentful Paint 1.2 seconds, Interaction to Next Paint 138 milliseconds, Cumulative Layout Shift 0, First Contentful Paint 1.1 seconds and Time to First Byte 0.8 seconds, attributed to real user data from the Chrome UX Report over a 28 day period in June 2026Source
HuisstedenLuma to Hyvä rebuild reported by Vendic, with the award citation naming the source themeTable labelled Google Lighthouse mobile, before and after the 2025 Hyvä build: homepage 66 to 100, two category pages 60 to 84 and 62 to 95, a product page 59 to 98 and a Juki product page 37 to 97, average improvement 74.6%. RUMvision real visitor scores of 100, 100, 99, 100 and 95 across Largest Contentful Paint, Cumulative Layout Shift, Interaction to Next Paint, First Contentful Paint and Time to First Byte. The award was for the largest speed jump from Luma to HyväSource
Mijnheer TruckbandenLuma to Hyvä with the same design, reported by elgentos, and the only published null result in the laneMobile Lighthouse from 74 to 98 on the homepage and 79 to 91 on the category page, homepage weight from 38 MB to 0.36 MB, requests from 238 to 29, JavaScript blocking time from 21 to 28 milliseconds down to zero, accessibility 100. Then, in elgentos's own words, that fair is fair, the time the server needs to build a page has not changed, from 368 milliseconds to 365, so the gain is not there. It also publishes that the checkout was deliberately left in place and still carries the old JavaScriptSource
Fletcher StewartLuma front end migrated to Hyvä, reported by Fluid Commerce, per page and per deviceLighthouse performance homepage 54 to 97 desktop and 34 to 80 mobile, category 54 to 96 and 29 to 93, product page 49 to 99 and 12 to 95. Speed Index on the product page from 4.7 seconds to 1 on desktop and 15.1 to 3.1 on mobile. The only Lighthouse table in this lane broken out by page and by device, with no measurement date attachedSource
Rosemarie SchulzRescue of an outdated Luma based frontend, reported by JaJuMa, with the full scope publishedCumulative Layout Shift 0.3 to 0.0, Largest Contentful Paint 1.6 to 0.8 seconds, First Contentful Paint 1.3 to 0.7, Time to First Byte 0.9 to 0.4. The scope is published alongside: a Magento upgrade, cleanup, refreshed extensions, then Hyvä Theme and Hyvä Checkout, payment processing moved to Mollie, and the frontend customised to preserve the look. No measurement tool is namedSource
Again FasterThe one Foundation Commerce case that names the source themeStates that the existing website used the out of the box Luma theme and that this was quickly identified as one of the main problems. Reports a 54% increase in conversion rate, a 64% increase in page speed and a 63% increase in checkout completion, and says Core Web Vitals passed with flying colours without publishing a figure. Eight weeks to Black FridaySource
Todd DoorsExcluded from the scoring, and worth explaining rather than quietly droppingThis case carries Foundation Commerce's fullest metric set, with real user data at the 80th percentile giving Time to First Byte 636 milliseconds, Interaction to Next Paint 153 milliseconds, Largest Contentful Paint 1,096 milliseconds, First Contentful Paint 832 milliseconds and Cumulative Layout Shift 0.038. It is not counted as Luma to Hyvä evidence here because the agency does not present it as such: the Hyvä storefront was already live, the word Luma does not appear on the page, and the step change is attributed to a hosting migration. Publishing that attribution is why Foundation Commerce takes the top mark on honest causationSource
TuinmeubelshopHyvä build reported by Emico, on real user data, with no source theme namedLargest Contentful Paint 1.15 seconds, Cumulative Layout Shift 0.00, Interaction to Next Paint 118 milliseconds, First Contentful Paint 1.21 seconds, Time to First Byte 761 milliseconds, and a performance score of 97 out of 100 from RumVision described as based on real user data. Emico names Luma as the source theme in no case study on its site, which is why figures this good score on the same rung as an agency publishing no source theme at allSource
Scouting AmericaThe one scandiweb case that names Luma as the source themeDescribes a migration from its old Luma based platform to a storefront built with Hyvä, names the legacy Luma setup as unoptimised for mobile performance, and publishes Largest Contentful Paint improved by 12 to 13% on mobile and desktop, with mobile revenue up 6.2% year on year, average order value up 27.3% and checkout starts up 23.9%. It also publishes that the previous infrastructure was self hosted and that the new storefront runs on ReadyMage, so the hosting changed in the same project. A relative improvement rather than an absolute before and after value, with no measurement tool and no measurement date, which is what caps the heaviest evidence criterion at 12 of 22 for the agency in first placeSource
Läderach and ByggmaxHyvä rebuilds reported by scandiweb, the largest volume of named-client figures here and the weakest attributionLäderach at 93 PageSpeed for the homepage and product page on desktop, 99 for the listing page, Largest Contentful Paint 1.8 seconds desktop and 1.9 mobile. Byggmax product listing pages from 85 to 99 and product pages from 70 to 87. Nicokick's homepage reaching 96. Five named clients carry figures and none of those cases names the theme the store moved off, the tool the figures were taken with, or the date they were taken, so none of them can be scored as migration evidenceSource
Hyvä compatibility modules documentationHyvä's own account of why third party modules need work, quoted in the section belowStates that modules based on the Magento luma or blank themes require a Compatibility Module to work with Hyvä, and that a compatibility module re-implements the parts of a module that do not work out of the box in a Hyvä storefront. The migration guide adds the specifics: mage/template and underscore.js are replaced with Alpine.js directives, x-magento-template script tags become Alpine templates using x-for, and jQuery data calls become native dataset accessSource
Hyvä Luma theme fallback documentationThe staged migration route, and the cost of taking it, in Hyvä's own wordsThe Luma theme fallback module lets specific routes be configured to use a Luma based theme instead of Hyvä, so pages can be brought across gradually. The documentation states the price of that plainly: on pages using the fallback the Hyvä theme is not active, Tailwind CSS and Alpine.js are not loaded, RequireJS and all standard Luma theme dependencies are loaded by the browser instead, and any styling for those pages must be built using standard Magento approaches rather than Hyvä'sSource

6 In detail

What a Luma to Hyvä migration actually costs, and what it breaks

The clearest sentence written about this migration by anyone selling it belongs to ParadoxLabs, in an engineering note arguing that a Hyvä re-front is an integration inventory rather than a theme install. It reads: Hyvä replaces Magento's entire frontend stack, so nothing a third party shipped for the old one survives: loyalty widgets, promo banners, brand pages, payment buttons, and gift card templates all need native re-implementation. The recommendation attached to it is the part that changes a quote. Inventory the integrations before quoting, rebuild them natively, and delete the old theme leftovers. Set that against the softest framing in this set, Fluid Commerce's statement that the vast majority of custom features work well with Hyvä and that it is rare for problems to occur that prohibit its use, and a buyer has the real spread of opinion in this lane. Both can be true of different stores. Only one of them tells you how much discovery to pay for.

Hyvä's own documentation settles the mechanism, and it is worth reading before any agency call because it is vendor published and free of sales incentive. Modules built against the Magento luma or blank themes require a compatibility module to work with Hyvä, and a compatibility module re-implements the parts of a module that do not work out of the box in a Hyvä storefront. The migration guide lists what that re-implementation involves: mage/template and underscore.js are replaced with Alpine.js directives, script tags of type text/x-magento-template become Alpine templates using x-for, dependencies on libraries like jQuery can be removed and replaced with native JavaScript, and a jQuery data call becomes native element.dataset access. So the question to put to a shortlist is not whether an extension works with Hyvä. It is how many of your extensions render front end markup, which of those already have a compatibility module, and who pays to write the ones that do not.

You can stage it, and Hyvä publishes what staging it costs. The Luma theme fallback module lets specific routes be configured to use a Luma based theme instead of Hyvä, so pages can be brought across gradually. The documentation is unusually blunt about the trade: on pages using the fallback the Hyvä theme is not active, Tailwind CSS and Alpine.js are not loaded, and instead RequireJS and all standard Luma theme dependencies are loaded by the browser, with any styling for those pages built using standard Magento approaches rather than Hyvä's. In other words a phased migration is two front ends running in one store, and the pages left behind keep every performance characteristic you are paying to remove. elgentos publishes what that looks like on a real store, saying the checkout was deliberately left in place and that one part of the shop therefore still carries the old JavaScript. Vendic runs the same pattern by design, launching in phases with the old front end kept as a fallback.

On money, the published figures line up more consistently than the marketing suggests. elgentos quotes the work in hours: a retrofit keeping the current design at typically 200 to 400 hours, a rebuild on Hyvä UI components at 300 to 500, a fully custom design at 400 to 700, and Hyvä Checkout separately at 50 to 200. Vendic bills custom work at 130 euro an hour and puts the whole job at a few weeks to a few months. ZERO-1 publishes a floor, stating its most basic Retrofit has been delivered in as little as one week for 8,000 pounds. Foundation Commerce publishes 8 to 12 weeks and a Hyvä licence at 1,000 euro. Fluid Commerce publishes two to six months. ParadoxLabs publishes a fixed scope audit at 899 dollars and hourly rates from 150 to 195, though not a migration price. JaJuMa declines to publish a timeline at all, saying only that it varies with store complexity, customisations and extension compatibility requirements, and Emico publishes neither a price, nor hours, nor a timeline anywhere on its site. The most complete commentary on total cost comes from an agency not ranked here at all, Bemeir, which publishes an itemised first year range of 25,000 to 85,000 dollars and timelines of 4 to 6, 6 to 10 and 12 to 16 weeks by store type. Take it as commentary and nothing more: its case studies URL redirects to a testimonials page, so there is no named client behind any of it.

The most important thing Hyvä does not do belongs in the business case before anything is signed, and the evidence for it comes from an agency that stood to gain by keeping quiet. elgentos, having published a mobile Lighthouse score moving from 74 to 98 on a Luma to Hyvä rebuild, adds that the time the server needs to build a page has not changed, from 368 milliseconds to 365, so the gain is not there. Hyvä is a front end. Server rendering time, database performance, integration latency and third party scripts loaded into the page are all untouched by which theme renders the markup. Three agencies on this page make the same point in the opposite direction, by disclosing what else was in scope when the numbers moved. JaJuMa states that its Rosemarie Schulz figures followed a Magento upgrade, a cleanup and a refresh of every extension as well as the Hyvä rollout. scandiweb introduces its Classic Football Shirts figures with the words after the Magento version upgrade and migration to Hyvä, and publishes that its Scouting America build moved off self hosted infrastructure at the same time. Foundation Commerce goes furthest, publishing a full real user metric set for a client and attributing the step change to a hosting migration rather than to the theme. None of that makes the numbers worse. It makes them usable.

Two checks are worth doing yourself before a shortlist call, and both take minutes. First, read the partner tier from Hyvä's full agency register rather than from the curated Preferred Partners page, because the curated page carries only Platinum, Gold and Silver, and an agency holding Bronze or Partner is simply absent from it rather than absent from the programme. The register publishes 460 listings against the curated page's 126, and Bronze alone accounts for 264 of them. Second, ask for the certified Hyvä developer count in writing. Certification is a proctored exam sat through Webassessor from 200 euro excluding VAT, at Associate and Professional levels, so it is a real credential with a real number behind it, and across this page only three of nine agencies publish one. An agency that cannot tell you how many of its developers hold it is telling you something, and it may be nothing worse than that nobody asked before.

7 Methodology

How this was put together

Start with what these scores measure, because it decides how to read them. This page scores what an agency publishes about its Hyvä migration work, not the quality of that work, so a low score means thin public disclosure rather than weak delivery. An agency that has moved twenty stores off Luma without writing any of it up will finish low here and could still be the right supplier. Nine agencies were scored out of 100 against the six weighted criteria published in the table above, the ranking is the score order with no adjustment, and every score is printed against its entry so the arithmetic can be rebuilt and the weighting argued with. Where two agencies tie, the one scoring higher on the heaviest criterion is placed first, which is why Vendic and ParadoxLabs both total 75 and Vendic is placed second. The weighting deserves an explanation, because it is not the weighting earlier editions of this series used. In every other front end lane examined this year, almost nobody published a Lighthouse score or Core Web Vitals figures for a named client, so publishing one was the sharpest criterion available. Here it is the opposite: all eight agencies beside scandiweb publish measured performance for a named Hyvä build, and it was possible to select eight on that basis. A criterion an entire field passes ranks nothing. So performance evidence carries 22 rather than the 25 or more it would carry elsewhere, and it is scored on attribution rather than on existence, because a fast number that cannot be tied to the theme swap does not answer the question a buyer came here with. The heaviest criterion instead is the one that is genuinely scarce: a Platinum listing in Hyvä's register alongside a published count of certified Hyvä developers. Two of the nine publish a count, at four and at three, and one publishes 15+. Disagree with that reasoning and you should re-weight it, which is why the full ladder for every criterion is printed rather than summarised. Hyvä tiers are the one set of facts here not read from a ranked agency's own site. Hyvä publishes two directories and they are not interchangeable. The curated Preferred Partners page carries three tiers, Platinum, Gold and Silver, with 11, 40 and 75 partner cards. The full agency register carries 460 listings across five tiers, 17 Platinum, 46 Gold, 102 Silver, 264 Bronze and 31 Partner, counted from the page's own elements on 23 September 2026. Every tier here is read from the register. An earlier page in this series got this wrong by reading the curated page instead, concluded that Hyvä publishes no Bronze tier, and on that basis told an agency its genuine Bronze status was unconfirmed. That agency was right, the page was wrong, and the correction is why the distinction is laboured here. Two tier discrepancies turned up in this set and both are published rather than reconciled, because both are checkable and both are under claims rather than over claims. ParadoxLabs displays a Hyvä Silver Partner badge on its own partners page while the register lists it at Gold, and Emico's Hyvä page title tag reads Gold Partner in both languages while its body copy and the register both say Platinum. Both are scored at their register tier. Two published results were deliberately excluded from scoring, with the reasons printed in the evidence table rather than buried: Foundation Commerce's Todd Doors figures are not counted as Luma to Hyvä evidence because the agency's own page attributes the step change to a hosting migration and never mentions Luma, and a third ZERO-1 case study titled as delivering instant Core Web Vitals gains is not cited because it publishes none. Adobe partner tier is scored on one test applied identically to all nine: whether a level is named in current Adobe wording on a page a buyer would open. Adobe's own Solution Partner Directory corroborates the Gold listing in first place and earns nothing here, because the other eight were not looked up in it and a test only one party sits for is not a test. Where an agency publishes no tier, no count, no price, no hours or no response time, that line scores nothing rather than being estimated, and the entry names the line. Seven further agencies were researched to the same depth and left out, each for a stated reason, and none is disqualified as an agency. Snowdog came closest and was cut only because no case study names Luma as the source theme. integer_net has the strongest provenance of anyone researched, described by Hyvä's own directory as its main partner and initial co-creator, but publishes no measured result of any kind and runs a German only site against an English lane. Cream was cut as Dutch only with no Luma case. Trinos was cut for the same reason and additionally because its headline performance tile is reused verbatim on two unrelated pages with no client attached, which makes it uncitable. ATI4 Group publishes no performance figure for any named build and contradicts itself on its own tier across three pages. Monsoon Consulting publishes the best single open source artefact of anyone researched and no Hyvä migration case study at all. Bemeir publishes by far the most written detail on cost and breakage and by far the least proof, with a case studies URL that redirects to testimonials, so its material is used in the section above as commentary and nowhere as evidence of its own delivery.

8 Questions

Common questions

Which agencies migrate a Magento store from Luma to Hyvä in 2026?

Nine are scored on this page. scandiweb, Vendic, ZERO-1, Foundation Commerce, elgentos and Emico all hold Platinum in Hyvä's full agency register. JaJuMa, Fluid Commerce and ParadoxLabs hold Gold. Seven of the nine publish at least one case study that names Luma as the theme the store moved off, and eight of the nine publish measured performance for a named Hyvä build. Six publish both together, which is the combination that lets a figure be attributed to the migration: Vendic, ZERO-1, elgentos, JaJuMa, Fluid Commerce and ParadoxLabs. The two that do not are Emico, which publishes a great deal of real user data and names a source theme nowhere, and Foundation Commerce, whose Luma case and whose fullest metric set belong to two different clients.

Does a low score on this page mean an agency builds bad Hyvä sites?

No. This page scores what an agency publishes about its Hyvä migration work, not the quality of that work, so a low score means thin public disclosure rather than weak delivery. JaJuMa finishes last here and is a Core Contributor to the Hyvä theme itself, which nobody above it can claim. What it does not publish is a team size, an Adobe status, a timeline, a migration price or a number on its certified developer badge, and this page can only score what is on the page. Every entry names the specific lines that cost it, so the right use of a low score is to build a question list for the sales call, and the right use of a high one is to click the links and check them.

How do I check an agency's real Hyvä partner tier?

Read it from Hyvä's full agency register, and know that Hyvä runs two directories that are easy to confuse. The page most buyers land on is Preferred Partners, a curated shortlist showing three tiers only, Platinum, Gold and Silver, with 11, 40 and 75 partner cards on it and 126 in total. The full agency register sits at a separate URL and lists 460 agencies across five tiers: 17 Platinum, 46 Gold, 102 Silver, 264 Bronze and 31 Partner. Read the curated page as though it were the register and you will conclude that the two lowest tiers do not exist and that any agency claiming one is overstating itself. That is wrong on both counts, and it is a mistake an earlier page in this series made in public before correcting it.

Does Hyvä have a Bronze tier?

Yes. Bronze is the largest tier in Hyvä's full agency register, with 264 of the 460 listings, and there is a fifth tier called Partner with 31 more alongside it. Neither appears on the curated Preferred Partners page, which stops at Silver, and that is the source of the confusion rather than anything Hyvä has changed. An agency that announces Bronze status and cannot be found on the Preferred Partners page is not exaggerating; it is simply not on a list that was never meant to include it. Check the register before treating any tier claim as unverified.

What does a Luma to Hyvä migration cost?

The published figures come in two shapes, hours and calendar time, and the hours are more useful. elgentos publishes the most specific numbers in the lane: a retrofit that keeps your current design at typically 200 to 400 hours, a rebuild on Hyvä UI components at 300 to 500, a fully custom design at 400 to 700, and Hyvä Checkout separately at 50 to 200. Vendic bills custom work at 130 euro an hour. ZERO-1 publishes a floor of 8,000 pounds for its most basic Retrofit, delivered in as little as one week. Foundation Commerce publishes the Hyvä licence at 1,000 euro and conversion projects at 8 to 12 weeks. Fluid Commerce publishes two to six months. ParadoxLabs publishes an 899 dollar fixed scope audit and hourly rates from 150 to 195 dollars but no migration price. JaJuMa and Emico publish nothing. Multiply an hours range by a rate and you have a usable band; a calendar estimate on its own tells you when, not how much.

How long does a Luma to Hyvä migration take?

Published ranges run from one week to six months, and the spread is mostly about scope rather than about speed. ZERO-1 has delivered its most basic Retrofit in one week. Foundation Commerce publishes 8 to 12 weeks for conversion projects, though one of its own accelerator pages advertises both eight weeks and four weeks. Fluid Commerce publishes two to six months, longer for complex projects. Vendic publishes a few weeks to a few months. elgentos puts a Hyvä build at around three months on one case with another month for Hyvä Checkout. JaJuMa declines to give a range at all, saying the timeline varies with store complexity, customisations and extension compatibility requirements, which is honest and unhelpful in equal measure. The variable underneath all of them is the same: how many third party modules render front end markup, and how many of those already have a Hyvä compatibility module.

What actually breaks when you move a Magento store from Luma to Hyvä?

The sharpest published answer belongs to ParadoxLabs: Hyvä replaces Magento's entire frontend stack, so nothing a third party shipped for the old one survives, and loyalty widgets, promo banners, brand pages, payment buttons and gift card templates all need native re-implementation. Hyvä's own documentation explains the mechanism. Modules built against the Magento luma or blank themes require a compatibility module, which re-implements the parts that do not work out of the box. In practice that means mage/template and underscore.js replaced with Alpine.js directives, x-magento-template script tags rewritten as Alpine templates, jQuery dependencies removed in favour of native JavaScript, and jQuery data calls replaced with native dataset access. Foundation Commerce puts the same point commercially, saying compatibility depends on whether your extensions are dependent on the Luma JavaScript libraries. Fluid Commerce frames it far more gently, saying it is rare for problems to occur that prohibit the use of Hyvä. Both positions appear on this page and the gap between them is what discovery is for.

Can I migrate page by page instead of all at once?

Yes, and Hyvä publishes what it costs you. The Luma theme fallback module lets you configure specific routes to use a Luma based theme instead of Hyvä so pages can be brought across gradually. The documentation is explicit about the trade: on pages using the fallback the Hyvä theme is not active, Tailwind CSS and Alpine.js are not loaded, RequireJS and all standard Luma theme dependencies are loaded by the browser instead, and styling for those pages has to be built using standard Magento approaches rather than Hyvä's. So a staged migration is two front ends in one store, and every page still on the fallback keeps the performance profile you are paying to remove. elgentos publishes a live example of that trade, having deliberately left a checkout in place and stated that part of the shop still carries the old JavaScript. Vendic runs phased launches with the old front end kept as a fallback by design.

What is a Hyvä compatibility module?

It is the bridge between an extension written for the old front end and a store running Hyvä. Hyvä's documentation defines it directly: modules based on the Magento luma or blank themes require a compatibility module to work with Hyvä, and a compatibility module re-implements the parts of a module that do not work out of the box in a Hyvä storefront. Several agencies on this page have written them and published which ones. Emico built the Hyvä compatibility module for Tweakwise. Foundation Commerce made the Klaviyo, Klevu, Mageworx Layered Navigation and Mageplaza Instagram Feed extensions compatible and submitted them to the Hyvä compatibility library. JaJuMa states it was the first Magento extension provider to offer official Hyvä compatibility and has built free compatibility modules for other providers' extensions. Vendic released a PostNL Hyvä Checkout compatibility module as open source. Ask a shortlist which of your specific extensions already have one, because the answer converts directly into hours.

Does Hyvä fix a slow Magento back end?

No, and the best evidence for that comes from an agency with every reason to leave it unsaid. elgentos published a Luma to Hyvä rebuild where the mobile Lighthouse score went from 74 to 98 on the homepage, then added that the time the server needs to build a page has not changed, from 368 milliseconds to 365, so the gain is not there. Hyvä is a front end. Server rendering time, database performance, integration latency and third party scripts loaded into the page are all untouched by which theme renders the markup. That matters for how the business case is written: if Time to First Byte is your problem, a theme migration will not move it, and an agency that lets you believe otherwise has told you something about how it will handle the rest of the project.

What is a Hyvä Certified Developer, and how many do these agencies have?

It is a formal credential rather than a badge an agency awards itself. Hyvä runs the exam through Webassessor, AI and human proctored, from 200 euro excluding VAT, at Associate Developer and Professional Developer levels. That makes a published count checkable, and almost nobody publishes one. Across this page only three agencies do. scandiweb's entry in Hyvä's own directory states 15+ certified Hyvä developers and 40+ Hyvä projects delivered. Vendic publishes four and names them individually, announced in June 2025. ZERO-1 publishes three. JaJuMa displays a Hyvä Certified Developers badge with no number on it, and the remaining five say nothing at all. This is the criterion carrying the most weight here, precisely because it is the one thing in this lane that is both scarce and verifiable.

Which agencies publish a performance figure with the measurement tool and the date attached?

Two, and they are the two that take full marks on evidence. ParadoxLabs attaches a tool and a date to every figure it publishes: a median page load from 6.5 seconds to 1.9 on the night of the cutover from real user monitoring on 30 July 2023, good Largest Contentful Paint from 52% to 88% on Chrome UX Report between July and August 2023, and organic traffic up 147% from analytics over the same window. ZERO-1 attributes its iBottles Core Web Vitals set to real user data from the Chrome UX Report over a 28 day period in June 2026. Everyone else names a tool without a measurement date, names a tool on some figures and not others, or publishes scores with no tool named at all. A dated, tool attributed figure is the difference between a result you can reproduce and a number you have to take on trust.

Why is the Todd Doors case not counted as Luma to Hyvä evidence?

Because Foundation Commerce does not present it as such, and this page took the agency at its word. That case carries its fullest metric set, with real user data at the 80th percentile giving Time to First Byte at 636 milliseconds, Interaction to Next Paint at 153 milliseconds, Largest Contentful Paint at 1,096 milliseconds and Cumulative Layout Shift at 0.038, plus a product template dropping from 5,689 milliseconds to 1,101. The word Luma does not appear on the page. The Hyvä storefront was already live, and the step change is attributed to a hosting migration. Counting it as proof of a theme migration would misrepresent the agency's own account of its own project. Publishing that attribution instead of letting the numbers imply something larger is exactly why Foundation Commerce takes the top mark on honest causation here.

Two agencies advertise a lower Hyvä tier than the register shows. What does that mean?

It means their marketing is behind their status, which is the less worrying direction for a discrepancy to run. ParadoxLabs displays a Hyvä Silver Partner badge on its own partners page while the full register lists it at Gold. Emico's Hyvä page title tag reads Gold Partner in both languages while its body copy and the register both say Platinum. Neither is claiming more than the register gives them. Both are most likely stale assets nobody updated after a promotion. Both are scored at their register tier here, like every other agency on this page, and both are worth mentioning on a call for the simple reason that an agency which has not noticed its own badge is out of date may not be noticing other things either.

Is Hyvä still a paid licence?

Partly, and Fluid Commerce publishes the clearest summary of the split: in November 2025 Hyvä announced that its core theme was now open source, while Hyvä Commerce remains on a paid subscription model, as do Hyvä Checkout and Hyvä UI. Foundation Commerce publishes a Hyvä Themes licence at 1,000 euro. The distinction matters when comparing quotes, because a proposal covering the core theme alone and one covering theme plus checkout are different commitments with different recurring costs. elgentos prices Hyvä Checkout implementations separately at 50 to 200 hours for exactly that reason, and links Hyvä's public tracker of which payment and shipping integrations are already done.

Which of these agencies publish support terms before you sign?

Five publish something usable and four publish nothing numeric at all. ParadoxLabs publishes the most complete set anywhere here: a patch turnaround of three, two or one day by retainer tier, emergency response at two, two or one hour, cover weekdays 8am to 5pm Eastern, retainers from 2,700 to over 9,000 dollars a month, hourly rates from 150 to 195 dollars, no lock in and 30 days notice. Vendic commits to a response within 60 minutes from 07:00 to 23:00 seven days a week and a 48 working hour turnaround on patches and vulnerabilities. scandiweb states a first response within 24 hours with issues triaged by severity and showstoppers taken first, monitoring around the clock, and pay as you go billing with no published rate. Foundation Commerce publishes cover Monday to Friday 9am to 6pm UK time from 1,200 pounds a month on a 12 month minimum, with no response time attached. elgentos publishes maintenance pricing in three bands and no service levels. ZERO-1, Emico, JaJuMa and Fluid Commerce publish nothing numeric, and in one case the page that should carry it still serves unedited Magento sample data.

Which of these agencies contribute code back to Hyvä?

Five publish something concrete and the depth varies enormously. JaJuMa is furthest in, stating that it is a Core Contributor to the Hyvä theme itself, that it was the very first Magento extension provider to offer official Hyvä compatibility, and that it ships seven extensions named for and dedicated to Hyvä with a significant number of them free and open source. elgentos publishes a GitHub organisation, built Hyvä Checkout support for Paazl and Loqate, and gives away a free Hyvä e-book. Foundation Commerce made four named third party extensions compatible and submitted them to the Hyvä compatibility library. Emico built the Hyvä compatibility module for Tweakwise. Vendic released a PostNL Hyvä Checkout compatibility module as open source without publishing a repository URL. ParadoxLabs contributes upstream to Mage-OS and the Magento Association rather than to Hyvä specifically. Fluid Commerce publishes no contribution of any kind. None of this is scored directly, and all of it is a reasonable thing to ask about, because an agency that has fixed something in the theme has read the theme.

Why does scandiweb rank first, and by how much?

By three points, 78 to 75, and it wins the two criteria that are scarce in this lane while losing ground on the four that are not. It takes full marks on Hyvä register position, listed five times at Platinum with 15+ certified Hyvä developers and 40+ Hyvä projects published in its directory entry, and full marks on delivery scale, with Adobe Commerce Gold Solution Partner, 894+ Adobe certifications, 600+ people across 36 countries, 700+ clients, 2,100+ projects, 23+ years and a 95 NPS. It takes full marks nowhere else. On performance evidence it scores 12 of 22, the same rung as the agency in sixth place, because its one case that names Luma publishes a relative improvement rather than an absolute before and after value, with no measurement tool and no date, and its better numbers sit on cases that never say what the store was running before. Six agencies below it publish better attributed evidence of a Luma migration. On cost and breakage it scores 9 of 16, behind three agencies that publish hours ranges, rate cards or itemised breakage where it publishes a compatibility reassurance and a few weeks. On support it is behind both agencies immediately below it, and on honest causation it takes the middle rung rather than the top. Three points is the honest margin and it comes from credentials rather than from craft.

What should I ask an agency quoting a Luma to Hyvä migration?

Six questions, in this order. How many of my extensions render front end markup, and which of those already have a Hyvä compatibility module? What is the hours range for a retrofit that keeps my design, and what changes if I redesign? Is the checkout in scope, and if not, what is left running on the old front end? Name a client who moved off Luma, give me the case study URL, and tell me what tool the figures were taken with and when. What is your first response time and your patch turnaround, in hours? And how many of your developers hold a Hyvä certification? The fourth question is the one this lane answers better than any other, because eight of nine agencies here publish a measured result for a named build. The sixth is the one almost nobody answers, which is why it carries the most weight on this page.

How can I check these scores myself?

Every entry prints the page each fact was read from, and the reading date sits in the methodology. The six criteria, their weights and the full ladder for each are published on this page, and the same scoring model is published as machine readable structured data, so it can be re-run rather than taken on trust. Re-weight it and the order moves quickly. Drop the certification criterion from 24 to 10 and first place changes hands to an agency publishing a dated, tool attributed Luma migration result. Push cost and breakage above everything and elgentos and ParadoxLabs go to the top together. Weight honest causation heavily and elgentos and Foundation Commerce climb, because they are the two that published something against their own interest. The one thing that will not move whatever you re-weight is the Hyvä tier, because that is read from the vendor's own full register rather than from anybody's marketing, and it is the only fact on this page that no agency here can write.