Most of the confusion about SAP WM end of life comes from blending dates that belong to different systems. LE-WM inside ECC runs on one clock. Classic WM carried into S/4HANA under a Compatibility Pack ran on another, and that one has already stopped. Stock Room Management and EWM inside S/4HANA run on a third. Ask which date applies before asking what to do about it.
What every clock has in common is the destination. SAP has made Extended Warehouse Management the go-forward warehouse solution, and that turns a finance-led upgrade into a warehouse change whether anyone planned for it or not. Which tier you land on is a separate call, set out in basic or advanced EWM, and the whole migration is laid out on the SAP WM to EWM migration page.
The dates, in one table.
Sourced from SAP: the December 2025 announcement on Compatibility Packs, the 13 October 2026 update to the private edition transition option, SAP Note 2269324, SAP Note 3591251 and SAP's published maintenance strategy. Confirm each against your own releases and contract before you plan around it.
Which date is yours.
Still on ECC with LE-WM.
Your date is 31 December 2027, or 2030 if the business buys extended maintenance. That sounds like time, but at the time of writing (November 2026) it is about 14 months. A programme going live by December 2027 should already have its warehouse destination decided, and the warehouse is usually the last workstream to get attention. The conversion approach itself depends on where the warehouse will land, so the floor inventory is worth doing before the S/4HANA plan is locked. That inventory is what a Floor Audit produces: one day on site with a senior consultant, a plain-language memo within five working days, and no proposal attached. Request a Floor Audit. The sequencing question is covered in where the warehouse sits in an S/4HANA programme.
On S/4HANA, still running classic WM.
Your date has passed. The functions that fall inside Stock Room Management carry on, because it is part of the S/4HANA core. The ones outside it (task and resource management, the automation interface, waves, cross docking, yard, value-added services, decentralised WM) are your exposure. What to check and the three paths that follow are in classic WM on S/4HANA after the Compatibility Pack. Not sure which functions fall outside Stock Room Management on your site? .
Running decentralised EWM 9.x on SCM.
Mainstream maintenance for EWM 9.5 ends on 31 December 2027, the same day as ECC. The move is to EWM on S/4HANA, embedded or decentralised, and it is a migration in its own right. The architecture call is covered in embedded or decentralised EWM.
Already on Stock Room Management or EWM.
No end-of-life date is forcing your hand. The question is whether the system still fits the operation, which is a health check question rather than a deadline.
Counting on the 2035 transition option.
On 13 October 2026, SAP said transition option subscriptions may run to 31 December 2035, with further prerequisites, two years past the 2033 it gave when the option launched. That is already being read as "ECC is safe until 2035", and for most sites it isn't. To qualify, ECC has to be on SAP ERP, private edition, on SAP HANA before the end of 2030, and each system has to be at least 2 TB. The Max Success Plan is required from 2031 to 2033, at a fee on top.
The price depends on when you sign for private edition: equivalent terms for contracts signed by the end of 2025, a 20 percent uplift for 2026, and no published number from 2027. Products outside the option need a mitigation plan, and both those and the 2035 conditions sit in SAP Note 3591251. Miss any of it and your dates are still 2027 and 2030. Clear all of it and the warehouse still lands on Stock Room Management or EWM at the end: the extra years change when that call gets made, not whether.
Can you still make 31 December 2027?
Count back from the date. Cutover and hypercare sit at the end. Before them come testing and floor training, the build, the design, and the decision on destination: Stock Room Management, basic EWM or advanced EWM. A programme that has not chosen its destination is not really working to 2027. It is working to 2030, and that is a legitimate plan if it is made on purpose. Extended maintenance is a bridge that buys design time. It is not a destination, and it does not change what the warehouse eventually has to move to.
Three questions tell you which side of the line you are on.
- Has the business signed off the warehouse destination in writing, separately from the finance conversion?
- Is there a list of the WM functions the floor uses, by shift?
- Is the cutover window protected from your peak trading period?
If any answer is no, treat 2027 as a risk and price extended maintenance into the business case now. A Floor Audit answers the second question in a day.
Why the floor is the risk, not the ledger.
A finance migration is hard, but it is a controlled environment: known data, known users, a known cutover. A warehouse migration is not. It changes what every operator touches, how every shift opens, and how every pallet is recorded, in a live operation that has to keep dispatching while it changes underneath the people running it. The finance module does not down tools if the cutover wobbles. The warehouse does, and the customer notices the same day.
On most 2027-driven programmes, the warehouse is scoped as a downstream workstream under a finance-led programme. That is exactly the setup where the floor gets compressed: the timeline becomes the reporting metric, readiness becomes the line item that gets squeezed, and the execution leg is treated as configuration rather than operational change. The cutover of a live warehouse is where that compression shows.
Greenfield or brownfield, for the warehouse.
The migration choice most people frame at the ERP level has a warehouse version that matters just as much. A greenfield EWM build is a chance to design the execution leg from a clean sheet, around how the operation actually runs today rather than how it ran when the old system was configured. A brownfield path preserves more but carries the old compromises forward, including the workarounds nobody has documented. Neither is automatically right. The point is to make that decision deliberately, for the floor, and not inherit it from the finance track.
What to do now.
Work out which clock you are on, from the table above and SAP's own notes, and get your position confirmed by your SAP account team in writing. Then list which WM functions the floor actually uses, by shift, because that list decides whether Stock Room Management, basic EWM or advanced EWM is the destination. Name the operational risks up front: master data, hardware, local team capability, and the gap between any group template and the local operation. And insist the warehouse has a senior voice in the room before the delivery model is locked, not after.
The 2027 clock is a finance headline with a warehouse bill attached. Plan the floor, or pay for it in hypercare.
How Luminar helps here.
We are the independent, local specialist that shapes the EWM position before delivery begins: the deployment approach, a requirements baseline grounded in how the floor runs, and an honest readiness view with the operational risks named early. We do not sell you the build, and we are not licensing advisers, so the advice is about your operation and your floor. Whether the programme is greenfield or brownfield, we make sure the warehouse is not the workstream that quietly gets compressed on the way to a 2027 date.