Quick Summary
Legacy SAP decommissioning means retiring an old SAP system once you have mapped its dependencies, removed unused custom code, classified data for retention, and archived what you must keep. Most companies move closed records into a read-only archive, such as SAP ILM, and then shut the live system down in phases.
- Map every instance, interface, batch job and report owner before any shutdown work begins.
- Check batch jobs and scheduled interfaces, not just recent logins, to judge whether a system is unused.
- Remove or document unused custom code before migrating it to avoid paying to move and test it twice.
- Agree retention periods with legal and compliance, since tax and audit rules vary by country and sector.
- Shut down in phases with a parallel run for each unit so problems surface while the source system still runs.
Table of Contents
- Why Retire a Legacy SAP System Now
- Step 1: Assess the Legacy Landscape and Map Dependencies
- Step 2: Identify Unused SAP ECC Custom Code Before You Retire It
- Step 3: Classify Data and Set Retention and Compliance Rules
- Step 4: Extract, Validate and Archive Structured and Unstructured Data
- Step 5: Run a Phased Shutdown, Audit Trail and End-User Change Management
- A Worked Legacy SAP Decommissioning Example and Checklist
- Start Your Decommissioning Project with Kagool
- Frequently Asked Questions
Why Retire a Legacy SAP System Now
Last Updated: November 19, 2026
Legacy SAP systems quietly drain budgets. Enterprises that decommission them can reduce operational costs. At Kagool, we help IT leaders decide when retiring an old SAP environment makes more sense than keeping it alive, and how to do it without losing data they need.
Keeping legacy applications running carries recurring costs for licences, hardware, support contracts and specialist staff. Money spent there is money not spent on S/4HANA, analytics or AI.
Two forces make 2026 a practical moment to act. First, the industry is moving toward “clean core” strategies, where the new ERP stays lean and historical data lives elsewhere (ERP Today, 2026) (Cloud ERP and a clean core can innovate your business). Second, memory costs are rising.
Decommissioning is not the same as deleting. Most companies still need old transactions for audits, tax returns and warranty claims. The goal is to move that data into a read-only archive, such as SAP Information Lifecycle Management (SAP ILM), and switch off the live system.
The steps below follow a practical sequence: assess, clean up custom code, classify data, extract and archive, then shut down in phases. Each step includes a checklist you can use with your own team.
Step 1: Assess the Legacy Landscape and Map Dependencies
Before you start any legacy SAP decommissioning work, you need a complete map of what the old system does and who depends on it. Most decommissioning projects fail here, not in the technical work.
Start with an inventory:
- List every SAP instance, database, and client in use
- Record which business processes run on each one
- Note interfaces to other systems, including banks, carriers and reporting tools
- Identify report owners and the people who run month-end close
Then map dependencies. A system that looks idle may still feed a monthly regulatory report.
Watch out: Teams often assume a system with no recent logins is unused. Check batch jobs and scheduled interfaces too, because they run without anyone logging in.
Step 2: Identify Unused SAP ECC Custom Code Before You Retire It
Long-running SAP ECC environments often carry decades of custom code. Some of it still runs. For a detailed method to find unused custom code, see how to identify unused SAP custom code before migration. Much of it does not. Find the difference before you migrate anything.
Work through this list:
- Pull usage statistics for custom programs, transactions and reports
- Check batch schedules for jobs that have not run in 12 months or more
- Confirm with business owners which reports they still open
- Mark code as keep, rewrite, or remove
- Document the reason for each decision
Migrating unused code costs money twice: once to move it and again to test it. Removing it before migration keeps the new S/4HANA environment lean.
Step 3: Classify Data and Set Retention and Compliance Rules
Not all legacy data deserves the same treatment. Sort it into groups before you extract anything, because the classification you agree here drives what gets migrated, what gets archived read-only, and what gets deleted outright. Explore a strategic framework for archiving SAP data to plan your retention approach.
| Data type | Typical use | Suggested handling |
|---|---|---|
| Open transactions | Live processes | Migrate to the new system |
| Closed financials | Audit and tax | Archive, read-only access |
| Personal data | Privacy-regulated | Archive with access controls, or purge |
| Old logs and temp data | Rarely needed | Delete after review |
Set retention rules with your legal and compliance teams. Tax and audit periods vary by country and sector, so confirm local requirements instead of guessing. A common pattern is to keep closed financials for the statutory period plus a buffer, then move them to a lower-cost archive tier rather than deleting them.
Structured versus unstructured data. Ledger entries, purchase orders and customer master records are structured and usually move cleanly into SAP ILM or a data lake. Scanned invoices, email attachments, PDFs and images are unstructured and need their own repository with clear indexing, otherwise they become unsearchable the moment the source system goes dark. Classify both types separately, because the archive tooling and validation approach differ.
Data privacy and GDPR/CCPA. If your records include employee or customer information, privacy law applies to how long you keep it and who can see it after decommissioning. Build a purge workflow into the plan rather than bolting it on later:
- Identify which fields in the legacy system hold personal data (names, addresses, national IDs, payment details).
- Map each field to a lawful basis and a retention period with your data protection officer.
- Decide per field whether to archive with access controls, pseudonymise, or purge before archiving.
- Record the decision and the legal basis in your data inventory so you can defend it later.
- Test that purged records cannot be retrieved from backups or the archive.
Watch out: teams often archive the whole database to be safe, which preserves personal data past its retention period and creates a compliance liability rather than removing one. Purge or pseudonymise before the archive is sealed, not after.
Keep the classification and retention decisions in a single document that legal, IT and the archive vendor all sign off on. That document becomes the reference point for the post-decommissioning audits described later in this guide.
Step 4: Extract, Validate and Archive Structured and Unstructured Data
This is the heavy lifting. Structured data, such as ledger entries and purchase orders, usually moves into SAP ILM or a data lake. Unstructured documents, such as scanned invoices and attachments, need their own repository with clear indexing.
Validate before you switch off:
- Reconcile record counts between source and archive
- Spot-check totals for financial periods
- Test that archived documents open and search correctly
- Confirm that audit users can retrieve records
The timing for this phase depends on data volume and system complexity.

