Key takeaways

  • The risk in a decommission isn’t the hardware — it’s data, dependencies and disposal evidence.
  • Sanitise media to a recognised standard and keep evidence for every device. This is handled through a partner, not by the engineers removing the kit.
  • Dispose through licensed, WEEE-compliant recycling under chain of custody. This is also handled through a partner. DACPROS does the on-site removal and handover.

Decommissioning a rack, a row or a whole hall looks like demolition, but it behaves like surgery. Pull the wrong cable and you take down a live service two racks over. Skip a sanitisation step and you have a data-protection incident waiting in a skip. Lose the paperwork and you can’t prove anything to an auditor. A good decommission is defined by what you can evidence afterwards, not how fast the racks emptied.

Here is the checklist, in order, with who normally carries out each step. On a DACPROS IT decommissioning job we do the physical work: de-racking and handover. You do the planning, backups and shutdown. Data destruction and recycling (steps 5 and 9) are handled through a partner.

The 10-step checklist

  1. Audit and tag every asset. Build a verified inventory of everything in scope — make, model, serial, asset tag, rack location — and reconcile it against your CMDB. If it isn’t on the list, it doesn’t move. Who: you, with us recording serial numbers as equipment comes out.
  2. Map dependencies. Confirm what each device actually serves: power feeds, network uplinks, shared storage, anything cross-connected. This is where “we thought that was dead” incidents are prevented. Who: you.
  3. Plan the sequence and window. Agree the shutdown order, site access, escort requirements and the change window with every stakeholder — including the colo, if it’s a shared facility. Who: you, with us on access and timing.
  4. Take final backups and confirm restorability. Back up anything that might be needed again, and actually test that it restores before you power the source off. A backup you haven’t verified is a hope, not a copy. Who: you.
  5. Sanitise the data. Securely erase or physically destroy storage media to a recognised standard, and record evidence for every single device. Agree the method and the records you need before anything leaves the site. Who: a partner, decided with you.
  6. Sequenced power-down. Power devices off in dependency order, logging each step and confirming nothing live drops as you go. Who: your team. We disconnect once you confirm.
  7. De-cable and de-rack. Remove cabling and hardware methodically, labelling anything being retained or relocated. Take photos as you go where the site allows. Who: DACPROS.
  8. Secure transport. Anything leaving the floor for reuse, resale or destruction should travel under sealed, tracked transport with an unbroken chain of custody. Who: DACPROS prepares, labels and hands over; collection is arranged with your haulier or the partner.
  9. WEEE-compliant recycling. Retired equipment should go to licensed, WEEE-compliant processors so hazardous materials are handled correctly and disposal is documented. Who: a partner.
  10. Hand over the evidence. Gather the final inventory, the removal record, chain-of-custody records and the destruction and recycling records into one bundle. Who: DACPROS provides the removal record by serial number. Destruction and recycling records come from the partner.

(That’s nine numbered actions plus the audit-pack handover — ten discrete checkpoints, and the tenth is the one auditors care about most.)

The two failures that cost the most

Unverified data sanitisation (a compliance and reputational risk) and missing disposal evidence (it was done properly, but you can’t prove it). Both are paperwork problems, and both are avoidable if you agree the records you need with your partner before the equipment moves.

Why sequence matters more than speed

The temptation on a decommission is to get the racks empty quickly. But the expensive mistakes all come from doing things out of order — de-racking before sanitising, powering down before checking dependencies, transporting before logging custody. A slower, sequenced exit is almost always the cheaper one, because it doesn’t generate a second project to clean up the first.

Where most teams need help

Internal teams usually have the knowledge but not the bodies — a decommission is a burst of work with a hard deadline and a need for certified hands on the floor. That’s the shape of a smart hands engagement. Our IT decommissioning service covers the physical steps and the handover, and the ITAD and recycling pages explain how data destruction and recycling are handled through a partner. If you’ve got an exit coming up, tell us the site and the timeline.