SAP ECC end of support 2027: what Indian manufacturers should do

SAP ECC end of support in 2027 is really the end of mainstream maintenance for ECC 6.0 on enhancement packages (EHP) 6, 7 and 8, on 31 December 2027. On EHP 5 or lower, mainstream maintenance already ended on 31 December 2025.

Nothing switches off on 1 January 2028. ECC will keep posting invoices and running MRP. What changes is what SAP will fix, which statutory updates it ships, and what your auditors will ask.

This guide is for IT heads and CFOs still on ECC 6.0. It covers what ends, the impact on GST and internal financial controls, four realistic options, a decision table and a 90-day plan.

The answer depends on your enhancement package. SAP announced the 2027 and 2030 dates in February 2020; the split by enhancement package is in SAP Note 2881788 and its maintenance timelines post.

Also note:

It is not "no support", but it is much thinner. An SAP presentation from 2023 lists the restrictions:

On security, SAP's Security Notes page says that, as a rule, releases going into customer-specific maintenance are considered for high-priority security notes (CVSS 7.0 or higher) in their first 12 months. This applies only to support packages shipped within the last 24 months. For ECC on EHP 5 or lower, which entered customer-specific maintenance on 1 January 2026, that window closes around the end of 2026. The full terms are in SAP Note 52505, "Support after end of mainstream maintenance".

In SAP GUI, choose System > Status, open the product version (component) details and find SAP_APPL. For ECC 6.0 the release starts with 6, and the third digit is the enhancement package. So 606 or 616 is EHP 6, 617 is EHP 7, 618 is EHP 8, and 605 is EHP 5. Note the support package level too.

Statutory changes reach ECC as SAP Notes and support packages; SAP's learning material cites new tax legislation as a typical trigger. When GST e-invoicing (IRN) arrived in 2020, SAP delivered its ECC solution through notes and SAP Document Compliance, with a minimum support package level for each EHP (SAP, March 2020).

The rules keep moving. GSTN introduced phase 3 of HSN reporting in Table 12 of GSTR-1, with separate B2B and B2C values and new validations, from the February 2025 return period (GSTN).

Under customer-specific maintenance, SAP stops delivering legal changes, so every future GST, e-invoice or e-way bill change that needs code becomes your own build, test and support job.

Ask your support team how many India legal-change notes they applied in the last two years. That is roughly the work you would carry yourselves.

Under the Companies Act, 2013, your statutory auditor reports on the adequacy and operating effectiveness of internal financial controls with reference to financial statements (section 143(3)(i)). Directors of listed companies confirm the same (section 134(5)(e)). An audit committee's terms of reference include evaluating internal financial controls and risk management systems (section 177(4)(vii)).

Running ERP on thinner vendor support is not a control failure in itself, but it is a risk someone must assess, own and document. The NIST control catalogue frames the choice simply: replace components the vendor no longer supports, or arrange alternative support, in-house or external (NIST SP 800-53, control SA-22). Expect your auditor to ask which you chose, and for evidence.

SAP's Product Availability Matrix lists the database, OS and kernel releases it supports with ECC, and each vendor has its own end dates. Under customer-specific maintenance, SAP does not guarantee new kernels for new database or OS releases. If your database or OS vendor ends support for your version, you may not be able to move to a supported one while staying on ECC. List each end date next to the ECC dates.

SAP describes three routes in Getting Started With SAP S/4HANA 2025:

Commercially, you can take RISE with SAP (a cloud subscription) or an on-premise licence run by you or a hosting provider. SAP recommends RISE, but an SAP expert noted on the SAP Community post above that on-premise S/4HANA, supported until at least 2040, also allows a two-step move. LogicMotive sells neither, so we have no stake in your choice.

Of the four options, only this one puts you back on SAP mainstream maintenance for the long term. It is also the largest project, and SAP's maintenance timelines post notes that transition projects typically take months or even years.

Extended maintenance is offered only for EHP 6, 7 and 8. SAP describes its scope as broadly comparable to mainstream maintenance, and calls it a bridge for customers who cannot finish in time, not a long-term alternative.

It fits when you have decided to move but cannot go live before the end of 2027. Plan to order by Q3 2027, as SAP advises. If you are on EHP 5 or lower, it is not open to you as you stand; ask SAP in writing whether an EHP upgrade would change that.

