# SAP ECC End of Support Assessment: Pick Your Path Before 31 December 2027 > Source: https://netray.co/tools/sap-ecc-2027-maintenance-exit-path-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Twelve scored questions on EHP level, database, custom code, CVI, add-ons, budget and contract appetite that map your SAP ECC 6.0 system to one of four maintenance exit paths, with the dates that apply. ## Category sap ## Erp SAP ECC 6.0 ## Audience - SAP Basis administrator - SAP architect - CIO - SAP program manager ## Tool **Kind:** assessment **Questions:** #### Which enhancement package is your SAP ERP 6.0 production system on? **Help:** Check in System > Status > Component information (SAP_APPL and EA-* levels). Per SAP Note 2881788, mainstream maintenance to end 2027 and extended maintenance apply to EHP 6 and higher. **Options:** ##### EHP 0 to 5 (mainstream maintenance already ended 31 Dec 2025) **Score:** 0 ##### EHP 6 or 7 **Score:** 2 ##### EHP 8 **Score:** 3 #### What are your Unicode status and database platform? **Help:** S/4HANA runs only on Unicode and SAP HANA. The SAP ERP private edition transition option also supports SAP HANA only. **Options:** ##### Non-Unicode on Oracle, DB2, SQL Server, MaxDB or Sybase ASE **Score:** 0 ##### Unicode on one of those databases (AnyDB) **Score:** 1 ##### Unicode on SAP HANA (Suite on HANA) **Score:** 3 #### How many custom (Z/Y) development objects are in the system? **Help:** Count from TADIR for the customer namespaces, then check usage with SCMON or UPL data before you plan remediation. **Options:** ##### More than 20,000 **Score:** 0 ##### 5,000 to 20,000 **Score:** 1 ##### 1,000 to 5,000 **Score:** 2 ##### Fewer than 1,000 **Score:** 3 #### How large is your modification footprint (SPDD and SPAU work at the last upgrade or support package)? **Options:** ##### Several hundred modified SAP objects or unknown **Score:** 0 ##### Roughly 50 to 300 objects **Score:** 1 ##### Fewer than 50 objects **Score:** 2 ##### Only SAP Notes, no true modifications **Score:** 3 #### How far along are you with Business Partner and Customer Vendor Integration (CVI)? **Help:** Conversion to S/4HANA requires every customer and vendor to have a Business Partner. This is a mandatory pre-conversion step. **Options:** ##### Not started **Score:** 0 ##### CVI checks run, findings not fixed **Score:** 1 ##### Customising done, data cleansing in progress **Score:** 2 ##### All customers and vendors synchronised to BP (MDS_LOAD_COCKPIT) **Score:** 3 #### What is your database size and archiving position? **Help:** Size drives HANA memory, conversion downtime and subscription sizing. Check the largest tables in DB02 or the database monitor. **Options:** ##### Several TB and growing, no archiving **Score:** 0 ##### Some archiving on a few objects only **Score:** 1 ##### Regular archiving of the large objects (FI_DOCUMNT, MM_MATBEL, SD_VBAK and similar) **Score:** 3 #### Are your add-ons and industry solutions confirmed for the target? **Help:** Maintenance Planner blocks a conversion when an installed add-on has no released successor. **Options:** ##### Not checked **Score:** 0 ##### Checked, some have no S/4HANA path **Score:** 1 ##### Most confirmed, a few replacements needed **Score:** 2 ##### All confirmed via Readiness Check and Maintenance Planner **Score:** 3 #### How heavy and how documented is your interface landscape? **Help:** Count active partner profiles in WE20 and outbound ports in WE21 as a starting inventory. **Options:** ##### Hundreds of interfaces, many undocumented custom RFCs and IDocs **Score:** 0 ##### Documented, but heavy custom IDoc and RFC reliance **Score:** 1 ##### Documented and mostly standard IDoc message types or middleware **Score:** 3 #### What budget is approved for 2026 to 2028? **Options:** ##### Nothing approved **Score:** 0 ##### Discussed, not approved **Score:** 1 ##### Approved for a study or preparation phase **Score:** 2 ##### Program funded through go-live **Score:** 3 #### What internal SAP skills can you commit? **Options:** ##### Small team keeping the lights on, no S/4HANA experience **Score:** 0 ##### Some S/4HANA training, no project experience **Score:** 1 ##### Experienced team plus a contracted partner **Score:** 3 #### Would you sign a RISE with SAP subscription and move off perpetual licence maintenance? **Help:** The transition option is a subscription offering that sits on top of SAP ERP, private edition. Have your licence team review what happens to existing perpetual licences. **Options:** ##### No, we will not move to a subscription **Score:** 0 ##### Only as a last resort **Score:** 1 ##### Yes, open to it **Score:** 2 ##### Already negotiating or signed **Score:** 3 #### Does a regulator, customer contract or auditor require vendor-supported software? **Help:** Validated GxP systems, defense contracts and some financial audits often ask for supported software and current security patches. **Options:** ##### No, third-party support is acceptable to auditors and customers **Score:** 0 ##### Internal policy prefers vendor support **Score:** 2 ##### Yes, contractually or by regulation **Score:** 3 **Bands:** #### Convert now (brownfield) **Min:** 75 **Max:** 100 **Verdict:** Your system is technically close and the money and people are there. A system conversion before 31 Dec 2027 keeps you on mainstream maintenance the whole way and avoids paying for extended maintenance. **Recommendations:** - Run SAP Readiness Check on a recent production copy and assign every simplification item to an owner. - Run the S/4HANA ATC checks on custom code and retire unused objects found through SCMON or UPL. - Do a Maintenance Planner run for the target release to confirm add-ons before you sign the conversion plan. - Plan at least two full mock conversions with SUM (with DMO if you are on AnyDB) to measure real downtime. - Target go-live well before 31 Dec 2027 so a slipped cutover does not push you into extended maintenance. #### Extended maintenance to 2030, then convert **Min:** 50 **Max:** 74 **Verdict:** You can get there, but not safely by end 2027. Extended maintenance from 1 Jan 2028 to 31 Dec 2030 buys three years for EHP 6 and higher; use it for preparation, not delay. **Recommendations:** - If you are below EHP 6, upgrade to EHP 8 first: extended maintenance does not cover EHP 0 to 5. - Opt in to extended maintenance before 31 Dec 2027. Systems that do not opt in move to customer-specific maintenance from 2028. - Finish CVI and Business Partner synchronisation now; it does not depend on the target date. - Start archiving the largest objects to cut HANA sizing and conversion downtime. - Fix a conversion date in 2029 or early 2030 with a fallback window before 31 Dec 2030. #### Private edition transition option (2031 to 2033, RISE) **Min:** 25 **Max:** 49 **Verdict:** A conversion before end 2030 looks unlikely, but you need vendor support. SAP's SAP ERP, private edition, transition option gives business continuity for ECC from 2031 to 2033 if you meet its prerequisites. **Recommendations:** - Read SAP Note 3591251 for the eligible products and current prerequisites; SAP's October 2026 update says subscriptions may run to 31 Dec 2035 with further prerequisites. - Plan the move: the system must be migrated to SAP ERP, private edition on SAP HANA before 31 Dec 2030. - Expect the max success plan to be required during 2031 to 2033, charged on top of the transition option, and a minimum system size of 2 TB; confirm both with SAP. - SAP said final pricing for later sign-ups will be communicated closer to availability to purchase in 2028; budget the decision for 2027. - Do not treat it as an end state: keep CVI, custom code clean-up and archiving moving so the S/4HANA conversion is ready by 2033. #### Stay and plan third-party or customer-specific maintenance, with risk **Min:** 0 **Max:** 24 **Verdict:** You are neither ready to convert nor willing to subscribe, and nobody forces vendor support. Staying is possible, but plan it as a managed risk with a documented exit date. **Recommendations:** - Customer-specific maintenance gives access to known fixes only; plan for no new legal changes or support packages from SAP. - If you consider third-party support, write down how you will get tax and legal changes, security fixes and kernel or database support. - Isolate the system: restrict RFC destinations, gateway ACLs (reginfo and secinfo) and internet-facing ICF services. - Freeze or minimise new custom development so a later conversion does not get harder. - Revisit this assessment each year; budget or regulatory changes can move you into a different band. ## Content **Intro:** This assessment scores twelve facts about your SAP ECC 6.0 system and maps the result to one of four exit paths from the 2027 end of mainstream maintenance. Each result lists the next technical steps and the dates SAP has published for that path. **Sections:** #### The dates that apply to SAP ECC 6.0 **Body:** SAP announced in February 2020 that mainstream maintenance for SAP Business Suite 7 core applications, including SAP ERP 6.0, runs to 31 Dec 2027, with optional extended maintenance from 1 Jan 2028 to 31 Dec 2030. SAP Note 2881788 ties this to enhancement packages: EHP 6, 7 and 8 get the 2027 and 2030 dates, while EHP 0 to 5 left mainstream maintenance at the end of 2025. Customers who do not opt in to extended maintenance by end 2027 move to customer-specific maintenance from 2028. In February 2025 SAP added the SAP ERP, private edition, transition option, which covers ECC from 2031 to 2033 for systems moved to SAP ERP, private edition on SAP HANA before 31 Dec 2030. **Bullets:** - 31 Dec 2025: mainstream end for EHP 0 to 5 - 31 Dec 2027: mainstream end for EHP 6 to 8 - 31 Dec 2030: extended maintenance end, and deadline to be on private edition on HANA for the transition option - 2031 to 2033: transition option period (SAP Note 3591251) #### How to use the score **Body:** Answer for your production system, not the landscape average. Each question scores 0 to 3 and the total is shown as a percentage. High scores mean the system and the organisation can convert soon; low scores mean you lack readiness, the will to sign a subscription, or any external pressure to stay vendor-supported. The score is a heuristic, and some answers are hard gates that override it. If you will not sign a RISE subscription, the transition option is closed. If you are below EHP 6, extended maintenance is not available until you upgrade. If a regulator requires vendor support, third-party maintenance is not a real choice even with a low score. #### Where to get the answers in the system **Body:** EHP level: System > Status > Component information, or the product version in the SAP Solution Manager landscape data. Unicode and database: System > Status shows both. Custom code: count TADIR entries in the customer namespaces and collect usage with SCMON for several months. Modifications: the SPAU and SPDD lists from your last support package or EHP update. CVI: run the CVI pre-checks and look at open items in MDS_LOAD_COCKPIT. Add-ons: run Maintenance Planner for the target release and SAP Readiness Check for simplification items and sizing. Interfaces: partner profiles in WE20, RFC destinations in SM59 and IDoc volumes in WE05 or BD87. #### Common mistakes **Body:** Treating 2030 as the deadline when you are still on EHP 5 or lower: you already left mainstream maintenance and need an EHP upgrade just to reach extended maintenance. Leaving the extended maintenance opt-in to the last quarter of 2027. Assuming the transition option is a free extension: it is a separate subscription with its own prerequisites, including SAP HANA and a migration to private edition by end 2030. Starting custom code remediation before you know which objects are actually used. Forgetting that CVI work is the same whichever path you choose, so delaying it only shortens the time you have later. **Cta:** If you want your team to query ECC data, custom code inventories or IDoc volumes in plain English on your own servers while you plan the move, we can set that up. **Faq:** #### When does SAP ECC support end? **Answer:** Mainstream maintenance for SAP ERP 6.0 EHP 6 to 8 ends on 31 Dec 2027. Optional extended maintenance runs to 31 Dec 2030. EHP 0 to 5 left mainstream maintenance at the end of 2025. After that, the SAP ERP, private edition, transition option covers 2031 to 2033 for systems that meet its prerequisites. #### Does SAP support for ECC 6.0 end in 2030? **Answer:** Extended maintenance, the last standard vendor support for ECC, ends on 31 Dec 2030 and must be opted into. Systems that do not opt in move to customer-specific maintenance from 2028. Support beyond 2030 is only through the transition option, which requires SAP ERP, private edition on SAP HANA before 31 Dec 2030. #### What happens if ECC is out of support? **Answer:** The system keeps running. Under customer-specific maintenance you get known fixes, but no new legal changes or support packages. That matters for payroll, tax and statutory reporting, and for security notes. Kernel, operating system and database versions also drift out of their own support matrices. #### Can I upgrade ECC directly to S/4HANA? **Answer:** Yes, a system conversion (brownfield) uses Software Update Manager, with Database Migration Option if you are not yet on SAP HANA. The source must be Unicode, and customers and vendors must be converted to Business Partners first. Check the minimum source release for your target S/4HANA release in the conversion guide. ## Search terms sap ecc end of support, sap ecc end of life, when does sap ecc support end, sap ecc out of support, sap ecc upgrade to s/4, sap support for ecc 6.0 ends in 2030, sap ecc extended maintenance 2030, sap erp private edition transition option --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json