In this article
Signs it is time
- End of support. Microsoft ended support for Windows 10 on October 14, 2025. Extended support for SQL Server 2014 ended on July 9, 2024, and for SQL Server 2016 on July 14, 2026. Without security patches, every newly discovered flaw stays open, unless you pay for Extended Security Updates, sold for a limited time. For Windows 10, organizations can buy them for up to three years, at a price that doubles every year.
- Every change is risky. A small fix breaks something else, and nobody dares touch the code anymore.
- The knowledge is gone. The original developer is no longer around, and there is no documentation.
- It cannot connect to anything else. No API, manual exports, double data entry all around it.
- It holds the business back. New needs get turned down because "the system doesn't allow it."
The 3 approaches
| Approach | How | Risk |
|---|---|---|
| Rewrite everything at once | A new system is built alongside, then you switch over on a given day | High: months with nothing delivered, then a switchover where everything has to work at the same time |
| Replace gradually | The new system grows around the old one and replaces it piece by piece | Low: each step is small, tested, and reversible |
| Modernize in place | You keep the system, update its foundations, clean it up, and add tests | Low to medium: a good choice when the architecture is sound |
Developers have a name for the second approach: the Strangler Fig pattern, described by Martin Fowler as a gradual approach to modernizing existing systems. Like the fig that grows around a tree, the new code settles in next to the old and takes over one function at a time, until the old system no longer does anything.
The method, step by step
- Take stock. Who uses the software, and for what? Which functions are critical, and which are no longer used? Where is the data? What does the system run on (server, database, versions)?
- Set up a safety net. Tested backups, and automated tests on critical behavior: they confirm that the old and the new give the same result.
- Break it down. Choose a first piece with real value and little risk: a report, a module, a screen.
- Run old and new side by side. Users go through the new system for that piece, and the old one keeps handling the rest. No downtime.
- Migrate the data in stages, with checks at each pass.
- Repeat, piece by piece, then retire the old system once it is no longer used.
Pitfalls to plan for
- Rules hidden in the code. The old software does things nobody documented: a particular rounding rule, an exception for one customer. They have to be found before they are lost.
- Real data is rarely clean. Duplicates, fields used for something else, inconsistent formats: migration often takes more effort than expected.
- The users. They know the old system by heart. Involve them early, and change the interface as little as possible at first.
What it costs
It all depends on the size of the system and its condition, which is exactly why we start with an audit. The advantage of the step-by-step approach: each step has its own budget, and you can stop or slow down at any time with a system that works. Our general ranges are in the guide how much custom software costs in Quebec.
Our take
Taking over existing systems is a big part of our work. We take over systems already in production, such as the Taxi Coop iOS and Android apps, which we maintain and keep improving. If your critical software is aging badly, have it assessed: we will tell you whether to modernize it in place, replace it step by step, or leave it alone for a while longer.
Sources
- Microsoft Learn: Windows 10 Home and Pro lifecycle
- Microsoft Learn: Windows 10 Extended Security Updates
- Microsoft Learn: SQL Server Extended Security Updates FAQ (end dates)
- Martin Fowler, "Strangler Fig," 2024
Sources checked on November 12, 2026. Programs and prices change, so always check the official page before you decide.