Magento Web Development Company: Magento 2 and Adobe Commerce Builds, Integrations, Upgrades and Support

Updated October 2026 · Written and maintained by the Progression Agency strategy team

A Magento web development company designs, builds, integrates and maintains online stores on Magento Open Source and Adobe Commerce, from the catalog and checkout to the ERP connection behind them. We work for brands, manufacturers and distributors whose catalogs, B2B rules or store views have outgrown simpler platforms, and we judge every release by orders, conversion and uptime. Progression Agency is based in New York City and works with clients across the United States and worldwide.

What does a Magento web development company do?

It handles everything that needs a developer on a Magento store: builds, front-end themes, custom modules, integrations, upgrades, performance and security. A good partner also tells you which of those you do not need yet.

Magento 2 and Adobe Commerce builds

A build starts with the data, not the design: attribute sets, product types, categories, store views and the rules that set price and stock. Get those right and the theme, search and checkout have something solid to sit on. Get them wrong and every later change costs more. Our ecommerce development page covers the same principle across platforms; this page is the Magento specialist treatment.

Custom Magento development services: modules, extensions and audits

Custom Magento development services cover the logic no marketplace extension provides: a pricing rule tied to a contract, a configurator, a returns flow or an Admin screen for a team that works differently. We write it as a proper module with its own tests and configuration, so it survives upgrades. Before writing anything we read what is already installed, because many stores carry modules that duplicate each other or were never removed after a trial.

Magento theme development and Magento web design

Magento web design is the storefront shoppers see: category and product templates, search, cart, checkout and account pages. We design with the real catalog, including the longest product names, the products with forty variants and the categories with no images, so the templates hold up after launch. Theme choice, covered below, decides how fast those pages load.

Magento B2B development

Trade and wholesale buyers expect their own prices, payment on account and a fast way to reorder. On Adobe Commerce most of this comes from B2B for Adobe Commerce, which we configure and extend; on Magento Open Source it is custom work or third-party modules. Either way the hard part is the data: which company sees which catalog, at what price, with which approval rules.

Magento checkout customization and payment integration

Checkout changes carry the most risk because they touch revenue directly. We change checkout in small, tested steps: an extra field, a delivery date, a purchase order number, a payment method, a shipping rule. Each change is measured against completed orders before the next one goes live.

Is Magento still the right platform for your store?

Often yes for large or complex catalogs, B2B selling and several store views; often no for a small catalog that a hosted platform would run with less effort. The honest answer depends on what the store does that a simpler platform cannot.

When Magento or Adobe Commerce is the right answer

Magento earns its running cost when the business needs control: deep custom logic in checkout or pricing, thousands of configurable products, several brands or regions in one Admin, a hosting environment the merchant chooses, or B2B features such as negotiated quotes. Those stores tend to need a Magento agency on call, and the platform rewards the investment.

When Shopify, BigCommerce or WooCommerce is the better answer

A store with a few hundred products, standard checkout and no unusual integrations usually spends less and moves faster on a hosted platform. We say so in the first call. Our Shopify agency page and the BigCommerce versus Shopify comparison cover those platforms, and Shopify versus WooCommerce covers the WordPress route.

Magento vs Shopify for complex catalogs

The question is rarely features in general; it is one or two specific needs. If the store depends on company accounts with shared catalogs, on several websites with different currencies, or on code-level changes to checkout, Magento usually fits. If it depends on speed of launch, a small team and predictable monthly cost, a hosted platform usually fits.

Magento Open Source or Adobe Commerce: which edition fits?

Magento Open Source is the free edition the merchant hosts and supports; Adobe Commerce is Adobe’s licensed edition, sold with additional features and Adobe support, including the B2B module. Most of the code-level work on this page applies to both.

Who owns Magento today?

Adobe does. Adobe reported in its quarterly filing with the US Securities and Exchange Commission that it completed its acquisition of Magento Commerce on June 18, 2018. The paid edition is now sold as Adobe Commerce, and the free edition continues as Magento Open Source.

Adobe commerce development on cloud infrastructure

Adobe Commerce development on Adobe’s cloud infrastructure follows Adobe’s deployment process, with environments, build and deploy steps defined by Adobe. On merchant hosting the team designs that pipeline itself. We work in either, and the scope states which.

Which Magento versions are supported, and when should you upgrade?

Under Adobe’s Adobe Commerce lifecycle policy, each 2.4 release gets three years of standard support from general availability, covering quality fixes, security patches and support. Plan the upgrade a year before your release leaves standard support, not after.

What the extra year and the security-only window mean

Adobe offers Adobe Commerce customers on 2.4.6 and 2.4.7 one additional year of support at no additional cost. For 2.4.4, 2.4.5 and 2.4.6 it also publishes a security-only transitional period: isolated security fixes, no quality fixes, and described by Adobe as a one-time exception. Treat that window as time to finish an upgrade, not as a place to stay.

Will there be a Magento 3?

Adobe’s published lifecycle lists 2.4 releases through 2.4.9 and announces no Magento 3. Plan around the 2.4 line and Adobe’s dates, and treat any claim about a future major version as speculation until Adobe publishes it.

