Rebuild vs Modernise vs Patch: A Practical Guide
Rebuild vs modernise vs patch framework with cost and risk comparisons. Decide the safest path for ageing software and legacy platforms.
Rebuild vs modernise vs patch framework with cost and risk comparisons. Decide the safest path for ageing software and legacy platforms.
Who this is for
IT leaders and operations managers dealing with ageing business software that's becoming expensive to maintain or limiting business growth.
Question this answers
Should we rebuild our old system from scratch, modernise it piece by piece, or just keep patching it?
What you will leave with
When you are dealing with ageing software, the options feel binary: suffer through it or spend a fortune replacing it. But there are actually three distinct approaches, each with different cost profiles, risk levels, and timelines.
Throw away the old system, design and build a new one from the ground up.
When it works:
Risks:
Replace the old system piece by piece while keeping it running. New features go in the new system; old features get migrated over time.
When it works:
Risks:
Keep the existing system, fix what is broken, add what is missing, accept its limitations.
When it works:
Risks:
| Criterion | Rebuild | Modernise | Patch |
|---|---|---|---|
| Typical cost | Highest | Moderate | Lowest |
| Timeline | 6-18 months | 3-12 months (phased) | 2-8 weeks per fix |
| Risk level | High | Medium | Low per patch, high cumulative |
| Business disruption | Significant (migration cutover) | Low (gradual transition) | Minimal |
| Long-term value | Highest (modern foundation) | High (modernised incrementally) | Low (technical debt grows) |
| New features during project | No (until new system launches) | Yes (new system handles new work) | Yes (but limited by old system) |
The strangler fig pattern is the most reliable approach for modernising critical systems. Named after the strangler fig tree that gradually grows around its host, the pattern works like this:
This gives you the benefit of a rebuild with the safety of incremental delivery. At any point, if the project stalls, you still have a working system: partly old, partly new, but functional.
Rebuilding replaces old software with a new system designed from scratch. Modernising replaces it piece by piece while it keeps running, with new features going into the new system. Patching keeps the existing system, fixes what is broken and adds what is missing while accepting its limits. Each approach carries a different cost profile, risk level and timeline.
Rebuilding business software from scratch makes sense when the technology is genuinely obsolete, with no developers or vendor support, when the architecture is fundamentally broken, or when business needs have changed so much that the old system cannot adapt. The system should also be small enough for a bounded project. Rebuilds typically take 6 to 18 months, with no new features during the build.
Patching an ageing system is the right choice when the core is still fundamentally sound, the technology still has developer support, and the immediate needs are specific and well defined. It also suits a constrained budget, or buying time to plan a proper replacement. The catch is that each patch makes the next one harder, so patching can be cheap now and very expensive later.
The strangler fig pattern replaces an old system one component at a time while the old system keeps running. You pick a clear boundary such as reporting or a customer portal, build the new version, route users to it, move the data, switch off the old component once the new one is proven, then repeat. If the project stalls, a working system remains.
Incremental modernisation is the safest way to update a mission-critical system that cannot go offline. Replacing it piece by piece spreads the cost over time, keeps business disruption low, and lets new capabilities arrive during the migration. If unsure, modernise one component first, prove the approach works, then decide whether to continue piece by piece or commit to a full rebuild.
Ask the author
Ask it here and it comes straight to the founder. No sales call, no obligation, and a real answer even if the answer is that you do not need us.
Kasun Wijayamanna
Founder, replies within one business day
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
Built here. Your data stays here.
Thanks for reaching out. We will get back to you within one business day.
See what else we do