Give providers the same problem statement

Describe the current architecture, supported environments, business workflows, data stores, and integration dependencies. State the modernization objective and constraints on downtime or rollout. Share the same sanitized brief with each candidate so differences in proposals reflect their approach rather than different assumptions about the work.

Ask candidates to identify unknowns before estimating implementation. Useful questions concern data quality, hidden batch jobs, unsupported libraries, and access to domain experts. A proposal that confidently prices an undefined migration without explaining discovery assumptions should receive closer scrutiny, regardless of its presentation quality.

Request comparable proof of capability

Ask for authorized references or public case material that describes starting conditions, work performed, verification, and the provider's actual role. Treat an unrelated technology logo as weak evidence. Where confidentiality limits detail, request a concrete explanation of the team's proposed approach to your own constraints.

Use a bounded discovery or technical exercise when appropriate: map one workflow, identify migration risks, and propose a reversible first increment. Evaluate the reasoning and resulting artifacts. Do not ask for production access or confidential code before the necessary permissions and commercial arrangements are established.

Evaluate delivery and ownership terms

Compare who owns data migration, rollback, incident response, security review, and post-change maintenance. Clarify how progress and acceptance will be demonstrated. A provider with a strong implementation team may still be unsuitable if your organization expects operational responsibilities that its proposal does not include.

Document tradeoffs rather than producing a universal ranking. A small repository cleanup and a multi-country platform replacement need different capabilities. Getzilla's repository workflow is a tool a team can use while changing code. It should not be scored as a substitute for a contracted, end-to-end enterprise modernization provider.

Working sheet

Provider evaluation questions
CriterionAsk forWarning sign
System fitRelevant constraints and proposed approachOnly a broad technology list
DiscoveryExplicit unknowns and investigation planEstimate without assumptions
MigrationData validation and rollback ownershipMigration treated as a minor detail
AcceptanceObservable checks per incrementProgress measured only by activity
HandoverRunbooks and maintainership planOwnership ends without transition
Download this worksheet (CSV)

Questions about how to compare legacy modernization companies

Which modernization company is best?

Define your scope first, then compare relevant evidence and responsibilities. This guide does not fabricate vendor rankings.

Are case studies enough to choose a provider?

They help establish relevance, but you still need a proposal, references where available, and explicit responsibilities for your own system.

How should I use the working sheet?

Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.

Sources and further reading

Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.

Make the next change verifiable.

Getzilla is an open source workflow for changes to existing repositories. Inspect the project, define acceptance checks, and keep independent review in the loop.

See the repository workflow See current access and pricing