A Practical Guide for Retiring Legacy Applications 

Informatica White Paper 

It’s not uncommon for companies that have been in business for a while to have hundreds of legacy applications that deliver limited value--but still involve significant operational and maintenance costs. 

Many of those organizations are now asking some key questions: Why continue to waste money maintaining applications that no longer add value to the business? Why not redirect that money to where it will benefit the organization?

But retiring legacy applications can be tricky. Some are reusable. Some need to be retired. How do you tell which is which? Do you retire all the data or just the data required for business needs and regulatory compliance? How do you preserve the business context of the data? How do you secure it? How do you access it after it’s been retired?

In short, how do you retire a legacy application and the supporting software and hardware stack, and still keep the data accessible for reporting, regulatory compliance, and regular business needs?

This paper discusses strategies for retiring legacy applications, how to make decisions about which applications should be retired, and the seven key steps involved in legacy retirement. It also introduces the key advantages of the Informatica solution for application retirement.

 

Note: To view PDF files, download the latest version of Acrobat.