Skip to content
Free tool, 2026 edition

Hyvä compatibility checker: will your extensions work with Hyvä?

Pick your installed Magento extensions from the list below, get a per-extension Hyvä compatibility status in 30 seconds. Database of 50+ popular extensions, hand-checked against Hyvä Themes 1.3+ in 2026. Knowing this BEFORE you start migration saves $5-15k in surprise rework.

  • 50+ popular extensions covered (paid + free)
  • Per-extension status: ✓ Compatible / ⚙ Hyvä module available / ⚠ Not yet / ✗ Blocker
  • Generates a copy-paste audit report you can share with your dev team
Adobe-Certified Magento developer who builds on Hyvä Updated quarterly · last sweep Q2 2026
The checker

Pick your extensions, get verdicts in 30 seconds

Tick every extension installed on your store. Filter by name or category. Click "Check selected" to see the verdicts. Click "Generate report" for a copy-paste markdown audit you can paste into Slack or send to your dev team.

No extensions match: try clearing the search or category filter.

selected

Your compatibility verdict

selected. ready need work blockers

Markdown audit report: copy & paste
  • 50+ Extensions in the database

    Hand-curated list of the most-installed paid & free Magento extensions across performance, SEO, B2B, search, loyalty, subscriptions, shipping, RMA, page-builder, payment, marketplace, GDPR and analytics. We add new entries every quarter.

  • Hand-checked Tested against Hyvä 1.3+ in 2026

    Every status row was verified by installing the extension on a Hyvä 1.3+ staging store, running the frontend through real customer flows, and confirming whether the vendor ships an official Hyvä compat module or whether bridging work is needed.

  • Honest Unknowns flagged, not faked

    When a vendor has gone silent or we haven’t been able to test, we mark the row ? Unknown instead of guessing. Risk-honest reports beat polished-but-wrong ones every time.

  • $5-15k Average rework saved

    Knowing which extensions are blockers before the migration starts, not after, is the single biggest predictor of a migration that lands on time and on budget. Most surprise-rework comes from extensions discovered post-cutover.

What the verdicts mean

Six things to know about Hyvä extension compatibility

Read these once, then re-run the checker and the verdicts will all make sense, including which Partials are 6-hour ports and which are 30-hour ones.

  • What “compatible” really means

    A “Compatible” verdict means the extension renders its frontend HTML correctly under Hyvä, doesn’t inject Knockout/RequireJS, doesn’t break checkout, and survives a clean Hyvä reindex. Backend admin panels work unchanged on every status, the verdicts only judge storefront behaviour.

  • How Hyvä compat modules work

    A “Hyvä module” row means the vendor (or community) ships a small bridge package, usually free, that re-renders the extension’s frontend in Tailwind+Alpine instead of Luma’s Knockout. You install vendor/extension-hyva next to vendor/extension, run setup:upgrade, and the storefront just works.

  • Why “Partial” needs porting work

    A “Partial” row means the backend works perfectly but the frontend has Knockout/RequireJS pieces that need rewriting in Alpine. Typical port budget: 6 to 30 hours per extension depending on the size of its frontend surface (a quote-cart UI is bigger than a static info-block).

  • What blockers actually look like

    A “Blocker” row means the extension can’t cohabit with Hyvä at all, usually because it owns the entire checkout flow (one-step-checkout extensions are the classic case). The fix is replacement, not bridging: swap to Hyvä Checkout (free, included with the theme since 1.3) and migrate any custom payment integrations to it.

  • How Hyvä Checkout replaces OSC

    Mageplaza, Amasty, and IWD One-Step-Checkout extensions are all marked Blocker because Hyvä Checkout already does what they do, one-page checkout, < 1s render, every major gateway. Hyvä Checkout is a commercial licence (the Hyvä Theme itself is free and open source since 10 November 2025). Drop the OSC extension, install Hyvä Checkout, configure your payment methods, done.

  • How to test before committing

    For every “Partial” or “Unknown” row, spin up a Hyvä staging copy of your store with the extension installed, run your top 5 customer flows (PDP → cart → checkout → order → account), and document any visual / functional gaps. Two days of testing per uncertain extension saves weeks of post-migration surprises.

From audit to deploy

The 5-step Hyvä migration process this report fits into

