SAP EHS After 2027: What the Maintenance Dates Mean

SAP ends mainstream maintenance for SAP ERP 6.0 at the close of 2027. This guide sets out what SAP has published about that date and the ones after it, where environment, health and safety functions sit in SAP S/4HANA today, and what an EHS team has to decide about its records. We read SAP's public pages on 21 October 2026. SAP Notes and several support pages need a login, so we did not read them; the last section lists what that leaves open. It is general information, not advice, and it recommends no vendor and no path.

The short answer

For SAP ERP 6.0 and the other core applications of SAP Business Suite 7, SAP gives mainstream maintenance until 31 December 2027, then optional extended maintenance from 1 January 2028 to 31 December 2030 at a premium of two percentage points on the maintenance basis. A system without extended maintenance moves to customer-specific maintenance, where SAP stops adapting the release to legal changes and new technology. For its largest customers that will not finish in time, SAP sells a time-bound transition option from 2031, with conditions that must be met before the end of 2030. For SAP S/4HANA, SAP commits to keep at least one release in maintenance until the end of 2040, and each release from 2023 on gets seven years of mainstream maintenance.

The classic EHS components are documented as part of SAP ERP 6.0, so in our reading they follow those dates. An EHS team then has three broad paths: move EHS with the ERP to SAP S/4HANA, stay on the old system while extended maintenance lasts, or move the EHS records to a specialist tool and keep SAP for the rest. All three need the same groundwork: a list of the records, their history and how long each must be kept.

What "SAP EHS" can mean

The name covers three generations of software that SAP documents separately. Which one a site runs decides what can convert, what has to be migrated and what has to be rebuilt.

On sap.com the S/4HANA offerings are sold as SAP S/4HANA for EHS workplace safety, with a cloud variant, and SAP S/4HANA for EHS environment management. The workplace safety page lists incident management, operational risk management, chemical management, change management and occupational health; the environment page lists air emissions, water, waste, and compliance obligations and permits. In ERP 6.0, safety data sheets and dangerous goods sat in Product Safety and Dangerous Goods Management; the Public Edition help files chemical compliance for products under Product Compliance, apart from EHS, so ask where those classic records would go (see SDS). SAP's strategy note of July 2025 says it is breaking EHS up into connected modules rather than one central record system.

Watch the names. SAP's 2025 and 2026 news posts speak of SAP Cloud ERP and SAP Cloud ERP Private, while the help portal still files the EHS documentation under the S/4HANA edition names. Tie each name on a quote to a documentation set and a release number. Our SAP EHS profile keeps the S/4HANA offerings apart by edition and records the one module price SAP shows on its US pricing pages, for Environment Management; the private edition of Workplace Safety is priced on request.

Both current documentation sets have an Occupational Health component. The on-premise version covers health surveillance protocols, schedule planning, examination data such as diagnoses and work restrictions, and reporting. It lists the SAP components it needs for person data, among them Personnel Administration and Organizational Management. A plan for occupational health is therefore also a plan for HR master data.

The dates SAP has published

What customer-specific maintenance means

SAP's learning material describes this phase as the point after which a release is no longer adjusted to outside requirements, with legal changes and support for new technology as its examples. The 2020 announcement said fixes for known problems would continue at the same fee. The October 2026 post adds that, after 2030, support for systems on third-party databases or Java is restricted further, including kernel patches and database tooling, and that customers should not treat this phase as a long-term way to run business-critical systems in those environments. For the details SAP points to Note 52505, on support after the end of mainstream or extended maintenance, and, for third-party databases, to Note 3832186; both need a login.

For an EHS system the legal-change point bites directly: injury and illness logs, reports to authorities and regulated substance lists change when the law does. In our reading, a classic EHS installation in customer-specific maintenance would keep running, but keeping its regulatory content current would become the customer's own work.

SAP S/4HANA releases

From release 2023, SAP S/4HANA moved to a new release every two years, with three feature package stacks per release and support package stacks after that. Each release from 2023 on stays in mainstream maintenance for seven years, against five for earlier releases. In October 2026 the help portal shows release 2025 at FPS02, and the Public Edition documentation at 2608. The end date for a given release is in the Product Availability Matrix and SAP Note 2900388, both behind a login, so ask for it in writing for the release you are offered.

