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.
Orchestration
§01 — how a migration runsMailboxes, drives and chats cost what you picked — per person, no surprises. SharePoint is billed per GB, so its content is measured and shown to you before a single byte moves.
The long copy runs at full rate while everybody carries on working in the source.
Creates, moves, edits and deletions on the source are reconciled to the destination on the next pass.
A per-item report naming what landed, what did not, and why — not a percentage and a shrug.
What moves
§02 — the 5 workloadsMail, calendar and contacts, still working at the other end.
what to expect →Everyone’s own files, with their version history and original dates.
what to expect →One-to-one and group chats, with their original authors.
what to expect →Document libraries, with version history and original dates.
what to expect →Conversations with their original authors, dates and threading.
what to expect →Design the destination
§03 — SharePoint designerA team site or a communication site, with its name, URL, owner and document library — then a nested folder tree of any depth, in the order you choose, with folder colours from SharePoint’s own palette.
Named roles with their members, each a person or an existing group. Every role gets read or write on a folder, never both. Folders you choose break inheritance from their parent and get their own SharePoint groups, which is what makes a designed structure hold its shape.
Provisioning creates the site, the library, the folders and the groups. Then map your existing content into the structure you designed — from SharePoint, a file system or another source — rather than copying the mess you had.
System stack
§04 — what it is built onOther 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.
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.
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.
Security posture
§05 — the trust boundaryControl 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.
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.
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.
Invite a client’s IT contact to watch a single migration. They see that migration and nothing else — no other client, no connections, no billing.
Transparent licensing
§06 — what it costsRates shown are the starting band and fall with volume — each workload on its own count. NZ customers add 15% GST. Overseas customers are zero-rated. Billing is in NZD; USD is indicative only (≈ US$9.00 per mailbox today).
see the full pricing≈ US$2,122.45 · plus NZ$567.00 GST for NZ customers. USD is indicative; billing is in NZD.
SharePoint Designer
§07 — a separate productNot a migration unit and not per user — one charge covers a design, and every later edit to it. One design builds one site, so a second site is a second design. Migration content is charged separately at the rates above.