An application is retired when its purpose disappears or another solution takes over. In Grassroot IT, this is a deliberate lifecycle decision covering data and dependent work as well as the application itself.
Clarify the successor and data handling
Establish who will perform the task in future. Agree required data and outputs when handing over. Consider retention duties, traceable business transactions and open issues. Define who may access retained data later and how access remains possible.
Handle unneeded data through the approved procedure. Suitable deletion or sanitisation depends on storage and sensitivity. The National Institute of Standards and Technology (NIST) explains an information- and media-based approach in SP 800-88, revision 2. Removing a file reference alone does not demonstrate secure sanitisation.
Make completion traceable
Review access, scheduled runs and connections to other applications, removing them within the authorised scope. Give users and affected owners the information needed for replacement. A short closure record identifies the decision, data handling, remaining retention and responsible party.
Organisational value remains a criterion through completion: necessary services must continue when the old solution is replaced.