Skip to content

Legacy ModernizationLegacy application modernization without stopping the work.

Legacy application modernization is deciding whether to stabilize, update, rebuild or move an older system, then changing it without a single risky cutover. We assess your system, identify its risks and cost each option, including cloud migration and doing nothing, and you choose the approach before implementation starts. It is for businesses running software they cannot upgrade and cannot turn off, including a build a previous vendor left unfinished.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing

What you get

What you walk away with.

  1. Dependency map and risk register
  2. Sequenced plan of independently valuable slices
  3. Characterization tests for legacy behavior
  4. Reconciliation tooling proving data parity
  5. Rollback procedure for every slice
  6. Decommissioning plan with license and hosting savings

Sounds like

You might recognize one of these.

  • We can’t upgrade it and we can’t turn it off.

  • The vendor we hired left it two-thirds finished and walked away.

  • We built it on a low-code platform and it can’t handle the volume any more.

  • The person who built it has gone, and it was mostly them and an AI.

How it runs

Phases and timing.

  1. 3–5 weeks

    Modernization assessment

    Code and data archaeology and interviews with the people who keep it running, ending in a costed plan with three options, including doing nothing. Fixed fee, quoted against your estate and budget.

  2. 1–2 weeks

    Inherited system review

    For one system you did not build and now own. Four answers: what you have, what it costs to keep, what it costs to replace, and our recommendation, which is sometimes to keep it. Fixed fee, quoted on the first call.

  3. 8–12 weeks

    First slice

    Move one valuable capability off the legacy system and run both in parallel until the numbers agree.

  4. 6–24 months

    Sustained migration

    Slice after slice on a predictable cadence, with the legacy footprint reported every month.

The detail

What the scope includes.

Legacy Modernization and Cloud Migration

We review the existing code, data, dependencies and operating risks. Where possible, we interview its builders or maintainers. Discovery has a fixed fee based on system size and complexity.

More about Legacy Modernization and Cloud Migration

When discovery is done, you get a report on how the system works today and your options for what to do next:

Stabilize
Fix the riskiest problems and document what's there
Modernize in stages
Replace one part at a time while the old system keeps running
Rebuild
Replace the system entirely, with a planned cutover and data migration
Migrate to the cloud
Move the system to cloud infrastructure, with responsibilities for maintenance, access, backups and data protection agreed in the plan

We compare the cost, schedule and risk of each option. You choose the approach before we quote implementation. The migration plan includes testing, data checks and rollback arrangements.

When this service fits

  • You want to cut the cost and risk of maintaining old infrastructure
  • You want help managing infrastructure and data protection
  • You want systems that scale without adding overhead
  • You want to reduce operational risk and improve reliability
  • You want to get to market faster
Show all 6 parts of the scope
  • Archaeology and dependency mapping

    Before anything changes, we map what calls what, which jobs are load-bearing and which tables are read. Most modernizations fail on surprises this stage removes.

  • Strangler-fig migration

    A routing layer lets new code take traffic route by route, so the old system shrinks steadily instead of being replaced on one date.

  • Data migration and reconciliation

    Dual-write, backfill and automated reconciliation prove old and new agree, row by row, before anything is cut over.

  • Characterization testing

    Undocumented systems get a test suite that captures what they do today, including bugs the business depends on. That suite makes change safe.

  • Inherited builds: low-code, no-code and AI-generated

    The logic may live in a platform’s configuration, and the ceiling is usually a license tier or record limit. We map what is yours, what is locked in, and what leaving costs.

  • Mainframe and thick-client exits

    AS/400 and RPG, COBOL batch, VB6 and WinForms, Access and Excel VBA, on-premise Delphi. Discovery finds the hard part of each before the estimate is written.

Show the tools we use
Legacy we work in
  • AS/400 · RPG
  • COBOL
  • VB6
  • Delphi
  • Access/VBA
  • ColdFusion
Migration patterns
  • Strangler fig
  • Change data capture
  • Dual-write
  • Anti-corruption layer
Targets
  • PostgreSQL
  • Azure
  • AWS
  • .NET 9
  • TypeScript
  • Python
Proof
  • Reconciliation harnesses
  • Golden-master tests
  • Shadow traffic

Questions

Common questions.

  • A dependency map and risk register, a sequenced plan of independently valuable slices, characterization tests for legacy behavior, reconciliation tooling that proves data parity, a rollback procedure for every slice and a decommissioning plan. The assessment takes 3 to 5 weeks and ends in a costed plan with three options, including doing nothing.

  • Yes. Moving to the cloud is one of the options the assessment costs, next to stabilizing, updating and rebuilding, and the targets include Azure, AWS and PostgreSQL. Dual-write, backfill and automated reconciliation prove the old and new systems agree before anything is cut over. A cloud migration changes who is responsible for what; it does not remove your own security and data obligations.

  • AS/400 and RPG, COBOL batch, VB6 and WinForms, Access and Excel VBA, on-premise Delphi and ColdFusion, plus inherited low-code, no-code and AI-generated builds. Discovery finds the hard part of each before the estimate is written.

  • Usually yes, and it’s often the right structure. The people who know the legacy system are an asset, not an obstacle; we typically pair with them rather than replacing them.

  • Every slice must deliver value on its own and measurably shrink the legacy footprint, and we report both monthly. The plan is the deliverable before any code moves: the U.S. Government Accountability Office found that agencies without a complete, documented modernization plan “will have an increased risk of cost overruns, schedule delays, and project failure”.

    Information Technology: Agencies Need to Develop Modernization Plans for Critical Legacy Systems (GAO-19-471) (opens in a new tab), U.S. Government Accountability Office

  • Sometimes the answer is that the system is fine, and the review says so and tells you what to fix instead. It is a standalone fixed-fee engagement, not a lead-in to a project. You get three options costed side by side, and doing nothing is one of them.

  • Requirements almost never were complete, and a rewrite that trusts them inherits the gap. Characterization testing captures what the system actually does today, so we change it deliberately rather than accidentally.

The other practices

Where this practice stops, and who picks it up.

Software that runs a business process: the application, the data behind it, and the integrations that keep it fed.

Next step

Tell us what’s breaking.

Forty-five minutes, no charge. We’ll say what we’d do, what it would likely cost, and whether what you already have can be made to work.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.