SAP ECC 2027 Deadline: Options for Manufacturers

The SAP ECC 2027 deadline is December 31, 2027, when mainstream maintenance ends for SAP ERP 6.0 on enhancement packages 6, 7 and 8. Optional extended maintenance runs through December 31, 2030 for a premium of two percentage points. After that, or if you skip it, SAP moves you to customer-specific maintenance. ECC keeps running throughout.

For a mid-size manufacturer with one or two ECC instances and a dozen plant systems hanging off them, the date matters less than the order of decisions it forces: what to pay SAP between 2028 and 2030, whether to convert or reimplement, and how to keep MES, quality and customer portal work moving while that gets settled.

What exactly ends on December 31, 2027?

Mainstream maintenance for the core applications of SAP Business Suite 7 ends on that date. SAP's maintenance strategy page lists those core applications as SAP ERP 6.0, CRM 7.0, SCM 7.0, SRM 7.0 and SAP Business Suite powered by SAP HANA, and the 2027 date covers the latest three enhancement packages.

Older enhancement packages already passed their date. Arne Schmidthals, Business Development Chief Expert at SAP, confirmed in a March 2025 interview with Natuvion that mainstream maintenance for ERP 6.0 with EHP 0 through 5 ended on December 31, 2025, and that extended maintenance is offered only for EHP 6, 7 and 8. If your system is on EHP 5 or lower, you have been in customer-specific maintenance since January 1, 2026.

To check your enhancement package, open the Status screen in SAP GUI and look at the installed software component SAP_APPL. As ecosio's walkthrough explains, the middle digit flags HANA capability and the last digit is the EHP, so 617 is ERP 6.0 with EHP 7 and 618 is EHP 8. The S/4HANA 2040 commitment comes from SAP's February 2020 announcement, which also set the current Business Suite 7 dates.

What does SAP extended maintenance cost through 2030?

Extended maintenance costs two percentage points more on your maintenance basis (the license value your annual support fee is calculated from), for every support offering, from January 1, 2028 through December 31, 2030. That wording is on SAP's maintenance strategy page and matches the 2020 announcement.

Two points on the rate is more than two percent on the bill. In 2009, Computerworld reported SAP Enterprise Support pricing at 22% of license fees per year. On that rate, a manufacturer with a $1,000,000 maintenance basis paying $220,000 a year would pay about $240,000 a year for extended maintenance, roughly 9% more. Your contract may carry a different rate or discount, so run the numbers on your own basis.

The scope stays close to mainstream maintenance. SAPinsider's October 2026 summary quotes SAP's release strategy describing it as similar to mainstream maintenance at an additional fee, and SAP training material saying it adds no new features, functions or enhancement packages. Legal changes and support packages keep arriving, which for a US manufacturer mostly means tax, payroll and year-end reporting updates.

What happens under customer-specific maintenance?

Customer-specific maintenance starts automatically when mainstream or extended maintenance ends, and you keep paying your full maintenance fee. SAP stops delivering legal changes and support packages, stops guaranteeing technology updates, and drops its response-time SLAs.

SAP Note 52505, which defines the phase (a published copy dated November 2024 is public), lists the restrictions: no delivery of legal changes, no support packages, no guarantee of technology updates such as new database or operating system versions, and no support for new interfaces. Known problems are still covered, but you may have to pay for SAP to solve new ones, especially in custom enhancements. The service level agreements for initial response times and corrective measures are no longer delivered. Upgrade paths SAP provided before the phase began stay available, so an upgrade from an older EHP to EHP 8 should still be open; confirm the path for your system.

The practical effect depends on what runs in ECC. A plant that runs US payroll in ECC HCM stops getting SAP's tax table and reporting updates. A plant that runs only finance, materials management and production planning feels it as a support and security problem instead: a priority-one incident with no response-time commitment, and an auditor or cyber insurer asking for patch evidence.

Did SAP change the ECC dates in 2025 or 2026?

No. The 2027 and 2030 dates are unchanged as of October 2026. SAP did add three things that change the math: a paid transition option that runs ECC in SAP's private cloud through as late as 2035, new maintenance commitments from July 2026 that make it easier to mix SAP and third-party support, and an October 2026 notice about third-party databases after 2030.

