Retiring hardware sounds simple until you are standing in front of a live cabinet with production traffic still flowing, a stack of drives full of sensitive data, and a loading dock that needs a scheduled appointment. A clean decommission protects your data and leaves you with records you can trust six months later. Here is a practical sequence experienced hands follow, whether you are pulling one server or clearing an entire cage.
1. Inventory and plan before you touch anything
Every good decommission starts on paper, not with a screwdriver. Walk the cabinet and record what is actually there: make, model, serial number, asset tag, rack position (U location), and the power and network connections feeding each device. Photograph the front and rear of the rack before any cables move, so you have a reference for what "before" looked like.
Cross-check that physical list against your CMDB or spreadsheet, because the two rarely match. Confirm which systems are truly out of service versus quietly still in use. If your records are stale or you are inheriting someone else's rack, a structured inventory and asset audit is worth doing first, so you are not finding surprises with a pallet jack already on the floor. Check dependencies too: shared power strips, cross-connects, and anything downstream that could go dark when you pull a box.
2. Decide how data gets destroyed
Data handling is the part you cannot get wrong, and it should be settled before the gear leaves the rack. There are three common approaches; the right one depends on your compliance requirements and whether the drives will be reused.
- Software wipe (erasure): Overwrite drives using a standards-based tool so they can be redeployed or resold. This preserves the hardware and produces a certificate per drive, but it takes time and only works on healthy media.
- Degaussing: A magnetic field renders spinning disks and tape unreadable. It is fast and thorough for magnetic media, but it destroys the drive and does nothing for solid-state media.
- Physical destruction (shredding or crushing): The most defensible option for SSDs and any drive holding regulated data. The media is physically reduced so nothing can be recovered.
Whichever path you choose, capture serial numbers and generate a certificate of data destruction for each drive. That paperwork is what an auditor or a client will ask for later. Decide up front whether media is wiped on site, pulled and destroyed off site, or shipped intact under chain of custody, because that decision changes how you pack.
3. Power down and unrack safely
With data handled, bring systems down gracefully. Shut down the operating system, confirm the box is truly idle, then power off at the PSU and unplug from the PDU. Label every cable as you remove it, or cut and bag them if they are being retired, so you are not leaving a bird's nest for the next tenant. Remove patch cables and coordinate the release of any cross-connects with the facility so you are not billed for circuits you no longer use.
Unrack from the top down for stability, and never underestimate weight. A loaded chassis or a battery-heavy UPS can exceed what one person should lift, so use a server lift or a second set of hands. Keep the rails, cage nuts, and mounting hardware if the cabinet is staying, and pull blanking panels and PDUs last when the whole cabinet is being cleared.
4. Pack and palletize for transit
How you pack determines whether gear arrives intact or as a warranty claim. Use the original boxes and foam when you have them; otherwise use anti-static bags for boards and drives, and rigid, well-cushioned boxes for chassis. Do not stack heavy servers on light ones.
For anything moving by truck, palletize: strap units down, distribute weight evenly, shrink-wrap the load, and label each pallet clearly. Keep an itemized packing list that ties back to your inventory so the receiving side can verify the count against what left the floor.
5. Book freight and manage chain of custody
Facilities like Digital Realty and other colocation providers require a scheduled dock appointment and often a ticket for equipment leaving the building, so arrange this in advance. Match the carrier to the load: parcel for a single unit, LTL freight for pallets, and a white-glove or asset-recovery courier when chain of custody matters. Record who took possession, when, and for what, and keep signed manifests. If drives are traveling for destruction, the chain of custody paperwork matters as much as the destruction certificate.
6. Update records and close out
The job is not done when the truck leaves. Retire each asset in your CMDB, release the rack positions, and cancel the power, cross-connect, and space line items with the facility so billing actually stops. File the destruction certificates and freight manifests with the project, and take a walk-through photo of the empty cabinet as proof the space was left clean. Good records are what let you prove, later, exactly what happened to every serial number.
Where hands help
Decommissioning rewards a calm, documented sequence rather than rushing a cage clear at 2 a.m. If you would rather not send your own staff across the country for it, our team handles the full server decommissioning workflow on the floor, with photos and paperwork at each step. You describe the scope, we confirm access and freight, and you get a clean record of what left the building.
Remote hands vs. smart hands
What the two terms actually mean, and which one your task needs.
ResourceWhat is a cross-connect?
How physical interconnections work inside a colocation facility.
ResourceWhat to expect from a remote hands visit
How a dispatch runs from ticket to photo-documented sign-off.
HubAll resources
Guides and explainers on data center hands-on work.
Need servers pulled, wiped, and shipped from a metro or Ashburn facility? Request service at remotehands.nyc/#request or call dispatch at (707) 733-3342, 24/7. We confirm access, scope, and pricing before any work starts.