Pricing and quotation guide
Legacy software modernization cost
Legacy modernisation is hard to price without looking inside the system, because the work depends on how the code is built, what it connects to and how much is undocumented. That is why a paid assessment usually comes first. Just as important is the cost of not modernising: slow changes, rising support effort, security exposure and the risk of a failure nobody can fix quickly.
This page explains how modernisation is costed, how routes compare and how to weigh them against doing nothing.
Illustrative diagram
- Assessment
- Stabilise
- First stage
- Review
- Further stages
- Retire old system
What drives modernisation cost
- Route chosen
- Rehosting is usually smaller than staged replacement.
- System size
- Number of features, screens and integrations.
- Code condition
- Structure, tests and documentation affect speed of change.
- Hidden rules
- Undocumented logic takes time to uncover and verify.
- Data
- Volume, formats and synchronisation during transition.
- Availability needs
- Zero-downtime switching needs more planning.
Costs paid to third parties (separate from our fees)
- New hosting and infrastructure
- Licences or services replacing old components
- Running two systems during transition
- Staff time for knowledge sharing and testing
Running old and new side by side is a real cost and should appear in the budget.
The cost of doing nothing
| Cost | How it shows up |
|---|---|
| Slow change | Simple requests take weeks; opportunities missed |
| Support effort | Time spent keeping the system running |
| Knowledge risk | Dependence on one person or an outside supplier |
| Security exposure | Unsupported components without fixes |
| Failure impact | Disruption if the system stops and cannot be restored quickly |
Why assessment comes first
Quoting a large modernisation without examining the system means guessing, and guesses either include a large margin or lead to overruns. A short, paid assessment reviews code, hosting, data and knowledge, then sets out realistic routes with ranges for each. It also produces documentation that is useful whatever you decide. Treat the assessment as a standalone deliverable you own.
Ask what the assessment will produce before agreeing it.
Comparing routes on cost
Stabilise only
Suits you when
- System rarely changes
- Main risks are backups, hosting and documentation
Watch out for
- Lower spend now, but underlying problems remain
Rehost
Suits you when
- Hardware or hosting is the main risk
Watch out for
- Moderate cost; code issues remain
Staged replacement
Suits you when
- Technology unsupported or design no longer fits
Watch out for
- Higher total, spread across stages; two systems for a while
Example: staging the spend
Illustrative example — not a client case study
Situation: A business relies on an old order system running on an unsupported server.
- An assessment finds the hosting risk urgent and the code workable.
- Stage one rehosts the system with verified backups and monitoring.
- Later stages replace the reporting and customer areas in turn.
What this shows: The most urgent risk was addressed quickly, and later spending was planned as each stage proved itself. This example is illustrative.
Building the budget
Now
- Assessment
- Stabilisation: backups, documentation, monitoring
- Urgent security measures
Stages
- Each stage with its own estimate and review
- Parallel running costs
- Data migration and checking
After
- Hosting and maintenance of the new system
- Retirement of old infrastructure
- Ongoing improvement budget
Savings to count
Modernisation can reduce costs as well as add them: lower support effort, retired servers and licences, faster changes and less time lost to workarounds. Estimate these honestly and include them in the comparison, but do not count them before the old system is actually retired.
Living with uncertainty in estimates
Even after an assessment, modernisation estimates carry uncertainty, because old systems hold surprises. Good estimates show ranges and identify where the biggest unknowns lie, such as an undocumented integration or a poorly understood calculation. Budgeting a contingency and reviewing estimates at the end of each stage keeps spending under control without pretending the uncertainty is not there.
Be wary of a quotation that is precise without having looked at the code.
Timing the investment
Modernising before a crisis is usually cheaper than after one. When a system fails, work happens under pressure, choices narrow and costs rise. Planning the first steps while the system still runs gives time to choose the right route and spread spending sensibly.
Supplier and licence fees
If an outside supplier still maintains the old system, their fees belong in the doing-nothing column, along with any licence renewals for outdated components.
Presenting costs to decision-makers
Show each route with its range, timescale, risks and what it leaves unresolved, alongside the doing-nothing column. A one-page comparison is easier to decide on than a long technical report.
Questions about legacy software modernization cost
Why is legacy modernisation hard to price?
The work depends on code, integrations and undocumented rules that need examining first.
What does an assessment cost cover?
A review of code, hosting, data and knowledge, with realistic routes and ranges.
What is the cost of doing nothing?
Slow change, support effort, knowledge risk, security exposure and failure impact.
Which route is cheapest?
Stabilising or rehosting usually cost less now but leave deeper problems.
Do we pay for two systems at once?
During staged replacement, yes; include it in the budget.
Can modernisation save money?
It can reduce support, hosting and licence costs once the old system is retired.
Can modernisation estimates be precise?
Not fully; good estimates show ranges and name the biggest unknowns.
Request a Custom Quote
Ask about Legacy software modernization cost
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.