Opening a second office in another state looks a lot like an office move. You still need desks, a network, phones and a date to work to. The difference is what happens to the first office. After a move, it's gone. After you open a second office, you have two, and anything in your IT that was set up on the assumption of one location needs checking.
This checklist covers what most often gets missed: identity and access, the parts of Microsoft 365 that are tied to a place, what you can promise on support, and a handful of admin jobs that tend to surface a few weeks too late.
The internet usually isn't what holds you up
In an office move, the internet connection and the phone number port usually set the date. Carriers work to their own lead times and you can't hurry them. A second office in a serviced or shared building is often different. The building already has internet, and you can be online the day you get the keys.
The slow part is identity and access. Someone has to decide how staff at the new site will sign in, which systems they can reach, and what happens to conditional access rules that were written when everyone worked in one city. That can take weeks. It also tends to get left off the project plan, because nothing physical has to happen for it.
Decide early whether the new site is a branch or a peer
This decision affects almost everything else. It's also easy to leave unspoken until two people find out they assumed different answers.
A branch depends on head office. Systems, licences, escalations and decisions all route back there. It's cheaper and quicker to set up, but when the link to head office has a problem, so does the branch.
A peer can run on its own. It has its own internet, local services where latency makes them necessary, and it can keep working when the other office can't.
Most second offices should start as a branch, set up so they can become a peer later without starting again. In practice, that means avoiding anything that ties you to one location and would be painful to undo: licences locked to a site, an on-premises server that only exists in one city, or DNS records and file paths that assume there's only one office.
Microsoft 365: check anything tied to a location
Most of Microsoft 365 doesn't care where people sit, which is exactly why the few settings that do care get missed. Check these:
- Conditional access and named locations. If a policy trusts your head office IP range, staff at the new site will either be blocked, or someone will add a quick exception to get them working and forget to take it out. The second outcome is the worse one.
- Teams Phone emergency addresses. Every user on a calling plan has a registered emergency address. When someone moves interstate, theirs is wrong until somebody updates it. It's a compliance requirement, and it matters on the day someone has to call 000.
- Data residency. Confirm where your data is stored rather than assuming, especially if a client contract says where it has to be kept.
- Licences tied to a site. Any software or hardware licensed to an address, a site or a MAC address will need to be reissued, the same as in a move.
- Printers, scan-to-folder and anything with a fixed IP address. These get set up once and forgotten, until someone at the new office tries to scan a document.
Our Microsoft 365 management page explains how we look after the tenant side of this.
Only promise the support you can deliver
If your business supports customers, a second office raises an obvious question: can you offer the same response times there?
Start by splitting your services into two groups. The first is anything your whole team delivers remotely, like help desk, monitoring, Microsoft 365 administration and project work. It makes no difference which city the customer is in, so those service levels can apply at the new site from the first day.
The second group is anything that needs a person to turn up. Response times here depend on who's nearby. If the new office has two people, one is on leave and the other is at another job, you'll miss the target however good they are. Until the local team is big enough to cover for each other, offer on-site visits by arrangement instead of against a fixed clock. This matters most if your agreements include service credits or other penalties for a missed target.
We write our own agreements the same way. Remote response targets are financially backed, so if we miss one, the client is compensated. On-site attendance is included, never billed as a callout, and booked in with the client rather than timed.
The admin that turns up late
None of these are difficult. They just tend to come up a few weeks after they should have.
- Every place your address appears. Your website, invoices, email signatures, contracts and letterhead all need both addresses. Change them together rather than one at a time as you notice them. Address details that don't match across the web can hurt how both offices show up in local search.
- Google Business Profile. Check eligibility before you create a listing. Google requires a permanent, staffed location with its own signage, and many shared or serviced offices don't qualify. If a listing is suspended, Google can act on the whole account, which puts your existing listing at risk too.
- The building network. In a shared building you don't control the firewall, the segmentation or who else is connected. Treat the building network as untrusted and put your own firewall between it and your devices.
- Your asset register. Record which site each device belongs to from the start. Adding locations to an asset list later takes far longer than you'd expect.
- Backup and recovery plans. A plan written for one office often assumes the people and the equipment are in the same place. Check that it still works when they aren't.
- After-hours access. Know who holds keys and access cards at the new site, and how the building itself handles after-hours entry.
Give the coordination to someone at head office
A second office means a landlord or building manager, a carrier, an IT provider and the staff who are moving, all working to one date. It's tempting to put the person who's moving in charge, but they're the worst choice. They're packing, looking after clients and getting to know a new city at the same time. Give the job to someone at head office who has the time to chase people.
In a second office, identity and access take longer than the internet.
An office move is limited by carrier lead times you can't shorten. A second office is limited by how many of your systems assume there's only one location, and most of those assumptions sit in identity and access.
If you're planning a second site, or you've already opened one and the IT hasn't caught up, we can help you work out which of your single-office settings still hold. Read about our IT strategy work, or book a 30-minute call.