Table of Contents

Table of Contents

10 Years of Doing Nothing About the Old Server.jpg
calendar icon
Published on Nov 20, 2026
user smile icon
Super Admin

10 Years of Doing Nothing About the Old Server

The server sits in a closet behind the finance office, next to a mop bucket that hasn’t moved since 2019. It runs invoicing. It has run invoicing since before the current CFO started, and when somebody asks whether it should be replaced, the usual answer is a shrug, since it hasn’t failed yet. Plenty of mid-sized companies keep a machine like it. Most assume that leaving it alone is free.

It isn’t. Over a decade, the cost follows a fairly predictable path, and the early years look harmless. Waiting costs the same money, only later and in smaller pieces nobody planned for. By Year 10, the migration support for aging applications that seemed optional in Year 1 is the only choice left. Here’s how the invoice arrives.

Years 1 to 2: The Quiet Part

Nothing breaks in Year 1. That’s the trouble with it. Dennis, who wrote most of the batch jobs back in 2009, retires in April; there’s a sheet cake, and by Tuesday everybody is back at their desks.

He isn’t the only person heading for the door. In the Arcati Mainframe Survey, 62% of respondents said finding people with modern mainframe skills was still among their hardest problems, and 70% had worked in mainframe jobs for more than 20 years. Replacements? Hard to find. Postings sit open for months, and the contractors who do show up charge rates that make the CFO wince. Then there’s everything Dennis never wrote down: why the nightly job runs at 2:40, or which table must stay untouched on the last day of the quarter. That kind of knowledge turns into rumor inside a year.

For companies facing this growing knowledge gap, exploring legacy application migration services can help preserve critical business logic and reduce dependence on a shrinking pool of specialists.

By Year 2, the wiki page that documents the system was last edited 4 years ago. Nobody’s sure the last person who edited it still works there. Everybody says they’ll update it soon.

Years 3 to 5: The Patches Stop

Attackers like old software for a plain reason: the holes are already public. Exploiting a software vulnerability was how 20% of the breaches in Verizon’s 2025 report began, up 34% from the previous edition. Somewhere around Year 3 or 4, the vendor drops support for the database under the application, and the fixes stop. Every flaw found after that date stays open. Anybody with a search engine and a free evening can read about it. Security staff know this. They file a ticket, and the ticket lands somewhere below the office and moves on the priority list.

Workarounds, mostly. Somebody puts a firewall rule around the old box, and staff get a quiet instruction never to connect it to the guest wifi.

Costs creep in sideways after that. Extended support contracts, when a vendor still sells them, rise at every renewal, and the team that should be planning next quarter’s release spends its Thursdays explaining to auditors why a 12-year-old operating system still appears on the network diagram. A company in this position could hire outside help to move the application onto a supported platform, and by Year 5 many consider it seriously, then look at the calendar and decide on next year instead. Next year will cost more.

Years 6 to 8: Things Stop Talking to Each Other

What happens to an old system when everything around it keeps moving? Mostly it gets left behind. The company swaps its CRM for a newer model. The payment provider rewrites its interface. Somebody buys a reporting tool whose connector was never tested against a 14-year-old database. A contractor gets hired to patch the connector, leaves after 6 weeks, and takes his notes with him. Each change is reasonable by itself, and by Year 7 the whole arrangement is duct tape and good intentions.

Firms in this field, N-iX among them, are often called in around this point to untangle connectors that nobody fully understands. A migration partner arriving in Year 7 inherits every problem together. Not a pleasant opening month either. Breakage doesn’t arrive in any particular order, but a few kinds turn up again and again:

  • The payment provider retires its old API version on a Friday, and the nightly sync starts failing at 3 a.m.
  • Month-end reports that took 40 minutes in Year 2 now eat most of a working day.
  • A new hire asks whether the system has an API. It doesn’t.
  • Partner files in current formats bounce back with an error code and no explanation.

None of it makes the news. Whoever restarts the sync at 3 a.m. remembers every night anyway. The CFO sees none of it, only a line on the monthly IT report that says “minor incidents.”

Years 9 to 10: The Audit Letter

The letter arrives on a Monday. It’s polite and very specific. It asks for proof that stored records are encrypted and for an access log covering the past 12 months. The old system can produce neither. The CFO reads it standing up, then walks down the hall to find out who owns the server in the closet.

Regulators revise their expectations every few years, and the application keeps meeting the expectations of the year it was built; the gap widens a little each quarter, in silence, until a person with a clipboard measures it. Cyber insurers start asking questions too, and the answers show up in the premium. A breach would land hard on top of that, since IBM’s 2025 report put the global average cost at $4.44 million, a sum that weighs heavily on a company whose core system cannot say who touched what.

By Year 10, legacy application migration services stop being a line item somebody can postpone and become a deadline set by outsiders, with regulators and insurers chief among them. Not a crisis, exactly. A calendar. The project that could have begun in Year 1 as a plan now begins as a rescue, with fewer people who remember the system and a budget nobody enjoys defending.

Epilogue

The decade of doing nothing has a price, and it arrives in pieces. Companies that begin early, with a specialist partner such as N-iX, choose the date themselves. The rest have it chosen for them, usually by a letter or a failed sync. The closet behind the finance office stays shut a while longer, but somebody will have to open it.

Save 20%
On New Registration
Use Coupon
fenced20

Safeguard Your Child Against Online Threat

Register Now
Cancel Any Time Available on Android iOS
Logo