ardelvo.
← All perspectives

Refresh, move or consolidate?

Aging hardware does not automatically justify a like-for-like refresh. The right decision depends on workload value, facility fit and the cost of disruption.

Start with workload disposition

Group systems into retain, retire, replace and relocate. Do this before inventory turns into a shopping list.

Test the facility case

Compare remaining lease term, power and cooling headroom, resilience gaps and hands-on support. A good platform in the wrong facility is still a poor investment.

Price the whole change

Include licensing, migration effort, outage planning, temporary overlap, data transport, installation and support—not only hardware acquisition.

Make reversibility visible

Identify which decisions lock the organization into a facility, platform or vendor. Preserve options where the cost is reasonable.

Sequence around business risk

Move low-risk services first, protect shared dependencies and define rollback criteria before the change window.

The best answer is often mixed: retire some equipment, refresh the workloads that belong on-premises, and move only what has a clear destination.

Compare the choices on the same basis

Use a common evaluation period and a consistent set of cost categories. Include installation, migration, support, licensing, facility charges, temporary overlap and eventual retirement. Record where an estimate is uncertain instead of presenting a precise total built on weak inputs.

OptionQuestion to resolve
RetainCan the current equipment remain supportable for the intended period?
RefreshDoes the existing location still fit the workload and operating model?
RelocateCan the destination meet requirements without creating avoidable migration risk?
ConsolidateWhich dependencies and failure domains would become shared?
RetireHave the business owner and data owner approved removal?

Build the change plan before the order

List shared services, physical connections, application owners and recovery dependencies. Decide what can move together and what should be separated. Document the conditions for stopping or reversing a change, including who can make that call.

Hardware retirement also needs its own work package. Include asset ownership, data-handling requirements, chain of custody, approved disposal methods and the evidence the organization must retain. Do not assume equipment removal also proves that the data has been handled correctly.

Use this brief as a starting point for planning. Confirm equipment and facility requirements with the relevant suppliers and qualified specialists.

Discuss your project