SAP Commerce EoMM Preparation: What Stops Working and How to Get Ready

SAP Commerce on-premise version 2205 reaches End of Mainstream Maintenance on July 31, 2026 (SAP Help Portal, 2026). After that date, SAP stops delivering security patches, legal compliance updates, and platform improvements for on-prem installations.

This isn’t a soft deprecation. It’s a hard capability cutoff that affects security, compliance, and long-term viability. Over 3,200 companies currently run SAP Commerce (6sense, 2025) — and many haven’t started planning their transition.

TL;DR: After July 31, 2026, SAP Commerce on-prem loses: security patches, legal/tax updates, third-party library updates, Java version support, and SLA-backed enterprise support. You’ll still have access to the software, but running an unpatched commerce platform with customer payment data creates serious risk. Start your migration assessment now — Commerce Cloud migrations take 3–6 months, and July 2026 is closer than it feels.

What Exactly Stops Working After July 2026?

SAP has been a Leader in the Gartner Magic Quadrant for Digital Commerce for 11 consecutive years (SAP News Center, 2025). That leadership is now concentrated entirely on SAP Commerce Cloud. Here’s what the on-prem cutoff means in practice.

No security patches. This is the most critical issue. Your commerce platform handles customer payment data, personal information, and order records. Running an unpatched system with known vulnerabilities isn’t just risky — it may violate GDPR, PCI DSS, and other compliance frameworks.

No legal or tax updates. VAT rate changes, new regulatory requirements, updated tax calculation rules — SAP won’t deliver these for on-prem. You’ll need to implement them yourself or accept compliance gaps.

No third-party library updates. When libraries like Spring, Solr, or Apache components release security fixes, SAP won’t package them for on-prem. Your team will need to handle dependency management directly.

No Java VM support. As Java releases new versions (and deprecates old ones), SAP won’t test or certify on-prem compatibility. Eventually, your platform will run on an unsupported Java version — another compliance and security risk.

Known-problem resolution only. SAP will help with previously documented issues. Encounter something new? That may require additional fees, with no SLA guarantees.

The software doesn’t stop running on August 1, 2026. But running it becomes progressively riskier and more expensive as your team absorbs responsibilities that SAP previously handled.

Why Is SAP Moving Everything to the Cloud?

90% of businesses that migrated e-commerce platforms reported revenue improvements (commercetools, 2024). SAP’s cloud-first strategy reflects a broader industry shift — and the cloud version offers genuine advantages over on-prem.

Continuous updates. Commerce Cloud receives regular feature releases, security patches, and compliance updates automatically. No more scheduling maintenance windows for upgrades.

Managed infrastructure. SAP handles servers, scaling, patching, CDN, and disaster recovery. Your team focuses on business logic and customer experience rather than infrastructure operations.

AI and personalisation. New capabilities like AI-driven product recommendations, intelligent selling services, and personalised merchandising are cloud-only features.

Integration ecosystem. Deeper integrations with SAP S/4HANA, SAP BTP, and third-party services through standardised APIs. Commerce Cloud’s extension framework supports modular, composable architecture.

Composable Storefront. The modern Angular-based frontend (formerly Spartacus) is actively developed for Commerce Cloud. On-prem users don’t receive storefront updates.

The gap between on-prem and cloud capabilities widens with every release cycle. After EoMM, it accelerates.

For a detailed look at Spadoom’s SAP Commerce Cloud capabilities — including pricing, migration methodology, and industry use cases — visit our SAP Commerce Cloud solution page.

How Should You Prepare for EoMM?

83% of data migration projects exceed their budgets or schedules (Bloor Group, 2023). Starting early is the single biggest factor in avoiding that statistic. Here’s a practical preparation timeline.

Now (16+ months before EoMM): Start the assessment. Audit your current customisations, map your integrations, and profile your data. This takes 2–4 weeks and gives you the information needed to plan the migration accurately.

3–6 months before migration start: Define the approach. Direct migration to Commerce Cloud? Hybrid with a custom frontend? Composable architecture? The right answer depends on your team, timeline, and business requirements.

12–16 months before EoMM: Begin the migration. A typical Commerce Cloud migration takes 3–6 months. We completed Franke’s in 90 days — but that required a standards-first approach and experienced resources. Leave buffer for unexpected integration complexity.

