SAP S/4HANA
SAP S4HANA Maintenance Data Migration: Keep Your History for Shutdown Planning
In an SAP S4HANA maintenance data migration (S/4HANA), a system conversion keeps data in the converted system, but a new implementation loads data with migration tools whose standard PM object selects only open orders, and a selective data transition keeps a chosen time slice, so maintenance history can be left behind. SAP ends mainstream Business Suite 7 maintenance at the end of 2027. MaintWiz can take in the history for shutdown planning.
SAP statements come from SAP support, news, learning and Help pages read in October 2026. MaintWiz statements describe the shutdown module.
How MaintWiz helps: Moving to S/4HANA should not mean losing maintenance history. The MaintWiz shutdown module connects to SAP through the PM or the MM module, with SAP staying the system of record. See the module · Get the SAP preparation worksheet
By Jai Balachandran · Published · Last reviewed
What MaintWiz adds:SAP PM or SAP MM modeSAP stays the system of recordPR and PO status per partPlan on top of your orders
The deadline
When does SAP ECC maintenance end?
SAP provides mainstream maintenance for Business Suite 7, which includes SAP ERP 6.0 (ECC), until the end of 2027, with optional extended maintenance from 2028 to the end of 2030 at a premium, and SAP said on 7 October 2026 that these dates have not changed. 1,2
| Item | What SAP says | Source |
|---|---|---|
| Mainstream maintenance | SAP will provide mainstream maintenance for Business Suite 7 core applications until the end of 2027 | SAP: Maintenance 2040 |
| Optional extended maintenance | Available from the beginning of 2028 until the end of 2030, at a premium of two percentage points on the maintenance basis | SAP: Maintenance 2040 |
| After that | Customers who do not take extended maintenance, or whose period has ended, receive customer-specific maintenance | SAP: Maintenance 2040 |
| Latest statement | The dates for SAP Business Suite 7 maintenance have not changed (7 October 2026); moving the database to SAP HANA does not extend mainstream or optional extended maintenance | SAP News, October 2026 |
| S/4HANA | An innovation commitment for SAP S/4HANA until the end of 2040 | SAP: Maintenance 2040 |
The planning consequence for maintenance teams is simple: whatever path you take, decide early what happens to your maintenance history, because it is easiest to extract while the old system still runs.
Dates are as stated on the SAP pages cited at the time of writing; check SAP's current pages before you plan.
Three paths
What happens to maintenance history in an S/4HANA migration?
A system conversion keeps data in the converted system, a new implementation loads data with migration tools whose standard PM object selects only open maintenance orders, and a selective data transition lets you choose a time slice of closed items, so in the last two paths maintenance history is left behind unless you plan to keep it. 3,6,4,5
| Path | What SAP says it is | What it means for maintenance history | Source |
|---|---|---|---|
| System conversion (brownfield) | A guided technical process for a 1:1 conversion of an existing SAP ERP system to SAP S/4HANA that lets you keep your investments in data, processes and custom code | History in the converted system stays in the system, because data is converted rather than reloaded; clean up data volumes first | SAP Learning: System conversion |
| New implementation (greenfield) | A new SAP S/4HANA system built from scratch | Data is loaded with migration tools. SAP's migration object for PM maintenance orders selects orders of types PM01, PM02 and PM03 whose status is created or released, so closed orders are outside its default scope | SAP Help: PM maintenance order migration object |
| Selective data transition | An alternative to a system conversion and a new implementation: a data migration into an S/4HANA system with selective scope and individual transformations | Scope is chosen. SAP describes transaction data as open items plus a time slice of closed items, for example two years, and says complexity rises if the time slice is too short | SAP: Selective Data Transition, SAP Learning: Selective Data Transition |
SAP's selective data transition page says the approach "typically" includes migrating a certain amount of historical data and that complexity increases if the time slice is too short. 4 The statement about the PM maintenance order object comes from SAP Help; it implies that closed history is not in the default scope, and should be confirmed against the full object description for your release. 6
Consultancy articles often say history is left behind in a greenfield move; this page rests on SAP's own pages only.
Software
How does MaintWiz help when maintenance history is left behind?
MaintWiz can take in historical maintenance data from the old SAP system so shutdown planners keep durations, repeat findings and equipment history, and it then connects to the new SAP system through the PM or the MM module with SAP as the system of record.
About MaintWiz. MaintWiz is an industrial AI platform with IoT, SAP integration and predictive maintenance (PdM) capabilities. Its shutdown and turnaround module helps plants plan, schedule, execute and close out shutdown work.
What the shutdown module covers
As described on the MaintWiz shutdown maintenance product page.
- Historical maintenance data can be imported so planners keep durations, repeat findings and equipment history (formats agreed in implementation)
- SAP integration through the PM or the MM module, one mode per customer; SAP stays the system of record
- Gantt chart with critical path and float, baselines that show what moved
- Close-out and archive of past shutdowns, with deferred items
- Import and export with Excel, Primavera P6 and Microsoft Project
- Reports and tables export to Excel
Proof
What MaintWiz customers report
Figures as published in MaintWiz case studies on maintwiz.com. They come from maintenance management projects, not shutdowns.
What to keep
Which maintenance history helps shutdown planning?
The history that helps most is the orders and operations of past stops with their durations, hours and costs, the revision that ties orders to a stop, the components used, the notifications and codes that show repeat findings, and the equipment and location history. 7
Estimates built from history are covered in how to plan a plant shutdown and lessons from past stops in the lessons learned guide.
| History element | Typical SAP object (verify in your system) | How a planner uses it |
|---|---|---|
| Past shutdown orders and operations | Maintenance orders and operations (AUFK, AFIH, AFVC) | Durations, crews and hours for the next estimate |
| Revisions | Revision objects | Identify which orders belonged to which stop |
| Components used | Order components and reservations (RESB) | Parts and long-lead items used in past stops |
| Notifications and codes | Notifications (QMEL) and catalog codes | Repeat findings and emergent work |
| Equipment and functional locations | Equipment (EQUI) and functional locations (IFLOT) | Scope per asset; failure and repair history |
| Costs | Order cost records | Cost of past stops against budget |
SAP says order data is entered in the maintenance history and is important for evaluations and future planning. 7 The table names typical SAP objects; names and fields differ by release and configuration, so confirm them with your SAP team. Estimates built from your own history are better than generic ones: see how to plan a plant shutdown and how to estimate a shutdown budget.
Bringing it in
How do you bring maintenance history into a shutdown tool?
Bring maintenance history into a shutdown tool in five steps: decide the scope and window, extract before cutover while the old system runs, map each element to the plan, load and validate against the extract, and set how new orders arrive from the new SAP system; MaintWiz can import historical maintenance data for this.
Terms are in the shutdown turnaround glossary and the data map is in the free shutdown templates. A free Excel version is available: Maintenance history extraction and data map (.xlsx).
| Step | What to do | Check |
|---|---|---|
| 1. Decide scope | Choose the time window and the elements to keep; record the decision | Owner and date agreed |
| 2. Extract before cutover | Take the extract from the old system while it still runs; keep a frozen copy | Counts by year recorded |
| 3. Map to the plan | Map each element to the shutdown plan's fields: equipment, orders, durations, findings, parts, costs | Every kept field has a home |
| 4. Load and validate | Load into the plan; compare counts, dates and costs against the extract | Sample of 50 orders matches |
| 5. Keep it current | Decide how new orders reach the plan from the new SAP system | Owner, direction and frequency set |
The formats and objects MaintWiz imports are agreed during implementation. A data map and validation checklist is in the free shutdown templates. For the ongoing exchange with SAP see SAP PM shutdown management and SAP MM shutdown materials.
Timeline
What should maintenance teams do before the 2027 ECC deadline?
Before mainstream ECC maintenance ends at the end of 2027, decide the transition path and the history window, extract and freeze the maintenance history while the old system still runs, load the kept history into the system where planners will use it, and reconcile new orders daily for the first shutdown. 1,2
For past stop measures see the shutdown KPI guide and the shutdown case study.
| When | Task | Why |
|---|---|---|
| Now | Choose the transition path and the history window; name an owner | The path decides what is left behind |
| Before cutover | Extract and freeze maintenance history; validate counts | The old system is the only complete source |
| At cutover | Load kept history; confirm revisions and equipment links | Planners need to find past stops |
| After cutover | Reconcile new orders daily for the first shutdown | Catches exchange gaps early |
| By end of 2027 | ECC mainstream maintenance ends; extended maintenance runs to end of 2030 at a premium | SAP statement, sapstrat |
The timeline is a working template. SAP's dates are on the pages cited.
Visuals
Save the S/4HANA history charts
Two charts to share with your migration team. Click either for the full-size image.
FAQ
Frequently asked questions
When does SAP ECC maintenance end?
Mainstream maintenance for Business Suite 7 ends at the end of 2027; optional extended maintenance runs to the end of 2030 at a premium; SAP said on 7 October 2026 that the dates have not changed. 1,2
Does moving to SAP HANA extend maintenance?
No. SAP says moving to SAP HANA does not extend mainstream or optional extended maintenance. 2
What happens to maintenance history in an S/4HANA migration?
It depends on the path: a system conversion converts the data in place, while a new implementation loads data with migration tools and a selective data transition lets you pick a time slice. 3,6,4
Does the PM migration object include closed orders?
SAP Help describes the object as selecting orders of types PM01 to PM03 in created or released status, so closed orders are outside its default scope; check the full description for your release. 6
What is selective data transition?
A data migration into an S/4HANA system with selective scope and individual transformations, an alternative to a system conversion and a new implementation. 4
Which history helps shutdown planning?
Past shutdown orders with durations, hours and costs, the revision, components used, notifications and codes, and equipment history.
How do you bring history into a shutdown tool?
Decide scope, extract before cutover, map to the plan, load and validate, and set how new orders arrive. MaintWiz can import historical maintenance data.
Where can I see how MaintWiz works with SAP?
See SAP PM shutdown management and SAP MM shutdown materials.
Sources
Sources
- SAP Support, Maintenance 2040 (maintenance strategy for SAP S/4HANA and SAP Business Suite 7)
- SAP News Center, Planning Beyond 2030: What SAP Business Suite 7 and SAP NetWeaver Customers Using Third-Party Databases or Java Need to Know (7 October 2026)
- SAP Learning, Understanding the Concept of an Upgrade and an SAP S/4HANA Conversion
- SAP Support, Selective Data Transition Engagement
- SAP Learning, Illustrating Selective Data Transition
- SAP Help, PM - Maintenance order (SAP S/4HANA data migration object; read from the search summary of the page, the page itself did not load by script)
- SAP Library, Maintenance Order (Plant Maintenance, PM)
- US Government Accountability Office, GAO Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G, December 2015)
Plan on top of SAP, keep SAP as the record
Book a demo and bring your SAP setup. We will walk through how MaintWiz can work with it.