The desks have arrived and the internet connection is active, yet staff cannot open a shared application or print a customer document. An office move can fail at the point where separate installations are supposed to become one working environment. A carrier’s completion notice does not prove that the business is ready to operate.

An office network cutover plan sets out how the business will move from the old site to a tested working network at the new one. It names the prerequisites, the people making decisions and the evidence needed to proceed. Start this work before choosing the final moving window.

When arranging managed IT services for a move, identify the network management tasks included in the project and the ongoing managed network service that follows. Installation, cutover acceptance and routine support are separate responsibilities, even when the same provider carries out all three.

Define what ready for work means

Ask each team to identify the tasks it must perform on the first working day. Opening email, taking calls, accessing a line-of-business application and using a shared printer are more useful acceptance tests than a general instruction to check the internet.

Separate the carrier handoff from the office network

Confirm the exact location where the carrier delivers service and who connects it to the business equipment. Check building access arrangements, installation appointments and any landlord requirements. A circuit installed in a telecommunications room may still need a completed path to the office’s equipment cabinet.

Have the team responsible for the managed network environment review that path. Include power, rack space, cabling and the equipment required between the carrier connection and employees. Record who supplies and tests each part rather than assuming it belongs to another contractor.

Confirm applications that depend on the old location

Some applications or partners may recognize the business by a particular network address or connection. Ask the administrator to identify relevant allowlists, site links and remote access arrangements. Changing location can affect them even when employee usernames remain the same.

For companies arranging business IT support in Mississauga or managed IT services in North York, give the provider the old and new site details together. A move is a dependency problem, not simply a delivery address change for existing equipment.

Build a sequence with named prerequisites

Write down the order in which work must happen. Cabling inspection may need to finish before access points can be tested. The new connection may need to be usable before the firewall configuration is finalized. Identify tasks that can be completed in advance and those that require the actual cutover window.

Inspect the new space before moving equipment

Check that the planned cabinet has suitable power and that ventilation and access are appropriate for the equipment. Verify cable labels against outlets employees will use. Do not discover on moving day that the reception desk has no working network connection.

If telephones or access points draw power from the network switch, review the switch’s available PoE power budget. Moving an existing device to a new switch does not prove that the new switch can power all connected equipment simultaneously. Confirm the combination before staff depend on it.

Review wireless coverage in the actual layout

A floor plan helps with preparation, but walls, furniture and neighbouring networks affect real performance. Test the spaces where staff will work and move. Include reception, meeting rooms and any area where mobile devices support daily operations.

Use the explanation of workplace Wi-Fi roaming problems when planning a test that involves walking between areas. A strong signal beside one access point does not establish that a device will remain connected throughout the office. Record the locations and tasks tested.

Preserve the configuration before changing it

Take an approved configuration backup and record the settings needed to recover the current network. Check that the person performing the move can access the relevant administration tools through an authorized account. Keep recovery information available if the usual office connection is unavailable.

Keep the move focused

Avoid combining the relocation with every overdue network improvement. A new firewall, a different email setup and a redesigned wireless network may each be reasonable projects, but simultaneous changes make fault isolation and recovery harder. Identify which changes are actually required for the move.

The business record should explain both the existing arrangement and planned differences. AGMN’s article on usable IT documentation provides context for maintaining those details. For the cutover, add responsible names, dependencies and the agreed test sequence.

Preserve security boundaries

Do not connect every device to one flat network just to get through the first day. Carry forward the approved separation between employee systems, visitors and other devices. Confirm that the new configuration implements those boundaries rather than only reusing familiar wireless names.

The Canadian Centre for Cyber Security’s baseline cyber security controls offer a useful reference for reviewing secure configuration. AGMN’s article about separating guest Wi-Fi addresses the visitor-network requirement in more detail.

Set the go-or-stop decision before the window

Choose a person with authority to decide whether the business proceeds, pauses or uses the fallback. Define the latest safe decision time. Waiting until the moving crew has removed essential equipment may leave no practical way to return to the previous arrangement.

Agree on a realistic fallback

A fallback might involve approved remote work, limited operation from another location or retaining part of the old environment temporarily. Each option needs testing and business approval. Confirm that employees can access required information securely and that customer-facing work can continue within the agreed limits.

AGMN’s guidance on preparing for an internet outage is relevant to connection loss during the move. The cutover plan should go further by defining which incomplete dependencies prevent a move from proceeding and who communicates that decision.

Protect the period between sites

Equipment and business information can be exposed while packed, transported or awaiting installation. Assign custody, restrict unnecessary access and identify who confirms arrival. Keep a list of essential devices so the team can locate them without opening every box.

Retain old services long enough for the agreed acceptance process where practical and contractually appropriate. Do not cancel a working connection or related service solely because the new site has an installation date. The acceptance result should drive the operational decision.

Run an end-to-end working test

After installation, have a representative employee perform real tasks using approved test information. Confirm login, application access, file access and printing where relevant. Ask a colleague to verify the result from the receiving end of the task rather than relying only on the initiating screen.

If the move includes business telephone systems, test the main incoming number, an outgoing call and relevant call-handling routes. Confirm any site-location information with the voice provider, including requirements affecting emergency calling. Do not place emergency test calls without the provider’s approved process.

Check meeting-room connectivity using the equipment people will actually bring. Include remote attendees in an approved meeting test. Review alerts and network health after the normal workload begins, because a quiet evening test cannot reproduce every first-day condition.

Leave the new office with an operating record

A hypothetical business might approve the move after its core applications pass, while recording a non-essential meeting-room issue for later repair. That decision is reasonable only when someone has assessed the effect and named an owner. Do not label the entire site ready while leaving critical failures unexplained.

Update diagrams, service details, equipment locations and support contacts after acceptance. Remove temporary access and arrangements when their purpose ends. A successful move leaves employees able to work and the support team able to understand the new site without reconstructing moving day from memory.

For network planning and ongoing support around an office move, discuss your requirements with AGMN before the cutover window is fixed.