OpenLegacy Blog

How to Avoid These 5 Common Mistakes in a Legacy Modernization Project

Share this:

When your team is gearing up for a legacy modernization project, the uncertainty of how smoothly and quickly it will go can cause a lot of people a lot of headaches. That is only natural, as it is a huge undertaking that is critical to get right.

You can cure many of those headaches by simply avoiding five common mistakes that plague legacy modernization projects. We have seen them all, and the good news is that they are easy to avoid.

1. Choosing the wrong vendor

We hate to break it to you, but your brother-in-law who is a whiz at systems engineering is probably not the right person to undertake your legacy modernization project.

  • When you are looking for a vendor to work with, ask:
  • How many projects have you done like ours?
  • How long do they typically take?
  • How many have you delivered on time and on budget?
  • What kind of ROI did you deliver on those projects?
  • What information do you need from us before you can start?
  • What can we expect during the process?
  • How customizable is your solution?
  • How much control will we have over the new system? Can we maintain and update it in-house?
  • Do we have to pay up-front or monthly license fees?

2. Communicating on the fly

For any relationship to flourish, clear and honest communication is key. This is just as true at home as it is during a legacy modernization project. We have found that weekly email updates and team meetings are the perfect way to keep everyone in the loop, while executives appreciate monthly updates.

3. Forgetting to conduct an application portfolio assessment

Take it from us: Your vendor will be forever grateful if you conduct an application portfolio assessment before your first meeting. It should include all existing application and data types, hardware and software, and interdependencies.

4. Waiting to test til the very end

Make sure your legacy modernization project has testing built in every step of the way. When adjustments are made as the project progresses, it will go faster and smoother and greatly limit (or eliminate) bugs, glitches, and other surprises when it’s time to launch.

5. Underestimating how many people to involve

The legacy modernization projects that are most successful have the necessary resources committed to it. You will definitely want a project manager to run meetings, liaise with the vendor, and keep everyone on track, and you will also want to include subject matter experts in those meetings (as needed, of course), such as systems, applications, operations and database specialists.

Want to use a vendor committed to providing only successful legacy modernization projects – that save you time and money? Check out our case studies today!

Tags: Legacy Modernization, Open APIs

Share this: