Legally diligencing an operating data center differs from diligencing an ordinary technology company because value sits in time-limited, conditional rights: whether the investment registration certificate still matches actual operations, how many years the land lease has left and whether it transfers or changes investor, and which maintenance conditions attach to incentives already enjoyed that the buyer must keep satisfying post-deal. The first diligence cluster must answer whether the transaction is structurally feasible: a share purchase preserving the entity usually preserves the whole paper stack, while an asset and project purchase drags a chain of per-right transfer procedures, and the structure choice should be fixed after the preliminary diligence round, not before.
Project and land cluster: whether the deal is structurally possible
The operations cluster holds four file groups deciding whether post-deal revenue survives. The data center service registration and related service notifications, live and matching the scope actually operated under Decree 163/2024/ND-CP. Customer contracts: remaining terms, change-of-control and early termination clauses, historical SLA performance and accumulated breaches customers may invoke after the change of owner. Data and cybersecurity files: impact assessments, incidents and their handling, graded system security assessment results, because the buyer inherits both the seller’s compliance history and its undiscovered violations. And power duties: whether registered capacity transfers with the project, and how the power purchase contract and any DPPA are treated on change of owner, since power capacity is the most precious operating asset of a fully-let data center.
Operations cluster: service registration, customers and data
Diligence findings should not rest in the report; they must convert into concrete deal mechanics. Curable breaches become conditions precedent with deadlines and completion standards before closing. Unquantifiable risks become specific seller warranties and indemnities backed by a price retention long enough for the risk to surface. Short-dated papers — a land lease running low, a registration needing update or insurance near expiry — become price adjustments or post-closing renewal cooperation duties. A diligence report unconnected to deal mechanics is a report merely to read, and a data center buyer pays for diligence to renegotiate price and terms, not for one more file in the archive.
Turning diligence findings into transaction mechanics
Finally, the diligence team must cross-check between clusters instead of reading each in isolation: financial-statement revenue must match the live customer contract list; power capacity sold to customers must not exceed registered capacity and real redundancy; machine-room area under lease must match the fire acceptance file. These three reconciliations catch most material misstatements in a data center deal, and they only surface when the file layers sit side by side in one well-organised data room.
Frequently Asked Questions
What legal items must be checked when acquiring a data center?
Project status and incentives, land and remaining lease term, telecom service registration, the customer contract list with change-of-control clauses, data and system security files, fire acceptance and registered power capacity duties.
Does the data center’s land lease transfer to the new owner?
In a share deal the landholding entity is unchanged so the lease continues; in a project transfer, succeeding to the land lease follows the lease conditions and the project transfer procedure under Investment Law 143/2025/QH15, usually needing lessor or park board approval.
How are data compliance breaches handled in the transaction?
Converted into mechanics: seller remediation before closing where feasible, or specific warranties and indemnities with a price retention long enough for the risk to surface, and price adjustment for unquantified breach exposure.
This article has been quality-reviewed by the FLAW AI Legal Council