INDUSTRIESI07Global Operations
One standard,
every time zone.
IT for organisations operating across borders. The hard part is rarely the technology. It is that every country picked up its own suppliers, its own habits, and its own idea of what normal looks like.
WHAT WE HEAR
The four sentences we hear most in your sector.
- 01
Every office does it differently.
Each one solved its own problem locally and sensibly at the time. Ten years later there is no shared standard and no way to support any of it centrally.
- 02
Nobody can tell me where our data actually sits.
A question that stays theoretical until a customer contract, a regulator, or an acquirer asks it, at which point it becomes urgent and expensive.
- 03
Our Auckland team files a ticket at five and hears back at nine tomorrow.
Which is fine for a password reset and not fine for an outage. Coverage has to follow where people actually work.
- 04
We acquired a business and inherited its IT whole.
Two tenancies, two sets of suppliers, two ways of onboarding a person, and a plan to consolidate that keeps slipping.
THE STACK
The systems you actually run.
Not a list of logos. These are the platforms we support, migrate, and get called about in this sector. If yours is missing, it usually means we have not worked with it, and we will say so rather than nod along.
Identity across borders
The one thing that genuinely has to be single and consistent, because everything else hangs off it.
- Microsoft Entra ID
- Conditional access by region
- Single sign-on
- Cross-tenant collaboration
- Guest and contractor access
Workplace platforms
Usually more than one tenancy after an acquisition, and consolidating them is a project rather than a setting.
- Microsoft 365 multi-geo
- Google Workspace
- Tenant-to-tenant migration
- Shared collaboration spaces
Network and connectivity
Performance across distance is a design question. Backhauling Sydney traffic through Auckland is a decision somebody made once and nobody revisited.
- SD-WAN
- Regional internet breakout
- Site-to-site connectivity
- Global failover
Residency and jurisdiction
Where data lives, who can reach it, and under whose law. This is the part that turns up in contracts and due diligence.
- Regional data residency
- Sovereign hosting
- Cross-border transfer controls
- Jurisdictional access records
WHERE WE HELP
Four things we do for global operations specifically.
- 01
One standard, applied everywhere
A single build, a single identity platform, and one way to onboard and offboard a person, whichever country they are in. Local variation where it is genuinely required by law or by language, and nowhere else.
- 02
Coverage that follows the work
Support hours arranged around where your people actually are rather than around one head office clock, with an escalation path that does not depend on somebody in a different hemisphere being awake.
- 03
A defensible answer on data residency
A documented picture of what is held where, who can reach it, from which jurisdiction, and under what terms. Assembled once and kept current, because it is always requested under a deadline.
- 04
Consolidation after an acquisition
Merging tenancies, identity, and suppliers in a sequence that keeps both businesses trading, with a day-one plan that covers what must work immediately and a longer plan for everything that can wait.
WHAT YOU ANSWER TO
The obligations that shape the work.
We make the systems match your obligations. We are not your lawyer or your compliance adviser, and where a question turns on interpretation we will tell you to take advice rather than guess on your behalf.
Privacy Act 2020
New Zealand law makes you responsible for personal information you send overseas, requiring comparable safeguards wherever it lands. Operating across borders does not dilute that, it extends it.
GDPR
Follows the data rather than the company, so holding personal information about people in the European Union can put you in scope wherever you are based. New Zealand holds an adequacy decision from the European Commission, which simplifies transfers here considerably.
Australian Privacy Act
Most New Zealand businesses expanding offshore go to Australia first, which brings its own privacy regime and its own notifiable data breach scheme. Similar in shape, different in detail.
Contractual residency clauses
The strictest requirement is usually one somebody already signed. Customer contracts frequently specify where data may be held, and those clauses outlive the person who agreed them.
WHAT IT COSTS
Per user, per month, with a scoped consolidation project
Ongoing support is per user per month regardless of which country the user sits in, so the cost model does not punish you for expanding. Consolidation work, tenant migrations, and new country setups are quoted as projects. Where coverage outside New Zealand business hours is required, that is priced explicitly rather than hidden in a service level nobody reads.
WHERE TO START
The services that matter most here.
FAQ
Questions from your sector
01Can one IT provider support offices in several countries?
For most of what an organisation needs, yes, because the work is overwhelmingly remote and the platforms are global. What genuinely needs local presence is hands-on work: a device that has to be touched, a new office fit-out, or a network fault at a site. We handle that through partners in-country under our management, so you keep one relationship and one standard rather than negotiating a different arrangement per market.
02How do we work out where our data actually lives?
System by system, and it takes less time than people expect. For each platform: which region hosts it, where the backups and replicas sit, who administers it and from which country, and what the contract says. The result is usually a few surprises, most often in smaller tools nobody reviewed. Assembling it once and keeping it current is far cheaper than reconstructing it when a customer asks.
03We have two Microsoft 365 tenancies after an acquisition. Should we merge them?
Usually yes, eventually, but not immediately. Running two for a period is normal and often sensible, since a rushed merge is disruptive and a merge before the businesses have actually integrated solves a problem you do not yet have. What should happen early is cross-tenant collaboration so people can work together, and one identity standard so onboarding and offboarding are consistent. The full merge follows when the business case is real.
04Does supporting multiple time zones cost significantly more?
It depends on what you actually need. Extended coverage for genuine outages is a modest step up. Full follow-the-sun coverage for every request is a different proposition. Most organisations we work with need the first and not the second, and it is worth being honest about which before paying for the wrong one.
05Our head office is in New Zealand but most of our staff are not. Does that change anything?
It changes where your obligations come from and where your coverage needs to be. Your New Zealand entity carries Privacy Act responsibilities for personal information it sends overseas, and each jurisdiction your staff sit in may bring employment, privacy, and tax considerations of its own. On the technology side it mostly means the design should stop assuming head office is the centre, because for your users it is not.
06Should our data stay in New Zealand?
Sometimes, and it is worth establishing which of your obligations are actual rather than assumed. New Zealand law does not generally mandate onshore storage, and the stricter requirements usually come from a customer contract, a government requirement, or a sector expectation. Where onshore hosting genuinely is required, we deliver it through sovereign cloud and can evidence it properly.
Start with the map.
What you run, where it sits, and who supports it, country by country. Almost nobody has that, and everything else follows from it.
← All industries