Run the checker, get a written audit, plan the ports, test on staging, deploy with the cutover and rollback plan agreed in writing. Same process for every store I’ve migrated.

  1. 01

    Audit

    I clone your repo (or work off a snapshot), run `bin/magento module:status`, list every composer-installed third-party module, and cross-reference it against this checker’s database plus a vendor-by-vendor compat scan against Hyvä 1.3+. Output: a written extension audit. ~2 days.

    Extension audit
  2. 02

    Compat check

    Each extension gets a verdict: Compatible / Hyvä module / Partial / Not yet / Blocker / Unknown, with a port-budget estimate for every Partial and a replacement plan for every Blocker. Unknowns get a 2-hour spike to lock the verdict. Output: locked compat matrix.

    Locked verdicts
  3. 03

    Plan port

    For Partials, spec the Alpine rewrite per extension, sized in days. For Blockers, spec the swap-out (Hyvä Checkout / native Hyvä alternative). For Hyvä modules, queue the install. Output: line-item migration plan with fixed prices per extension.

    Migration plan
  4. 04

    Test

    Set up a Hyvä 1.3+ staging copy, install every Hyvä compat module, port every Partial, replace every Blocker, run regression on top 5 customer flows for each, and verify Lighthouse 90+ is preserved. Iterate until UAT-clean. Output: passed UAT report.

    UAT-clean staging
  5. 05

    Deploy

    New Hyvä theme deployed alongside Luma, traffic shifts via DNS. The cutover time and the rollback plan are agreed with you in writing before launch. Smoke-test every customer flow against the live order log for the first 4 hours. Output: live Hyvä storefront with extension parity.

    Live + monitored
What your audit might look like

Three real-world audit profiles

Where does your store land? The third profile is the one to catch BEFORE you sign a migration contract: Blockers in the critical-path flow can stretch a 6-week project to 14.

  • Mostly Compatible

    Lucky audit…

    • 80% of extensions Compatible / Hyvä module
    • 0-2 Partial, small port budget ($1k to $3k each)
    • Zero Blockers (or just OSC, replaced by Hyvä Checkout)
    • Migration scope: 4-6 weeks at standard pricing
    • Total surprise-rework risk: low
    • Best for: stores with mostly-recent paid extensions from major vendors
  • Heavy Partial Work

    Real porting effort…

    • 5+ Partials with frontend customisation
    • Per-extension port budget $3k to $8k
    • 1-2 Blockers needing replacement
    • Migration scope: 8-10 weeks, pricing scales with port count
    • Total surprise-rework risk: medium
    • Best for: stores 3+ years old with older extension stack
  • Has Blockers

    Replacement needed…

    • 3+ Blockers OR Blockers in critical-path flow (checkout / catalog)
    • Replacement plan needed before scope locks
    • Migration scope: 10-14 weeks; might delay launch
    • Per-blocker swap budget $4k to $12k
    • Total surprise-rework risk: high without this audit
    • Best for: knowing this before you sign the migration contract
What clients say

Stores I’ve audited & migrated to Hyvä

Real clients, real Hyvä migrations: including the rough audits where Partials and Blockers caught us before they bit.

Magento work and feedback View Upwork profile

  • Illustration of Magento 2 development work for a sports footwear and hockey shop
    Sports footwear and hockey shop, Netherlands
  • Illustration of Magento 2 development work for a photo printing supplies wholesaler
    Photo printing supplies wholesaler, Netherlands
  • Illustration of Magento 2 development work for an educational toys and books shop
    Educational toys and books shop
  • Kishan has done an excellent job in a timely manner. He is very knowledgeable, has a very positive attitude, easy to communicate.

    Z. K.Magento 2 client
  • He is technically strong, approaches problems thoughtfully, and focuses on stable, long-term solutions.

    E. H.Magento 2 client
  • Kishan was a pleasure to work with! He is highly skilled, professional, and delivered outstanding results on time.

    M.Magento 2 client
FAQ

Honest answers to the questions everyone asks about Hyvä compatibility

How is “compatibility” defined here?

A verdict of Compatible means the extension renders its frontend HTML correctly under Hyvä 1.3+, doesn’t inject Knockout or RequireJS dependencies, doesn’t break the cart or checkout flow, and survives a clean reindex + setup:upgrade. Backend admin behaviour is identical regardless of frontend theme, every status here judges only the storefront. So if a verdict says “Compatible”, you can install it next to Hyvä without porting work; if it says anything else, the row description explains exactly what gap remains.

What does “Hyvä module” mean, do I install something separate?

Yes. A Hyvä module verdict means the vendor (or community) ships a small bridge package, usually free, distributed via composer or marketplace, that re-renders the extension’s frontend in Tailwind+Alpine instead of Luma’s Knockout. The pattern is: composer require vendor/extension-hyva alongside the original vendor/extension, run setup:upgrade, and the storefront just works. Both packages are required, the original handles the backend and business logic, the Hyvä one re-skins the frontend.

My extension says “Partial”, what work is needed?

A Partial verdict means the backend works perfectly under Hyvä but parts of the frontend, usually small AJAX widgets or PDP-block JS, are still in Knockout/RequireJS and render either broken or not at all. The fix is rewriting the frontend templates in Alpine.js + Tailwind. Port budget is quoted per extension, depending on how big the frontend surface is. A simple PDP info-block is a small port; a quote-cart UI or marketplace vendor-storefront is a much larger one. The Partial-row description on the checker tells you which surface needs work.

