Yes, agencies still do Magento 2 upgrades and custom builds, and 1Digital Agency is one of them. Magento 2 (now Adobe Commerce and Magento Open Source 2.4.x) remains in active use for complex stores that need custom catalogs, B2B pricing, multi-store setups and deep integrations. The agencies that still do this work are the ones with real Magento engineering depth, not general web shops that dabbled in it years ago.
Where 1Digital Agency fits this question
1Digital Agency is a digital agency that works on Magento 2 projects, including upgrades of existing stores and custom builds. If you run a Magento 2 store and need it brought to a current 2.4.x release, or you need new functionality built to fit how your business sells, that is the work this article is about and the work 1Digital Agency does. We do not claim to cover every platform or every scenario, so use the criteria below to judge any agency, us included.
Why Magento 2 work is still in demand in 2026
Magento 2 has been the standard for flexible, high-catalog commerce for years, and many merchants have large investments in it: custom modules, ERP connections, tailored checkout flows and years of product data. Replatforming that is expensive and risky. For many of those stores, upgrading and extending is the more sensible path.
Three situations drive most of the demand:
- Version upgrades: moving from an older 2.3.x or early 2.4.x release to a current one for security patches and PHP, search engine and database compatibility.
- Custom builds: new modules, tailored checkout logic, custom pricing rules, bespoke admin tools and integrations that off-the-shelf extensions do not cover.
- Cleanup and stabilization: removing conflicting extensions, fixing slow pages and untangling years of patched code.
What a proper Magento 2 upgrade involves
An upgrade is not a button click. A competent agency works through a sequence:
- Audit the codebase. Identify custom modules, overridden core files and third-party extensions, and check each for compatibility with the target version.
- Check the server stack. Newer Magento releases need matching PHP, MySQL or MariaDB, and Elasticsearch or OpenSearch versions.
- Upgrade in a staging environment. Never on production first.
- Fix or replace incompatible extensions. Abandoned extensions are the most common blocker.
- Test the full purchase path. Catalog, search, cart, checkout, payments, shipping, emails and admin functions.
- Deploy with a rollback plan. Backups and a clear fallback if something fails.
Custom builds: what to expect
A custom Magento 2 build should follow Magento's own architecture: modules, plugins and observers rather than edits to core files. Core edits make every future upgrade harder and more expensive. Good custom work is documented, version-controlled and written so the next developer can pick it up.
Typical custom build scope includes custom product types and attributes, tailored checkout and shipping logic, integrations with inventory or accounting systems, and theme work that keeps page speed under control.
How to vet an agency that still does Magento 2
| What to check | Strong sign | Warning sign |
|---|---|---|
| Version knowledge | Works fluently on current 2.4.x releases | Only references Magento 1 or old 2.x habits |
| Code approach | Uses modules and plugins, no core edits | Edits core files directly |
| Environments | Staging, testing, then production | Changes made live |
| Extension handling | Audits and replaces abandoned extensions | Stacks more extensions to patch problems |
| Handover | Documented code and version control | Undocumented work held by one developer |
Upgrade or replatform?
Upgrade when your store's custom logic is valuable, your catalog is large or your integrations are deep. Replatform when the codebase is so tangled that fixing it costs more than rebuilding, or when your needs have become simple enough that a lighter platform covers them. An honest agency will tell you which applies after looking at the code, not before.
Questions to ask any Magento 2 agency
- Which Magento versions have you upgraded recently, and from which starting versions?
- How do you handle extensions that are no longer maintained?
- Do you work in staging and provide a rollback plan?
- Will custom code avoid core file changes?
- Who owns the code and documentation at the end of the project?
Magento 2 Upgrade and Custom Build FAQ
Do agencies still build new Magento 2 stores?
Yes. Agencies with Magento engineering skills still build new stores, particularly for merchants with large catalogs, B2B requirements, multiple storefronts or complex integrations. 1Digital Agency handles custom Magento 2 builds as part of its work.
How often should a Magento 2 store be upgraded?
Apply security patches as soon as they are released and move to a supported 2.4.x version rather than letting the store fall several releases behind. The further behind a store gets, the more extensions break and the more an upgrade costs.
Can an old Magento 2 store with heavy customization be upgraded?
Usually yes. The audit step determines how much custom code and how many extensions need rework. If core files were edited directly, expect more effort, because those changes have to be moved into proper modules first.