Data-center moves and decommissioning
Move the services, retire the equipment, keep the recordsServices map to racks, ports, power, and owners; then cutover, validation, rollback, equipment release, media handling, removal, and final record updates run in sequence.
What Data-center moves and decommissioning includes
A migration plan connects logical services to physical ports, cables, power feeds, racks and owners. The sequence should include prerequisites, freeze points, acceptance tests, rollback criteria and escalation roles.
Decommissioning is not bulk removal. Equipment and media require positive identification, authorization and disposition. Data sanitization method and evidence are selected by the asset owner’s information policy and current guidance.
Question to answer before designWhich dependencies must move together, what proves the service is restored, and who authorizes the disposition of each retired asset?
This service may fit when:
- A site, room, cage or platform is closing
- Equipment must move during a limited outage
- Assets and cables cannot be matched to current services
- Retired media needs controlled sanitization or destruction
What the system includes
A complete scope covers each part below and the connections between them.
Source state
Services, assets, links and data before the change
Migration wave
Sequenced dependency group with owners and timing
Target state
Expected ports, services and acceptance observations
Disposition path
Reuse, return, sanitize, recycle or authorized destruction
How site information becomes a tested project
A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.
What we confirm before design
- Service, application and physical dependency map
- Asset, serial, rack, port and ownership inventory
- Target-state capacity and configuration readiness
What those findings determine
- Cutover method: Use dependency coupling, available duplication and outage tolerance.
- Rollback: Define a time boundary and observable trigger for rollback.
- Removal: Require asset-owner release before physical removal.
What you should receive
- Migration/decommission runbook
- Asset, port and cable reconciliation
- Time-stamped change and acceptance log
The exact inputs, decisions, and acceptance records depend on the site and signed scope.
Project stagesSurvey through closeoutView details
How the work moves from survey to closeout
Each stage should produce the records and test results needed before the next stage begins.
- 01
Discover dependencies
Map services to assets, ports, links, power, owners, vendors and change restrictions.
EvidenceDependency matrix, asset/port inventory and unknowns log - 02
Plan waves and rollback
Group changes, define prerequisites, acceptance tests, stop criteria and recovery paths.
EvidenceRunbook, responsibility chart and approved rollback criteria - 03
Execute and validate
Perform each authorized wave, observe services and record deviations before proceeding.
EvidenceTime-stamped change log and service acceptance results - 04
Decommission and reconcile
Remove only released assets, control media disposition and restore the space.
EvidenceDisposition/chain record, sanitization evidence and final inventory
Design choicesCompare the available approachesView details
How to choose the right approach
The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.
What we need to know
- Service, application and physical dependency map
- Asset, serial, rack, port and ownership inventory
- Target-state capacity and configuration readiness
- Change window, acceptance and rollback thresholds
- Data classification and disposition policy
What you should receive
- Migration/decommission runbook
- Asset, port and cable reconciliation
- Time-stamped change and acceptance log
- Exception and rollback record
- Disposition, sanitization and space-restoration evidence
When this service makes sense
- Data-center exit or consolidation
- Row, cage or network refresh
- Equipment relocation between facilities
- Documented removal after a completed service migration
What we verify first
- Unknown shared dependencies
- Vendor, carrier and facility change approvals
- Live-service and rollback timing
- Data handling, chain of custody and authorized disposal
Site contextSee where this work is usedView details
How site conditions change the design
Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.
What people usually ask
What is the difference between migration acceptance and project completion?
Migration acceptance confirms the agreed services and dependencies work in the target state. Completion also reconciles records, exceptions, assets, removed infrastructure and owner handoff.
Who decides how drives or other media are sanitized?
The asset and data owner should select the method from applicable policy and current guidance. The project then records the authorized method, execution and verification evidence.
When should cabling be removed?
Only after the associated service and asset are positively identified, released by the owner and checked for shared or hidden dependencies.
Standards and referencesReview the source materialView details
Sources used for this guide
These references inform the guide. The adopted code, engineer of record, authority having jurisdiction, manufacturer instructions, and signed agreement control the project.
Covers data-center telecommunications infrastructure, topology and related facility coordination.
Open reference ↗BICSI · reviewed 2026-08-20BICSI Library of ICT Manuals and StandardsOfficial index for ICT installation, outside-plant, WLAN, DAS, data-center and bonding/grounding references.
Open reference ↗National Institute of Standards and Technology · reviewed 2026-08-20SP 800-88 Rev. 2: Guidelines for Media SanitizationCurrent guidance for selecting, performing and documenting sanitization before media reuse or disposal.
Open reference ↗ASHRAE · reviewed 2026-08-20Data Center ResourcesOfficial technical hub for data-center thermal, cooling, power and environmental guidance.
Open reference ↗