What should be done before anything moves?
- Inventory every device with serial number, model and rack position
- Photograph racks front and rear
- Map every cable: source port, destination port, cable type
- Apply labels that survive transit and match the map
- Confirm destination racks, power and connectivity are ready
Agree the sequence
Decide which racks or devices move together, what order they come down and go up, and where the engineers need to confirm before the next step.
Controlled disconnect
- Disconnect only what the plan says, in the order it says
- Keep cables with their equipment or in labeled bundles
- Record anything that differs from the pre-move map
Handling and transit
- Protect fiber, optics and rails from damage
- Track each item from source to destination
- Agree who owns transport and insurance
Reinstall and verify
- Install equipment in the destination rack positions
- Reconnect from the port map
- Verify each port against the pre-move record
- Photograph the final state and report exceptions
What stays with your engineers during a migration?
The physical checklist supports the migration. Application cutover, logical validation and service health stay with the engineering team.
How should cables and labels be handled during a move?
Cables are the part of a migration most likely to cause confusion afterward. Label each end with the same identifier before disconnecting, and make sure the labels will survive transit and handling.
Keep cables with the equipment they belong to, or bundle and tag them by rack and port range. When the destination rack is ready, reconnect from the port map rather than from memory.
What risks are specific to the physical move?
- Equipment damaged in handling or transit
- Rails, cables or optics left behind at the source
- Rack positions at the destination that differ from the plan
- Power or space not ready when equipment arrives
- Labels lost or unreadable
- Unclear ownership of transport and insurance
How do you verify the physical result after reinstalling?
Verification mirrors the pre-move record. For each device, confirm the rack position and power feed. For each cable, confirm both ends against the port map and check link state. Record every difference and photograph the finished racks.
Only after the physical verification is complete should engineers begin logical validation, so a physical error is not mistaken for a configuration problem.
How do the phases of a physical move compare?
Scroll the table sideways for more.
| Phase | Main goal | Typical evidence |
|---|---|---|
| Plan and inventory | Know exactly what exists and where it goes | Asset list, rack elevations, port maps |
| Disconnect | Remove equipment without losing track of connections | Photos before, labels on every cable, a disconnect log |
| Transit | Move equipment safely with a record of custody | Packing list, serial check at each handover |
| Reinstall | Place and connect equipment as designed | Photos after, serials, deviations from plan |
| Verify | Confirm the physical result with your engineers | Link and power checks, signed completion record |
What should you decide before the move day?
- Which devices move together and which move on a separate date
- What happens if a device does not power on at the new site
- Who is on site at both ends and how they communicate
- Which cables are reused and which are replaced
- What the acceptance criteria are for each rack
What if a device does not power on after the move?
- Stop and record what was done and what is seen
- Check power feed, cable and outlet before assuming a fault
- Compare with the photos taken before the move
- Tell the remote engineer and agree the next step
- Record the outcome and whether a spare or RMA is needed
