Magento 2 and Adobe Commerce, done properly.
This is the work the agency is built around. Security upgrades onto a supported release, Hyvä frontend migrations, full replatforms, and the PIM, ERP and 3PL integrations that sit behind them.
Our engineers learned this on stores for globally recognised brands, where a slow page or a failed deployment is a board-level problem. The same review process, staging environments and accessibility requirements apply here whatever the size of the store.
- Adobe Commerce
- Magento 2
2.4.5 and 2.4.6 stopped getting security patches on 11 August 2026.
2.4.4 went unsupported in April. If your store is on any of them it is still taking payments, still passing PCI scans on the surface, and quietly accumulating unpatched vulnerabilities that nobody is going to fix.
Upgrading is not the hard part. The hard part is the third-party extensions - that is where the cost sits, and it is the part most quotes guess at. We inventory every extension and every integration before anyone writes a number down, which is why our quotes do not move halfway through.
- ✓ You are on Magento 2 or Adobe Commerce and want to stay
- ✓ You are running 2.4.6 or older and know you are exposed
- ✓ Page speed is costing you in SEO, ad quality score or conversion
- ✓ Your catalogue is connected to a PIM, ERP or 3PL that has to keep working
Good fit if
- ? You are evaluating platforms from scratch - Shopify may be the honest answer
- ? Your turnover is under £500k and Magento's overhead may outweigh it
- ? You need the store live in under six weeks
Worth a conversation first if
What 2.4.8 actually requires
The reason an upgrade is a project rather than a command. Most of these are the hosting stack, not the application - and each one has to be right before the store will run.
- PHP
- 8.3 or 8.4
- Database
- MySQL 8.4 LTS or MariaDB 11.4
- Search
- OpenSearch 2.x - Elasticsearch support removed
- Cache
- Valkey 8.x
- Message queue
- RabbitMQ 4.x
- Biggest cost driver
- Third-party extension compatibility
What we do on Magento
Six things, done to the same standard whether the store turns over £200k or £20m.
Security upgrades
Onto a supported release. Fixed price, fixed scope, every integration regression tested on staging before it goes near production.
Hyvä frontend migration
Tailwind and Alpine.js in place of the old stack. Dramatically lighter pages and top-tier Core Web Vitals, with your catalogue, checkout and extensions intact.
Replatform and new builds
Bespoke storefronts drawn for your catalogue and the way people actually buy from you - not a demo theme with your logo dropped on it.
PIM, ERP and 3PL integration
An upgrade is where these quietly break. We inventory every connection first, test each one, and hand you the list of what was touched.
Core Web Vitals work
LCP, CLS and INP tuned against real field data from your own traffic, not a lab score on an empty cache.
Magento Care
Patching, monitoring and a named engineer on rolling monthly support, so the store never falls this far behind again.
What it costs
Ranges rather than a single number, because the spread is real: it depends on how many third-party extensions you run and how far behind you are. The audit is what turns a range into a fixed price.
Health & Upgrade Audit
Six stages, one senior engineer, and a document that says exactly where the store stands and what it costs to fix.
- Version, patch and vulnerability position
- Full extension compatibility inventory
- Core Web Vitals baseline from field data
- Costed, prioritised remediation plan
Security Upgrade
Onto a supported release, with every integration regression tested before launch.
- Core and extension upgrades
- Hosting stack brought to requirement
- Staged rollout
- Two weeks of hypercare
Upgrade + Hyvä
The one most stores actually need: supported release and a frontend rebuild in a single project, so the store is disrupted once rather than twice.
- Everything in the security upgrade
- Bespoke Hyvä frontend
- UX and design in-house
- Core Web Vitals sign-off
Hyvä Frontend Migration
For stores already on a supported release that need the speed and the redesign, not the version work.
- Bespoke Hyvä theme
- Checkout and cart UX
- Extension compatibility pass
- Cross-device QA
Replatform / New Build
A new Magento 2 store, or a move onto Magento from somewhere it has outgrown. B2B, multi-store and Adobe Commerce builds start at £60,000.
- Discovery and technical spec
- Bespoke design and build
- Data and catalogue migration
- Integration build
Magento Care
Three tiers of ongoing patching, monitoring and development time.
- Security patches applied on release
- Uptime and performance monitoring
- Named engineer
- Monthly development allowance
Apart from the fixed-fee audit, all prices here are indicative. You get a fixed quote once we have scoped the work. The £950 audit is credited in full against any project over £10,000 booked within 60 days. Offer price against a £1,950 list, valid until 31 October 2026. Every price here is our fee. The Hyvä licence (about €1,000 per production domain, plus about €500 for Hyvä Checkout) and any Adobe Commerce licence (from around £15,000 a year) are paid to those vendors directly.
Not sure which version you are on?
Send us the URL and we will tell you the release, whether it is still supported, and what that means - free, and with no obligation to do anything about it.
How a Magento project runs
Audit
Version position, extension inventory, integration map and a performance baseline. You get the findings whether or not you go ahead with us.
Scope and fixed price
The audit turns the range into a number. Scope is written down, and so is what is not in it.
Build on staging
Coding standards, version control, code review. Every integration tested against a copy of production, not a clean install.
Launch and hypercare
Staged release, two weeks of close monitoring, then Core Web Vitals and accessibility measured again on real pages.
Magento services in detail
Each one has its own page with scope, price and what is included.
Magento Health & Upgrade Audit
Six stages, one senior engineer, and a document that tells you exactly where your store stands and what it costs to fix.
Read moreMagento 2 Security Upgrade
Unsupported stores moved onto a supported release. Fixed price, fixed scope, regression tested, two weeks of hypercare.
Read moreMagento 2 Upgrade + Hyvä
Supported release and a bespoke Hyvä frontend in one project - £19,500 to £29,000, so the store is disrupted once rather than twice.
Read moreMagento 2 Hyvä Theme Development
A fast, lightweight Hyvä frontend for your existing Magento 2 store, built for speed, Core Web Vitals and conversion.
Read moreMagento Replatform & New Build
A new Magento 2 store, or a move onto Magento from a platform you have outgrown. £25,000 to £45,000, or from £60,000 for B2B and Adobe Commerce.
Read moreMagento Care
Patching, monitoring and a named engineer on rolling monthly support - £750, £1,850 or £3,500 a month.
Read moreFind out what shape your store is actually in.
Five days, one senior engineer, and a document that tells you where the store stands and what it costs to fix. £950, credited in full against any project over £10,000 booked within 60 days.