Magento 2 Upgrade + Hyvä
The combination most Magento stores actually need. A security upgrade onto a supported release and a bespoke Hyvä frontend, planned and delivered as a single project.
Done separately these are two rounds of regression testing, two staged releases and two periods where the team is watching the store instead of running it. Done together it is one.
One disruption, not two.
2.4.5 and 2.4.6 stopped receiving security patches on 11 August 2026. Most stores on them also have a Luma frontend that is costing them in Core Web Vitals, ad quality score and conversion. Those are two problems with one overlapping fix.
Upgrading first and rebuilding the frontend six months later means paying twice for the same regression testing, the same integration checks and the same launch window. The combined project shares all of it.
- ✓ You are on 2.4.6 or older and the frontend is dated too
- ✓ You have one launch window available, not two
- ✓ Core Web Vitals are hurting SEO or paid performance
- ✓ Your PIM, ERP or 3PL integrations have to keep working throughout
Good fit if
- ? You are already on a supported release - the Hyvä migration alone is cheaper
- ? The frontend is fine and you only need the version work
- ? You are considering leaving Magento entirely
Worth a conversation first if
What the combined project covers
Version and patch work
Core and extensions brought onto a supported release, with the hosting stack raised to requirement.
Bespoke Hyvä frontend
Designed in-house for your catalogue, built on Tailwind and Alpine.js. Not a demo theme with your logo on it.
Extension compatibility
Every third-party extension inventoried and tested against both the new release and Hyvä before the build starts.
Integration regression testing
PIM, ERP, 3PL and CRM connections tested against a copy of production, not a clean install.
Core Web Vitals sign-off
LCP, CLS and INP measured on real field data before and after, and signed off before launch.
Two weeks of hypercare
Close monitoring after the staged release, with the engineers who built it still on the project.
How it runs
Audit
Version position, extension inventory, integration map and a performance baseline. The £950 audit is credited in full against this build.
Design
UX and interface drawn for your catalogue, reviewed with you before a line of frontend code is written.
Build
Version work and frontend build in parallel on staging, under code review and version control.
Launch
Staged release, two weeks of hypercare, then Core Web Vitals and accessibility measured again on real pages.
Ready to get started?
Tell us about your project and we'll put together a plan - no obligation, no jargon.