A legacy application modernization project has to proceed at the pace that best matches an enterprise's specific needs. Instead of completely replacing everything all at once, a more gradual and strategic approach that fits the development of a business as well as the technology that they use. Joe McKendrick touches on this issue in an article for Insurance Networking News by calling for a measured approach to updating the mainframe.
Potentially destructive effects may result from trying to layer new solutions on top of older ones, McKendrick says, referencing a piece by Bradley de Souza for CIO New Zealand. Souza compared refurbishing legacy systems to urban renewal plans that remake entire areas at once, when plotting out change over time could have been more effective.
Because ensuring continued performance and runtime is constantly important, enterprises are under pressure to complete changeovers with a minimum of effort and cost. McKendrick says that "more organic" change, which fits into the operational pace of a business, is preferable.
"Simply dropping a huge technology solution on top of a business will never, in and of itself, magically deliver positive transformation, market growth, and profits," he writes. "It takes work on the ground, which eventually should be supported by technology."
Legacy applications solutions need to be selected to accommodate each individual business. A key part of the conversion process is the beginning, when IT managers and professionals have to plan out how a modernization will proceed, and how this will impact operations on a day-to-day basis as the system still runs. Weighing current each option individually helps determine an effective strategy.
Make the older applications in your system easier to incorporate into newer computers and devices through a long-term modernization solution. Find one that matches your needs and can be implemented correctly over time, so you reap the full benefits.