Move to Microsoft 365 without breaking your business.
We have migrated Pacific organisations from Google Workspace, on-premises Exchange and legacy mail platforms. The work happens out of hours; your team keeps working throughout; every phase up to cutover is reversible. The week after cutover is the natural time to harden — and we scope both engagements together so the security baseline lands while everyone is still in re-login mode anyway.
Most migration pain comes from the same four mistakes.
Migration is a well-understood operation — the technical mechanics have been the same for a decade. What differentiates a smooth project from a painful one is rarely the tooling. It is the discovery work, the pre-staging discipline, and the willingness to keep a rollback path open until the very last step. The migrations that go wrong tend to share the same handful of failure patterns.
Common ways migrations go sideways:
-
The big-bang weekend that runs late
Cutover scheduled for Friday night, half the mailboxes still syncing by Monday morning, staff arrive to find Outlook prompting for credentials they don't have. The recoverable version of this is uncomfortable; the unrecoverable version costs trust.
-
Identity left in two places
Mail moved but identity stayed on the old directory — passwords don't sync, MFA isn't enforced, conditional access can't apply because Entra ID doesn't yet own the user. Months pass; the security baseline never lands.
-
Shared drives that weren't fully scoped
Pre-migration discovery missed a Google Shared Drive that turned out to be where Finance keeps half its working files. Two days post-cutover, somebody asks where the 2024 audit folder went.
-
No hypercare window
Cutover completes, the migration consultant moves to the next project, and your team is left to file tickets through a generic support channel for the next two weeks while password resets, calendar share repairs and mobile mail config issues stack up.
Discovery, pre-stage, cutover, hypercare — in that order, with a rollback path open the whole way.
Six phases, none of them new ground. The discipline is in completing each phase before moving to the next, and in carrying the rollback path through every step until cutover is fully complete. Every project we run uses the same framework regardless of scale — what changes is the time spent in each phase, not the phases themselves.
-
Discovery and scope
Inventory the existing environment — mailbox count, mailbox sizes, shared mailboxes, distribution lists, calendars, Google Shared Drives or on-prem file shares, OneDrive footprint, Teams or Slack workloads, identity sources, and any third-party tools that hook into mail (CRMs, ticketing, marketing platforms). The findings shape the cutover plan; nothing kicks off without them.
-
Pre-stage and configure
Provision the Microsoft 365 tenant, configure DNS records that don't disrupt active mail (autodiscover, SPF, DKIM where applicable), provision identities, set up Entra ID with MFA and Conditional Access policies, and seed mailboxes with delta sync from the source environment so cutover only has to move a small final delta.
-
Cutover
Scheduled out of hours, typically a Friday evening or weekend. Final delta sync, MX record swap, identity provider cutover, and validation across a representative set of users. Mobile mail reconnects automatically for most users; the rest get a documented 30-second reconfig.
-
Hypercare
Two weeks of dedicated post-cutover support. Daily standup with your team, every ticket triaged inside an hour, mobile reconfiguration, shared-mailbox permission tuning, delegate access verification. After hypercare, the relationship moves into managed service or you take it back internal.
-
Hardening (recommended)
Most migrations are immediately followed by a Microsoft 365 Hardening engagement — activating Conditional Access, MFA enforcement, Defender for Business, Intune device compliance and anti-phishing. The week after cutover is the natural time because users are already through the Outlook re-login pain.
-
Reversibility
Until the final cutover step, every phase is reversible — source mail keeps flowing, source identity keeps authenticating. Even at cutover, the rollback path is documented and rehearsed. We do not run cutovers that we cannot back out of.
Source environments we migrate from.
Each source platform has its own quirks, and the cutover plan looks different in each case. The grid below covers the migrations we run most often in Pacific markets.
-
Google Workspace
Gmail, Calendar, Drive (including Shared Drives), Contacts, Groups. Drive-to-SharePoint or Drive-to-OneDrive mapping decided per workspace based on how the team actually used the source. Coexistence supported during the migration window so the calendars stay aligned.
-
On-premises Exchange
Exchange 2013, 2016 and 2019 to Exchange Online. Hybrid (recommended for over ~50 mailboxes) keeps source and destination synced and lets you migrate users in batches. Cutover (under ~50 mailboxes) moves the whole environment in a single weekend window.
-
Legacy IMAP / POP
Older mail hosts (cPanel, generic ISP mail, Zimbra, Roundcube) migrated via IMAP. Email moves; calendar, contacts and rules typically don't — addressed by separate export-import paths during pre-stage.
-
Tenant-to-tenant
Cross-tenant migrations after acquisitions, divestitures, rebrands or splits. Coexistence supported throughout (calendar free-busy across tenants, shared distribution lists, cross-tenant Teams), with a defined cutover for identity and mail when the deal closes.
Migration and hardening land cleanest when they happen together.
The week after a cutover is the perfect time to activate the security controls Microsoft 365 Business Premium and Enterprise SKUs include — Conditional Access, MFA enforcement, Defender for Business, Intune device compliance, anti-phishing. Users are already through the Outlook re-login pain; one extra MFA prompt at the same time is the cleanest moment to introduce it. We typically scope migration and hardening together as a single project so the security baseline lands with the new tenant rather than being deferred.
See Microsoft 365 HardeningFrequently asked questions.
The questions South Pacific decision-makers ask most often before they engage on a Microsoft 365 migration.
How long does a Microsoft 365 migration typically take?
For a small business under 50 mailboxes migrating from Google Workspace or a legacy mail host, the full project from discovery to end of hypercare runs four to six weeks. Larger organisations (50 to 500 users) on hybrid Exchange typically plan eight to twelve weeks because users are migrated in batches and there are usually more integrated systems to coordinate. The cutover step itself — the part where mail and identity actually move — is normally a single weekend window for cutover migrations, or a series of nightly batches over two to three weeks for staged or hybrid migrations.
Will our team lose access to email during the migration?
No. Every migration we run is designed so users keep working throughout. During pre-stage we synchronise mailboxes from the source to Microsoft 365 in the background, so on cutover night only the final delta needs to move. Mail keeps flowing on the source environment up to the cutover moment, then keeps flowing on Microsoft 365 immediately after. Outlook reconnects automatically for most users; the rest get a brief documented reconfig that takes under a minute. Mobile mail reconnects automatically in most cases.
What happens to existing emails, calendars and files when we migrate?
Emails, calendars, contacts and rules move with the mailbox to Microsoft 365 — full mailbox content, including the years of historical mail. Files migrate separately, depending on where they live: Google Drive content moves to OneDrive (personal files) and SharePoint (Shared Drives) with a mapping agreed during discovery; on-prem file shares can move to SharePoint or stay on-prem with managed sync if there's a reason. Folder structure, ownership and sharing permissions are preserved where the destination supports them; anywhere they don't translate cleanly, we flag it during discovery so the team isn't surprised post-cutover.
Can we migrate from Google Workspace without losing Shared Drives?
Yes. Google Shared Drives are migrated to SharePoint sites — typically one SharePoint site per Shared Drive — with the team membership translated to SharePoint permissions. Folder structure and file metadata are preserved. The piece that needs care is link rewriting: if your team has Google Drive URLs pasted into documents, emails or third-party tools, those won't auto-rewrite. Discovery includes auditing the most-trafficked Shared Drives for embedded links and either rewriting them as part of cutover or leaving Google Drive accessible read-only for a defined window so the links continue to resolve.
Should we migrate to Microsoft 365 before or after hardening the security baseline?
Migrate first, harden immediately after — usually within the first week of hypercare. Hardening before migration adds value only if your existing tenant has been used for some time; if you're greenfield-migrating to a fresh tenant, the security baseline should be configured as part of the pre-stage step so users land in a properly secured environment from day one. Either way, the Microsoft 365 Hardening engagement (Conditional Access, MFA enforcement, Defender for Business, Intune device compliance, anti-phishing) is the natural successor to migration and we typically scope them together in a single statement of work.
What is the difference between cutover, staged and hybrid migration?
Cutover migration moves the entire environment in a single weekend window — suited to organisations under about 50 mailboxes where the source environment can be retired immediately. Staged migration moves users in batches over several weeks, useful when mailboxes are large or when the team can only absorb a limited number of cutover users per night. Hybrid migration (specific to Exchange) keeps the source and destination synchronised over an extended coexistence period, with users moved individually; recommended for over 50 Exchange mailboxes or for organisations that need a long parallel-run window. We pick the right approach during discovery rather than defaulting to one — the wrong choice for a given environment is the biggest single cause of migration pain.
What does a Microsoft 365 migration cost?
Migrations are quoted as a fixed fee based on the user count, source environment, complexity of the file-share migration and whether hardening is bundled. A small-business Google Workspace migration of 20 to 30 users typically lands in a few thousand New Zealand dollars depending on scope; a 200-user hybrid Exchange migration with file-share moves and hardening is a materially larger engagement. The CSP licence cost (Microsoft 365 subscriptions themselves) is a separate ongoing line item not part of the migration fee. We scope every migration before quoting so there are no surprises at invoice time.
Plan your Microsoft 365 migration.
A short scoping call gets you a fixed-fee migration plan with a defined cutover window and a hardening package scoped alongside.