From read-only assessment to signed reconciliation
Five phases. You can stop after the assessment — it costs nothing and writes nothing.
- 01
Assessment
Read-only discovery against both tenants. Nothing is written, so it's safe to run before any commercial commitment.
- Mailbox, archive, OneDrive, SharePoint, Groups and Teams inventory
- Sizes and item counts per object, with a throughput projection
- Risk findings — oversized items, unmapped identities, missing targets
- 02
Mapping and scope
Decide what moves and where it lands. Source objects are matched to destination identities before anything copies.
- Automatic matching by UPN, with manual override where identities differ
- Optional auto-provisioning of destination users that don't exist yet
- Batches you control — pilot a handful before committing the estate
- 03
Migration
Bulk copy runs under Exchange's migration throttle budgets. Passes resume rather than restart, so an interruption costs a scan, not a re-copy.
- Idempotent by design — re-running skips what's already in the destination
- Large items routed through a chunked upload path automatically
- Throttling is honoured, not fought: pauses are expected, not failures
- 04
Coexistence and delta sync
Scheduled passes copy what has arrived since the last successful run, so the destination stays current while you plan cutover.
- Runs on a schedule you set — six hours by default
- Only fetches new mail, so it stays fast as the estate grows
- A full re-sync recovers anything historical that delta wouldn't revisit
- 05
Verification and cutover
Completeness is established by comparing messages, not counts, and recorded in a signed report.
- Message-ID set difference across primary, archive and recoverable items
- Explicit list of anything present at source and absent at destination
- Domain cutover orchestration with a documented rollback path
Run the assessment before you decide
It's read-only, and it tells you the real size of the job — including the archives that usually double it.