Colour theme
Book a consultation

Planning replacement for ageing systems

Review ageing servers, network devices and business applications, then prioritize replacement using support status, exposure and recovery needs.

A hand pressing a key on a calculator beside a stack of banknotes.

An old server can still run an important application while its replacement becomes harder to plan. The records it holds, the systems that depend on it and the people who know how to restore it all affect that decision.

Review those dependencies before a failure makes the timetable for you. Start with a short list of systems needing action, then assign an owner and a next step for each.

Build an inventory with business context

Record the product, version, location, support status and business owner. Include firewalls, remote-access gateways, storage, hypervisors and the applications running on servers. A supported operating system can still run an unsupported application or sit behind an unsupported device.

For each system, ask which work stops if it’s unavailable and which other systems rely on it. Check scheduled tasks, service accounts, integrations, licences and access needed by an external supplier. Confirm who holds the configuration and recovery instructions.

Our computer-replacement guide covers staff devices. This review focuses on shared infrastructure and applications that other parts of the business depend on.

Check support against the exact product

Use the vendor’s lifecycle information, including edition and version. Microsoft’s lifecycle directory is a starting point for its products; other suppliers maintain their own support notices. Record the link and the date you checked it.

Separate a hardware warranty from security updates and application support. A maintenance payment doesn’t necessarily extend every part of the stack. If an extended-update program is proposed, confirm eligibility, coverage, cost and its end date before relying on it.

The Canadian Centre for Cyber Security’s obsolete-product guidance recommends transitioning away from unsupported products. It prioritizes exposed and critical systems and treats isolation and restricted access as temporary measures during a planned transition.

Prioritize exposure and business impact

Age alone doesn’t set the order. Review three groups first:

  • Exposed network equipment: devices providing internet or remote access, especially where updates have stopped or aren’t being applied.
  • Unsupported business systems: applications and servers that need old protocols, obsolete dependencies or broad access to keep working.
  • Systems with uncertain recovery: important services whose backup, configuration or restore procedure hasn’t been demonstrated.

Have IT check what’s exposed. A device being called a firewall doesn’t tell you whether its management interface is reachable from the internet. Include suppliers’ access and exceptions in that check.

Choose priorities using support status, exposure, information sensitivity and the effect of downtime. Write down the reasoning so the business can compare an urgent change with a planned replacement.

Prove recovery before changing production

Check whether you have the installation media, licences, credentials, configuration and data needed to recover. Ask when a restore was last tested and what it demonstrated. A successful backup job doesn’t answer whether the application will start and produce usable records.

The Cyber Centre’s IT recovery-plan guidance describes testing in a separate environment and distinguishes exercises that leave production running from cutover tests that can interrupt it. Agree on a test suitable for the system and the disruption the business can accept.

For specialist equipment or an application tied to old hardware, involve the supplier before testing or altering its connections. A general server upgrade plan may miss a dependency essential to its operation.

Turn findings into a funded change

Give each priority an owner, target date, proposed replacement, migration dependencies and an end date for any temporary workaround. Include implementation, licences, staff training and expected downtime in the estimate.

Plan acceptance checks and a rollback decision before the cutover. Agree who will verify that the business process works on the replacement. After acceptance and any required preservation period, retire the old system through a documented process that handles stored data, credentials and remaining dependencies.

Use the IT budget guide to carry these costs into the plan. At the next review, check whether the agreed actions happened and whether temporary exceptions still have an owner and a credible end date.


Featured Image Credit