How a Magento upgrade runs

We copy production to staging, update the core, then work through extensions and custom modules one at a time, fixing deprecated code and theme overrides as they surface. Integrations are tested with real orders, and the release goes out at a quiet hour with a tested rollback. Most of the effort sits in third-party code, not in Magento itself.

Luma, Hyva or headless: choosing the Magento front end

Luma-based themes suit stores that want the standard storefront adapted; Hyva suits stores that want a lighter, faster theme rebuilt on Magento; headless suits stores that need a separate front end shared across channels. The choice shapes cost, speed and who can maintain the store later.

Hyva theme development services

Hyva theme development rebuilds the storefront templates on Hyva’s stack and replaces or adapts each extension’s front end. According to Hyva’s own announcement, the Hyva Theme became free from November 10, 2025 under the OSL3 and AFL3 licenses, while Hyva Checkout, Enterprise and Commerce remain commercial and Hyva UI is sold as a separate product. Budget for the build work and for any commercial Hyva products you choose, not for the theme itself.

Headless Magento development and PWA storefronts

A headless storefront reads catalog, cart and customer data from Magento’s APIs and renders pages in a separate app. It suits merchants who sell through several front ends or who want front-end releases independent of Magento upgrades. It also doubles the systems to maintain, so we recommend it only when that independence pays for itself. Our headless versus traditional CMS guide explains the wider trade-off.

Where the ranking side lives

Theme choice affects Core Web Vitals and crawlability, and that SEO side of the work is covered on our page on search for Magento stores. Here the focus stays on building and maintaining the storefront.

Magento ERP integration and other integrations

Integrations decide whether the store runs itself or needs staff to rekey orders, stock and prices. We write each one as a data flow with an owner, a schedule and a defined failure path.

Magento integration with NetSuite, Epicor, Sage and QuickBooks

ERP integrations fail at the edges: a new customer the ERP has never seen, a product code that changed, a price list that expired, an order edited after export. We map every field, decide which system is the source of truth for each one and build alerts for the cases that do not match. Where the ERP itself needs work, our ERP development team picks it up.

PIM and OMS connections

A product information system keeps attributes and copy in one place; an order management system routes orders across warehouses and stores. Magento can take either role partly, and the scope settles which system owns what so data is never edited in two places.

APIs, middleware and scheduled jobs

Some integrations call Magento’s APIs directly; some run through middleware; some still depend on files exchanged on a schedule. We pick the simplest pattern that meets the timing the business needs, and document it so the next developer can follow it. Our API development page covers custom interfaces in more depth.

Magento migration services, in both directions

We move stores onto Magento, between Magento versions and, when it is the honest advice, off Magento. Every migration protects three things: data, URLs and integrations.

Magento 1 to Magento 2

Adobe’s Data Migration Tool moves settings, data in bulk and later changes such as new orders and customers from Magento 1 to Magento 2. Themes and customizations do not carry over: developers rebuild them for Magento 2. Stores still on Magento 1 should plan a rebuild rather than a port.

Other platforms to Magento

Moving onto Magento usually follows growth: a catalog, B2B model or set of regions the old platform cannot hold. We map products, customers, orders and URLs before any build work, then rehearse the import until it runs cleanly.

Magento to Shopify migration: when leaving is the honest advice

If a store uses little of what Magento offers, a move to Shopify or Shopify Plus can lower running cost and free the team from upgrades. We assess it fairly, list what would need an app or a workaround, and plan redirects for every indexed URL. Our website migration services page covers the redirect and launch work, and our Shopify ecommerce agency page covers life after the move.

Magento performance optimization and security

Most slow Magento stores are slow for ordinary reasons: undersized hosting, too many extensions, a heavy theme, a cache that is not doing its job or indexers running at the wrong time. Each is measurable and fixable.

Why is Magento 2 so slow on some stores?

Usually because of what surrounds it. We check hosting capacity, full-page cache hit rate, database queries, indexer mode, cron health, the number of extensions observing every request, and the weight of the theme and third-party scripts. The fix list is ranked by effect on real pages, starting with product and category templates.

Magento speed optimization on the front end

Front-end weight comes from JavaScript, images and third-party tags. A Hyva rebuild removes much of the first; image handling and a tag review deal with the rest. We measure before and after on the templates that take the most traffic.

Security patches and the patch cadence

Security fixes arrive through Adobe’s releases and patches during a release’s support period, which is one more reason to stay on a supported 2.4 release. We apply patches on staging first, test checkout and integrations, then release to production.

• Hosting capacity measured at peak traffic, not on a quiet day
• Full-page cache hit rate on category and product pages
• Slowest database queries and the code that triggers them
• Indexers set to update on schedule where the catalog allows
• Cron jobs running, finishing and not overlapping
• Extensions that observe every request, and whether each is still needed
• Theme weight: JavaScript, CSS and images on the busiest templates
• Third-party scripts loaded on every page
• Admin users, two-factor settings and unused accounts

Magento support and maintenance services

