Several suppliers can list the frameworks your application might use next. Fewer proposals explain how the team will discover undocumented behavior, validate old records and preserve work if a cutover needs to stop.
Choosing a legacy software modernization company means evaluating how it handles uncertainty and operational responsibility. Technology experience matters, but the selection should also test the supplier's ability to define scope, produce evidence and leave your team able to operate the result.
Compare responses to the same brief
Give shortlisted suppliers the same workflow summary, dependency inventory, representative data profile and constraints. State what you know and what remains uncertain.
Ask each supplier to explain the proposed first engagement. A bounded assessment or capability trial should have deliverables, acceptance conditions and a clear next decision.
Avoid comparing an implementation-only quote with a proposal that includes migration, training and support. Normalize scope before judging price.
Evaluate the discovery method
Ask how the team will identify integrations beyond the source repository. Request its approach to operational interviews, runtime observation, data profiling and recovery review.
A strong answer should distinguish facts from assumptions and identify who resolves business-rule ambiguity. It should not promise complete understanding from a repository scan alone.
Our assessment checklist can serve as a common basis for that conversation.
Request evidence relevant to your constraint
A supplier's experience with a framework does not establish its experience with your migration problem. Ask for examples involving comparable data, availability, integration or operating constraints.
Have the supplier explain the problem, its responsibility, verification method and limits of the reported result. Do not require confidential client material; an appropriately anonymized explanation can still demonstrate a method.
For an illustrative database migration discussion, useful evidence would explain mapping and reconciliation decisions rather than showing only the new application interface.
Test the proposed delivery and ownership model
| Area | Question to ask |
|---|---|
| Scope | What is included, excluded and assumed? |
| Rules | Who accepts behavior and intentional changes? |
| Data | How are exceptions and reconciliation handled? |
| Cutover | What happens to new transactions during recovery? |
| Staffing | Who performs the work and handles escalation? |
| Handover | What can our team build, deploy and recover afterward? |
| Support | What service responsibilities apply after launch? |
Request named roles and responsibilities even if individual staffing is finalized later. Clarify how knowledge remains available if a team member changes.
Review security and access arrangements
Determine what repository, environment and data access is necessary. Agree how access is granted, reviewed and removed.
OWASP ASVS can provide a basis for specifying relevant web application security verification requirements. Agree a scope and evidence rather than accepting a general claim that the new application will follow best practices.
Include temporary migration tools and environments in the responsibility discussion. They can handle sensitive records even if they are not part of the final product.
Inspect the commercial assumptions
Ask what happens when an assumed interface or data condition proves incorrect. A useful proposal defines the decision process, approval responsibility and effect on scope or schedule.
Clarify ownership of source code, deployment definitions, data mappings and operational documentation. Make knowledge transfer an accepted deliverable, not an informal final meeting.
Review support terms using precise definitions. Response, diagnosis, workaround and resolution are different commitments.
Start with a reviewable commitment
A limited first engagement can reveal how the supplier investigates, communicates uncertainty and works with your internal team. Define what you should receive even if you decide not to continue.
Tranz Technologies offers software modernization assessment and delivery. Discuss your current constraints with the workflow, dependencies and acceptance requirements you want a partner to address.
Talk through your software challenge.
Share your existing system, the constraints and what needs to change.
Discuss your project ↗