Establish and Document Full Application Retirement

This chapter explains how to establish and document the Full Application Retirement of an Application.

Why Full Retirement Must Be Managed as a Program

Retiring an Application is far more than switching it off. Every Instance must be Decommissioned and Torn Down; every Integration must be removed or redirected; its data must be migrated, archived, or disposed of according to retention rules; its contracts, licenses, and support arrangements must be ended; its users must be moved to a replacement or told the service is ending; and its record must be updated. Each of these depends on knowledge of the Application, which is why Applications with poor documentation are so difficult and expensive to retire.

Establish Full Application Retirement

When the Business Application Owner decides to retire an Application, establish a retirement plan covering:

• Decision and rationale: why the Application is being retired, who approved it, and what replaces it, if anything.

• Users and business processes: how users and processes will transition, and how they will be notified.

• Downstream dependencies and Integrations: which Applications and processes depend on it, and how each will be changed.

• Data: what data must be migrated to a replacement, archived for retention, or securely disposed of, according to the Application’s retention rules and any legal holds.

• Instances: the Decommissioning and Tear-down of every Instance, including any that must remain available in a restricted capacity for a retention period.

• Contracts, licenses, and support: which agreements must be terminated or allowed to lapse, and by when, to avoid unnecessary renewals.

• Security: removal of accounts, access, Security Secrets, certificates, and network rules.

• Record and documentation: the transition of the Application Record to a Retired lifecycle status, and the archiving of the Application Documentation.

Document and Share the Retirement

Record the retirement plan, its execution, and evidence of completion for each item, such as data disposal certificates, contract termination confirmations, and Tear-down verifications, in the Application Documentation. On completion, set the Application Record to Retired, archive the Application Documentation so that it remains available for audit and reference for as long as required, and notify portfolio, architecture, risk, and finance functions.

Best Practice: Establish and Document Full Application Retirement

It is a best practice to both establish and document the solution for retiring an Application: plan and execute its retirement as a program covering users, dependencies, data, Instances, contracts, security, and records, record evidence that every item was completed, and archive its documentation rather than deleting it.

Benefits: A documented, complete retirement actually delivers the savings and risk reduction that justified it, with no forgotten Instances, renewals, or data left behind. Archiving the documentation preserves the knowledge needed to answer later audit, legal, and historical questions about an Application that no longer exists.

Common Antipatterns

Connections to Related IF4IT Practices and Inventories

The Application Portfolio Management (APM) Best Practices addresses modernizing and retiring applications deliberately and measuring rationalization progress. The Systems Development Lifecycle (SDLC) Best Practices describes the Retirement, Decommissioning, and Disposal phase.