Does My Legacy System Need Modernizing? Signs Not to Ignore

Your legacy system needs modernizing if it shows one or more of these signs: its technology is out of vendor support, only one person or contractor understands it, it reaches e-invoicing, banks or new apps only through manual exports, or every small change takes weeks. For example, extended support for SQL Server 2014 ended in July 2024, and .NET 8 and .NET 9 support ends on 10 November 2026, according to Microsoft. If the system is stable, isolated and cheap to keep, the right call may be to wait.

In part 1 of this series you listed the systems your business cannot run a day without. Now we ask of each one: does it really need modernizing?

Sign one: the technology is out of vendor support

Every product you buy or build on has a date when support ends. After that date the vendor ships no new security fixes, so any vulnerability found later stays open in your system. The first question for each system is: what technology is it built on, and when does its support end? These examples come from Microsoft's product lifecycle pages, and they are among the most common technologies underneath business systems:

Sources: Microsoft's pages for Windows Server 2012 R2, SQL Server 2014 and .NET. Note that leaving support does not mean the system stops tomorrow. It means the risk rises every month, and paid security updates buy you time to plan; they do not remove the decision.

Knowledge signs: who understands it, and what it runs on

• One person understands it. If every fix waits for one employee or one outside developer, your system depends on their holidays and their resignation. This is the most dangerous sign, because it shows up in no report until the absence happens.
• Nobody dares touch the machine. A server in a side room that everyone knows must not be restarted, with spare parts no longer sold. If it stops, the business stops, and there is no ready replacement.
• Only the code knows the business rules. How a discount, a commission or a permission is calculated lives in the software alone, with no document explaining it. That is exactly what we will extract with AI in part 4.

Integration and speed signs: the system slows the company down

• It cannot connect to e-invoicing without workarounds. According to ZATCA's e-invoicing roll-out phases page, phase one started on 4 December 2021, and the integration phase with ZATCA's systems started on 1 January 2023 in waves, with each business notified at least six months before its wave. If your system can only issue a compliant invoice through a middleman program or manual work, read our guide to wave 25 and ZATCA integration.
• Banks and apps need manual exports. Someone exports a file from the system every day to upload to the bank, the online store or the delivery platform. Every manual step is a chance for error and lost time.
• A simple change takes weeks. Adding a field, a report or a price change means a request and then a wait, because any change might break another part nobody understands.
• Reports are rebuilt in Excel every month. If your team exports data and rearranges it by hand to see what is going on, the system stores data but does not answer your questions. And if your real system is a spreadsheet to begin with, start with when the spreadsheet stops being the answer.

When not to modernize yet

Modernization is not a goal in itself, and some legacy systems should stay as they are for a while. Waiting may be the better choice when these conditions hold together:

• Stable: it has not had a serious failure in a long time, and you rarely need to change it.
• Isolated: it is not connected to the internet and does not need to talk to other systems, so the vulnerability risk is lower.
• Cheap to keep: more than one person understands it, and maintaining it costs little money or time.
• Being replaced anyway: if you are moving to a ready-made product soon, do not invest in modernizing a system that is about to retire.

In that case the right decision is to watch it: record when its technology leaves support, make sure a working backup exists, and document what it does. If you decide to modernize later, we explained the safe way in our guide to legacy modernization without downtime.

The Origami view

We build systems and integrations and modernize old ones, and yet the first thing we do with any legacy system is ask why it should be modernized at all. A system that has run the company for years deserves respect, and many systems need a new integration or good documentation rather than a rebuild.

So we start by assessing each system on support, knowledge, integration and speed of change, then propose the smallest step that lowers the risk, whether that is an integration, a migration or an AI-assisted rewrite with an engineer reviewing every line. If you want a view on your own systems, take a look at our services.

This week's exercise: score each system out of 8

Take the list of systems you wrote in part 1 and give each one a score from 0 to 2 on each of the four axes, where 0 means no problem, 1 a minor problem and 2 a clear problem:

• Support: is its technology supported? (2 if support has ended or ends within a year)
• Knowledge risk: how many people understand it? (2 if it is one person or one vendor)
• Integration: does it connect to invoicing, banks and other systems without manual work? (2 if the connection is manual)
• Speed of change: how long does a simple change take? (2 if it takes weeks)

This is a ranking tool, not a final verdict: a system scoring 6 out of 8 or more deserves planning now, 3 to 5 means watch it and set a date to reassess, and 0 to 2 means let it run. Any system scoring 2 on knowledge risk alone needs urgent documentation, whatever its total.

Coming next

You now have a list of systems and a score for each. In part 3 we turn that list into a full inventory: who owns each system, who uses it, what data it holds and whether that includes personal data, what it connects to, what breaks if it stops, and when its licenses renew, followed by the five choices for each system: keep, retire, replace with a ready product, move as is to the cloud, or rebuild.

Sources

• Microsoft: Windows Server 2012 R2 lifecycle — end of extended support and the paid Extended Security Update years.
• Microsoft: SQL Server 2014 lifecycle — extended support ended July 2024; paid updates until July 2027.
• Microsoft: .NET lifecycle — .NET 8 and .NET 9 support ends November 2026; .NET 10 until November 2028.
• ZATCA: e-invoicing roll-out phases — phase one 4 December 2021; integration phase from 1 January 2023 in waves.
• AWS Transform: official service page — part 1's example of AI-assisted modernization.