Hyvä compatibility: Which Magento extensions work?
Every paid Magento extension that touches the frontend needs a Hyvä compatibility module before it renders correctly under Hyvä. Without one, the extension's backend logic still runs — admin config, observers, events — but its visible output is silent. Customers see nothing where the extension was supposed to render.
The good news: most major vendors now ship a Hyvä compatibility module of their own. The bad news: the long tail of smaller and older extensions don't, and you need a custom compat for each.
This post is the practical guide to checking what works and what doesn't, plus what custom compat costs when you need it.
The first place to check: compat.hyva.io
compat.hyva.io is the community-maintained Hyvä Compatibility Tracker. Every paid Magento extension that has a Hyvä compat module — vendor-supplied or community-contributed — is listed there with status, version compatibility, and a link to the module.
Before any Hyvä migration scoping call, the merchant should know:
- The full list of paid extensions on their store (vendor + version + license status)
- Which of those are listed on compat.hyva.io with status "Compatible" (vendor compat available)
- Which are listed as "Workaround" (community-contributed compat exists)
- Which are listed as "Not Compatible" or "Unknown" (you need custom compat)
This 15-minute exercise saves weeks of project-discovery time.
Categories of extension compatibility
In rough order of "how much work it is":
1. Vendor-shipped Hyvä compat (zero work)
The extension vendor publishes their own Hyvä compat module. Installation is composer require + a config flip. 30 minutes per extension.
Vendors that ship Hyvä compat as of 2026:
- Amasty (most of their major extensions)
- Mageplaza (most modern extensions)
- Aheadworks (selected extensions)
- Mirasvit (selected extensions)
- MGS (selected extensions)
- Mageworx (selected extensions)
- Yotpo, Klaviyo, Bloomreach (the marketing tools)
- Stripe, Adyen, Klarna, PayPal, Worldpay, Mollie, Braintree (payment gateways)
- Signifyd, Riskified (fraud)
- ShipperHQ, ShipStation (shipping)
This list grows every quarter. Check compat.hyva.io for current status — the vendor list is more important than any blog post.
2. Community-contributed Hyvä compat (low work)
Open-source compat modules contributed by Hyvä community members for widely-used commercial extensions. Often published under MIT license, often by Hyvä-specialist agencies (including us — we publish ours via our GitHub org).
Installation is composer require from a public registry. The risk is maintenance — community compat is only as current as someone's last commit. Verify the compat module supports your extension version before counting it as a free win.
3. Custom Hyvä compat needed (medium-to-high work)
When neither vendor nor community has shipped a compat module, you build one. Cost ranges:
- Display-only extensions (banners, badges, content blocks, social proof widgets): £1,500–£3,000 per extension, 1–3 days of work
- PDP / PLP-touching extensions (product variant selectors, configurators, image galleries): £2,500–£5,000 per extension, 3–5 days
- Checkout-touching extensions (payment, fraud, shipping rate calculators, gift cards, store credit): £4,000–£8,000 per extension, 5–10 days plus order-flow testing
The variance comes from how deeply the extension hooks into the frontend. Display-only is straightforward template re-implementation. Checkout-touching needs integration testing across real orders.
What a Hyvä compat module actually does
For the technical readers — the pattern from docs.hyva.io:
- A new Magento module that depends on the original extension's module
- Layout updates that target the original extension's blocks and replace them with Hyvä-rendered versions
- Hyvä-native templates (.phtml files) re-implementing the extension's frontend output using Tailwind classes and Alpine.js components
- Magic strings and event dispatchers preserved so the extension's admin configuration carries over unchanged
- Optionally, an Alpine store if the extension needs reactive client-side state (e.g. a configurable price calculator)
The pattern is well-documented; the work is mechanical but tedious. A specialist builds these 2x faster than a generalist learning the pattern.
When to skip compat and switch extensions
Sometimes the right answer isn't to build compat — it's to replace the extension with a Hyvä-native alternative. Two scenarios where we recommend swapping:
1. The extension is deeply abandoned. If the vendor hasn't shipped updates in 18+ months, building compat now is sinking budget into something that will need replacing anyway. Better to replace with a maintained Hyvä-native alternative.
2. A native Hyvä module exists. When there's a Hyvä-first equivalent that does the same job at comparable cost, swapping is cleaner than maintaining a custom compat in perpetuity. Often the Hyvä-native version performs better and has a smaller code footprint.
We tell you which path is cheaper at the scoping stage — not after you've already commissioned the compat module.
The "we need to know our extension list" problem
The single biggest cause of Hyvä migration scope creep is discovering an extension mid-project that wasn't on the original list. Each surprise extension adds 1–2 weeks to the timeline and £1.5k–£8k to the budget.
How to avoid this: do the extension inventory thoroughly before the scoping call. Include:
- All extensions in
composer.json(vendor + version) - Any extensions in
app/code/*not delivered via Composer - Any third-party themes or modules even if "we don't really use them"
- Any extensions in admin → System → Extension Manager (or composer.lock)
- Custom in-house modules that touch the frontend
Pasting composer.json + composer.lock into a shared doc is usually enough.
What about ZIP-installed extensions?
Some older or budget extensions still ship as ZIP files for manual install rather than Composer. These are usually the worst case for Hyvä migration because:
- The extension code is often older, less maintained
- No version tracking means harder to verify compat module versions
- Composer-based vendor compat usually targets Composer-installed extensions only
If you have ZIP-installed extensions, plan to either:
- Upgrade to a Composer-distributed version (often paid)
- Replace with a Hyvä-native alternative
- Build custom compat (the most expensive option)
ZIP-installed extensions are why Magento upgrades take longer than they should; same problem applies to Hyvä migrations.
The compat module library — why it compounds
A specialist Hyvä agency accumulates a library of custom compat modules over time. By their 10th Hyvä migration, they reach for a pre-built module instead of writing one from scratch — that's the difference between a 6-week and 10-week project on the same scope.
For us specifically: we've shipped 100+ custom Hyvä compat modules across our client work, with a meaningful subset open-sourced via our GitHub org. New clients benefit from the library — extensions that would be a 2-week custom-compat build for a first-time Hyvä team are a 30-minute install for ours.
This is the practical case for picking a specialist: the library compounds.
Pricing — what compat work actually costs
Per-extension custom compat cost:
| Complexity | Time | Cost |
|---|---|---|
| Display-only (banner, badge, content block) | 1–3 days | £1,500–£3,000 |
| PDP-touching (variant selector, configurator) | 3–5 days | £2,500–£5,000 |
| Checkout-touching (payment, fraud, shipping) | 5–10 days | £4,000–£8,000 |
| Cart-touching (gift card, store credit, bundles) | 3–7 days | £3,000–£6,000 |
| Customer account (subscriptions, wallets, returns) | 3–7 days | £3,000–£6,000 |
Bundled into a Hyvä migration, compat work is part of the overall fixed-price quote. Standalone (you have an existing Hyvä site and one new extension to add), the per-extension prices above apply.
Open-source contribution policy
When we build compat for a widely-used commercial extension, we publish it under MIT via our GitHub org. The wider Hyvä community benefits and the next customer who needs it gets it free.
Client-specific custom work (bespoke modules unique to one merchant) stays private by default. We'll discuss open-sourcing it at handover if the client agrees and there's wider community demand.
Bottom line
Most major Magento extensions have vendor or community Hyvä compat available — check compat.hyva.io before scoping. For the long tail of extensions without compat, custom modules cost £1.5k–£8k each depending on complexity. A specialist Hyvä agency has accumulated a library that means custom-compat work is faster + cheaper than starting from scratch.
The extension count is the single biggest variable in Hyvä migration cost. Get the inventory right before the scoping call.
Next steps
- Browse compat.hyva.io for the current vendor compat list
- See the Hyvä Compatibility services page
- See the Hyvä compatibility module glossary entry for the technical primer
- Read Hyvä module development: when do you need custom modules
- Book a scoping call — we'll audit your extension list and quote against it