The Problem with "Legacy" (Blog: ISV Blog)

Part of Tech Corner - The Problem With "Legacy"

If you don't change, you stagnate. It's bad enough in the "real" world - and forget about the technology sector. There are new acronyms and new paradigms every other month. There are young, hungry companies with zero technology bias, starting from scratch, with nothing to lose, nothing to convert and zero installed base. In short, they have no legacy to support.

A lot of ISVs have a problem. The 4GL that they've based their entire system on is either hopelessly out of date (Delphi, Oracle Forms); not being supported anymore (FoxPro); have a proprietary, non-SQL database (FileMaker, Progress, Access, Alpha 5); and/or have no way to support modern, standards-based technologies (web services, XML, HTML, PDF, etc.).

There are only two ways to go if you find yourself in that position:

1. Do nothing and continue doing what you're doing
   
2. Completely re-write your application in another more modern tool/technology

Option 1 is attractive because it doesn't involve any change on your part or your customers. The danger is that a new competitor will emerge without the legacy and packed full of the technologies and standards that customers are demanding.

Option 2 is painful. It involves a learning curve, re-training customers, data conversion and much more. The payoff is that you re-vitalize your existing customer base, gain new market share, and continue to have the ability to provide value to your shareholders, employees and end customers.

It's a tough business decision, and by not deciding, you've already made your choice.