Approved migration route
Merger & Tenant Consolidation Migration
Two companies. Two tenants. Two sets of data. One operating environment.
We plan the movement of identities, email, files and approved business data into the chosen target environment.
- Test migration
- Fixed scope
- Reconciliation
- Verification report
Price cue, ex GST
Assessment required
Get my migration scope Or call 1300 652 280Source totals against destination totals, every exception itemised, access revoked, acceptance signed.
How this migration runs
Every production migration passes the same gates. Nothing cuts over until a test migration has been run and the source and destination have been reconciled.
The full 17-gate method- 01–03Discover, secure access, confirm backup and rollback
- 04–06Scan the source, map it, clean what is agreed
- 07–09Test migration, reconcile counts, remediate exceptions
- 10–12Production migration, delta, cutover
- 13–15Validate, customer sign-off, revoke project access
- 16–17Apply retention rules, issue Verification Report
Questions people ask before this migration
What moves?
Identities, email, files and approved business data from both environments into the chosen target.
What does not move?
Anything the destination cannot hold, and anything the source cannot lawfully or technically export. Unsupported items are found during the source scan, recorded in the mapping and exclusions register before migration, and listed again in the Verification Report. Nothing is silently dropped.
How long does it take?
Most standard SME projects run two to six weeks from approved scope to sign-off. Volume, user count, permission complexity and your cutover constraints set the real schedule, which is fixed in the Statement of Work before work begins.
What access is required?
Administrative access to both the source and the destination, issued as project-specific credentials with a scheduled revocation date. Privileged credentials are held in an approved vault, never in email or chat, and access is removed at the end of the project.
What happens during cutover?
Cutover only runs after a successful test migration and a reconciliation of source against destination. We run the production transfer, capture a delta where the route supports it, switch mail flow or production processes, validate your critical workflows, revoke project access, then issue the Migration Verification Report for sign-off.