Microsoft 365 ↔ Google Workspace · any direction

Nothing left behind.
Precisely.

Deletions, moves and edits on the source are mirrored to the destination on the next delta pass — so two live tenants never drift apart mid-migration, and you can prove afterwards that nothing was lost.

Example runsample data
Sync throughput
118items/sec
Worker nodes
12/12
Batch 04 — global progress89.8%
INITDELTA_PASS_3SWEEP_CLEAN
a.whitfield@acmecorp.co.nz24/sSYNCING
j.reddy@acmecorp.co.nz30/sSYNCING
shared.accounts@acmecorp17/sDELTA
m.tuilagi@acmecorp.co.nzDONE
p.novak@acmecorp.co.nz28/sSYNCING
QUEUE_DEPTH 36 · RETRY 0 · THROTTLE_EVENTS 2

Orchestration

§01 — how a migration runs
01 / DISCOVER
Read-only inventory

Enumerate mailboxes, drives, sites and teams — sizes and item counts — before anything moves. Discovery costs nothing.

02 / SEED
Bulk first pass

The long copy runs at full rate while everybody carries on working in the source.

03 / DELTA
Continuous mirror

Creates, moves, edits and deletions on the source are reconciled to the destination on the next pass.

04 / PROVE
Reconcile and report

A per-item report naming what landed, what did not, and why — not a percentage and a shrug.

What moves

§02 — the four workloads
MAIL
Mailboxes
per mailbox

Mail, calendars and personal contacts, with inbox rules rewritten to point at the folders they moved to and out-of-office replies carried across. Shared, resource and archive mailboxes count as one unit each, at the same rate.

ONEDRIVE
Personal files
per user

Each person's own files with their version history and original dates intact — not a flat copy stamped with the date of the migration.

SHAREPOINT
Site libraries
per GB

Document libraries, chosen one at a time, with version history and source timestamps. Permissions and sharing links are reported rather than copied, deliberately: a new tenant is better designed than inherited, and the report is what you design from.

TEAMS
Channel conversations
per team

Messages arrive as messages — original authors, original dates, replies still threaded — including from people who have already left and have no account at the destination. Microsoft does not permit history to be written into private or shared channels by anyone, so those arrive as a readable archive in the channel’s own Files tab, where exactly its members can open it. Left behind entirely is the usual alternative.

System stack

§03 — what it is built on
Full-lifecycle delta

Other tools call it a delta when new mail arrives. Every state change is reconciled — including deletions, which is what keeps two live tenants identical rather than merely similar.

Cutover survival

Object IDs are stored beside the address, so a domain transfer part-way through a job does not orphan the mailbox. The job keeps running.

Official APIs only

Microsoft Graph and the Gmail API, with narrowly scoped application permissions. No legacy EWS, no basic auth, nothing waiting to be deprecated out from under you.

More than the messages

Personal contacts, inbox rules and out-of-office replies cross with the mailbox — rules rewritten to point at the folders they moved to. Files keep their version history and their original dates. What genuinely cannot follow, like Full Access grants or a private channel’s message history, is inventoried, or carried across in the closest form the platform allows, and named either way — rather than discovered by a user on Monday morning.

Security posture

§04 — the trust boundary
One side or two

Control both tenants and you connect both yourself, start to finish. Control one, and the other organisation attaches its own side without either of you handing over credentials.

Split credentials

In that two-organisation model, each side registers and holds its own credentials. Neither ever sees the other’s client secret or tenant ID — only a display name.

The source is only read

Nothing in the source is created, changed or deleted — every pass reads from it and writes to the destination. A Microsoft 365 source is asked for read and export permissions only; Google’s Calendar and Drive scopes have no read-only form, so that grant is wider than what we use.

Scoped guest access

Invite a client’s IT contact to watch a single batch. They see that batch and nothing else — no other client, no connections, no billing.

how the boundary works

Transparent licensing

§05 — what it costs
Standard rate
NZ$16.00/ unit · ≈ US$9.30

That is the price for one unit, and the most you will ever pay per unit — larger volumes only go down from here. A unit is one mailbox, or one user’s drive. Shared, resource and archive mailboxes each count as one, at the same rate.

1–49 unitsNZ$16.00
50–199 units9%NZ$14.50
200–499 units17%NZ$13.25
500–999 units25%NZ$12.00
1000+ unitstalk to us

One rate applies to the whole batch — 150 units bills every unit at the 50–199 rate. NZ customers add 15% GST. Overseas customers are zero-rated. SharePoint content is charged separately, per GB, and Teams per team — ask for a rate.

full price list
Estimate — mailboxes + drives
Rate applied
NZ$14.50
Volume band
50–199
Total, excl. GST
NZ$870.00

US$506.45 · plus NZ$130.50 GST for NZ customers. USD is indicative; billing is in NZD.