Business internet planning for office relocation that starts with a move date — “we need to be live that Monday,” “the lease starts on the first,” “IT can cut over that weekend” — usually fails at the first unvalidated suite, not at the first calendar square. A move date is a constraint. It is not the plan. If you do not write the exact new service address, landlord and demarc realities, order lead times, what runs in parallel at the old site, and what evidence means the new path is accepted, the next promised install week still controls the move.
This page is the first relocation plan. It is not a carrier order form. It is the set of questions that keep a date from being treated as a network design.
Why a move date is not the plan
Leases and furniture dates do not survey a riser, reserve an entrance, or confirm the building is lit by the provider you assume. A date also does not decide whether the old circuit stays up through the first production week, or whether numbers, firewalls, Wi-Fi, and a backup path move on the same night as the desks.
Moves fail in familiar ways: a building address instead of a suite, construction treated as an assumption, a backup path promised “after,” voice still pointed at old public IPs, or the old service disconnected before the new path was accepted. None of that is a surprise if the plan was only a date.
Treat the old site and the new floor as two location records, not one order. If other sites must keep talking to the new floor, use the live multi-location connectivity assessment so a single-site move is not the whole design.
What belongs on the relocation plan
Before anyone treats a move date as an install commitment, fill these rows:
- Decision identity: one-for-one replacement, a redesign, or a temporary plus permanent path — plus who approves technical, commercial, and facilities choices.
- New location record: exact address, suite or floor, hours, access constraints, and a local contact who can meet a survey. A marketing address is not a service address.
- Landlord and building: demarc, riser rights, escort rules, and what the building owner must sign. Write those dates, not only the furniture date.
- Current-site overlap: what stays live at the old address, through which day, and who may disconnect it. Overlap is a line item, not an accident.
- Work that must continue on day one: payments, voice, identity, cloud tools, and the admin path used to fix a bad cutover.
- Resilience at the new site: whether a backup path is in the first order or a later hope. The redundancy and failover requirements worksheet is the companion when independence has to be true on opening day, not “after we settle in.”
- Voice, numbers, and security boundary: what ports, what firewall, what Wi-Fi, and what must be proven before staff arrive.
- Acceptance: the tests that mean production, not a link light — and the owner who signs them.
- Commercial: term, one-time charges, construction, overlap months, and quote validity versus the move window.
The business internet quote-readiness checklist is the companion when every provider should answer the same location, install, and commercial fields so a fast promise is not compared to a complete install.
A working sequence, not a weekend hero story
Start with the new suite and the building constraints, then the order, then the overlap, then the test, then the disconnect. Reverse that sequence and the move date becomes a hope. Serviceability, landlord approval, construction, and number porting each consume time a weekend cutover cannot invent. If the remaining buffer cannot hold a failed first install, the move date is already late. Disconnect the old path because the new path passed the acceptance tests you wrote before anyone packed a box — not because the overlap invoice looked wasteful.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- Which suite they validated, and whether the result is a check or an estimate — not a building-level on-net claim.
- What the landlord must provide, and which dates sit on the landlord, not on the carrier.
- How long the old and new services can run together, and who owns the disconnect.
- What they will prove before the first production morning: voice, payments, identity, backup path, and admin access.
- What happens if the install misses the move date, in writing, including overlap and temporary options.
If those answers are a move date and a promised weekend cutover, you do not have an office relocation business internet plan. You have a calendar.
What this page is not
This is not a carrier ranking, not a moving-company checklist, and not a claim that The Data Partner already lit anyone’s new floor. Skip incentive talk, skip on-net building lists as a substitute for a suite record, and skip any suggestion that a lease date replaces acceptance tests. Write the rows. Then request the orders. If you want a second set of eyes on the plan, start with a conversation.