Choosing a Legacy System Modernization Partner: Questions to Ask Before You Commit

Modernizing a legacy system is risky enough without choosing the wrong partner. The system runs part of your business, few people fully understand it, and the work has to happen while it keeps running. Proposals for legacy software modernization services tend to look alike on paper, so the useful differences show up in the questions you ask. This post sets out the questions worth asking, what a good answer sounds like and the warning signs. It assumes you have decided to modernize. If you haven't, start with our post on modernization versus a rebuild.
How Will You Learn Our System?
1. What do you do before you propose a scope?
Legacy systems are poorly documented, so any scope given before the provider has looked inside is a guess. A good answer describes a defined first step: reading the code, mapping what the system does and how its parts connect, and giving you a written result. Ask whether you keep that result if you part ways afterwards.
2. How do you capture what the system actually does?
Some teams learn the system by working in it. Others reverse-engineer it first. On BlastAsia's Turnkey and xDD routes, for example, the existing codebase is mapped into a knowledge graph and a regenerated specification through the Xamun Software Factory before anything is rebuilt. Either approach can be right. What matters is that the provider can show you what the map looks like and who reviews it with you.
3. Who on our side do you need, and how much of their time?
A provider that needs no one from your side has not understood the problem. The people who know the business rules are essential, and their time has to be planned for.
What Will You Recommend?
4. Do you offer more than one way to modernize?
A provider with only one method will fit your system to it. Modernization can mean refactoring the existing code in place, rebuilding on the same stack, or moving to a new one. BlastAsia's App Modernization page describes all three: a dedicated developer team refactoring your code directly, and Turnkey or xDD rebuilding it on the same stack or a new one. Ask which the provider would pick for you, and why.
5. Will you tell us if we should not modernize?
Sometimes the right answer is to leave a stable system alone, retire it, or rebuild. A trustworthy provider is willing to say so, even if it means a smaller engagement. Our post on refactoring or replatforming shows how that choice is made.

How Will You Prove Nothing Breaks?
6. How do you show the new system behaves like the old one?
This is the question that matters most. A good answer covers automated tests, written business rules, and real cases from the old system that the new one must reproduce. If the old system has no tests, ask how the provider will create them.
7. How do we cut over, and how do we go back?
Ask for the plan to move from old to new while the business keeps running: what is replaced first, how long the two systems run side by side, and what the rollback is. BlastAsia's page describes a port of a B2B and B2C e-commerce platform off VB/ASP Classic and SQL Server 2000 onto .NET without disrupting the live storefront. Ask any provider for a comparable example and how it was done.
8. How do you handle the data?
Data usually outlives the application. Ask how it is moved, how it is checked after the move, and what happens to what you no longer need.
Who Will Do the Work, and Who Owns the Result?
9. Who will actually work on our system?
Ask who the engineers are, how long they have worked in your stack, and what happens if one leaves. Experience in the specific technology matters. BlastAsia has 25 years in outsourced software engineering, with a long record in C# and .NET. Ask any provider to show equivalent experience in yours.
10. Who owns the code, the documentation and the access?
You should hold all of it, on every engagement model, without a license that ties you to the provider. Ask for this in writing before work begins.
Warning Signs
A fixed price quoted before anyone has looked at the system. A single method presented as the answer for every system. No plan for testing, or "we will test at the end." A promise of no risk. A team that cannot name who will do the work. A contract that keeps the code or documentation on their side. Any one of these is worth a follow-up question.
How to Use This List
Send the ten questions to each provider in writing and compare the answers side by side. Differences in how specific they are will tell you more than differences in price. Then ask each provider to talk through the first step with the people who will do it.
If you are comparing partners for a legacy system, see our page on application modernization, or tell us what you are running and what is breaking, and we'll show you how we would start.
About BlastAsia: BlastAsia is a Philippines-based software company that builds AI-powered software for enterprises worldwide, whether it's a new application or AI layered on the systems you already run. We build it AI-natively: specifications first, with code generated and reviewed on the Xamun Software Factory, so delivery is faster and more predictable. Engage us as a dedicated team (xDD) or as a fixed-scope Turnkey build, and you own what gets built.




Comments