Data Centre Acquisition Models
Executive Summary
Key Takeaways
- ✓ A data centre acquisition model should verify the quality and durability of the target's existing contracted revenue, not simply accept the reported revenue figure, since contract-specific risk (renewal terms, SLA exposure, tenant concentration) determines its actual durability.
- ✓ Remaining capacity headroom should be independently verified against the facility's actual binding constraint, power, space, or cooling, since a target's reported nameplate capacity can overstate genuinely sellable remaining capacity.
- ✓ Synergy assumptions specific to a data centre combination, shared power procurement, network ecosystem consolidation, and overhead rationalisation, should be modelled with the same rigour and evidentiary standard as revenue and cost, not presented as an unsupported uplift.
- ✓ Post-acquisition integration risk, including any required technology or process standardisation across combined facilities, should be reflected in the acquisition model's cost and timeline assumptions.
Objective¶
This guide sets out how to model a data centre acquisition within Data Centre Financial Modelling, distinct from a greenfield development or internal expansion.
Verifying Contracted Revenue Quality¶
An acquisition model should verify the quality and durability of the target's existing contracted revenue rather than accepting the reported revenue figure at face value. Contract-specific renewal terms, SLA service credit exposure, and tenant concentration, covered in Data Centre Customer Contract Models, each affect how durable the reported revenue actually is, and should be verified directly against the underlying contracts.
Independently Verifying Remaining Capacity Headroom¶
Remaining sellable capacity headroom should be independently verified against the facility's actual binding constraint, power, space, or cooling, consistent with Data Centre Capacity Planning Models, rather than relying on the target's reported nameplate capacity, which can overstate genuinely sellable remaining capacity where a different constraint actually binds first.
Data Centre-Specific Synergy Assumptions¶
Synergy assumptions specific to combining data centre operations should be modelled with the same rigour and evidentiary standard as revenue and cost, not presented as an unsupported uplift:
- Shared power procurement. Potentially achieving a better utility rate or terms across a larger combined power load.
- Network ecosystem consolidation. Combining carrier relationships and cross-connect density across facilities to strengthen overall network ecosystem value.
- Overhead rationalisation. Combining operations, security, and administrative functions across the combined portfolio.
Post-Acquisition Integration Risk¶
Any required technology or process standardisation across combined facilities, aligning billing systems, monitoring platforms, or operational procedures, typically carries its own cost and timeline, and the acquisition model should reflect this explicitly rather than assuming integration proceeds without cost or delay.
Common Construction Pitfalls¶
Target's reported revenue accepted without contract-level verification. Misses renewal, SLA, and concentration risk that determines the revenue's actual durability.
Nameplate capacity relied upon without independent verification against the binding constraint. Overstates genuinely sellable remaining capacity.
Synergies presented as an unsupported uplift. Lacks the evidentiary standard applied to revenue and cost elsewhere in the model.
Integration cost and timeline assumed away. Understates the near-term cost and disruption of combining operations.
Recommended Practices¶
- Verify contracted revenue quality directly against underlying contract terms, not the reported headline figure.
- Independently verify remaining capacity headroom against the actual binding constraint.
- Model data centre-specific synergies (power procurement, network consolidation, overhead rationalisation) with full evidentiary support.
- Reflect integration cost and timeline explicitly in the acquisition model.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
Why can't a data centre acquisition model simply accept the target's reported revenue figure?
Because reported revenue does not reveal the underlying quality and durability of that revenue, contract-specific renewal terms, SLA service credit exposure, and tenant concentration each affect how durable the reported figure actually is, and the acquisition model should verify these underlying contract terms directly rather than accepting a headline revenue number.
How should remaining capacity headroom be verified in an acquisition?
Independently, against the facility's actual binding constraint, power, space, or cooling, rather than relying on the target's reported nameplate capacity, since nameplate capacity can overstate genuinely sellable remaining capacity if a different constraint, commonly power, actually binds first.
What synergies are specific to a data centre acquisition?
Shared power procurement (potentially achieving a better utility rate or terms across a larger combined load), network ecosystem consolidation (combining carrier relationships and cross-connect density across facilities), and overhead rationalisation (combining operations, security, and administrative functions), each of which should be modelled with the same evidentiary rigour as revenue and cost.
What integration risk should an acquisition model reflect?
Any required technology or process standardisation across combined facilities, for example aligning billing systems, monitoring platforms, or operational procedures, which typically carries its own cost and timeline that should be reflected explicitly rather than assumed away.
Related Articles
Data Centre Financial Modelling
Data centre financial modelling is the discipline of modelling a data centre operator's revenue, cost, and capital structure from its capacity-denominated drivers, power, space, and cooling capacity, rack density, and tenant contract structure, rather than the generic market-price and headcount-growth drivers used in most corporate models, or the pure occupancy-and-lease-term drivers of conventional commercial real estate. This page is the hub for the Knowledge Centre's data centre financial modelling content: how colocation, hyperscale, and enterprise business models each require a distinct model architecture, how rack revenue and occupancy are decomposed into their separable underlying drivers, and how capacity planning and financial KPIs tie the model together, as this domain expands to cover operations, revenue, investment, and governance practice across the sector.
Data Centre Valuation Models
Data centre valuation applies standard discounted cash flow methodology but requires bifurcating contracted (take-or-pay or long-dated lease) cash flow from uncontracted, renewal-dependent cash flow, and selecting a discount rate appropriate to each business model's risk profile, hyperscale build-to-suit versus diversified colocation versus enterprise/captive. This guide sets out how to structure a data centre valuation model and the sector-specific inputs a generic DCF template does not supply on its own.
Data Centre Financial Due Diligence
Data centre financial due diligence extends standard quality of earnings analysis with sector- specific verification, contract-by-contract revenue quality, independent capacity headroom verification against the actual binding constraint, and confirmation of how power cost pass-through risk is actually allocated under each material tenant agreement. This guide sets out the due diligence procedures specific to a data centre transaction, whether an acquisition, financing, or investment.
Data Centre Capacity Planning Models
Data centre capacity is jointly constrained by power, floor space, and cooling capability, and the binding constraint can shift as tenant rack density changes. This guide sets out how to model capacity planning across all three constraints simultaneously, how phased capacity delivery should be scheduled against demand, and why treating any single constraint as the sole capacity driver risks overstating achievable revenue.