Data-centre relocation: decom source, redeploy or retire.
Operator change, lease expiry, hyperscale cluster move, geographic consolidation — relocations trigger asset-by-asset decisions: redeploy at the new DC, retire and replace, or destroy and replace. We coordinate all three, with audit-ready evidence per path.
What happens to each device during a relocation
- ♦ Redeploy at new DC — wipe (NIST 800-88 Clear), photograph + log, transit to new site.
- ♦ Retire and replace — buyback at residual; new kit deployed at new DC.
- ♦ Destroy and replace — typically end-of-life kit; NIST 800-88 Destroy with evidence.
- ♦ Conditional redeploy — wipe + transit + verify-on-arrival; if not working, destroy.
- ♦ Spare-parts harvest — strip valuable components (RAM, drives) before destruction.
Why relocation projects need an explicit source-DC release deliverable.
A relocation isn't done when the new DC is live. It's done when the source DC is empty, photo-confirmed, and released back to the operator's re-lease inventory. Until then, you're paying for two DCs.
Our floor-space release deliverable runs per cage as it empties — phased release, not a single end-of-project sweep. That means the operator can start marketing your former cage to new tenants sooner, which often translates into a partial colocation refund or accelerated lease termination.
Maxicom Singapore — frequently asked
Can you do the new-DC deployment too, or just the source-DC decom?
We focus on source-DC decom + ITAD + floor-space release. New-DC deployment is typically handled by your build-out partner or the destination operator's smart-hands team. We coordinate with them on hand-over but don't replace them.