Legacy Migration or Legacy Replacement?

When it comes to leadership, be it political, business, or otherwise, it’s not unusual for a conflict to exist between the previous generation and the more recent one: the ‘old’ versus the ‘new’. The older generation typically offers stability, reliable execution, and a common ground to keep things safe and balanced, while the newer generation brings to the table novelty, a new way of doing things, fresh ideas, progress and a promise to ‘change the world’. This is evolution vs. revolution.
Technology decision makers frequently face a similar 'old vs. new' dilemma when it comes to legacy migration. Do we stay with the 'old', keeping our legacy systems running for as long as possible and only gradually migrating to new networks/systems? Or do we go 'new' by replacing our legacy equipment, ripping it apart and forklifting our infrastructure in order to enjoy a more innovative and current technology?
This type of decision is best made only after you evaluate the risk against the expected rewards, quantifying your migration efforts (time, material, costs) as well as the benefits of a newer technology. Sometimes, it will make more sense to revolutionize. Other times, a gradual evolution will prove best.
The good news is that we at RAD still invest a great amount in developing products that offer an excellent evolution path for many applications. For example, TDMoIP as a path to migrate TDM voice to an IP network. Or, the ability to migrate older protocols and/or older data communications gear (RS-232, V.35, RS-422, HS-UDP to name a few) over current and next generation networks (IP, ATM etc.).
And yes, assessing your scenario and qualifying and quantifying your options is complicated. If this type of challenge is familiar to you, I’d love to hear about your decision process.
