Clean · Before a Merger & tenant consolidation migration
Clean the data before it moves to the consolidated tenant, not after.
Carrying an unresolved mess into a new platform buys you the same problem at a higher price.
We profile the Microsoft 365 source, resolve what this specific route is known to break on, and agree the mapping decisions in writing. Then the migration runs once.
- Profiled before mapping
- Route-specific risks resolved first
- Decisions in writing
- One transfer, reconciled
Price cue, ex GST
From $2,500
Scope a pre-migration cleanup Or call 1300 652 280Cleanup can sit in front of a Merger & tenant consolidation migration we perform, in front of one your own team performs, or stand alone against your current environment. The deliverable is the same either way.
- Australian managed
- Delivered remotely
- Source data never deleted
- Verification report at sign-off
What gets resolved before a Merger & tenant consolidation migration runs
The sequence is deliberate. Profiling determines the decisions, the decisions determine the mapping, and the mapping determines what the migration is allowed to create.
- Identity reconciliation across every estate — the same person, one surviving account, decided individually
- Duplicate customer and supplier records across the two systems of record merged against agreed rules
- Overlapping SharePoint sites and Teams reviewed for merge, retain or archive
- Naming conventions reconciled before consolidation, not after, since renaming later is harder
- Licence position reviewed across all estates to stop paying twice
- Retention, legal hold and regulatory obligations from every entity established and preserved
What this route breaks on when nobody prepares
Two organisations are operating on two tenants and neither can see the other's calendars
The same person exists as two identities with two mailboxes
Domains are split across tenants and mail routing is unpredictable
Both estates have a system of record for the same customers
Licences are being paid for twice
A previous attempt merged files but left identity and permissions untouched
The proof you keep
The migration is verified against the cleaned source.
Cleanup and migration share one reconciliation: what the cleaned source held, what the destination accepted, and every item that did not make it with the reason why. Example format below.
Migration Verification Report
Cleaned source → the consolidated tenant · Example format
| Consolidation class | Cleaned source | In destination | Status |
|---|---|---|---|
| Tenants consolidated | 3 | 1 | Verified |
| Identities reconciled | 284 | 281 | 3 Accepted Exception |
| Mailboxes | 281 | 281 | Verified |
| SharePoint sites | 112 | 104 | 8 merged by agreement |
| Teams | 88 | 82 | 6 merged by agreement |
| Permission entries | 31,204 | 31,204 | Verified |
Accepted exceptions are itemised individually with a reason. Anything the destination cannot hold appears in the exclusions register before the migration, not as a surprise afterwards.
Free · About three minutes · No sales call required
Tell us what is moving to the consolidated tenant.
The route is already filled in. Add the volumes and whether history has to survive, and an engineer will come back with a range.
Questions about preparing this route
Why clean before the migration rather than after?
Because you pay twice otherwise, and the second time is harder. Data that arrives dirty has already been associated with the destination’s own structures — workflows, permissions, lifecycle stages, site hierarchies — so fixing it afterwards means unpicking those associations too. Cleaning at the source means the associations are built once, correctly.
What order should this happen in?
Identity first, always. Mail, files and CRM all attach to identity, so consolidating them before identity is settled means doing the work twice. The assessment produces a sequence, and the sequence is usually the most valuable thing in it.
Can we run on two tenants in the meantime?
Yes, and most organisations do for a period. Cross-tenant calendar sharing and directory sync make it workable. It is a bridge, not a destination — the cost of running two estates is mostly invisible and mostly larger than people expect.
Does cleanup delay the migration?
It usually shortens the migration and lengthens the preparation, and the total is normally lower. Volume reduction and pre-resolved mapping decisions both cut the cutover window, which is the part of a project that carries business risk.
Can you clean if someone else is doing the migration?
Yes, and it is a common arrangement. You receive the cleaned source, the mapping document and the exclusions register. Whoever performs the migration works from those. We do not need to be doing the move to do the preparation.
How is the cleanup itself verified?
A before-and-after count on every class of data touched, plus a list of everything deliberately excluded and why. A cleanup that cannot be quantified is indistinguishable from one that did not happen.