The transition option

SAP describes the transition option for SAP ERP as a time-bound subscription for its largest and most complex Business Suite 7 customers. It is centred on SAP ERP Central Component on SAP HANA and combined with services under the max success plan. SAP's August 2025 post sets the conditions: the system must be on SAP ERP, private edition on SAP HANA before 31 December 2030; SAP HANA is the only supported database; the system must be at least 2 TB; and products outside the option's coverage must be dealt with first. The October 2026 post adds that Java-dependent capabilities are not supported.

The price is an uplift on the SAP ERP, private edition subscription: none for customers who committed to that subscription by the end of 2025 with a start no later than 2026, a standard 20 percent for those who sign up in 2026, and not yet disclosed for later sign-ups, with the success plan fee on top. Both posts give the period as 2031 to 2033. A note dated 13 October 2026 at the top of the August 2025 post says subscriptions may run until 31 December 2035, with further prerequisites, and points to a Support Portal page that asked us to sign in. The products the option covers are listed in SAP Note 3591251, also behind a login, so whether a site's EHS components are covered is a question for SAP.

Three paths for the EHS team

SAP's dates apply to the ERP; where the EHS records live afterwards is a separate decision. The paths are not ranked, and many organisations will combine them, for example by converting the ERP and archiving one classic component.

On the third path, the vendor records we research say little. Of 212 profiles, 13 name SAP in an integration statement, by the counting rule of our integrations study, which read the records from 28 September to 14 October 2026. For 3 the name sits in a documented capability statement, for 7 the strongest statement is conditional on a plan, module or set-up, and 3 name SAP only in other record text. The SAP EHS profile itself is not counted, because its own name holds the keyword. A name in a record is not a tested interface; our article on integration claims explains why most are conditional.

For candidates, the SAP EHS alternatives page applies one published similarity rule to every profile and lists the result from A to Z. It is not a ranking, and it is not filtered by SAP interface, so ask each vendor the interface questions below.

Disclosure. The editor works at a vendor that pays for sponsored placement on this site. Its researched record, the text the study counts, does not name SAP, so it is not among the 13 profiles above, and the alternatives page lists it only when the same rule selects it, with a note when it does.

The records to plan for

Whichever path is taken, the work starts with a list: which record classes exist, how many of each, from which years, with which attachments and history, and how long each must be kept.

Three points apply across the table. First, count records by class in the old system before anything moves, and count again afterwards. Second, the retention clock outlives every contract and every system: health surveillance and exposure records carry some of the longest retention periods in safety law, and our exit guide gives US and British examples. Third, if the records leave a cloud subscription rather than an installation you run yourself, the same guide explains the EU Data Act's switching rules; for software on your own servers, exit depends in our reading on the licence (cloud and on-premise).

Questions to ask SAP or an SAP partner

• Which EHS components do we run today (the ERP 6.0 components, the Component Extension, or both), and which S/4HANA component replaces each one in the release you propose?
• For each classic component, what do the simplification items say for a system conversion, and what happens to records that have no target?
• When does mainstream maintenance end for the release you propose, as the Product Availability Matrix states it?
• If we stay on SAP ERP 6.0 after 2027, which EHS legal changes stop, from which date, and what would extended maintenance cost on our contract?
• Are our EHS components in the product coverage of the transition option (SAP Note 3591251), and does any part of our EHS landscape depend on Java or a third-party database?
• Which product names on the quote map to which documentation set and release, and which EHS functions are licensed separately?
• Which records, attachments and change documents can be migrated, and which can only be archived? How do we read archived records after the old system is switched off?

Questions to ask a specialist EHS vendor

• Which SAP products and releases does your interface support (SAP ERP 6.0, S/4HANA on-premise, private cloud, public cloud), and is it standard, configured or custom-built?
• Which data flows which way: employees, organisational units, locations or functional locations, equipment, materials, maintenance notifications, cost centres?
• Can you import historical incidents with their history and attachments, risk assessments and occupational health records? Who maps the fields, and who checks the counts?
• Where are occupational health records hosted, who can read them, and are reads logged?
• What can we export at the end of the contract, in which format, and within what period?

