For businesses leaving SAP WM, a legacy WMS, or an EWM rollout that never settled. This page covers where you are starting from, the four places you can land, and the migration stage by stage, from the licence call to hypercare. It is closer to teaching a licensed driver to drive by the law than handing someone the keys: the risk is bending a rigid system back into old habits.
Migrate · restructure · stabilise
The position. Every Australian site running SAP WM now has a decision to make. On S/4HANA, the Compatibility Pack that carried classic WM ran out at the end of May 2026. On ECC, mainstream maintenance ends on 31 December 2027. The choice is between Stock Room Management, basic EWM in the S/4HANA core, advanced EWM, or a decentralised warehouse system, and the right answer depends on what the floor actually does, not on what the licence conversation suggests.
How we work. We shadow operators before we touch the configuration, document where reality already diverges from the system, and make a deliberate call, in the open, on whether the system bends or the floor is retrained. We protect operational continuity through the change, keep standard EWM wherever it can carry the load, and refuse to weaken a rigid system just to preserve a workaround that should not survive the move.
The most common starting point in Australia. The warehouse has run on WM for a decade or more, it works well enough, and the floor knows it by heart. The clock here is ECC itself: mainstream maintenance for EHP 6 to 8 ends on 31 December 2027, with optional extended maintenance to 2030. The warehouse decision gets made inside the S/4HANA programme whether anyone plans it or not, so it is better planned.
Go deeper · SAP WM end of life: what the dates mean
Plenty of businesses converted to S/4HANA and kept WM running under the Compatibility Pack. SAP moved the end of those usage rights from 31 December 2025 to the end of May 2026. From here, the WM functions that sit inside Stock Room Management carry on; the ones outside it are the exposure. The first job is an honest list of which WM functions the floor actually uses.
Go deeper · Classic WM on S/4HANA after the Compatibility Pack
A legacy WMS at end of life, a bolt-on that never fitted, or ERP inventory management and spreadsheets doing the job of a warehouse system. The move to EWM here is part migration and part first build: there is data and habit to carry across, but much of the process design starts clean.
Go deeper · Inventory management is not a WMS · Choosing a warehouse system when SAP is your ERP · The greenfield build, stage by stage
The migration happened and the floor is worse for it: slower picks, workarounds, supervisors back on paper. This is a stabilisation job before it is anything else, and it starts on the floor, not in the configuration.
Go deeper · EWM rescue: a go-live that could not scan · Labour drift: the six-month signals
SAP's continuation of classic WM inside S/4HANA, with a reduced function set. It keeps WM's way of working, so the move is small. It does not include task and resource management, the control interface to automation, value-added services, yard management, cross docking, wave management or decentralised WM. Right for a smaller, low-automation site that runs well on WM today and has no plans that need what is missing.
Go deeper · Stock Room Management or EWM
Basic warehouse management ships inside S/4HANA under the Enterprise Management licence: inbound and outbound, internal movements, physical inventory, the warehouse monitor, resource management, and integration to production, quality and transport. Many businesses moving to S/4HANA already own it without realising. For many single sites, this is the sensible first landing.
Go deeper · Basic or advanced EWM: what your S/4 licence already covers
The extended functions: direct control of automation through the material flow system, waves, yard and dock appointments, labour management, cross docking, value-added services, kitting, slotting and cartonisation, among others. Worth paying for when the floor needs them on day one or in the next few years. Not worth paying for because a sales conversation made them sound inevitable.
Go deeper · Where the line between basic and advanced sits
The warehouse on its own system, connected to the ERP by interfaces. It earns its keep with several sites on one warehouse system, heavy automation, or a hard requirement to keep shipping while the ERP is down. Most single sites do not need it.
Go deeper · Embedded or decentralised EWM
Before anyone draws a target architecture, walk the operation and list the WM functions it uses every day, the ones it uses at month end, and the ones that are configured and dead. Add the spreadsheets that run beside the system and the places operators route around it. That list, not the configuration export, is what the migration has to carry.
Go deeper · System vs reality: four moments
Choose the destination on operational grounds: Stock Room Management, basic EWM, advanced EWM, embedded or decentralised. Read your own contract and SAP's scope description for your release, and get your position confirmed in writing. We read the floor; we do not sell licences or builds, so we have no destination to defend.
Go deeper · Basic or advanced EWM · Stock Room Management or EWM · Embedded or decentralised EWM
A pure technical lift rebuilds the old warehouse, workarounds included, on a new system. Redesigning everything at once on a live floor is how operations go down. The honest line sits between: keep what runs on standard and the floor trusts, redesign where WM was bent, and defer the rest to improvement after go-live.
Go deeper · Like-for-like or redesign · SAP WM vs EWM: what changes on the floor
Years of Z code sit between most WM sites and a clean migration. Each piece gets the same question: is this the part of the warehouse that is a competitive advantage, or a workaround for a process that standard EWM now handles? Most of it is the second kind, and carrying it forward costs more every year.
Go deeper · Z code is an arrogance tax
SAP's tooling moves warehouse product data, storage bins and stock, warehouse by warehouse. It moves what is in the system; it cannot tell you whether it is true. Bins that no longer exist, stock that is not there, missing dimensions and weights: all of it gets fixed before the freeze, with a named owner signing off each object.
Go deeper · Migrating WM data to EWM
Operators who have been fast on WM for years will be slow on new RF flows for the first weeks. Test with them, on real product, in the order a shift runs, and let the tests change the flows. A UAT run by the project team on project data proves very little about Monday.
Go deeper · The RF flow is the product · Readiness is not training
Unlike a new site, a brownfield cutover has stock to count and load, open orders to finish, and customers still expecting deliveries. Outbound volume gets managed down with sales ahead of the weekend, the go or no-go point has a deadline, and the whole cutover is rehearsed with production-like data before it counts.
Go deeper · Cutting over a live warehouse from WM to EWM · Cutover weekend: the runbook decisions
The first weeks decide which habits the new system inherits. A senior consultant stays on the floor through hypercare, because the workaround nobody reports in week two is the labour drift everyone notices in month six.
Go deeper · Hypercare done early · Labour drift: the six-month signals
A national operation went live on SAP EWM with another team and the floor could not scan. Luminar came in after go-live, stabilised the operation within 90 days, improved scalability by roughly 70% and set out a clear path forward.
A central SAP EWM template landing across ten warehouses in one APAC market, fitted to the reality of each site rather than forced onto the floor.
On ECC, WM is supported with the rest of the Business Suite, and mainstream maintenance for EHP 6 to 8 ends on 31 December 2027, with optional extended maintenance to 2030. On S/4HANA, classic WM ran under a Compatibility Pack, and SAP moved the end of those usage rights to the end of May 2026. The WM functions inside Stock Room Management continue; the rest do not. Check SAP Note 2269324 for your release and confirm your position with your SAP account team.
For a smaller warehouse with little automation, simple put-away and picking, and no need for waves, cross docking, yard management or value-added services, Stock Room Management can be the right answer. If the site uses any of those today, is automating, or is growing into a second site, it points to EWM. Decide on what the floor actually uses, not on what is configured.
Basic warehouse management sits in the S/4HANA core under the Enterprise Management licence, and many businesses moving to S/4HANA already own it. Advanced EWM, which covers automation control, waves, yard, labour management, cross docking and value-added services among others, is licensed separately. Exact scope varies by release and contract, so read your own.
Not literally. EWM's structures are designed, not translated one to one from WM, so some design work is unavoidable. The real question is how far to move: keep what runs well on standard, redesign where WM was bent with custom code or workarounds, and defer the nice-to-haves until the floor has settled.
Yes. SAP's migration runs per warehouse number, so a multi-site business can move site by site. The first site then becomes the rehearsal for the rest, which is worth planning for deliberately: pick a first site that will teach you something without putting the biggest customer at risk.
Warehouse product data, storage bins, bin sorting, fixed bin assignments and stock, with the S/4HANA Migration Cockpit handling EWM master data and customising per warehouse. What it cannot do is check whether the data matches the floor. Cleaning and reconciling before the freeze is still your job.
Beside them, on your side of the table. We do not sell the build, so we can read the architecture call, the scope and the cutover plan against what the floor needs, and say so in plain language. That works before the integrator is chosen, during the build, or after go-live if the floor is struggling.
A senior consultant on your floor for a day will tell you which WM functions you actually use, which of the four destinations fits, and what the honest timeline is. Plain-language memo in five working days, no proposal attached.