IT systems · Practical guide

Decommissioning SAP ECC after an S/4HANA migration

S/4HANA is running, but older batches and records may still require ECC. Before shutting down the legacy system, demonstrate that the required historical information remains complete, intelligible and accessible without running ECC in production.

Table of contents

At a glance

When can a regulated business switch off SAP ECC after an S/4HANA migration?

Demonstrate that historical records and their context remain complete, retrievable and intelligible in the successor system or archive. Assess outstanding transactions, interfaces, access rights, recovery and ownership. The accountable person can then base the shutdown decision on documented evidence. Successful S/4HANA go-live covers a different decision.

Migration and decommissioning have different acceptance criteria

Migration transfers the data the target system needs. Decommissioning ends the functions and dependencies of the old system. The projects are linked but answer different questions. Successfully migrating open purchase orders, for example, tells you nothing about whether a reviewer can still explain a historical batch decision from the archive.

This article covers historical GxP-relevant information from SAP ECC after an S/4HANA implementation. Tax archiving, data protection and other retention requirements may also apply. Assess quality records in their own right. The architecture depends on the release, objects, extensions and existing archives.

Identify the ECC functions to retire. Are these postings, searches, reports, interfaces or selected SAP clients? A system kept running with restricted functions still needs operating support. Stopping new transactions does not by itself mean the system has been decommissioned.

Sources: [1] [2]

Inventory historical business objects and their context

Start with questions the business and QA will need to answer. Which starting materials went into this batch? Which test results and decisions applied at the time? Which attachment explains the deviation? Use these questions to identify the objects and relationships to retain.

Record attachments, links, status histories, relevant changes, historical master data and any logic needed to display or interpret the primary records. A collection of tables may lose the relationships between them. A PDF is useful only if readers can retrieve the information they need from it.

Identify objects already archived and files held elsewhere. An ECC record may point to a separate content repository. Migrating only the database before shutting down that repository leaves document numbers intact while their attachments disappear. Include dependencies like this in scope before shutdown.

Inventory organised by the records people need to retrieve
Historical questionInformation neededDependency to check
Which batch was used? Document chain and batch assignment Object relationships and keys
Why was this decision taken? Inspection results, status and relevant history Evaluation logic and the context at the time
Where is the evidence? Attachment in a readable format Content repository and document link
What changed later? Relevant change information Archived history and user identity
Who can retrieve the records? Search access for authorised business users User management and roles

Sources: [1] [3]

Choose an archiving architecture that meets the evidence requirements

SAP describes ILM Retention Warehouse as one way to decommission systems and retain historical data. Check which objects, context and search functions your implementation actually covers. Confirm licences, release and implementation scope for the project. The architecture itself does not establish suitability for GxP use.

Options include controlled historical access, a specialist archive and selective migration to the target system. Compare search, relationships, readability, access and operations as well as export speed and storage cost. Can the business continue to use the records for the necessary period?

Identify the authoritative historical record for each relevant object. If part of the record resides in S/4HANA and the rest in an archive, document how users can trace the link. Retrieving it should not depend on finding a former administrator who remembers the setup.

Sources: [2] [1]

Acceptance test for retrieving a historical batch

For batch C-2048, a reviewer needs the material reference, inspection record, usage decision and explanatory attachment. The archive produces the batch number and record, but the attachment is accessible only through ECC. This search still depends on the legacy system.

Start with a business question and an agreed reference package. An authorised reviewer finds C-2048 without access to production ECC, opens the document chain, identifies the correct inspection record and reads the attachment. Compare the results with the reference package. Counting exported files cannot demonstrate those relationships.

Include cases covering different object types and known exceptions. Examples include an older archive generation, a corrected transaction, a missing or damaged attachment and a user without access rights. One straightforward case cannot cover the whole architecture. Explain your selection in terms of risk and known differences in the records.

Acceptance matrix for historical retrieval without ECC
Test caseExpected resultEvidence
Find C-2048 The correct historical batch can be identified unambiguously. Search criterion and result
Open the document chain Required relationships between materials and transactions remain intact. Comparison with the reference package
Read the attachment The correct content is available in a readable format. File, link to the record and displayed result
Interpret the history The original decision can be distinguished from a later change. Sequence of events
Attempt unauthorised access The role model protects the data. Evidence of the denied action
Restore the archive The required records can still be retrieved after restoration. Restoration evidence and a retrieval test by a business user

Sources: [1] [3]

Check completeness and meaning separately

For structured data, use counts by object type, key checks and comparisons of business content. Define the unit to count, such as source documents, line items, relationships or attachments. Matching document counts can conceal missing line items or incorrect links.

Check attributes that affect meaning, including units, dates, status, identity and master data valid at the time. A current material description can change how a historical transaction appears. Decide which historical information to retain and how users will recognise the version they are viewing.