Stay with SAP on customer-specific maintenance. You keep paying SAP's fees for the reduced scope above. Your own team or an SAP AMS and support provider fills the gaps, including statutory changes.

Move maintenance to an independent provider. Since 10 July 2026, SAP commitments made binding by the European Commission apply to customers worldwide for ten years (European Commission, commitments text, SAP):

SAP's support packages, SAP Notes and SAP-authored legal changes come only from SAP. From an independent provider you can contract for incident fixes, functional support, security hardening and statutory changes built as custom code. Before signing, ask how they would deliver the next e-invoice schema change, how fast, and who tests it.

This suits a stable ECC system with low change volume and a dated plan to move later or to replace ECC. If it means changing providers, plan the SAP AMS transition as carefully as the contract.

This is a time-bound SAP cloud subscription, centred on ECC on SAP HANA plus transformation services, for RISE customers who need time beyond 2030 (SAP News, August 2025). Its continuity services cover legal changes, security patches and bug fixing. The prerequisites are strict:

Customers signing up for SAP ERP, private edition in 2026 face a standard 20% uplift when switching in 2031; the uplift for 2027 or later sign-ups is undisclosed. SAP updated this on 13 October 2026: subscriptions may now run until 31 December 2035, with further prerequisites set out in SAP Note 3591251.

SAP expects most customers finishing by 2030 not to need this. If your ECC database is well under 2 TB, ask SAP how the minimum applies before planning around it.

Aim for a funded decision by mid-January 2027. FY 2027-28 runs from April 2027 to March 2028. That budget must cover an extended maintenance order that SAP advises completing by Q3 2027, fees starting 1 January 2028 and the first project phase. If your board approves budgets in February or March, have the numbers ready in January.

Weeks 1 to 3: take inventory.

Weeks 3 to 6: get the facts.

Weeks 6 to 10: decide the bridge and the destination. Choose your support model from 2028 and your end state: an S/4HANA route, the transition option or another ERP. Put both into the FY 2027-28 budget paper.

Weeks 10 to 13: brief the audit committee. Cover what ends, the option chosen, the risks accepted, offsetting controls (patching, network isolation, a statutory-change process) and the timeline. Share it with your statutory auditor before year-end fieldwork.

Whichever route you take, each custom program needs a decision: keep, fix or retire. SAP recommends running the Simplification Item check and Custom Code Migration worklists early in a conversion project.

Those tools show what will break technically, not what an old Z-program does for the business, who depends on it, or whether anyone still needs it. Without that, keep-or-retire decisions stall.

LogicMotive built ABAP Inferencer for this gap. It reads custom ABAP, writes plain-language documentation of the business logic, and flags complexity hotspots and dead code. Our guide to the keep, fix or retire method covers the rest.

No. The software keeps running. What changes is maintenance: on EHP 6 to 8, mainstream maintenance ends. You then either buy extended maintenance to 2030 or move to customer-specific maintenance, which excludes new legal changes, support packages and service level agreements.

SAP charges a premium of two percentage points on your existing maintenance basis for 2028 to 2030. The rupee amount depends on your licence base and support model, so ask SAP for a written quote. SAP advises completing the order by Q3 2027, and it is offered only for EHP 6, 7 and 8.

SAP describes extended maintenance as broadly comparable to mainstream maintenance, which includes legal changes, so confirm India localisation coverage in your contract. Under customer-specific maintenance SAP does not deliver legal changes, so your own team or support provider must build them.

Only if you are a RISE with SAP customer and your system has moved to SAP ERP, private edition on SAP HANA before 31 December 2030. You must also take the max success plan, and SAP states a 2 TB minimum system size. SAP said in October 2026 that subscriptions may run until the end of 2035, with further prerequisites.

What you get. LogicMotive runs ABAP Inferencer on 20 custom programs you choose (a mix across modules, including the ones your team is wary of touching) and returns plain-language documentation of each program's business logic, with complexity and dead-code flags, as input to your keep, fix or retire decision. Use it before you budget the S/4HANA project; it does not replace SAP's simplification checks.

What you provide. The source code of the 20 programs, under NDA, and a functional contact who knows the processes they support.

Request a custom code readiness check.