Magento 2.4.x version upgrades
Minor and patch version upgrades, including the ones that skip several releases because the store has sat still for two years.
Magento Upgrades
Magento Upgrade Services
We upgrade Magento 2 and Adobe Commerce stores — the version jump itself, the PHP move that usually comes with it, the extensions that will not come along quietly, and the testing that tells you it worked before your customers do.
Magento & Adobe Commerce engineering from Massachusetts, serving e-commerce businesses across the United States.
Technical expertise
- Magento 2.3 → 2.4.x upgrades
- Adobe Commerce & Adobe Commerce Cloud
- Mage-OS
- PHP 7.4 → 8.x migration
- Composer dependency resolution
- Extension replacement & rewriting
- Hyvä and Luma themes
- Data patches & declarative schema
- Staging environments and CI/CD
Overview
What we do, and why it matters
Most stores that are behind on Magento did not decide to be. An upgrade got quoted, the number looked big for something with no visible payoff, and it went to next quarter. Then the extension vendor stopped shipping updates, the PHP version went end of life, and next quarter got harder than this one.
The work is mostly not the upgrade command. It is finding out what your store actually depends on, deciding what to replace and what to rewrite, and building the environment where all of that can go wrong somewhere other than production. We scope it that way, and we tell you which parts are predictable and which are the ones that make estimates wrong.
Services
What's included
PHP version upgrades
Moving to a PHP version that is still getting security fixes, and fixing the custom code and extensions that break when you do.
Extension compatibility
Working out which third-party modules have a compatible release, which need replacing, and which were abandoned by their vendor and now belong to you.
Custom code review
Preferences and overrides that fight the new core, deprecated APIs, and the copy of a core class somebody pasted into a module in 2019.
Staging and testing
An environment that matches production closely enough to be worth testing on, plus a checklist of the flows that have to still work — checkout, payment, tax, shipping, admin.
Deployment and rollback
A deploy plan with the maintenance window, the order of operations, and the way back if something surfaces that testing did not.
Adobe Commerce upgrades
The same work on Adobe Commerce, including B2B modules and the cloud deployment pipeline where you are on Adobe Commerce Cloud.
Why Emyrix
What you get working with us
You find out what it involves before you commit
The audit comes first: current version, PHP, extension inventory, custom code, and where the risk actually sits. If the honest answer is that a rebuild is cheaper than the upgrade, we would rather say so at the start.
The store comes back working
Checkout, payments, tax, shipping and the admin flows your team uses daily get tested explicitly, because those are what an upgrade breaks and what nobody notices until an order fails.
You are not back here in a year
Customizations get moved into Magento extension points as we go, so the next upgrade is smaller than this one instead of the same size again.
FAQ
Frequently asked questions
How long does a Magento upgrade take?
It depends almost entirely on the extensions and custom code, not on how many versions you are behind. A reasonably standard store with a handful of well-maintained extensions is a matter of weeks including testing. A heavily customized store with abandoned modules can be a lot longer, and the audit is what tells the two apart. We would rather give you a number after looking than before.
Do we have to upgrade at all?
Eventually, because security patches stop being released for a version once its support window closes, and a store that cannot be patched is a store waiting to be a news story. But the timing is a business decision and there is usually more room in it than a vendor countdown suggests. We will tell you where you actually stand.
What happens to our extensions?
Each one gets checked for a compatible release. Where there is one, it comes along. Where the vendor has gone quiet, the options are replacing it with something maintained, rebuilding the part of it you actually use, or taking on maintaining it yourself — and we will tell you what each costs before you pick.
Will the site go down?
There is a maintenance window for the deploy, usually short and scheduled when your traffic is lowest. The work before it happens on a staging environment, not on your live store.
Can you upgrade PHP without upgrading Magento?
Sometimes, and it is a question to ask — if your Magento version supports a newer PHP than you are running, that is a smaller job with a real security benefit. More often the two are tied together, and doing them separately means doing the testing twice.
We are on Magento 1. Is that an upgrade?
No, and the distinction matters: Magento 1 to Magento 2 is a rebuild with a data migration attached, not an upgrade. It is scoped and priced differently. If a rebuild is not this year's project, OpenMage LTS keeps a Magento 1 store on supported PHP and getting security fixes in the meantime.
Related
Keep exploring
Work with Emyrix
Tell us about your store
Send us the URL and we will look at it — version and patch status, speed, caching, indexing, checkout — and tell you what we found.