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.