Office Relocation Checklist for IT: Move Your Office Without Downtime

Furniture can arrive a day late and nobody loses money. If the internet line, phones or ERP server are not working on Monday morning, the whole business stops. This office relocation checklist focuses on the IT side of a move — a 12-week timeline, internet lead times, a server move procedure, cabling and Wi-Fi at the new site, a weekend cut-over plan and day-one support — written for offices moving within or between the governorates.

Why IT is the riskiest part of an office move

Most moves are run by facilities or office managers who juggle landlords, fit-out contractors, movers and staff communications. IT often gets a single line on the project plan — “move computers” — which hides dozens of dependencies.

Consider what has to be true for staff to work normally on the first morning: the new building is connected to a provider, your line has been ordered and installed, the firewall has the new public IP addresses, every desk outlet is cabled and patched, access points are mounted, servers are back up with their data intact, phones ring on the right extensions, printers print and the door access system recognises staff cards. An office move IT checklist exists to make each of those dependencies visible early enough to act.

Typical consequences of poor IT planning

• No internet for days or weeks because the line was ordered late
• Servers damaged in transit or by condensation when powered up too soon
• Staff sitting at desks with no live network outlets
• External systems (banks, government portals, customer integrations) rejecting connections from the new IP address
• Lost assets because nobody recorded what left the old office

Building your IT office relocation plan

An IT office relocation plan is a short document that sits alongside the main move plan. It should be owned by one person — internal IT lead or an external partner — with authority to make decisions.

What the plan should contain

Section	Contents
Scope	Sites, headcount, systems in scope, what is being replaced rather than moved
Timeline	Key milestones from 12 weeks out to two weeks after the move
Responsibilities	Named owners for ISP, cabling, servers, desktops, phones, printers, security systems
Inventory	Complete list of equipment to move, replace or dispose of
Risks	Lead times, approvals, data loss, heat exposure, key-person dependencies
Cut-over runbook	Hour-by-hour plan for the move weekend, including rollback
Communications	What staff need to do before and after the move
Acceptance tests	What “working” means for each system on day one

If you are using a specialist for IT relocation services, ask for their runbook template early; it often surfaces questions you had not considered.

Start with an accurate inventory

A move is the best opportunity you will get to clean up your asset records. List every device with its serial number, user, location and condition, and tag anything untagged. Decide what to move, replace or retire. Our IT asset management services can turn this one-off list into a register you maintain after the move. For equipment you are retiring, arrange certified data wiping before it leaves your control.

The 12-week office relocation checklist

The timeline below assumes a typical move of 20 to 150 staff. Larger or multi-floor moves need more lead time.

12–10 weeks before

• Appoint the IT move owner and agree the budget approach and responsibilities.
• Confirm the new building’s service providers and order business internet lines.
• Complete the inventory and decide what to replace.
• Survey the new site with the fit-out designer (see next section).
• Review contracts: internet, phone numbers, leased equipment, software licences tied to location or hardware.

9–6 weeks before

• Finalise cabling, comms room and Wi-Fi design; issue to the fit-out contractor.
• Order new equipment (switches, access points, UPS, racks) to allow for shipping delays.
• Plan IP addressing, VLANs and firewall changes for the new site.
• List every external party that whitelists your IP address and notify them of the coming change.
• Confirm moving company, insurance and building loading bay bookings at both sites.

5–3 weeks before

• Cabling installed, tested and certified at the new site.
• Internet line installed and tested; firewall pre-configured and staged.
• Comms room power, cooling and UPS commissioned.
• Access points, door access and CCTV installed.
• Write the cut-over runbook and staff instructions.

2–1 weeks before

• Verify backups and perform a test restore.
• Pre-stage the network at the new site so it is live before equipment arrives.
• Label every device with its destination desk or rack position.
• Brief staff: what to pack, what not to touch, what happens on Monday.
• Confirm on-site support for day one.

Move week and after

• Execute the weekend cut-over (see below).
• Floor-walk support on day one and day two.
• Post-move review at two weeks; decommission and hand back the old site.

Surveying the new site

Never assume a new office is “ready” because the landlord says it has data points. Walk the space with your IT partner and the fit-out designer before drawings are frozen.

What to check