The SAP ERP, private edition, transition option

SAP announced this offering in February 2025 as an ECC subscription usable from 2031 through 2033, and says it is not a maintenance prolongation of SAP ERP. SAP's August 2025 details set the conditions:

• Systems must be migrated to SAP ERP, private edition (ECC under a RISE with SAP subscription) on SAP HANA before December 31, 2030. HANA is the only supported database.
• Each subscribed system must be at least 2 TB, and products not included in the option need mitigation coverage (SAP Note 3591251).
• The option is only available together with SAP's Max Success Plan, charged on top of the transition option price.
• Customers signing in 2026 get a standard 20% price uplift when they switch in 2031. The uplift for 2027 and later signings has not been disclosed.

An update on the same page dated October 13, 2026 says subscriptions may now run until December 31, 2035, with further prerequisites. SAP describes the offering as designed for its "largest and most complex customers." The 2 TB floor alone rules out many mid-size ECC systems, so for most readers here 2030 remains the planning date.

The July 2026 maintenance commitments

On July 9, 2026 the European Commission accepted binding commitments from SAP in case AT.40823 on how it sells on-premise maintenance. SAP's support page says they took effect July 10, 2026, apply globally to all current and future customers, and run for 10 years. The parts that matter for an ECC decision:

• You can split your SAP estate into separate Commercial Installations and, for each one, choose a different SAP support model, a different maintenance provider, or no maintenance. A split does not trigger repricing of licenses. SAP handles split requests within six months, and an approved split takes effect on the next January 1, April 1, July 1 or October 1.
• For products where customer-specific maintenance is the only available phase, you can terminate the licenses and their maintenance on three months' written notice before the end of the initial or renewal term.
• If you leave SAP support and come back, the reinstatement fee is waived and back maintenance is capped at the lower of 50% of the fees for the gap or six months of payments.
• In a divestiture, you can transfer the divested business's user licenses to the buyer without following SAP's split program rules.

Before July 2026, SAP's all-or-nothing rule made third-party support a bet on your entire SAP estate. Now a manufacturer can keep SAP support on the system it plans to convert and move a separate, stable installation to another provider. SAP lists what it considers technically integrated in SAP Note 3776551, so have your contract team read it before planning a split.

Third-party databases and Java after 2030

If your ECC system runs on a non-HANA database such as Oracle, IBM Db2 or Microsoft SQL Server, SAP's October 7, 2026 notice matters more to them than anything above. SAP's reseller and support agreements with third-party database vendors for these legacy environments end after 2030. SAP will stop database-specific support, including kernel patches and kernel security patches for those environments. A system conversion from Business Suite 7 on a third-party database to S/4HANA is available only until the end of 2030; after that, SAP says only greenfield transitions (new implementations) will be possible. Support arrangements for Java 8 and JEE5 on NetWeaver AS Java 7.5 also end with 2030.

What are a mid-size manufacturer's options after 2027?

You are making two separate choices: who supports ECC from 2028, and where your ERP ends up. Support can come from SAP extended maintenance, SAP customer-specific maintenance or a third-party provider. The destination can be S/4HANA through RISE with SAP, S/4HANA on premise, SAP's public cloud ERP, another vendor's ERP, or ECC for as long as it holds up.

RISE with SAP is SAP's program for existing on-premise customers, ECC shops included, to move to SAP Cloud ERP Private (the current name for S/4HANA Cloud Private Edition) in an SAP-managed cloud. SAP GROW is built on S/4HANA Cloud Public Edition, and SAP describes it as designed for companies new to SAP, so an ECC customer will mostly hear RISE from its account team. S/4HANA can also run on premise; SAP's own RISE FAQ addresses customers who already do that.

Moving to S/4HANA takes one of two broad routes. A system conversion carries your configuration, data and custom code forward and then remediates whatever S/4HANA no longer supports. A new implementation starts clean and migrates data into it. The amount of custom ABAP and the number of plant interfaces usually decide which is cheaper, and if your database is not HANA, the October 2026 notice puts a hard end-2030 date on the conversion route.

