01 · How to use this
How do you use these questions with legacy modernization companies?
Send the same questions in writing to every firm on your shortlist and compare the answers side by side.
- 01
Written answers are easier to hold a firm to later than a sales call. Score each answer 0 (none), 1 (vague) or 2 (specific and checkable).
- 02
These questions apply to any firm, from large integrators to small specialists. They sit under our legacy application modernization service page, and the wider buyer's guide is how to choose an application modernization company.
02 · The questions
What should you ask a legacy modernization company?
These 14 questions are grouped by risk. Questions 1 to 5 decide whether the work is safe; the rest decide whether it is affordable and accountable.
| # | Question | A good answer sounds like |
|---|---|---|
| 1 | How do you prove behaviour is unchanged? | Tests run before and after each change, with the results shared with you |
| 2 | What if we have no tests? | We write characterization tests around the code first, then change it |
| 3 | Who reviews each change? | A named senior engineer, not a tool's summary |
| 4 | How do you use AI, and who is accountable for the output? | AI drafts the change, an engineer reads and signs it |
| 5 | Which tools do you use, and where do they fail? | Named tools with stated limits, not 'our platform handles it' |
| 6 | Which approach do you recommend for each application, and why? | A per-application choice from the options, with the reason |
| 7 | What is the target platform, and can we leave it later? | Open, widely used targets; no new proprietary runtime we would depend on |
| 8 | How is the work phased? | Phases that stand alone and can each be reversed |
| 9 | How is the price set? | Scope agreed first, then a fixed price for one phase |
| 10 | What does the estimate leave out? | A plain list: licences, environments, your team's time |
| 11 | What is your plan for cutover and rollback? | A written plan, rehearsed, with a named rollback trigger |
| 12 | Who does the work, and where? | Named engineers, with location and time zone stated |
| 13 | Who runs the system after go-live? | A run plan agreed before cutover |
| 14 | Can we speak to a client with a similar project? | A reference you can call, or an honest 'not yet' plus a sample run |
03 · Testing and review
Why do the testing and review questions come first?
Testing and review decide whether a change can be trusted, so they matter more than price or tooling.
- 01
A firm that cannot say how it knows the old and new systems behave the same is asking you to take that on faith.
- 02
Ask to see an example test, a review record or a pull request from a past engagement with client details removed. If the firm uses AI-assisted tools, ask what happens when the tool's output is wrong, and who found the last such error.
04 · Price and scope
How should a legacy modernization company price the work?
A sound price follows an assessment, not precedes it.
- 01
Be wary of a firm that names a figure before anyone has read the code or listed the applications in scope.
- 02
A short paid assessment is a practical way to test a firm before a large commitment. Ours is the modernization assessment: fixed price agreed after a scoping call, quote on request. For cost context see application modernization cost.
05 · Warning signs
What are the red flags in a modernization proposal?
Each flag below means a question above went unanswered. Treat one as a prompt to ask more, and several as a reason to walk away.
| Red flag | What it usually means | What to ask |
|---|---|---|
| Price quoted before anyone reads the code | The estimate is a guess, and you carry the overrun | What assumptions is this price built on? |
| No testing phase in the timeline | Behaviour will be checked by your users after release | How is behaviour proved at each phase? |
| 'AI does it all' with no named reviewer | Nobody is accountable for the output | Who signs off each change? |
| Nothing said about cutover or rollback | Go-live is treated as an event, not a plan | What triggers a rollback, and how long does it take? |
| A proprietary platform as the target | You trade one lock-in for another | Can we run the result without your product? |
| References that cannot be named or checked | The proof may not exist | Which part of this can I verify myself? |
| Engineers not named, or swapped after signing | Seniority in the pitch, juniors in delivery | Who will do the work, and can they stay? |
06 · Disclosure
How would Ace8 answer these questions?
Ace8 is the modernization practice of AceMQ.
- 01
Our short answers: tests first; AI-assisted changes reviewed by AceMQ engineers; open targets; a fixed-price assessment before any larger commitment; and 24/7 run support from AceMQ after go-live, described on supported after migration.
- 02
On question 14, Ace8 has no case studies of its own yet. The AceMQ engineering team delivered a phased messaging migration for American National, and we offer a sample run in place of a client reference where none fits.
07 · Next step
What should you do with the answers?
Rank nothing yet: first list which questions each firm answered specifically, then check two answers independently.
- 01
If you want the application-level picture before you invite proposals, start from our legacy application modernization page or book a fixed-price assessment.