SAP Commerce On-Prem Support Ended Yesterday. Now What?

July 31, 2026 has come and gone. Mainstream maintenance for SAP Commerce on-premise, the platform most people still call Hybris, ended last week (SAP Help Portal, 2026). This is no longer a deadline post. The deadline is behind you.

If your shop still runs on-prem today, nothing broke on August 1. Your storefront is up, orders are flowing, and that is exactly what makes this phase dangerous: the cost of doing nothing is invisible until it is not.

TL;DR: Mainstream maintenance for SAP Commerce on-premise (release 2205, the final on-prem version) ended July 31, 2026. From August 2026 you have four realistic paths: run unsupported and absorb the risk, negotiate customer-specific maintenance, migrate to SAP Commerce Cloud (including the new ERP Edition for mid-size companies), or replatform off SAP. We have migrated Hybris shops in as little as 90 days (Franke, SAP Quality Award). This post gives you the honest math for all four options. Talk to us about your situation.

What Actually Changed on August 1

“End of mainstream maintenance” is precise SAP vocabulary, so let us be precise about it. Since August 1, 2026, for SAP Commerce on-premise:

• No regular security patches. When the next CVE lands in a bundled library, SAP will not ship a fix for your release. Your commerce platform, the system holding customer accounts and touching payment flows, accumulates unpatched vulnerabilities from now on.
• No legal and tax compliance updates. VAT changes, invoicing rules, privacy-driven changes: you maintain those yourself now.
• No new Java certifications and no platform improvements. The code you run today is the code you will run in three years, on an ageing runtime.
• Support only on special terms. SAP offers customer-specific maintenance arrangements beyond this point. SAP has not published a general price list for these; the terms are negotiated per contract, and everything we have seen in practice puts them well above what mainstream maintenance cost. Confirm the specifics with your SAP account executive before you budget around this option.

We covered the mechanics in depth before the deadline in SAP Commerce EoMM: what it means and the 2026 migration checklist. Both remain accurate. What has changed is your negotiating position and your clock: over 3,200 companies run SAP Commerce deployments (6sense, 2025), and the ones that waited are now all shopping for the same delivery capacity.

Option 1: Do Nothing and Absorb the Risk

This is the default option, because it requires no decision. It is also the only option whose cost grows every month.

Honest assessment: for a small, low-change B2B shop behind a hardened network, running unsupported for six more months while a migration is prepared can be a defensible, calculated risk. Running unsupported with no migration plan is not a strategy, it is a deferred incident.

The math that matters:

• Your security exposure compounds. Every unpatched CVE in your stack stays unpatched.
• Your compliance burden shifts to you. A VAT rule change now means custom development on a frozen platform.
• Your insurance and audit posture degrades. “We process payments on software whose vendor ended maintenance” is a sentence your CISO will eventually have to say out loud.

We did the cost-of-waiting math in detail here. The summary: waiting does not reduce the migration bill, it adds a risk premium on top of it.

Choose this only as an explicit, time-boxed bridge with a signed-off risk assessment, while one of the other three options is already in motion.

Option 2: Customer-Specific Maintenance

SAP will keep supporting you beyond mainstream maintenance, on individually negotiated terms. This buys real things: a patch channel for critical issues and a vendor on the hook.

What it does not buy: a future. You pay a premium to stand still. No new features, no roadmap, and the money you spend on extended terms is money not spent on the migration you will still have to do. In our experience this option makes sense in exactly one scenario: a large, complex estate that genuinely cannot migrate inside 12 months and needs a compliant bridge.

If that is you, negotiate now rather than after the first incident, and put the end date of the arrangement in the same board slide as the migration start date.

Option 3: Migrate to SAP Commerce Cloud

The natural path, and the one where your existing investment survives. Your data model, your business logic, much of your customization, and above all your ERP integration carry over. This is the option we know best, so judge our bias accordingly, and then check it against the referenced projects.

Track record, with real numbers:

• Franke: Hybris to Commerce Cloud in 90 days, SAP Quality Award. The full playbook is public: 30 days of preparation, ruthless scope management (35% of customizations eliminated), parallel workstreams.
• ANWR Group: 5M+ product SKUs on a headless B2B/B2C platform, 80% faster product data sync.
• Distrelec: monolith to headless architecture, 70% faster time-to-market, +15% conversion.

The ERP Edition angle for mid-size companies. Until recently, the honest objection from many on-prem shops was that full Commerce Cloud is oversized and priced for enterprises. SAP Commerce Cloud ERP Edition changes that calculation: a packaged, ERP-integrated deployment at a lower entry point, aimed exactly at the mid-market segment that has been sitting on on-prem because nothing else fit. Spadoom is a pilot partner for ERP Edition; we wrote up what it offers SMEs here. If “Commerce Cloud is too big for us” was your reason to wait, that reason expired this year too.

Realistic timelines from August 2026: 6 to 12 months for a typical migration, 4 to 6 for a disciplined fast-track, 90 days at the aggressive end with full preparation. See the solution page or the on-prem campaign page for the packaged assessment offer.

Option 4: Replatform Off SAP

Fairness requires saying it: leaving SAP Commerce entirely is a legitimate option, and for some companies the right one. If your commerce needs have simplified down to what Shopify Plus does out of the box, or your architecture strategy is genuinely composable and you have the engineering organization to own it, a replatform deserves a real evaluation. We compared the composable path honestly after EoMM here.

But look at who is producing most of the “leave SAP now” content: replatform vendors. Read those pieces with the same bias-check you applied to us two sections ago, and put numbers on what their pitch decks tend to gloss over:

• ERP integration rebuild. Your SAP ERP integration (pricing, ATP, credit checks, order orchestration, master data) is the most valuable and least visible asset in your current platform. On a replatform you rebuild it from zero, usually via middleware that becomes its own project.
• B2B depth. Contract pricing, punch-out, approval workflows, multi-level account structures: mature in SAP Commerce, often add-ons or custom builds elsewhere.
• The migration is not smaller. Catalog, customer, and order data still have to move. You save nothing on the data workstream; you add the integration workstream.
• Total timeline. Realistic replatform projects for an SAP-integrated estate run 6 to 12 months and beyond, which is the same window as an SAP-to-SAP migration, without the carry-over.

If you run SAP ERP and your B2B requirements are real, the total cost of ownership case usually lands on staying in the SAP stack. If you do not, run the evaluation honestly and make the vendors show integration line items, not just license comparisons.

The Timeline Math, Side by Side

The uncomfortable common denominator: three of the four paths involve months of running unsupported. That exposure started last week whether you decided anything or not. The only variable still under your control is how long it lasts.

What We Would Do in Your Position

First week: a two-page risk assessment of the current estate (versions, customization surface, integration inventory, compliance obligations). First month: a decision between options 2, 3, and 4 with real quotes on the table, not directional estimates. That sequencing matters because SAP-side negotiation leverage and partner delivery slots both get worse as more of the waiting cohort moves.

We have done this assessment enough times that we run it as a fixed-scope engagement, and the 90-day playbook shows what the aggressive end of execution looks like when the preparation is right.

Your support ended yesterday. Your options did not. They just got a clock attached.

Request a migration assessment or start with the on-prem decision page.