The "refresh every 5 years" rule of thumb made sense in 2010 — hardware aged faster, OEM warranties expired predictably, and capex cycles aligned. In 2026 the calculation is different. This is the decision framework Servnet runs with UK customers facing server refresh decisions.
The 3 refresh strategies
3-year refresh — premium hardware leases / consumption models (Dell APEX, HPE GreenLake). High flex, high cost, simple operations.
5-year refresh — traditional capex, OEM ProSupport throughout. Industry standard for 15+ years. Still appropriate for many.
7-year refresh — capex amortised longer, transition to TPM at year 4-5 when OEM gets expensive. Best 5-year TCO for stable workloads.
When 3-year refresh wins
AI / GPU workloads — generation-on-generation perf jumps justify aggressive refresh.
Trading floor / latency-critical FS — every CPU generation matters.
Consumption pricing (APEX / GreenLake) — capex shifts to opex, refresh is included in subscription.
When 5-year refresh wins
Standard virtualisation workloads where DDR5 + Gen5 NVMe + 25/100 GbE are the relevant generation shift.
Microsoft / VMware licensing cycles often align to 5-year hardware refresh.
OEM ProSupport remains economic through year 5 for most platforms.
When 7-year refresh wins
Stable workload (file servers, print servers, branch infrastructure, secondary database replicas).
TPM coverage from year 4-5 onwards typically 30-60% cheaper than continuing OEM at end-of-engineering tier.
Lowest 5-year TCO when modelled honestly — see our TPM TCO analysis.