1. Legacy applications tie up budget since legacy applications are more difficult to maintain.
I disagree replacement solutions end up costing 2-3 times what the original budget was and they still don’t meet the needs of the business.
2. Keeps IT from innovation
It is considered that legacy applications are more difficult to maintain and they also require much of the IT department’s attention. This is true to a degree but maintaining a solution can be cheaper than a replacement and you know what it does and how it works. The beauty of the IBM midrange platform is that is you can then take the best bits and integrate with new technologies to take advantage of innovation.
3. You can’t upgrade and move forward with Technology
It is considered that while legacy and custom while custom-built solutions sound nice on the surface, this approach comes with multiple problems. Due to limitations found within your legacy applications themselves, certain features cannot possibly be added to some legacy apps. Building modern features into an old foundation isn’t even an option for some companies. This ISN’T the case for IBM Midrange solutions. This platform is happy to run legacy applications that could be 20 yrs old alongside the latest technology without any hiccups.
4. Legacy Resources are expensive
It is thought that since most companies don’t have the skills or the time to customize their legacy applications, it often requires outside consultants…which drives the cost up. This is wrong you will find that the developers skilled in RPG are competitively priced and have years of business expertise that the newly skilled technicians can only dream to have. Even if the cost seems a little high their business expertise can save thousands in the long run.
5. It further ties you to outdated technology
This isn’t true with the IBM midrange platform you can have the best of both worlds.
6. The system is old fashion and the users Don’t like it
People don’t like change. When you replace legacy systems — don’t underestimate resistance. Replacing a legacy system asks a lot of impacted business units and users. Even a successful legacy replacement project can be highly unpopular.