Magento, now branded as Adobe Commerce in its commercial tier and Magento Open Source in its free tier, remains one of the most divisive platforms in agency commerce. It is simultaneously the platform that produces some of the highest-revenue retainers in the industry and the platform that produces the largest agency losses when scoped carelessly. In 2026, with Adobe Commerce growth slowing relative to SaaS competitors and Adobe shifting its enterprise focus toward Adobe Experience Cloud, the agencies still serving Magento clients are running a different playbook than they were five years ago. Most of the new revenue is in maintenance retainers and migrations off Magento; new greenfield builds are increasingly rare outside true enterprise. This Magento agency services guide is for owners and ops leads who already know how to operate on the platform and now need a practical 2026 view of pricing, retainer composition, migration economics, team structure, and risk.
Key Takeaways:
- Greenfield Magento builds in 2026 typically land between $80K and $400K, with migrations off Magento now exceeding new builds in agency revenue.
- Maintenance retainers on Magento are the highest-margin retainers in agency commerce: $4K to $25K per month, 65 to 75 percent gross margin.
- Adobe Commerce gross margin per client is 12 to 20 percent higher than Shopify Plus because of platform complexity barriers to in-housing.
- Migration-off Magento engagements (to Shopify Plus or BigCommerce) now run $60K to $250K and have become a productized service line in their own right.
- The single biggest risk on Magento is hosting and infrastructure; under-spec hosting destroys timelines and margin.
The Magento Market in 2026
According to recent BuiltWith ecommerce technology data, Magento and Adobe Commerce together still power tens of thousands of mid-market and enterprise stores worldwide, though the install base has been gradually shrinking as brands migrate to Shopify Plus or BigCommerce. For agencies, this means two parallel revenue streams:
- Serving Magento clients who are not migrating. These are typically $10M to $200M brands with deeply customized stacks, complex B2B, or international footprints that make migration unattractive. The retainers are large, sticky, and high-margin.
- Migrating Magento clients to SaaS platforms. Brands below $25M are increasingly moving to Shopify Plus or BigCommerce. Migration projects have become a productized service line in their own right.
A healthy Magento agency in 2026 typically derives 40 to 60 percent of revenue from maintenance retainers, 25 to 40 percent from migrations, and the remainder from new builds and ad-hoc projects. Five years ago, those ratios were inverted; new builds dominated.
Where Magento Still Wins
Use this filter on every inbound RFP. If two or more "Magento wins" apply and the client has the budget for proper hosting and a real retainer, Magento is defensible. If two or more "Magento loses" apply, productize a migration instead.
| Scenario | Magento wins | Migrate to SaaS | |---|---|---| | $25M plus brand with deep customization | Yes | | | Complex B2B with multi-tier pricing, EDI, punchout | Yes | | | International with 5 plus locales and tax engines | Yes | | | Custom catalog logic that SaaS cannot replicate | Yes | | | $5M to $25M brand wanting "set it and forget it" | | Yes | | Internal team has no Magento experience | | Yes | | Hosting bills are eating gross margin | | Yes | | Brand wants headless without an engineering team | | Yes |
The single most consistent qualifier is engineering depth, both inside the client and inside the agency. Magento punishes shallow staffing and casual hosting decisions in ways that newer SaaS platforms do not.
Pricing the Magento Build (When You Still Build New)
New Magento builds are increasingly rare, but they happen. Realistic 2026 pricing:
| Tier | Project fee | Timeline | Best for | Team | |---|---|---|---|---| | Tier 1 (focused) | $80K to $160K | 16 to 24 weeks | $5M to $15M brands with limited customization | 4 to 5 | | Tier 2 (standard) | $160K to $280K | 22 to 32 weeks | $15M to $50M brands with B2B or international | 5 to 7 | | Tier 3 (enterprise) | $280K to $700K plus | 28 to 52 weeks | $50M plus with ERP, PIM, multi-region | 8 to 12 |
Magento builds have higher hour counts than SaaS equivalents because:
- Theme architecture (Hyva, Luma) requires deeper engineering than Shopify themes.
- Integration with ERP, PIM, and OMS is rarely "just an app."
- Performance optimization is non-optional; default Magento performance is poor.
- Hosting architecture (Cloud, EE, custom) materially affects build cost.
- QA across customer groups, websites, and stores is multiplicative.
A reliable rule of thumb: a Magento build of comparable feature scope to a Shopify Plus build will cost 40 to 80 percent more in hours and carry 8 to 12 percent lower gross margin. Price accordingly, or do not bid.
The Maintenance Retainer: Where Magento Pays
Magento maintenance retainers are the highest-margin recurring revenue in agency commerce in 2026, and the reason most Magento agencies are still profitable. The math is simple: clients cannot in-house Magento expertise easily, so they pay for it externally at premium rates.
| Retainer tier | Monthly fee | Hours / scope | Best for | Renewal rate | |---|---|---|---|---| | Care plan | $3,500 to $8,000 | Patches, security, monitoring, monthly performance review, 8 to 16 hours dev | $10M to $25M brands | 85 to 95 percent | | Growth retainer | $8,000 to $16,000 | Above plus 30 to 60 hours dev, CRO, merchandising | $25M to $80M brands | 75 to 88 percent | | Embedded team | $16,000 to $25,000 plus | 2 to 3 FTE equivalents, weekly priority slot | $80M plus with active roadmap | 70 to 85 percent |
Operating discipline that protects retainer margin:
- Bill annually wherever possible. Annual billing reduces churn by 25 to 40 percent and converts retainer revenue into deferred revenue on the balance sheet.
- Cap hours, do not bank them. Banked hours create end-of-year scope cliffs.
- Include hosting in the retainer where you can. Marking up managed Magento hosting (Sonassi, Hypernode, Pronto Marketing, Adobe Commerce Cloud reseller) at 20 to 40 percent is standard and clients rarely negotiate it.
- Document security as an SLA, not a deliverable. "We will patch critical CVEs within 24 hours" sells better than "we will run monthly scans."
A senior Magento developer working with a junior pair can typically support 8 to 14 care-plan or growth retainers. The margin on a $7K retainer with $800 of hosting cost and 12 hours of dev time is typically 65 to 75 percent. Few agencies outside Magento achieve that combination of fee size and gross margin.
To stand up the retainer infrastructure properly, see our retainer management software comparison and the recurring billing platform most maturing shops deploy by year three.
The Magento Migration Service Line
Migrations off Magento have become the single fastest-growing service line for Magento agencies in 2026. The typical buyer is a $5M to $25M brand whose Magento bills (hosting, agency, license) have grown to a point where Shopify Plus or BigCommerce TCO is materially cheaper. A productized migration framework:
| Destination | Project fee | Timeline | Common pitfalls | |---|---|---|---| | Shopify (standard) | $30K to $70K | 10 to 16 weeks | Customer history truncation, SEO redirects | | Shopify Plus | $70K to $180K | 14 to 24 weeks | B2B replication, subscription state, app parity | | BigCommerce | $60K to $160K | 12 to 22 weeks | Catalog complexity, customer group mapping | | Headless (Next.js + Shopify/BigCommerce) | $150K to $350K | 20 to 32 weeks | Performance budget, CMS migration |
A reliable migration pricing model:
- Discovery (mandatory): $8K to $20K, two to four weeks. Audit of existing customizations, integration inventory, data shape, SEO baseline.
- Migration build: Standard project pricing per destination (above).
- Data migration: $8K to $30K typically as a separate SOW line. Customer records, order history, subscription state, loyalty balances.
- Stabilization retainer: $4K to $10K per month for the first 90 days post-launch.
Migrations are unusually profitable for three reasons: the discovery sprint qualifies the buyer rigorously, the destination platform is often simpler than Magento, and the post-migration retainer is sticky. Agencies that productize migrations typically see 55 to 65 percent gross margin on the build and 65 to 75 percent on the post-migration retainer.
For pricing math and scope templates, see our project pricing calculator and our platform migration hub.
Team Structure for a Magento Practice
A workable 12-person Magento agency in 2026:
- 1 partner / commercial lead
- 1 head of delivery
- 1 senior Magento architect (PHP, Hyva, Adobe Commerce)
- 2 mid-level Magento developers
- 1 senior front-end lead (Hyva or headless)
- 1 integrations engineer (PHP, Node, Python)
- 2 senior PMs (each running 6 to 8 retainers and 1 active project)
- 1 designer / merchandising lead
- 1 QA + launch ops
- 1 strategy / CRO lead
This shape supports roughly $2.5M to $3.5M in revenue at 55 to 65 percent gross margin with retainer-heavy mix. The most common mistake is hiring a third Magento developer before hiring an integrations engineer. The integration surface on Magento is larger than on any SaaS platform; an integrations specialist closes more deals than they cost.
For staffing ratios, anchor on a team utilization calculator and review capacity against retainer commitments weekly.
Hosting: The Make-Or-Break Decision
Magento performance is fundamentally a hosting problem. The cleanest determinant of project success on Magento, across hundreds of agency P&Ls we have reviewed, is whether the hosting was specified by the agency or the client. Three patterns work:
- Adobe Commerce Cloud (enterprise). Magento-managed cloud, expensive, predictable. Best for enterprise clients with budget.
- Sonassi, Hypernode, Pronto Marketing. Specialist Magento hosts. Best for $10M to $50M clients.
- Custom AWS or GCP with managed services. Best for $50M plus clients with internal engineering depth.
What does not work:
- Generic VPS hosting.
- Bargain shared hosting from a registrar.
- A client-chosen host with no Magento-specific tuning.
Mark hosting up 20 to 40 percent inside the retainer. Refuse to support sites on hosts you do not approve; the support cost of un-tuned hosting will destroy the project's economics.
Profitability Benchmarks
| Metric | Healthy range | Warning sign | |---|---|---| | Project gross margin | 40 to 55 percent | Below 30 percent | | Retainer gross margin | 65 to 75 percent | Below 50 percent | | Average retainer per client | $7K to $14K per month | Below $4K | | Retainer client LTV | $250K to $700K | Below $150K | | Annual revenue per FTE | $200K to $280K | Below $160K | | Senior developer utilization | 60 to 75 percent | Below 50 or above 85 percent | | Migration revenue share | 20 to 40 percent | 0 percent |
The most informative number on this list is migration revenue share. Agencies above 20 percent migration revenue are positioned for the next five years; agencies at 0 percent migration revenue are over-exposed to Magento's slowing growth.
Anonymized Scenario: A 14-Person Magento Agency in Manchester
A Manchester-based Magento agency we have benchmarked grew from $2.8M to $4.6M in annual revenue between 2023 and 2025 with four operating changes:
- Productized "Magento to Shopify Plus" and "Magento to BigCommerce" migration sprints at $48K and $42K respectively. Sold 9 migrations in 14 months, generating $400K plus of new revenue.
- Restructured care plans into three SKUs ($4.5K, $9K, $18K per month) and converted 78 percent of bespoke retainers within nine months. Average retainer grew 31 percent.
- Standardized hosting on Sonassi and Hypernode with a 30 percent retainer markup. Added approximately $90K of annual gross profit with no additional delivery hours.
- Hired one integrations engineer in early 2024. Cleared a 5-month backlog of integration work and lifted retainer gross margin from 58 percent to 71 percent.
P&L outcome: retainer share moved from 44 percent to 58 percent, migration share grew from 4 percent to 27 percent, EBITDA went from 14 percent to 26 percent. The owner reported that the most consequential change was productizing the off-ramp; clients who could not afford to stay on Magento now had a defined path with their existing agency, rather than churning to a Shopify shop.
Productized Service Lines That Sell
Six productized Magento offerings that consistently run profitably:
- Magento to Shopify Plus Migration Sprint ($55K to $140K, 14 to 20 weeks): Productized data migration, theme rebuild, app parity.
- Magento to BigCommerce Migration Sprint ($50K to $120K, 12 to 18 weeks): Same shape, B2B-focused.
- Magento Security Audit + Hardening ($8K to $20K): CVE patch review, hosting review, observability baseline.
- Hyva Theme Migration Sprint ($25K to $60K): Migration from Luma to Hyva for performance and maintenance.
- Magento Performance and Core Web Vitals Sprint ($10K to $25K): Cache, image pipeline, database tuning.
- B2B Configuration Sprint ($20K to $50K): Customer groups, multi-tier pricing, EDI, punchout.
Productized services collapse discovery cycles, predict utilization, and let junior PMs run them. Pair them with a productized service catalog so buyers can self-select.
Tooling and Operations Stack
A workable 2026 stack for a Magento agency:
- Local + staging: Warden, Docker, Magento Cloud staging environments.
- Deployment: Magento Cloud pipelines, custom CI on AWS or GCP, or DeployHQ for smaller stacks.
- Monitoring: New Relic, Datadog, Blackfire for performance.
- Security: Sansec eComScan, Mage Report, custom WAF rules at host level, documented incident response runbook.
- Agency ops: Time tracking, retainer billing, capacity planning bound together in an agency management platform.
- Client communication: A central client portal so requests do not live in email.
The most consequential tooling investment is the system that ties sold scope to delivered hours per retainer and per project. Without it, the third migration in a quarter quietly absorbs the time the first two over-ran.
Risks and How To Price Them
Magento engagements carry risks that newer SaaS platforms do not. Price them explicitly:
- Adobe roadmap risk. Adobe Commerce roadmap shifts are a real concern. Document this in the SOW with a clear platform-risk clause.
- Engineer scarcity. Senior Magento talent is shrinking. Pay premium rates and standardize on a smaller, stronger team.
- Security exposure. Magento is a high-value target for ecommerce fraud and skimmer attacks. Build the security retainer into every engagement, no exceptions.
- Performance under load. Magento performance is fragile. Always include a performance baseline and ongoing monitoring in the retainer.
- Migration pressure from the client's CFO. Many Magento clients will eventually leave for SaaS. Build the migration practice now so the off-ramp is yours.
For the legal language around these risks, see our SOW vs MSA guidance and your agency liability protections.
FAQ
Should we still take new Magento builds in 2026?
For $25M plus brands with complex B2B, international footprint, or custom catalog logic, yes. For $5M to $25M brands considering Magento for the first time, recommend Shopify Plus or BigCommerce instead. The build will be cheaper, the TCO lower, and the client will not blame you for ongoing platform costs in three years.
What gross margin should a Magento agency target?
A healthy blended gross margin is 55 to 65 percent with retainers above 65 percent and projects at 45 to 55 percent. Magento agencies typically run higher retainer margins than SaaS-platform agencies because of the platform-specialist premium.
How big should the migration practice be?
20 to 40 percent of revenue, depending on how aggressively your client base is migrating. Agencies with 0 percent migration revenue are over-exposed to Magento's slowing growth; agencies above 50 percent are effectively running a migration shop and should consider whether their long-term identity is Magento or platform-agnostic.
Should we offer Hyva theme migrations?
Yes, if you have at least one developer who has shipped two or more Hyva builds. The performance and maintenance gains are real, and the projects are scoped cleanly enough to productize. Refuse to bid Hyva work without that experience; the support cost of a poorly built Hyva theme is severe.
How do we compete with offshore Magento shops?
Don't compete on price. Compete on observability, security, retainer SLAs, and migration capability. Offshore shops rarely match domestic agencies on incident response, post-launch retainer execution, or productized migration off Magento. That is your wedge.
Closing
A profitable Magento agency in 2026 is a maintenance-and-migration business that occasionally builds new sites. The retainer margin is unmatched in agency commerce; the migration practice is the bridge to whatever your firm looks like in 2030. Treat both as core, not as defaults you fall back into.
If you are scaling a Magento practice and want to see how AgencyPro helps you run capacity, retainers, and profit-per-client in one place, book a demo and we will walk through the metrics that move first.