Rimini Street announced in June 2025 that it supports all SAP ECC 6.0 and S/4HANA releases through 2040 and claims savings of up to 50% on annual support fees. Spinnaker Support also supports ECC past SAP's dates. Those savings figures are the vendors' own claims, so get a quote. Leaving SAP support ends SAP-delivered legal changes and new SAP functionality, and the provider's own fixes and tax updates replace them.

Plenty of companies have not decided yet. Gartner figures reported by The Register in June 2025 said over 60% of SAP customers remained on ECC 6 on premise with no decision yet to move.

The rows turn on four facts: your database, how much custom code you carry, whether payroll and tax run in ECC, and when your current maintenance term renews. Change one of them and you may land in a different row.

How do you keep MES, quality and portals from depending on the ERP choice?

Put an integration layer you own between ECC and everything else. Plant systems talk to your layer through documented events and APIs, and only the layer talks to SAP. When the ERP changes, most of the rework lands in the SAP adapter, although you still revalidate field mappings and run end-to-end tests with each consumer.

Most mid-size ECC systems already have the raw interfaces. In SAP's Manufacturing Execution integration documentation, ECC sends released production orders to the MES as LOIPRO IDocs and receives confirmations back through a BAPI interface. Systems on NetWeaver 7.40 or higher include the SAP Gateway Foundation component (SAP_GWFND) as standard, so you can expose OData services without an add-on. The trouble is that each consumer was wired straight to these interfaces years ago, often through custom Z function modules nobody documented.

The S/4HANA service names in the first two rows appear in Cybus's S/4HANA integration guide; confirm the released APIs for your target edition in the SAP Business Accelerator Hub before designing against them. The layer also has to handle the unglamorous work: idempotent confirmation posting, retries with a dead-letter queue, and monitoring that tells the plant when SAP rejected a message.

Two cautions. First, a middleware layer does not change SAP licensing. SAP's indirect access guide says use can occur through a third-party interface or another intermediary system, so check your contract's indirect or digital access terms for documents your plant systems create. Second, if your integrations use the open-source RFC connectors, SAP stopped maintaining PyRFC and node-rfc in 2024, and both now carry deprecation notices. Build on SAP's Java or .NET connectors, or on OData, instead.

Documenting interfaces that only exist in custom code is reverse engineering of your own system. We used the same enumerate, probe, validate and abstract method on an undocumented SOAP CRM API for an ISP, where schema validation caught three vendor-side changes before they broke anything. If you plan to capture SAP traffic or decompile anything, read our post on whether reverse engineering software is legal first. This is not legal advice; review your license agreement and MSA with counsel. The wider method is in our guide to legacy system integration and reverse engineering with AI, and the shop-floor side is in MES integration across ERP and PLCs in legacy plants.

What should you do between now and 2030?

Inventory and get quotes before the end of 2027, decide on support for 2028 before mainstream maintenance ends, and finish any system conversion off a third-party database before the end of 2030. Everything else can move around those three dates.

1. Now: record SAP_APPL, SAP_BASIS, database and operating system versions for every ECC instance.
2. Now: pull your maintenance basis, support model, initial term end and renewal dates from the contract. Termination notice and split timing depend on them.
3. Now: list every inbound and outbound interface, including IDoc partner profiles (transaction WE20), RFC destinations (SM59), Gateway services, flat-file jobs and direct database readers. For each, note the consumer, the business owner, whether it calls standard BAPIs or custom Z code, and whether it creates documents that count under your indirect access terms.
4. Now: mark which processes depend on SAP legal changes, such as payroll, tax, statutory reporting and e-invoicing.
5. First half of 2027: get written quotes from your SAP account team and at least one third-party support provider for the same scope, and price 2028 to 2030 extended maintenance on your own rate.
6. Before December 31, 2027: decide. If you do nothing, SAP moves you to customer-specific maintenance automatically.
7. 2028 to 2030: run the conversion or reimplementation, and stand up the integration layer first so plant systems are not part of the cutover.

The interface list in step 3 is also the spec for the integration layer. Our manufacturing software development and legacy system modernization teams build both, and you can reach us here if you want help with the map.