For large datasets, a justified combination of automated checks across all records and targeted business cases may be appropriate. Consider known exceptions and high-impact scenarios. A sampling percentage alone cannot explain coverage. Investigate discrepancies and determine whether they affect other records systematically.

Sources: [1] [3]

Set the cut-off and resolve transactions and shutdown dependencies

Determine when the last relevant data state becomes available. An export taken before final corrections and closing entries can become obsolete. Define the final processing runs, incremental transfers and checks for unresolved transactions in the legacy process. Document the actual final state.

Inventory background jobs, interfaces, user directories, certificates, database access, reporting services and document stores. A replacement ERP process may still expect a nightly file from ECC. Plan how to disable each connection and what evidence will demonstrate controlled shutdown.

Plan fallback arrangements for the transition. Identify triggers, owners and resources. A backup only supports fallback if the necessary components can be restored under the planned conditions. Starting the database does not demonstrate that a business user can retrieve and interpret the records.

Sources: [1] [2]

Who authorises decommissioning and takes responsibility for the archive?

The final report connects scope, data reconciliation, retrieval tests, outstanding issues and technical shutdown activities. State any limits. If historical objects still require ECC, approve only the scope supported by evidence. Any remaining access needs an owner, operating support and access controls.

Assign archive ownership and define access procedures, restoration, format maintenance and periodic reviews. Include changes to operating systems, viewers and identity services. Historical data stay usable only if the required environment or a suitable replacement remains available.

The shutdown approval should record which evidence for continued business use was reviewed and who owns the decision. The project schedule and budget cannot establish whether records subject to retention will still serve their purpose after shutdown.

Sources: [1] [3]

Further reading:

Project experience and collaboration

Demonstrate access to historical ECC records before shutdown

With your data and process owners, choose an ECC transaction that staff must still be able to investigate after the change. We follow its documents, relationships and open follow-on transactions into the planned target system or archive. If the evidence there is complete, you can coordinate migration and shutdown. If a required function remains available only in the old system, assess controlled access to it or another solution. The authorised owner bases the decommissioning decision on the results and the responsibilities that remain.

Frequently asked questions about Decommissioning SAP ECC

Is a complete ECC backup sufficient for decommissioning?

A backup alone cannot demonstrate lasting, authorised access to intelligible records. Check restoration, software, licences, user identities, attachments and retrieval by the business. A backup can form part of the design if you demonstrate its suitability for the intended historical use.

Sources: [1]

Must all ECC data migrate to S/4HANA?

Not necessarily. Future business operations and historical retention may need different destinations. Preserve the relevant information, relationships and means of access. Justify which data you migrate, archive or may legitimately discard. Test the transitions between the chosen arrangements.

Sources: [1]

Does SAP ILM automatically establish GxP compliance?

SAP documents features of a possible architecture. Suitability depends on the objects, configuration, data transfer, retrieval and operating arrangements in your implementation. Assess the documented capabilities and your own acceptance evidence separately.

Sources: [2]

Can a PDF replace the historical SAP record?

Identify what the record must establish. Does the output preserve the relevant data, links and context in a usable form? A single PDF may be insufficient for a dynamic or linked record. Assess how the record is used before accepting a file format.

Sources: [3]

What happens to open transactions at shutdown?

Assign each outstanding transaction to a defined closure or transfer process. Check final processing runs and changes after the first export. Record the final data state and any limitations in the shutdown decision. An unresolved transaction remains in scope even after the planned shutdown date.

When is the decommissioning project complete?

When the approved scope is technically closed, the necessary historical access is demonstrated and a named owner has accepted ongoing operations. Document the purpose and limits of any residual access or transition arrangement. A successful S/4HANA go-live may be a prerequisite, but it does not close the ECC project.

Sources: [1]

Sources and review date

Sources were checked on 14 October 2026. The regulatory interpretation and product capabilities are supported separately. Adapt our examples, test matrices and templates to your intended use.

  1. European Commission, EU GMP Annex 11: Computerised Systems (2011)EudraLex listed this edition as current on 14 October 2026. It addresses applications, risks, operation and the data lifecycle. The proposed tests are our own examples.
  2. SAP, Using ILM Retention Warehouse for System DecommissioningSAP product documentation on decommissioning architecture. Check availability and coverage for the particular objects in your project.
  3. PIC/S, PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection guidance on data integrity, including electronic data, transfer, access and review.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Discuss your SAP ECC shutdown

We assess the records with your team and test what users can retrieve from the actual system. Tell us the intended use, the evidence you have and the next step you are considering.

  • GxP system decommissioning →

    Retire legacy systems while preserving data, context and auditability. We plan and manage the decommissioning so that data, metadata and audit trails remain readable and retrievable after shutdown.

Send a project enquiry Customer testimonials →