I have Blockers, what do I do about them?

Blockers can’t cohabit with Hyvä, they own a flow Hyvä also wants to own (most often the entire checkout). The fix is replacement, not bridging: remove the blocker, install the Hyvä native equivalent, migrate any custom config across. The most common case is a One-Step-Checkout extension, replaced by Hyvä Checkout (free, included in Hyvä 1.3+). For each Blocker the checker shows you what to swap to. Replacement effort depends on how many custom payment/shipping integrations you had hooked into the old flow, and is quoted per scope.

Why is One-Step-Checkout marked Blocker if Hyvä has its own checkout?

Exactly because Hyvä has its own checkout. Mageplaza, Amasty and IWD One-Step-Checkout extensions all rewrite Magento’s entire checkout in Knockout, which is the layer Hyvä replaces. Two checkouts can’t cohabit. Hyvä Checkout already does what those extensions do (one-page render, < 1 second, every major payment gateway, Klarna/Adyen/Stripe-element bridges) and ships free with Hyvä 1.3+. Removing the OSC extension also drops the licence fee, net win on cost, performance, and stability.

How accurate / current is the database?

Every row was hand-verified by installing the extension on a Hyvä 1.3+ staging store and running real customer flows, not auto-scraped, not vendor-claimed. The database is updated every quarter, plus ad-hoc whenever a vendor ships a new Hyvä bridge. Last full sweep: Q2 2026. If you spot a row that looks out of date based on your own testing, message me on WhatsApp, I’ll re-verify and update for everyone.

My extension isn’t in the list, what should I assume?

Treat it as ? Unknown: assume it might need work until proved otherwise. The fastest way to lock the verdict is a focused spike, install the extension on a Hyvä staging copy, click through the customer flows, screenshot any visual or functional gaps. That gives you the verdict, the porting effort, and the risk profile. If you have several unknowns, send the list via the audit form below and I’ll spike the lot together.

I’m about to start a Hyvä migration, what do I do with this report?

Three steps:

  1. Lock all Unknowns via focused spikes, never start a migration with unknowns in scope.
  2. Quote every Partial with a fixed-price port budget (use the per-extension hours estimate × your dev rate).
  3. Plan replacements for every Blocker, spec the swap-out (e.g. Hyvä Checkout for OSC) before the migration kicks off.

Add the totals and you’ve got a realistic Hyvä migration scope before you sign anything. Most surprise-rework on Hyvä projects comes from skipping this audit and discovering Partials / Blockers mid-build.

How much does it cost to port a “Partial” extension?

Per-extension port effort depends on the frontend surface:

  • Small frontend surface (one PDP block, one info-widget)
  • Medium surface (multi-block, AJAX category filter, customer-account page)
  • Large surface (quote-cart UI, vendor storefront, multi-step wizard)

Every port is part of a fixed written quote for your scope.

Does this work for custom in-house extensions?

The checker covers third-party extensions only, in-house custom modules need a per-module audit. Same verdict scheme applies: read the module’s frontend code, check whether it uses Knockout / RequireJS, count the number of phtml templates that reference Magento’s frontend JS APIs, estimate the Alpine port effort. As a quick rule of thumb, a custom module with no frontend code is automatically Compatible; one with 2 or more phtml templates and AJAX is almost always Partial. Send the module list via the audit form for a written verdict per module.

You said Hyvä 1.3+, what about earlier versions?

Hyvä 1.3+ is the recommended baseline because it ships Hyvä Checkout natively (no separate licence) and enables the official Adobe Commerce 2.4.9 native-Hyvä integration. Hyvä 1.2.x is still supported by every vendor compat module here, but if you’re upgrading the theme anyway, jump to 1.3+. Hyvä 1.1.x and earlier, some compat modules may have minor regressions; treat anything older than 1.2 as legacy and budget a small upgrade tax.

After all this audit work, is Hyvä migration still worth it?

Yes, almost always. Even with 5-10 Partials and 1-2 Blockers, the Hyvä migration is usually worth it: a faster storefront that tends to help conversion (measure it on your own store), and faster future feature builds (Tailwind+Alpine is faster to build with than Knockout). The audit just makes sure you go in with eyes open and a fixed budget, not with surprise rework eating the savings.

Send the report for a written audit + fixed-price migration plan

Paste the markdown report from the checker (or just describe your stack) and I’ll come back with verdicts on every Partial / Unknown, port budgets per extension, and a fixed-price scope.

Message me on WhatsApp

No form to fill. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Message me on WhatsApp

No form to fill. Send me a quick message. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Helpful to mention

  • Company
  • Store URL
  • Number of installed extensions
  • Main blocker / concern
  • Migration timeline
  • Edition

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

Fixed quote Discuss the scope and next steps Get a fixed quote