The Economics of Hosting and Cloud Migration

Introduction

A decision to relocate existing servers into colocation may appear to avoid the cost of replacing a deteriorating data centre. A move to public cloud may promise to remove the next hardware refresh altogether. Neither proposition establishes the financial case until the organisation understands which expenditure ends, which costs continue and which new obligations arise.

Part 1 considered why organisations keep, relocate or replace existing infrastructure, and why a hospital, local authority, government department or private enterprise might make different choices. This second briefing examines the economics that distinguish those options. It concentrates on the standard of business-case scrutiny required for a significant commercial decision, without treating every component charge as a separate finance exercise.

A credible appraisal starts with the existing estate, tests the cost of transition and examines the proposed future service over a consistent planning period. It also considers benefits that matter operationally: service continuity, restoration capability, responsiveness to demand and the time staff can redirect to higher-value work. Financial assumptions then become contractual dependencies—particularly when the timetable changes.

What is the buyer paying for in each model?

A retained on-site estate can require equipment refresh, building space, electricity, cooling, connectivity, manufacturer support, software licences and internal operations. Some costs are visibly charged to IT; others sit within estates, facilities or shared overheads. The cost of existing equipment may already be sunk, but future maintenance, energy, renewal and risk are not. Comparing a supplier quotation with only the current equipment-support budget therefore understates the baseline.

In direct colocation the customer generally continues to own its computing…