Data Centre Relocation Services
Move racks, equipment and connectivity through a controlled migration plan that protects assets, dependencies, change windows and recovery options.
A data centre relocation is the planned transfer of IT and network assets, connectivity and supporting records between racks, rooms or facilities. FDNS supports surveys, asset and cable mapping, destination preparation, de-racking and re-racking, fibre and copper changes, move sequencing, testing and documented handback.
What is a data centre relocation?
A data centre relocation is the planned transfer of IT and network assets, connectivity and supporting records between racks, rooms or facilities. FDNS supports surveys, asset and cable mapping, destination preparation, de-racking and re-racking, fibre and copper changes, move sequencing, testing and documented handback.
FDNS helps project teams establish what is moving, how it is connected and what must be ready at the destination. Asset identifiers, rack positions, patching records and service dependencies inform the move plan. Shutdown, transport, application recovery and validation responsibilities are agreed with the client before the change window.
The move sequence defines preparation, disconnection, handling, re-racking and reconnection, with checks at each agreed stage. Exceptions and rollback decisions are recorded against the runbook. Updated rack, asset and cable records support service validation and give the operations team a usable baseline after relocation.
What the service includes
Discovery and dependency mapping
We identify assets, racks, connections, owners, critical services, shutdown order, access, handling needs and unknowns that could affect the move. Reconcile asset identifiers and port records with the installed equipment before the move schedule is approved.
Destination readiness
Rack space, rails, power and cooling interfaces, pathways, patching, labels and network connectivity are verified with responsible teams before migration. Check rack space, power interfaces, cabling and access at the destination before releasing equipment from the source.
Runbook and change planning
Wave plans, roles, timings, decision points, communications, rollback, exception handling and validation are documented for approval. Allocate shutdown, handling, transport, reconnection and application validation responsibilities to named teams.
De-rack, transport and re-rack support
Assets are identified, disconnected under authority, protected, tracked, handled and installed at the approved destination. Use agreed asset identification and handling records to track equipment between source and destination racks.
Cabling and patching changes
Copper and fibre links, trunks, panels and patching are installed or modified, inspected and tested before service release. Prepare destination links and labels before the move where practical, reducing reconnection work during the change window.
Validation and close-out
Physical checks, connectivity tests and client application validation are recorded, with inventories, diagrams and exceptions updated. Reconcile moved assets and connections, recording test outcomes and unresolved service dependencies before handback.
Important design and delivery decisions
Data-centre infrastructure is changed repeatedly during its life. Early decisions therefore need to balance capacity and density with access, resilience, airflow, safety, security, testing and the ability of operations teams to understand the environment.
Move or replace
Age, support status, energy, reliability, compatibility and handling risk may make replacement or staged migration preferable to relocating every asset. Assess whether replacement equipment or parallel preparation reduces the risk and duration of the physical move.
Big bang or waves
A single event shortens transition but concentrates risk; phased waves provide learning and rollback opportunities but may require temporary inter-site connectivity. Choose phases around application dependencies, available change windows and the client's recovery requirements.
Physical versus service responsibility
FDNS can support infrastructure and asset movement, while application shutdown, data integrity, platform validation and business acceptance remain with authorised owners unless explicitly scoped. Identify who authorises shutdown and confirms application recovery; physical reconnection is only one part of service restoration.
Fallback strategy
Rollback must be realistic about asset location, cabling, data state, time remaining and decision authority, not simply a line in the plan. Define rollback triggers, decision times and escalation contacts before any equipment is disconnected.
Our controlled delivery process
The exact programme is adapted to the site, operator and principal contractor. These checkpoints provide a practical route from workfront release to operational handover.
1
Discover
Inventory assets, ports, dependencies, owners, service criticality, records and destination constraints. Produce an agreed inventory of source assets, connections and destination positions before finalising the move scope.
2
Design
Create target racks, connectivity, labels, routes, capacity and temporary-service requirements. Check the destination design against equipment dimensions, rack capacity, power interfaces and cabling requirements.
3
Plan
Build runbooks, waves, resources, handling, communications, approvals, rollback and validation. Agree the runbook, responsibility matrix, change window, handling arrangements and rollback decision points.
4
Prepare
Install and test destination infrastructure, stage materials, verify access and freeze uncontrolled changes. Label connections and prepare destination infrastructure so disconnection and reconnection follow controlled records.
5
5
Move
Execute authorised shutdown, identification, disconnect, handling, transport, re-rack and reconnect steps. Track equipment and cable changes against the runbook, escalating any mismatch before reconnecting services.
6
Validate
Test physical and network connectivity, support service-owner checks, update records and close exceptions. Record cabling tests, asset reconciliation and client service-validation decisions before closing the move.
Standards, testing and quality assurance
Relocations use the client’s change, information-security, asset, safety and operational controls, together with applicable data-centre and cabling standards. Handling follows equipment manufacturer instructions. FDNS’ ISO 9001, ISO 14001 and ISO 45001 management systems support controlled delivery, but application and data assurance remain with authorised owners unless contracted otherwise.
A standard does not replace the approved design or client work package. FDNS confirms the asset, link, environment, equipment interfaces and acceptance requirements before selecting installation details or test limits. Measurements and inspections use consistent identifiers and retain settings, native evidence and exceptions.
Delivery is managed through FDNS’ ISO 9001, ISO 14001 and ISO 45001 management systems. This supports controlled quality, environmental responsibilities and safety-led working in live data halls, construction zones, equipment rooms and multi-contractor environments.
Where FDNS data centre relocation services are used
FDNS data centre relocation services support organisations moving racks, network equipment, servers, storage and associated connectivity between rooms, halls or facilities. Typical projects include colocation migrations, data centre exits, consolidation programmes, hardware refreshes, estate rationalisation, mergers, rack-to-rack moves and phased moves into new data halls.
A successful migration depends on more than transport. Destination power, cooling, rack space, patching, fibre, copper, port allocation, carrier services, labelling, sequencing and rollback requirements must be ready before equipment is moved. FDNS uses a controlled approach so physical relocation and connectivity restoration align with the client’s change plan.
Common data centre relocation risks and how FDNS controls them
Common risks include incomplete asset records, missing dependencies, destination infrastructure not being ready, incorrect port mapping, unplanned downtime, damaged equipment and changes made outside the agreed migration sequence. FDNS controls these risks through surveys, asset and connectivity records, readiness checks, phased work packs, labelling, chain-of-custody discipline and agreed cutover procedures.
Where required, cabling, fibre testing, rack preparation and post-move verification can be built into the programme. This gives the client a clearer handover position and reduces the risk of arriving at the destination with equipment that cannot be connected or returned to service.
How data centre relocation differs from our other data centre services
Relocation is the controlled move and re-establishment of live technical infrastructure. Racking, cabling, fibre installation and testing may all support a migration, but each is a separate technical work package. FDNS can combine these under one coordinated relocation plan where the scope requires it.
Planning a controlled data centre relocation
A successful data-centre relocation depends on accurate asset, connectivity and dependency information, together with a controlled migration sequence and recovery plan.
Information needed for a relocation quotation
A data centre relocation should begin with a complete understanding of what is moving, what each asset depends on and what must be ready at the destination before the move starts. FDNS reviews rack elevations, equipment inventories, power feeds, copper and fibre connections, upstream and downstream dependencies, carrier services, target locations, change windows, restoration priorities and required rollback arrangements. This creates a migration plan based on service continuity rather than simply on physical transport.
For complex moves, the scope may also need phased migration waves, temporary connectivity, pre-cabling, pre-testing and destination readiness checks. These controls reduce the risk of equipment arriving at a new location before power, cooling, rack space or network connectivity is ready.
Relocation readiness and final handover
Provide asset lists, source and destination rack positions, connectivity schedules, power requirements, equipment weights, packaging constraints, security controls, access routes, loading arrangements, maintenance windows and any systems that cannot be powered down. Identify which assets require special handling, which links must be tested before and after the move, and who owns application validation once the physical infrastructure has been restored.
The brief should also define labelling, chain of custody, rollback criteria, spare optics or patch leads, drawing updates, cable remediation, disposal or storage requirements and the expected completion evidence. This gives FDNS a clear basis for sequencing, staffing, logistics and final acceptance.
Why choose FDNS for data centre relocation services?
FDNS combines physical infrastructure engineering with controlled migration planning, helping clients relocate racks, servers, storage and network equipment without losing sight of the connectivity and dependencies that make those systems work. We can coordinate copper, fibre, patching, labelling, pre-cabling, testing, asset movements and post-move verification within one work package. This gives the client a structured migration route with defined change windows, rollback points and handover evidence rather than relying on ad-hoc reconnection.
Migration Planning Around Dependencies
Power, network, storage, carrier, rack and application dependencies are identified before equipment moves. This helps establish the correct sequence and reduces the risk of restoring hardware before its supporting services are ready.
Pre-Cabling and Destination Readiness
Destination racks, fibre, copper, patching, power and access can be checked or prepared before the migration window. This shortens the time equipment remains offline and helps expose readiness issues before the critical move.
Controlled Asset and Connectivity Moves
Labels, rack positions, patching and connection schedules are managed against the approved move plan. This provides a clear reference for each migration wave and reduces the risk of equipment or links being restored to the wrong location.
Testing and Post-Move Verification
Where required, links can be tested before and after relocation so physical connectivity issues can be separated from application or configuration problems. Exceptions are recorded rather than left for the operations team to discover.
Clear Migration Handover
Updated rack information, connectivity records, test evidence and known exceptions can be included in the final handover. This gives the client a traceable record of what moved, where it moved to and what was verified before service restoration.
Frequently asked questions about data centre relocation and migration
1. What is included in a professional data centre relocation service?
Scope can include discovery, asset and connectivity inventory, destination design review, rack and pathway preparation, new cabling, move runbooks, labels, de-racking and re-racking support, controlled transport, patching, physical testing, record updates and coordination with service owners. Application and data responsibilities must be allocated explicitly.
2. How does FDNS minimise downtime during a data centre move or migration?
Downtime is reduced through dependency mapping, destination pre-build and testing, staged migration waves, rehearsed runbooks, accurate labels, pre-positioned tools and spares, decision gates, realistic rollback and representative validation. Some systems can use temporary or parallel connectivity, but that option must be engineered and tested.
3. Can a data centre relocation be delivered in planned migration phases?
Yes. Phased waves can reduce concentrated risk and allow lessons from early moves to improve later activity. They may require temporary network, storage, security or application connectivity between locations. The wave plan groups assets by dependency and business impact rather than moving equipment solely by physical rack order.
4. How are servers, storage and network devices tracked during a relocation?
Each asset can be linked to source and destination rack positions, serial or asset IDs, ports, cables, owner, move wave and status. Labels, scans, photographs and controlled checklists support chain of custody. Exceptions are recorded immediately so unidentified equipment is not moved on assumption.
5. What must be checked at the destination data centre before equipment is moved?
Checks include rack and rail compatibility, position and capacity, power feeds and connectors, cooling, weight and access, cable pathways, network and carrier links, fibre polarity and loss, patching, security, monitoring, labels, spares and operational approvals. Responsible specialists validate power, cooling and application requirements.
6. Can FDNS coordinate specialist transport and handling for data centre equipment?
Equipment handling and transport can be included or coordinated subject to the agreed service, vehicle, packaging, insurance, security, route, access and chain-of-custody requirements. Sensitive or manufacturer-controlled equipment may need specialist handling. The quotation identifies whether FDNS, the client or an approved logistics provider owns each step.
7. What is a data centre migration runbook and why is it important?
A runbook is the approved step-by-step plan for a move event. It identifies assets, roles, timing, prerequisites, shutdown authority, disconnect and reconnect sequence, cabling, handling, communications, evidence, decision gates, rollback and validation. It should be tested through review or rehearsal and controlled under change management.
8. How are connectivity and services validated after a data centre relocation?
FDNS can verify physical installation, labels, link lights, cabling and agreed network tests. Application, database, storage and business-process owners then complete their defined functional checks. Success criteria and evidence are written into the runbook so the move is not declared complete on the basis of power alone.
Related data centre services
Plan a controlled data centre relocation with FDNS
Share the source and destination sites, equipment inventory, rack layouts, migration windows, dependencies, cabling requirements and acceptable downtime. We can help build a phased relocation plan covering readiness, labelling, de-rack and re-rack activity, connectivity, testing and documented service handover.