Leaving legacy data behind creates the risk you are trying to avoid, so budget time to move it properly.
Step 5: Run a Phased Shutdown, Audit Trail and End-User Change Management
Switch off in stages, not all at once. Build a sequenced cutover plan with roles, validation checks and go/no-go criteria in the SAP data migration cutover plan. Shut down one business unit or region, confirm it runs cleanly for several weeks, then move to the next. A phased approach limits blast radius: if a batch interface or month-end report breaks, you find out while the source system is still available to fix it.
A practical sequence for each wave:
- Freeze changes to the legacy system for that unit so the archive stays in sync.
- Run a parallel period where users work in the new system but can still read the old one.
- Confirm the archive returns the same results as the live system for a sample of transactions and reports.
- Switch the unit to read-only archive access and monitor for a defined period.
- Decommission the unit’s access and record the sign-off.
Audit trail and post-decommissioning audit readiness. Most guides stop at data migration. The harder question is how you prove data integrity to tax authorities and auditors after the live system is gone. Keep an audit trail that records:
- Who approved each shutdown step and when
- Which datasets were archived and where they are stored
- Validation results and any exceptions found
- Access logs for archived data after go-live
- The retention rule applied to each dataset and the legal basis for it
A useful practice is to document each system’s decommissioning in a record that ties the archive to the source record counts, the validation results and the retention decisions. When an auditor asks for a closed period three years later, that certificate plus the archive index is what lets you answer without the legacy system. Test retrieval with a real audit request before you switch off, not after.
Change management for end users. Teams that lose a familiar report without warning will push back hard, and the people side of change often decides whether the project feels successful. Give each affected group a date, a replacement, and a training session before the old screen disappears. Identify the report owners and month-end close users during the assessment step and keep them in the loop through each wave. Where no replacement exists, agree a read-only archive view so users can still retrieve historical transactions without keeping the whole system alive.
Watch out: treating the shutdown as purely technical and communicating only at go-live is the most common reason a decommissioning project is judged a failure even when the archive works perfectly.
A Worked Legacy SAP Decommissioning Example and Checklist
Consider a manufacturer running separate SAP ECC systems in four countries. The team starts by mapping interfaces, then removes unused custom code before migration. It classifies financial records for ten years of retention and moves them to SAP ILM. It shuts down plant by plant over three months, with a parallel run for each site.
Use this checklist to track progress:
- Inventory of systems, interfaces and owners complete
- Unused custom code removed or documented
- Retention periods agreed with legal and compliance
- Archive validated against source record counts
- Shutdown plan approved with audit trail in place
- End users trained and replacement reports live
Start Your Decommissioning Project with Kagool
Decommissioning a legacy SAP system touches finance, IT, compliance and operations at once. Kagool works with IT directors and transformation leads on SAP and Microsoft-based data and ERP projects. Contact us to plan the first phase of your legacy retirement.
Frequently Asked Questions
How long does it take to decommission a legacy SAP system?
The duration of a legacy SAP system retirement project depends on the complexity of the architecture and the total volume of data. Systems with heavy custom code, many interfaces, or large historical archives sit at the longer end. Timelines also depend on how quickly business owners sign off on retention rules and how many data validation cycles are needed. Kagool can scope the timeline against your specific landscape during an initial assessment, and pricing depends on scope, data volume and delivery model, so request a quote for current figures.
How can you identify unused SAP ECC custom code before decommissioning?
Start by analysing usage logs and transaction statistics over a representative period, typically at least 12 months, to see which custom programs, reports and interfaces are actually executed. Cross-reference that with business process owners, who can confirm whether low-usage objects serve periodic processes such as year-end closing. Code that has no executions, no owners and no dependent interfaces is a strong candidate for retirement. Document every decision so the audit trail shows why each object was kept or removed.
What should organizations do with SAP data after decommissioning?
Data that must be kept for legal, tax or audit reasons should be migrated to a read-only archive or repository rather than left in a running system. SAP Information Lifecycle Management (ILM) can help manage retention periods and legal holds, and archived records should remain searchable so auditors can access them. Personal data needs particular attention under GDPR and similar privacy rules, so retention periods should be justified and deletion schedules enforced. Test that archived records can be retrieved before the legacy system is switched off.
Will SAP be supported after 2027?
Organizations still running SAP ECC should review SAP’s current maintenance announcements and plan their migration accordingly. Decommissioning the legacy system is usually part of the same programme as the move to S/4HANA. Check SAP’s current maintenance announcements directly, as support terms can change, and confirm which options apply to your contract.

