Keep email moving during a Microsoft 365 tenant migration
Moving a domain between Microsoft 365 tenants can require staged routing, temporary mail holding and a recovery plan. The right approach depends on how recipients are divided between the old and new tenants.
Request an Outage Readiness Assessment
Three migration arrangements
| Situation | Approach | What users experience |
|---|---|---|
| Short planned cutover | Hold accepted inbound mail with Backup MX; release when the target is ready | New incoming mail is delayed, not accessible in a queue-only service |
| Phased recipient migration | Route recipients individually to the appropriate tenant using an agreed gateway | Users remain on the tenant assigned for their migration stage |
| Users must continue working during cutover | Add independent StrataMail Email Continuity mailboxes for selected users | Prepared users can use separate continuity access while primary routing changes |
Illustrative staged migration
What we verify before migration
- Recipient ownership and acceptance in both tenants
- Inbound gateway, SPF, DKIM, DMARC and outbound sending design
- Fallback and rollback plan, message tracking, duplicate prevention and release order
- Critical-user access and recovery communications
Backup MX cannot fix an incorrect recipient map or a destination that permanently rejects a recipient. These issues must be addressed in the migration design.
Every deployment is engineered around your existing security gateway, mail provider, recipients and cutover schedule. Assessment and engineering are paid services. No public package price is quoted.
Next step
Talk to us about M365 migration continuity
Describe Your Challenge View Consulting Services
Tell us about your M365 migration continuity needs
Describe your situation and we will look into it and get back to you.
Describe Your Challenge Explore Consulting