Calgary & Alberta · Fully insured · Operating since 2002
(403) 612-7012Loading...
A move planning toolkit built from the documents a relocation actually produces. Each stage below lists what the artefact has to contain, and links to the guide that explains how to build it.
Toolkit
Nothing here is gated and nothing is a placeholder. The content is the guide it points to.
Every server, switch, router, UPS and appliance recorded with rack position, weight and owner, then extended with what each system depends on and what depends on it. Build the dependency side from a full month of traffic data, not from memory, so month-end batch jobs appear.
The per-connection record that lets the destination be a rebuild rather than a reconstruction. A-end and B-end identity, media type, VLAN and bundle membership, function, and the label ID physically applied to both ends of the cable before anything is disconnected.
One row per deliverable, one column per vendor, each cell marked in scope, excluded or unstated. Unstated is the column that decides the real cost. Price the gaps at what covering them with your own staff at overtime would cost, then compare.
A timed sequence for the window: arrival, shutdown, de-rack, load, transit, re-rack, re-cable, power-on, validation, handover. Each step carries a duration, a dependency and a named owner, and the window is built backwards from the last validation test.
Not a paragraph promising the equipment will come back. A decision point with a clock on it, a named decision-maker and deputy, the state the source site must be left in for rollback to be possible, a data reconciliation step, and an execution estimate.
Written before the window, in the same tier order as the power-on sequence, each test with an unambiguous pass condition and a named owner. Link, routing, name resolution, authentication, storage paths, application login, then a real business transaction end to end.
Sequence
The planning documents above exist to serve this sequence. Every project uses it, scaled to the footprint.
A dedicated project manager documents every asset, dependency and constraint before anything is unplugged.
Existing connections are mapped and labelled so the destination build matches the source exactly.
Controlled shutdown, disconnection and antistatic wrapping by trained specialists.
Custom carts, insured vehicles, and documented custody from dock to dock.
Equipment is re-racked and re-cabled to the mapped topology at the destination.
Power-on, connectivity and validation testing before the project is signed off.
Guides
Longer-form operational detail for each part of the plan.
The full phase-by-phase checklist, from the six-week audit through move week to the first two weeks after go-live.
Cutover windows, dependency mapping, phased versus big-bang migration, rollback planning and what causes overruns.
What the record contains, how it is captured and labelled, and what a move without one actually costs.
Qualifying questions, insurance and chain of custody, scope-of-work contents, and the red flags worth walking away from.
All four are listed on the IT relocation guides index. Scope, scheduling and cost questions are answered on the IT relocation FAQ, and completed projects are documented in the IT relocation case studies.
Delivery
The toolkit is enough to run a plan. These are the scopes the plan hands off to.
The scope and audit stage produces the asset inventory, the dependency map and the cutover sequence for your specific site, before a date is committed.