Moving equipment between cages in the same colocation facility is a relocation with a very short transit leg. The distance is often a few hundred feet of corridor, but work orders, cross-connects, power, and the floor route all run on the provider's lead times. With no truck and no second building, the temptation is to schedule it like a weekend task.
That assumption is where these projects go wrong. An intra-facility move carries almost every dependency of a full relocation, plus a few that only exist because the building belongs to someone else. The provider controls the doors, the floor, the power, and the cross-connects, and each of those runs on its own lead time.
Why Short Moves Get Underestimated
The physical distance is the smallest part of the job. What takes time is the paperwork and provisioning at the destination, and most of it cannot start until the new cage is contracted.
Teams that would never attempt a cross-country move without a plan will run an internal one from a spreadsheet. The result is a move day where the racks are ready to roll and the new cage has no live power, no cross-connects, and no approved work order for the crew.
Treat it as a colocation migration with a very short transit leg. The planning steps are the same ones described in any colocation migration planning guide: contract, provision, survey, schedule, move, verify.
What Happens to Cross-Connects When You Change Cages?
Every cross-connect that terminates in your current cage has to be re-created at the new one. That includes carrier circuits, links to cloud on-ramps, connections to other tenants, and any meet-me room patching.
The provider orders and installs these, and their turnaround is set by their own queue, not your move date. Some carriers also need to issue a new letter of authorization or reissue an order before the provider will run a new connection to their demarcation point. Start the inventory early: list every existing cross-connect by its provider circuit ID, its far-end party, and its port at your end.
Decide for each one whether it will be re-created in parallel or moved. Ordering new cross-connects to the new cage before the move costs a period of double billing, but it lets your IT team bring services up on the new paths before the old ones are disconnected. Moving a single cross-connect on move day turns it into a hard outage for whatever rides on it.
The physical patching inside the new cage, from the provider's demarcation panel to your racks, is planned like any new cabling build. Labels, patch panel layout, and cable lengths should be settled before the first rack rolls.
Work Orders, Escorts and House Rules
Colocation providers control who moves equipment through their common areas. Expect to submit a work order or method of procedure that names the crew, the time window, the route, and the equipment being moved. Some facilities require a provider escort for any movement outside a tenant cage, and escorts are booked against staff availability, often with a minimum notice period and an hourly charge outside business hours.
Check the house rules for:
- Approved hours for equipment movement and loading dock use
- Whether cardboard and packing materials are allowed on the data hall floor
- Requirements for floor protection, ramps, and anti-static measures, often modeled on ESD Association standards
- Badge and access list updates for every crew member
A crew that is not on the access list waits in the lobby.
What Power Does the New Cage Need?
The new cage needs circuits of the right voltage, amperage, and receptacle type, landed where your rack PDUs can reach them, and provisioning them is usually the longest lead item. If you are changing from single-phase to three-phase, or adding density, the provider may need to install new whips or breakers to NFPA 70, and that work is scheduled by their electrical team.
Confirm the receptacle type against your PDU plugs, not against a description in an email. A mismatch between an L6-30 and an L21-30 receptacle is a one-word difference on the order and a full stop on move day. Confirm the circuit is live and labeled before the move window opens, and have the provider review cooling and containment at the new cage against your expected heat load.
Planning the Floor Route
The route from cage to cage is rarely a straight corridor. Racks may need to pass through other suites, cross raised floor, take a freight elevator between levels, or travel through a loading area.
Walk it. Measure door widths, check ramp angles, and confirm the floor along the way is rated for a loaded rack on a dolly. Raised floor tiles near a perforated cooling row may not carry the same load as solid tiles, and a floor loading limit applies to the route as well as the final position.
Decide whether racks move populated or empty. Rolling a loaded rack a short distance on a smooth slab can be reasonable when the rack and casters are rated for it. Moving across thresholds, elevator gaps, or raised floor usually argues for de-installing the heaviest equipment, moving it separately on carts, and re-racking at the destination.
Phased Moves and Cutover
Most intra-facility moves are phased because they can be. The old and new cages share a building, so equipment can move in groups across several windows while both cages stay live.
The physical side of each phase is simple to describe: de-install a defined group, move it along the approved route, install and cable it at the new cage, and record what moved. The network infrastructure work in each phase covers racks, patching, and labeled cable runs.
The system side belongs to your own IT team. Shutting down applications, redirecting traffic, changing routing, and confirming services are healthy at the new location are decisions and tasks your team owns. Build the phase plan so that the physical move groups match the groups your IT team can shut down and bring back up together, and so that every phase has a defined point where the team confirms services before the next group is released.
Keep the old cage contracted until the last phase is verified and the old cross-connects are formally disconnected. Releasing it early to save a month of fees looks good until something has to go back.