The RFP template has sections on integration and on exit and data portability to send before a demo. The methodology explains how the profiles behind the counts are researched.

What we could not verify (21 October 2026)

• SAP Notes 2881788, 1648480, 52505, 2900388, 3591251 and 3832186, the Product Availability Matrix and the SAP release strategy pages need a login, so we did not read them.
• The Support Portal page on the transition option asked us to sign in. The possible end date of 31 December 2035 comes only from the note added on 13 October 2026 to SAP's August 2025 post; the October 2026 post still gives 2031 to 2033.
• We could not read SAP's simplification list for release 2025: the PDF is larger than our fetch tool accepts, and the Simplification Item Catalog asked us to sign in. We therefore cannot say what a system conversion does to each classic EHS component, such as Industrial Hygiene and Safety.
• Two PDFs on support.sap.com about the maintenance strategy and customer-specific maintenance carry a marking that limits them to use under a non-disclosure agreement. We did not use them as sources.
• We did not find public maintenance dates for the Component Extension for SAP EHS Management, and we did not read SAP's overall table of available migration objects, which may list objects that the EHS pages do not.
• Scope changes with each release and edition; we read the 2025 FPS02 and 2608 documentation only. We tested no SAP system and no interface, and the integration counts are statements in vendor material.

FAQ

When does mainstream maintenance for SAP ERP 6.0 end?

On 31 December 2027, for the core applications of SAP Business Suite 7 on their latest three enhancement packages. SAP's post of 7 October 2026 says the date has not moved.

Can we keep classic SAP EHS running after 2027?

Yes, on SAP's terms. Optional extended maintenance runs to 31 December 2030 at a premium; without it the system moves to customer-specific maintenance, in which SAP no longer delivers legal changes or support for new technology. A transition option from 2031 exists for qualifying large customers.

Does SAP S/4HANA have occupational health?

The current documentation for SAP S/4HANA (2025 FPS02) and for the Public Edition (2608) both include an Occupational Health component. Check its scope in the release you would run, its HR data needs, and how your classic records map to it.

Do EHS records have to move to SAP S/4HANA with the ERP?

Nothing in the maintenance pages we read requires it. The dates decide how long the old system is supported. Whether EHS moves with the ERP, waits, or moves to a specialist tool is the organisation's decision, and each path needs the same list of records.

Sources

Read on 21 October 2026.

• SAP Support Portal: Innovation commitment for SAP S/4HANA until 2040, clarity and choice on SAP Business Suite 7
• SAP News Center: press release of 4 February 2020 on the S/4HANA and Business Suite 7 maintenance dates, new SAP S/4HANA release and maintenance strategy (15 September 2022), updates for SAP ERP, private edition, transition option (4 August 2025, updated 13 October 2026), strategy update for SAP S/4HANA for EHS (17 July 2025), planning beyond 2030 for Business Suite 7 and NetWeaver customers (7 October 2026), SAP Cloud ERP Private 2025 FPS02 (13 October 2026)
• SAP Help Portal, SAP S/4HANA 2025 FPS02: Release cycles in SAP S/4HANA, Environment, Health, and Safety, Occupational Health, Environment Management
• SAP Help Portal, SAP S/4HANA Cloud Public Edition 2608: Health and Safety Management, Occupational Health, data migration objects in EHS, Incident Management and Environment Management, displaying changes in EHS objects, Product Compliance
• SAP Help Portal, older generations: Environment, Health and Safety in SAP ERP 6.0 EHP8 SP25, Incident Management in the Component Extension for SAP EHS Management 6.0
• SAP Learning: Discussing SAP maintenance and maintenance strategy
• sap.com: SAP S/4HANA for EHS workplace safety, SAP S/4HANA for EHS environment management
• EUR-Lex: GDPR, Article 9
• The QHSE Standard: the integrations study and the capability statements behind its counts; the SAP EHS profile