5 Questions to Ask Before a Legacy System Goes Dark
Retiring a legacy ERP (enterprise resource planning) system doesn’t mean the data inside it can simply be left behind. Organizations still need to preserve historical records, maintain accessibility and meet legal and compliance requirements after the system is shut down. In his Corporate Compliance Insights article, enterprise data practitioner Mani Chandra Raparla argues that ERP decommissioning is often overlooked compared with implementing the replacement system. While the new ERP gets a budget, project team and governance structure, the old system may get little more than a shutdown date. Raparla points out that data migration and record preservation aren’t the same thing. Companies typically move active data and some history into the new ERP, leaving years of closed transactions behind. Yet those older records may be exactly what an auditor, regulator or attorney needs later.
Before shutting down a legacy system, organizations should ask:
- What records need to be retained? Identify the data that must be preserved for business, legal or regulatory reasons.
- Where will the records be preserved? Decide where historical data will live once the legacy system is gone.
- Will the data still be accessible years from now? Archived information needs to remain usable and searchable when someone eventually needs it.
- Have legal holds been addressed? Make sure records subject to litigation or other legal requirements aren’t accidentally deleted.
- How will records eventually be destroyed? Retention doesn’t mean keeping everything forever. Organizations also need a process for securely disposing of data once its retention period ends.
The article also points to an emerging consideration: historical data may become increasingly valuable for AI and analytics. The quality and accessibility of today’s archives could influence what organizations can learn from their past. Raparla concludes that when a legacy ERP goes dark, the data shouldn’t disappear with it.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
