IT cutover is the programme that runs in parallel with the fitout build, and it is the programme most likely to leave the tenancy without working phones, network, or access control on the first morning of occupation. The reason is not that IT is inherently harder than construction. The reason is that the fitout programme is usually well-governed, with a single builder coordinating trades, while the IT programme is usually split between the tenant’s internal team, one or more external providers, the new telco, and the equipment supplier. When those parties are not sequenced against the fitout dates, the gaps show up at go-live.
Staff walking into a freshly completed office where nothing connects is an operational setback the fitout itself cannot prevent. The coordination that avoids it sits outside the construction scope and needs its own planning. What follows is how the IT cutover usually runs against a commercial fitout programme, where the typical gaps appear, and what the tenant can do in each stage to keep them closed.
Why IT cutover is its own programme
The construction programme hands over a building ready to receive IT services. It does not deliver the services themselves. Cabling is installed, power is in place, access control back-boxes are fitted, audio-visual cabling is pulled to the rooms that need it. What the building does not do is provision the network, cut over the telephone service, migrate the servers, connect the printers, load the access-control software, or confirm every desk and meeting room works before staff sit down. That is the IT cutover, and it runs from roughly four weeks before practical completion to about two weeks after.
Two features of the IT cutover make it distinct from the fitout build. The first is that it spans physical, logical, and service layers. A working network needs cables in place, switches configured, Wi-Fi tuned to the building, internet service cut over, and user devices pointing at the right servers. The second is that it depends on external parties whose timelines are not governed by the fitout contract: the telco provisioning the new service, the managed service provider reconfiguring the SD-WAN, the AV integrator programming the room controllers, and the access control vendor loading the new user database.
Each of those parties has its own lead time, its own commissioning process, and its own requirements to do its work on site. Coordinating them against the construction dates is the piece of work that sits with the tenant or their project manager, not with the builder.
The workstreams inside a typical office IT cutover
The full IT cutover usually includes: WAN (internet and intersite links), LAN (switches, Wi-Fi, cabling), telephony (fixed lines, unified communications, mobile integration), physical servers or cloud connectivity, end-user devices, audio-visual systems for meeting rooms, access control and alarm, printer and multifunction device rollout, and any specialist systems like point-of-sale, trading systems, or clinical software.
In most modern offices the server footprint is small and largely cloud-based, so physical server migration is a minor workstream or absent entirely. Telephony is often integrated into the unified communications platform rather than handled as separate lines. Access control may be tied to the building’s base service or managed as a tenant system with a dedicated controller in the comms room. Each tenancy has a slightly different mix, but the workstreams above are the working checklist in most cases.
The coordination task is to identify which workstreams apply, who is responsible for each, and what each needs from the building before it can run. Power to comms rooms, floor boxes under desks, and ceiling-mounted Wi-Fi locations are usually the physical-side enablers, and those need to be in place well before the services can commission against them. Power and data planning decisions made early in the fitout brief are what make the IT cutover possible; decisions left until the end of construction usually create gaps.
Who owns the IT cutover
The clearest projects have a single owner for the IT cutover workstream, sitting alongside the fitout project manager and reporting into the same governance rhythm. That owner is usually the tenant’s head of IT, an engaged managed service provider, or an external project manager retained specifically for the move. Without that role, accountability scatters: the telco answers to their own order book, the MSP schedules around their other clients, the AV integrator returns when their programming work is ready, and the fitout PM has no authority to pull them together.
The practical test is whether there is a single person who can answer two questions: when will every IT workstream reach each stage, and what does each workstream need from the building by when. If those two questions have a single authoritative answer, the coordination is in hand. If they need to be asked to three or four different parties with inconsistent dates, the coordination is already slipping.
On smaller fitouts, the tenant’s IT manager often takes this role informally. On larger fitouts, formal appointment of an IT transition lead is usually worth the cost, particularly where several vendors are involved or the cutover weekend carries material business risk.
The sequence that usually works
A workable cutover sequence typically runs in five stages. First, the new site is provisioned in parallel with the existing site: WAN services ordered, LAN equipment procured, telephone service arranged with porting scheduled, cabling confirmed against the fitout drawings. This stage sits four to eight weeks before handover and mostly happens in the background.
Second, the new site is commissioned without user load. Switches are installed and configured, Wi-Fi is surveyed and tuned, the WAN comes up, and the LAN is tested with representative traffic. This stage sits one to two weeks before handover and requires the comms room to be powered, air-conditioned, and cable-terminated. Any delay in the fitout programme on those specific items compresses this stage.
Third, the user-facing infrastructure goes live under test conditions. End-user devices are placed at desks and verified against the network. Printers are installed and tested. AV systems are commissioned room by room. Access control is loaded with the new user database. This stage runs across the final week before occupation and into the first few days of the new site being in use.
Fourth, the telephone porting and the internet switch-over are scheduled for a specific cutover window. This is usually a weekend or overnight window, chosen to minimise business impact. Porting in particular has a defined cut time set by the telcos; missing it delays the switch by days, not hours.
Fifth, the old site is gracefully decommissioned in parallel with the new site running. Servers and network equipment at the old site are retained in read-only mode for a defined period, usually a week or two, to allow rollback if a critical issue appears. Access control at the old site is disabled progressively as staff move. The old comms room is only fully decommissioned once the new site has been stable for an agreed period.
The cutover weekend
Most commercial IT cutovers concentrate the highest-risk transitions into a single cutover weekend, or a long weekend over a public holiday. The structure is familiar: business closes at end of trading on a Friday, the cutover team moves critical services from Friday evening through Sunday, and Monday morning opens on the new site with everything working.
What this compresses is the margin for error. A cutover weekend only works if every piece of infrastructure at the new site has already been commissioned and tested in the weeks before. Using the weekend to debug unconfigured equipment, or to discover that a patch panel was not terminated correctly, typically turns a 36-hour cutover into a 72-hour one, and Monday morning opens with staff unable to log in.
The useful discipline is to run a dry-run of the cutover at least once, one to two weeks before the real weekend. The dry-run identifies gaps while there is still time to close them. A cutover weekend that has been rehearsed runs smoothly. A cutover weekend that is the first time every system has been tested together runs late.
Dependencies the fitout programme must respect
Several construction milestones drive the IT cutover schedule, and delays in them cascade directly into IT readiness. The comms room is the first. It needs power, cooling, and the comms riser in place roughly two weeks before user-device rollout. Cabling termination and certification usually sit on the critical path; a delay in the electrician or data cabler can push the LAN commissioning by a week, which in turn compresses user testing.
Floor boxes, wall plates, and AV back-boxes need to be live at the same time. An AV integrator cannot commission a boardroom where the ceiling microphone cable has not yet been terminated. A printer cannot be tested at a desk without a working outlet and a data point nearby. The order in which a fitout is built has a direct bearing on when IT can get on site, and a fitout programme that does not flag the IT-enabling milestones separately usually runs into the problem that the services are “nearly ready” when the cutover weekend arrives.
The other dependency is physical access. IT vendors cannot commission hardware behind sealed ceilings or walls. They need the site open and accessible, and they need it clean enough to operate equipment safely. A fitout that is still in trade finishing during the intended IT commissioning week is a fitout that will hand over on the day but will not have working systems on the morning after.
Common failure modes
Several patterns recur across IT cutovers that do not land cleanly. The first is late discovery of missing cabling. The fitout brief did not include the data points where the new printer and the new AV equipment are now planned to live, and the cabling was not pulled. Adding them after ceiling close-up is disruptive and visible.
The second is telco timing. The WAN service was ordered on the telco’s standard lead time, but a carrier-side constraint has pushed the activation back by several weeks. Staff arrive at the new site with a working LAN but no internet. This is one of the few IT issues that can originate entirely outside the project team and still derail the go-live, and it is the reason telco services are usually ordered earlier than anything else.
The third is AV programming. Meeting rooms with integrated systems need room-by-room programming, and each room has its own scenarios, codecs, and calibration. An AV integrator arriving on site the week of handover without having programmed the rooms in advance rarely finishes in time. The rooms open with audio-visual systems that mostly work, and that “mostly” creates a rolling series of service calls in the first month.
The fourth is access control. New staff records, new credentials, and reader commissioning are time-consuming. A floor that opens with only half the staff enrolled in the access system creates operational friction from the first morning and takes weeks to resolve cleanly.
Making the plan visible before it is needed
The pattern that avoids most of these failure modes is a single integrated schedule, owned by one person, that shows every IT workstream alongside the fitout milestones it depends on. It does not need to be a complex tool. A simple list of workstreams, dates, owners, and dependencies is enough in most cases. What it does need is visibility to everyone involved: the fitout PM, the tenant’s IT team, the external vendors, and the executive sponsor.
Without that integrated view, each party works to its own plan and the gaps between plans are where the cutover fails. With it, the gaps are visible early enough to close. The time to build it is at brief stage, at the same point that power and data decisions are being made, not three weeks before practical completion.
If you are planning a fitout and the IT cutover programme is not yet integrated with the construction dates, we can walk the fitout milestones alongside your IT workstreams and help coordinate the full office fitout so the building and the systems go live on the same morning.
📞 Call us on 1300 60 93 93