3–4 months before EoMM: Go-live and stabilise. Plan for go-live at least 3 months before EoMM. This gives your team time to resolve post-launch issues while still having on-prem support as a safety net.

Key risk: waiting too long. If you start your migration planning 6 months before EoMM, you’ll be rushing. The migration partners with SAP Commerce Cloud expertise are already busy — the closer to the deadline, the harder it is to assemble the right team.

What Are Your Migration Options?

Not every organisation should take the same path. Here’s a quick comparison.

Direct migration to SAP Commerce Cloud (3–6 months). Best for: organisations with SAP-centric teams and deep customisations tied to SAP data models. Preserves your existing investment. Lowest risk. Fastest timeline.

Hybrid approach — Commerce Cloud backend, custom frontend (4–8 months). Best for: organisations that need frontend flexibility beyond Composable Storefront. Keeps SAP’s managed infrastructure while allowing a modern frontend framework (React, Next.js).

Composable commerce (9–15 months). Best for: organisations with mature engineering teams (5+ developers), API-first integration landscapes, and a timeline longer than 12 months. Maximum flexibility, but highest cost and complexity.

For most organisations facing EoMM, direct migration to SAP Commerce Cloud is the pragmatic choice. It’s faster, lower risk, and preserves existing customisation investments. The Franke migration — 90 days, 9 countries, SAP Quality Award — demonstrates what’s possible with the right methodology.

What’s the Cost of Waiting?

47% of IT leaders cite technical debt as a major driver of overspending (IDC, 2024). Every month you stay on unsupported on-prem after EoMM adds technical debt: security risk, compliance gaps, missed feature releases, and rising infrastructure costs.

The hidden costs of waiting include:

• Security incident liability. Running unpatched commerce software with customer payment data creates regulatory exposure under GDPR, PCI DSS, and industry-specific frameworks.
• Talent scarcity. Fewer developers want to work on unsupported platforms. Recruitment becomes harder and more expensive.
• Integration drift. As ERP, payment, and logistics partners update their APIs, your unupdated integrations break — and there’s no SAP support to help fix them.
• Partner availability. Migration partners with SAP Commerce Cloud expertise are a finite resource. As the deadline approaches, availability decreases and rates increase.

Starting now costs less than starting later — both in migration costs and in accumulated risk.

Ready to start planning? We begin with a discovery workshop that audits your current system, maps your integrations, and recommends the right migration path — before EoMM forces a rushed decision. Talk to us.

Frequently Asked Questions

Does SAP Commerce on-prem stop working after EoMM?

No. The software continues to run. But SAP stops delivering security patches, legal updates, third-party library updates, and Java version support. You can still use the platform, but you absorb all maintenance responsibility — including security vulnerability management and compliance updates. For most organisations running commerce platforms with customer payment data, this creates unacceptable risk.

How much does a SAP Commerce Cloud migration cost?

Costs range from CHF 250K for a streamlined lift-and-shift to CHF 800K+ for a complex multi-market migration with significant customisation rework. The main cost drivers are: number of integrations, customisation complexity, data volume, and number of storefronts. We completed the Franke migration (9 countries, Composable Storefront) in 90 days — demonstrating that standards-first approaches reduce both timeline and cost.

Can we extend mainstream maintenance beyond July 2026?

SAP hasn’t announced any extension of the EoMM date. After July 31, 2026, on-prem customers move to customer-specific maintenance only — which means resolution of known problems only, possible fees for new issues, and no SLA guarantees. Extended maintenance may be available at additional cost but doesn’t include the same scope as mainstream maintenance.

What if we can’t migrate by July 2026?

You can continue running on-prem after EoMM, but with reduced support and increasing risk. The practical impact depends on your industry’s regulatory requirements. Financial services, healthcare, and e-commerce platforms handling payment data face the highest compliance risk. If you can’t complete a full migration by July 2026, consider a phased approach: migrate the most critical functions first, then complete the transition in a follow-up phase.

Should we wait for SAP to announce new migration tools?

No. The tools and methodologies for Commerce Cloud migration are mature and well-tested. Waiting for better tooling is a common rationalisation for delayed action. The risk of waiting (compressed timeline, limited partner availability, accumulated technical debt) outweighs the marginal benefit of slightly improved migration tools. Start your assessment now.