A support plan keeps the store patched, monitored and moving forward between projects. It covers a set number of developer hours a month, a response time for incidents and an upgrade roadmap.

Hire Magento developers: a dedicated developer, a project team or a retainer

Hire a dedicated developer when you have steady work and someone to direct it; a project team when the job has a defined end; a retainer when you need support and small changes without a full-time hire.

Hire a Magento developer for a defined job

An upgrade, an integration or a module is usually best as a fixed project with a written scope, acceptance tests and a warranty period. You know the cost before work starts and the code is yours at the end.

Dedicated Magento developers inside your team

When the in-house team needs capacity, our developers join its sprints, use its repository and follow its review rules. A lead on our side reviews the work so quality does not depend on one person.

Code ownership and handover

The merchant owns the code. We work in a repository the merchant controls, document modules and integrations, and hand over access, credentials and deployment notes at the end of any engagement, so changing partners later is routine.

How much does Magento development cost?

Magento and Adobe Commerce work is quoted after a written scope, because cost follows the catalog, the integrations, the front-end choice and the amount of custom code, not the platform name.

Our published ecommerce build rows, for reference

Our website design and development page lists fixed-scope ecommerce rows written for Shopify and WooCommerce builds: ecommerce under 200 SKUs from $34,000 over 12 to 18 weeks, and ecommerce with ERP, PIM or fulfillment integrations from $78,000 over 20 to 32 weeks. Those are not Magento prices. Magento and Adobe Commerce builds, upgrades and integrations are quoted separately after a written scope.

Costs outside the build

Budget also for hosting, any Adobe Commerce license, paid extensions, commercial Hyva products if chosen, payment processing and a support plan after launch. We list each one in the scope so the total is visible before you commit.

How we run a Magento project in four phases

Audit, scope, build and launch. Each phase ends with something you can check: a written report, a signed scope, a working staging store and a launch with a rollback plan.

1. Audit: code, extensions, hosting, integrations and data reviewed, with a written report of risks and quick wins
2. Scope: features, integrations, front-end choice, acceptance tests, schedule and price agreed in writing
3. Build: two-week sprints demonstrated on staging, with integration tests run against real data
4. Launch: content freeze, final data sync, redirects checked, release at a quiet hour, rollback ready, then a warranty period

Magento development partner, not just a vendor

After launch a Magento web development company should stay on the roadmap: the next release, the next integration, the next upgrade date. That continuity is what merchants usually mean when they look for a Magento development partner rather than a one-off build.

How to choose a Magento development agency

Choose a Magento web development company on evidence you can check: code samples, upgrade history, integration experience with your ERP, and how the agency hands over code. Badges and portfolios matter less than answers to specific questions about your store.

Best Magento development company for your store

There is no single best Magento development company; there is the Magento web development company whose experience matches your catalog, integrations and budget. Shortlist on those, then compare written scopes rather than headline rates.

Questions to ask in the first call

Which version would you move us to, and when? Which of our extensions would you remove? How would you connect our ERP? What would you not build? The answers show quickly whether a team knows Magento or just lists it.

How AI assistants answer Magento questions, and what gets a store named

Merchants now ask ChatGPT, Claude, Perplexity, Gemini, Microsoft Copilot and Google AI Overviews questions like which Magento agency handles NetSuite, whether to upgrade or move to Shopify, or what a 2.4 upgrade involves. The answers lean on pages that state specifics plainly, and a Magento web development company that publishes those specifics is easier to name.

What the assistants tend to cite

For platform facts they cite Adobe’s own documentation, such as the lifecycle policy and Experience League guides. For provider questions they draw on agency pages that describe services in specific terms, comparison tables, directory and review profiles, and public code or extension listings.

What a merchant or an agency should publish

Dated upgrade notes, integration pages that name the systems connected, clear comparison tables and short, quotable answers to common questions. Our AEO for ecommerce page covers how a store gets cited in those answers.

A Magento agency in New York, working with merchants nationwide

As a Magento web development company based in New York City, we work remotely with merchants across all 50 states and worldwide. New York merchants can meet the team in person; everyone else gets the same process over video, a shared repository and a staging store.

Progression is independent and is not affiliated with Adobe. Magento, Adobe Commerce and Hyva are trademarks of their respective owners, named here only to describe the platforms we work on.

Related services for Magento merchants

A Magento web development company handles the store itself; these pages cover the work around it: ranking it, marketing it and building what sits next to it.

• Ecommerce development across platforms, including our short take on Magento suppliers
• Magento SEO for layered navigation, canonicals and store views
• Ecommerce SEO for catalogs on any platform
• Shopify SEO and WooCommerce SEO if you move
• Ecommerce app development for a mobile app on top of the store
• ERP development when the back office needs its own work
• Custom software development for tools beyond the store
• Ecommerce website redesign for a new storefront
• Product configurators for made-to-order catalogs
• Conversion rate optimization after launch
• Ecommerce marketing and ecommerce email marketing
• Custom software versus off-the-shelf tools for the build-or-buy question

Frequently asked questions