How to Plan a Software Modernization Budget for the Next Year
Price the old system, the transition and the new run rate separately. This sample shows how overlap and delay change the total.

Build a next-year modernization budget by estimating current operations, transition work, training and the cost of running the new system. Count both run costs during overlap, and use a contingency tied to identified risks.
Key takeaways
- Set expected start and retirement dates for both systems.
- Estimate run costs separately from one-time transition work.
- Revise the forecast after discovery and trial conversion.
What belongs in the worksheet?
Use annual cash cost and staff capacity as separate views where useful. Convert staff time to a cost for comparisons only if the finance team agrees on the rate and the treatment.
| Cost group | Include | Estimate basis |
|---|---|---|
| Current operations | Hosting, licences, support and recurring repair work until retirement | Recent bills, planned retirement date and team time |
| Transition | Discovery, implementation, data conversion, testing and rollout | Work packages with assumptions and estimate ranges |
| Training and handover | Staff training, updated documentation and support readiness | People, sessions and coverage needed |
| Overlap | Time when both systems incur regular operating costs | Months each service is active |
| Contingency | Identified uncertainties such as a longer overlap or extra migration work | Risk, cost range, decision owner and release condition |
| New operations | Hosting, licences, monitoring, maintenance and support | Monthly run rate and expected first active month |
What does a sample year look like?
In a fictional plan, the old system costs CAD 3,000 per month and runs January through August. The new system costs CAD 2,000 per month and starts in July. Add CAD 42,000 for transition, CAD 6,000 for training and CAD 8,000 reserved for documented risks.
| Line | Calculation | Year-one amount |
|---|---|---|
| Old operations | 8 × CAD 3,000 | CAD 24,000 |
| New operations | 6 × CAD 2,000 | CAD 12,000 |
| Transition and training | CAD 42,000 + CAD 6,000 | CAD 48,000 |
| Contingency allocation | Separate reserve | CAD 8,000 |
| Total budget | Sum of the four lines | CAD 92,000 |
Both run costs already include July and August. If retirement slips by two months while the new start stays the same, the old system adds CAD 6,000 in this example. Decide whether that scenario draws on contingency or requires approval for more funding. The new system's twelve-month operating cost at the assumed rate is CAD 24,000, before any other changes.
When should you revise the budget?
Review it after dependency discovery, the first trial conversion and before each expansion decision. Update the forecast with actual spend, unresolved risks, remaining staff capacity and the latest retirement date. Use the phased modernization roadmap to tie spending to release and recovery checkpoints. Discuss Modernization & Maintenance with Wizy.
Frequently asked questions
How do you budget for two systems running at the same time?
Include each system’s operating cost for every month it remains active. Identify the overlapping months so you can recalculate the impact if either schedule changes.
What belongs in a modernization contingency?
Tie the reserve to uncertainties such as a delayed retirement or additional migration work. Record the estimated impact and who can approve using the reserve.
How is the first-year budget different from the new system’s annual run rate?
The first-year budget includes transition work and any cost of running the old system. Annual run rate projects twelve months of normal operation for the new system.
