Services · Data Center Decommissioning
A facility exit is a records project with freight attached
The equipment will move regardless. What separates a clean decommissioning from an expensive one is whether, eighteen months later, you can still say what every serial was, where it went and how it was sanitized.
The failure mode
Nobody loses a data center. They lose the record of one.
Decommissioning goes wrong in a predictable way. Discovery is compressed because the lease date is fixed, the inventory is taken from a register nobody has reconciled in three years, equipment is staged in a corridor, and the project generates evidence in fragments — a spreadsheet here, a certificate batch there, a recycler's weight ticket that references nothing.
Then, later, someone asks what happened to a specific storage array. And the honest answer is that it cannot be established.
That is not a logistics failure. It is a failure to treat the exit as a records exercise from the first day — which is why our sequence starts with a serialized opening inventory and ends with one closeout package built against it.
Seven phases
What happens, in what order, and what each phase leaves behind
Every phase produces a document. The closeout package is those documents assembled against a single opening baseline — not collected afterwards from whoever still has them.
- 01
Discovery
Serialized opening inventory built against your CMDB or asset register, with variance identified before anything moves. The inventory is the baseline every later reconciliation is measured against.
ProducesOpening inventory and variance report - 02
Decommissioning engineering
Sequence, freight profile, packaging, custody model, legal-hold handling and the execution plan — authored by our technical services engineers and agreed in writing before a date is booked.
ProducesDecommissioning plan and scope statement - 03
On-site execution
Our national field crews perform the physical decommissioning under our own project management — equipment removal and de-racking within the managed scope, labelling, packaging and staging — then palletized and manifested against the opening inventory. LTL or FTL by lane, with EDI 214 in-transit visibility rather than a tracking link somebody has to check.
ProducesCustody transfer, outbound manifest, in-transit visibility - 04
Secure receiving
Inbound assets enter a mesh-enclosed, lockable receiving cage and are reconciled against the manifest before joining general stock. Legal-hold items segregate immediately.
ProducesChain-of-custody receipt, reconciliation - 05
Sanitization
Every data-bearing component sanitized against NIST 800-88 by media type, with a certificate issued per device. No asset advances without a valid certificate; manual overrides are not permitted.
ProducesPer-device erasure certificate - 06
Valuation & disposition
Configuration-level identification, testing and grading. Equipment with a market is remarketed; the rest is consigned to qualified, certified downstream recyclers under manifest.
ProducesSettlement statement, downstream manifests - 07
Closeout
The complete evidence package assembled as one record: reconciled inventory, certificates, custody transfers, settlement and downstream manifests.
ProducesProject closeout package
Why infrastructure is different
An endpoint process applied to a data center gets both halves wrong
A populated rack is many assets, not one line
A 2U server is a chassis, a set of drives, memory, processors and sometimes an accelerator, each with its own handling requirement and its own residual value. Providers who inventory at chassis level are simultaneously under-sanitizing and under-recovering, and neither error is visible until much later.
Storage is the actual risk
Arrays, caching tiers, boot media, RAID controllers with battery-backed cache, and drives that were pulled and replaced years ago and never left the room. Data-bearing media in a facility exit is rarely where the register says it is.
Network gear holds data too
Switches, routers, firewalls and load balancers carry configurations, routing tables, credentials and VPN parameters. A great deal of decommissioned network equipment leaves buildings unsanitized because nobody classified it as a data-bearing asset.
Depreciation runs on a clock
Infrastructure loses secondary-market value fast, and equipment that sits in a staging area for three months while a project stalls is worth measurably less than the same equipment moved in week one. Sequencing is a financial decision, not just a logistical one.
Scope
Where our scope starts, in writing, before a date is booked
Decommissioning RFPs frequently go wrong because two parties assume different answers to the same question. So we state the boundary explicitly rather than leaving it to the statement of work.
- On your floor
- Decommissioning engineering and planning, project scoping and execution planning, technical project management, and on-site technical execution by our own national field crews — including equipment de-racking and removal as part of the managed project. This is WesternTechSystems Technical Services, not a subcontracted introduction.
- From your floor to ours
- Custody transfer at the point of removal, manifested transport, and secure receiving into a mesh-enclosed cage reconciled against the opening inventory before anything joins general stock.
- In our facility
- Sanitization, testing, configuration-level valuation, remarketing and the closeout evidence package — performed in our own R2v3 and RIOS certified facility in Lewisville, Texas.
- Beyond our facility
- Material with no reuse or resale route is consigned to qualified, certified downstream recyclers under our R2v3 Appendix A downstream vendor management scope, with manifest documentation. The physical recycling is performed by those vendors, not by us — what we perform is the qualification, the routing and the documentation that makes the chain auditable past our loading dock.
- Named specialist scope
- Some facility exits require functions outside our scope — teardown of liquid-cooled systems, fluid handling, or specialist heavy rigging beyond managed project removal. Where a project needs one, it is identified during planning and the scope statement names who performs it. We would rather write that down before a date is booked than discover it on the morning of the exit.
- What we will not imply
- That a certificate covers more than it does. Our R2v3 data-sanitization appendix covers logical sanitization. Where your policy requires physical destruction of media, say so during scoping and we will tell you plainly how that is handled and by whom.
The control worth knowing about
Unsanitized assets cannot be shipped or invoiced
In our highest-volume programs, wipe validation is enforced at two separate points — at label creation and again in ERP fulfilment. An item without a passing wipe record is blocked from finished goods, from shipping and from invoicing.
Blocked, not flagged. The distinction matters more than it sounds. A flag depends on somebody reading it. A block does not.
The same architecture governs decommissioning work. Sanitization is not a step that precedes release; it is the condition of release, and the certificate is what satisfies it.
How sanitization works hereFAQ
What decommissioning project owners ask
Where does your scope start and stop?
How do you handle a facility where the register is out of date?
What happens to drives?
Can equipment be sanitized before it leaves our site?
How is legal hold handled?
What is retired infrastructure actually worth?
Can we witness the process?
How fast can you move on a lease deadline?
What do we receive at the end?
Do you operate nationally, or only around Dallas?
What if the facility contains AI or accelerated computing hardware?
Do you recycle the material yourselves?
Do you handle a phased exit rather than a single event?
Start with discovery, not with a date.
Tell us the site, the deadline and what you believe is in the room. The gap between that belief and reality is where the project actually lives.