Data center decommissioning checklist: what to settle before anyone touches a rack

Before consulting anyone

1. Physical inventory. Walked, not exported. Serials where they matter.
2. Dependency map. What still talks to what, observed rather than assumed. If a migration is running, see how it interlocks with the exit.
3. Data classification. Which devices hold data, and what each class requires.
4. Access confirmation. Elevator, dock, hours, badging, insurance requirements, from facilities, in writing.
5. Evidence standard. What your auditors will ask for, agreed with them beforehand.
6. Acceptance criteria. What “done” means for the room, written down.

Settled in that order, these six items are the opening of the data center decommissioning plan itself.

During the project

• Labelling before disconnection, always. Unlabelled hardware becomes unreconcilable within hours.
• Custody transfers recorded at the moment they happen, not reconstructed later.
• Exceptions logged as they occur: failed erasures, missing assets, unexpected devices.
• A daily count that matches the inventory, checked daily rather than at the end.

At close-out

• Reconciliation: inventory in, disposition out, exceptions explained.
• Certificates matched to serials, not to counts.
• Recycling evidence for regulated material.
• Settlement detail for resold assets.
• Formal acceptance of the room condition.

Turning the checklist into a decommissioning project plan template

A checklist says what has to be true. A project plan says who makes it true, by when, and what proves it. The quickest decommissioning project plan template is this checklist with four columns added to every line.

• Owner. One named person, not a department. Facilities owns access, IT owns dependencies, security or compliance owns the evidence standard.
• Evidence. The document that closes the line: a signed inventory, a written release per system, a certificate matched to serials.
• Date. Worked back from the fixed end point, usually the lease or contract end, rather than forward from today.
• Status and exceptions. Open, closed, or closed with an exception that is written down and explained.

Group the lines by phase, in this order: scope and inventory, dependencies and release, data classification and method per media type, physical works, disposition, close-out and acceptance. A line cannot close before the line it depends on, and the plan makes that visible.

Items a data center decommissioning checklist usually misses

• Failed drives kept in a drawer or a returns box after replacement. They are data bearing and belong in the inventory.
• Backup tapes, spare drives and removable media in storerooms and cages nobody claims.
• Network devices holding configuration and credentials, and management controllers on every server.
• Leased equipment that goes back to its lessor, with its own return conditions and its own data question.
• Carrier circuits, cross-connects, support contracts and software licences tied to the room, which keep billing after the hardware is gone.
• Badge access, alarm contacts and monitoring for a space that no longer exists.
• The reinstatement terms of the lease or colocation contract: cabling, floor tiles, cages and fixed fittings.

Each of these is a line with an owner, not a footnote. Where the data-bearing items end up, and what record each one needs, is on the certificate of destruction page.

Frequently asked questions