• Building connectivity: which providers (e& or du) serve the building, and whether fibre is already in the riser to your floor.
• Existing cabling: category, condition, labelling and whether test results are available. Certify it rather than trusting it.
• Comms room location: distance to the furthest desks, ventilation, power and whether the room shares space with electrical or plumbing services.
• Ceiling type and height: affects access point mounting and cable routes.
• Building rules: working hours for noisy work, riser access, fit-out approval process and contractor permits.

In Egyptian free zones and many mainland towers, the landlord or authority requires approval of fit-out drawings, including IT works, before contractors start. Build that approval time into the plan. If the new site is effectively a fresh build-out, it can be easier to treat it as a full IT setup for a new office rather than a simple move.

Internet, phones and external services

Order lines early

New business fibre lines can take anywhere from a few days to several weeks to install, depending on whether the building is already connected and how busy the provider is. If the building has no existing fibre to your floor, civil or riser works may be needed. Order as soon as the lease is signed and consider a temporary 5G or LTE router as a fallback for day one.

Phone numbers

Ask your provider whether your existing fixed numbers can move with you, especially when moving between governorates or between exchange areas. If you use a cloud phone system or Microsoft Teams Phone, numbers are less tied to location, but you still need adequate bandwidth and quality of service at the new site.

IP address changes

Your new line will almost certainly come with new public IP addresses. Make a list of everything affected:

• Site-to-site VPNs with branches, warehouses or partners
• Remote access VPN settings
• Bank, payment gateway and government portal whitelists
• Cloud application conditional access rules
• DNS records for any self-hosted services, and SPF records for mail
• CCTV or alarm remote viewing

Missing one of these is the most common cause of “everything works except…” on Monday.

Cabling, comms room and Wi-Fi at the new office

The physical network at the new site should be finished, tested and live before a single PC arrives.

Cabling

Plan data outlets for every desk, printer, screen, door reader and camera, plus spares. Insist on certified test results and a labelling scheme. Our structured cabling guide explains Cat6 vs Cat6a and what a proper handover should include, and our structured cabling team can design and install it as part of your fit-out.

Comms room

Treat the comms room as a priority, not a cupboard. It needs dedicated power, a UPS, 24/7 cooling and lockable access. If you are moving servers, the room requirements are higher; our server room requirements guide has a full checklist.

Wi-Fi

Do not simply rehang old access points in the same pattern. Different walls, glass and ceiling heights change coverage. A predictive or on-site survey of the new floor, followed by a validation survey after installation, avoids dead spots in meeting rooms. If your existing access points are more than five or six years old, a move is a natural time to upgrade with wifi installation in Cairo designed around the new layout.

How to move office IT equipment safely

Knowing how to move office IT equipment safely is mostly about packing, labelling and protecting kit from heat.

Desktops and peripherals

• Ask staff to back up anything stored locally (ideally, nothing should be).
• Shut down properly; do not just pull the plug.
• Bag and label cables, power adaptors and docking stations with the user’s name and new desk number.
• Pack monitors upright in purpose-made crates.
• Laptops should travel with their users where possible.

Network and rack equipment

• Photograph every rack and patch panel before disconnecting.
• Export and save device configurations (firewalls, switches, controllers).
• Label every cable at both ends if it will be reconnected.
• Remove heavy devices from racks before moving the rack; never move a loaded rack.

Heat and condensation

In summer, the inside of a closed van can become extremely hot within minutes, and electronics left in it can be damaged. Keep IT equipment in air-conditioned vehicles where possible, minimise time in transit and never leave equipment in a parked vehicle. When equipment moves between very different temperatures and humidity levels, leave it boxed to acclimatise for a few hours before powering on to avoid condensation inside the casing.

Moving servers without losing data

Servers deserve their own procedure. Spinning disks, RAID arrays and ageing power supplies are most likely to fail during a power-down and restart, not during normal running.

Server relocation checklist

☐ Full backup completed and verified with a test restore

☐ Second copy of critical data held off site or in the cloud

☐ Hardware health checked (disk, RAID, PSU and fan status) and any warnings resolved first

☐ Vendor support contract confirmed active, with on-site parts available if needed

☐ Configuration, IP settings and licence keys documented

