What Does It Take to Retire an Old Business System Without Losing Its Records?
Every organisation has at least one system it no longer loves but cannot switch off. Vendor support ended years ago, only two people still know how it works, and the licence and hosting bills keep arriving. It stays alive for one reason, its records are still needed. That is why application retirement should be planned like a project, with the same care as the implementation that once launched the system. Treated as a side task, shutting down old software tends to stall or go wrong quietly. Exports get taken and trusted without checking. A server gets switched off and, months later, an auditor asks for a record nobody can reach. Planned properly, the project has a clear shape. Inventory what exists, decide what has to survive, move those records into a governed archive, validate the move, and only then decommission. Start With a Full Inventory The first phase is a plain inventory of the system and everything connected to it, written down rather than held in one person's memory. Wh...