IT ISSUE · PROJECTS AND CHANGE
Technology retirement planning
Rarely blocked by the system. Blocked by not knowing what still points at it.Retiring a system is rarely blocked by the system. It is blocked by not knowing what still points at it, because the things that depend on an old server are usually small, automatic and invisible until the morning they stop.
What tends to still depend on it
- A scheduled report nobody remembers requesting.
- A scanner or device sending to an old address.
- A mapped drive in somebody's startup.
- An application talking to it by name or by address.
- Records kept for compliance rather than for use.
- A backup job still protecting it, or no longer protecting what replaced it.
Find the dependencies, then turn it off in stages
We identify what the system does now rather than what it was built for, what still connects to it, what has to be kept and for how long, and what replaces each function.
The safe way to retire something is to make it unavailable before you make it gone. Disconnect it, leave it recoverable, and wait through the business events that could still expose a dependency, including month end where relevant. Anything that breaks in that window is a dependency nobody listed, and finding it while the system can be switched back on is the entire difference between a retirement and an outage.