☐ Applications and databases shut down cleanly in the correct order

☐ Servers removed from racks, packed in original or suitable cases

☐ Transported in a climate-controlled vehicle by trained staff

☐ Acclimatised before power-on at the new site

☐ Powered on in the correct order (storage, then hosts, then applications)

☐ Services tested by application owners before sign-off

If your servers are ageing, consider whether this is the moment to virtualise, consolidate or move workloads to the cloud instead of moving the hardware. Our server installation team can help with either path, and for critical systems a backup and disaster recovery service lets you fail over temporarily so the business keeps running even while the hardware is in transit.

The weekend cut-over

Since the Egyptian moved to a Saturday–Sunday weekend for most private businesses, Friday evening to Sunday is the natural move window.

A sample runbook

When	Task	Owner
Friday 17:00	Final backups complete and verified	IT lead
Friday 18:00	Staff log off; desktops shut down; movers start packing	Facilities / movers
Friday 20:00	Servers and network equipment powered down in sequence	IT engineers
Saturday 08:00	Equipment arrives; acclimatisation begins	Movers / IT
Saturday 12:00	Rack equipment installed; core network and firewall up	IT engineers
Saturday 16:00	Servers powered on; applications tested	IT / app owners
Sunday 09:00	Desktops connected; phones, printers and Wi-Fi tested desk by desk	IT engineers
Sunday 15:00	Go/no-go decision; rollback triggered only if critical systems fail	Move owner
Monday 07:30	Floor-walk support begins	IT support

Rollback planning

Decide in advance what happens if a critical system fails. Options include running from the backup or DR copy, operating from the cloud for a few days, or keeping the old site live if the lease allows overlap.

Day-one support and post-move review

Day one

Station engineers on the floor from before staff arrive. Most issues are simple — a monitor cable, a printer driver, a phone extension — but quick fixes keep confidence high. Keep a shared issue log so problems are tracked and patterns spotted.

Two weeks after

Hold a short review: what broke, what was slow, which documentation needs updating. Update network diagrams, the asset register, and the IP whitelist list. Hand back the old premises with all equipment removed, cabling left as required by the lease, and any disposed devices accompanied by data destruction certificates.

Printable IT relocation checklist

Copy this IT relocation checklist into your project tracker.

Planning

☐ IT move owner appointed

☐ Inventory complete; move/replace/dispose decided

☐ IT office relocation plan written and approved

☐ Contracts and licences reviewed

New site

☐ Site survey done with fit-out designer

☐ Fit-out and IT approvals obtained from landlord or authority

☐ Cabling installed, certified and labelled

☐ Comms room power, UPS and cooling commissioned

☐ Wi-Fi surveyed, installed and validated

☐ Internet lines installed and tested; backup connection ready

Systems

☐ Firewall and network pre-configured

☐ External IP whitelists and VPN partners updated

☐ Phone numbers and extensions confirmed

☐ Door access and CCTV operational

Move weekend

☐ Backups verified and restore tested

☐ Runbook issued with owners and times

☐ Equipment labelled with destination

☐ Servers moved per server procedure

☐ Desk-by-desk testing complete

After the move

☐ Day-one floor support in place

☐ Issue log reviewed and closed

☐ Documentation and asset register updated

☐ Old site cleared and data wiped devices certified

Common mistakes

• Ordering internet late. The single most common cause of a delayed move.
• Trusting existing cabling at the new site. Untested cabling causes intermittent faults for months.
• Moving servers without a tested restore. A backup you have not restored is a hope, not a plan.
• Forgetting IP whitelists. Bank and portal access breaks quietly until someone needs it urgently.
• Leaving equipment in hot vehicles. Egyptian summer heat can damage electronics quickly.
• No rollback plan. Without one, a failed server becomes a business outage.
• Skipping the post-move review. Lessons and documentation updates are lost.

Frequently asked questions

Conclusion

A successful move is decided weeks before the movers arrive. Use this office relocation checklist to start early, order your internet first, survey and build the new network before equipment arrives, protect your servers with tested backups and a proper procedure, and run the cut-over to a written plan. With a clear owner and a realistic timeline, staff should notice little more than a new view on Monday morning. For more practical planning advice, explore our IT guides.