Microsoft 365 tenant-to-tenant migration is one of the most technically demanding tasks in IT administration — and one of the most common. Mergers, acquisitions, company rebranding, domain consolidations, and divestitures all drive the need to move users, mailboxes, and data from one Microsoft 365 tenant to another. The migration tools — BitTitan MigrationWiz, Quest On Demand Migration, Microsoft's own cross-tenant migration feature — handle the mailbox data. None of them protect inbound email during the DNS propagation window. That gap is exactly what StrataMail fills.
The Problem: DNS Propagation During Cutover
Every Microsoft 365 tenant-to-tenant migration requires changing the domain's MX records as part of the cutover — pointing inbound mail from the old tenant's mail routing to the new tenant's. The problem is that DNS propagation is not instantaneous. Depending on the domain's TTL settings and how various DNS resolvers cache records, propagation can take anywhere from 15 minutes to 48 hours.
During that propagation window, inbound email behavior is unpredictable. Different senders resolve the domain differently depending on which DNS resolver their mail server uses and when that resolver last refreshed its cache. Mail may route to the old tenant, the new tenant, or neither. Mail routed to the old tenant after cutover may be rejected, deferred, or lost if the old tenant is already decommissioned. Mail routed to neither goes nowhere and eventually bounces.
What Migration Tools Don't Cover
BitTitan MigrationWiz, Quest On Demand Migration, and Microsoft's native cross-tenant migration feature are all designed to move mailbox data — calendar items, contacts, historical email, folder structures — from one tenant to another. They handle the data movement problem thoroughly.
What they do not handle is the live inbound mail protection problem during the DNS cutover window. None of them act as an MX receiver, queue new inbound messages, or protect against the DNS propagation race condition. This is not a flaw in these tools — it is simply outside their scope. But it means every Microsoft 365 tenant migration has an unprotected window unless something else is put in place.
How StrataMail Solves It
StrataMail is provisioned before the migration cutover begins — typically 24 to 48 hours in advance — and configured as a secondary MX record for the domain being migrated. During the migration window, StrataMail acts as a neutral catch-all MX that accepts inbound mail regardless of which tenant DNS resolvers are currently pointing to.
- Senders resolving the old MX still have a fallback — StrataMail is configured at a lower priority that catches anything the old tenant rejects or defers
- Senders resolving the new MX route normally to the new tenant
- Senders resolving neither — or catching StrataMail as the only available MX — have their mail accepted and queued by StrataMail
- All mail captured by StrataMail during the window is held for up to 30 days and released to the new tenant once the cutover stabilizes, retried every 5 minutes until delivered
The admin dashboard shows queue depth, delivery status, and event log in real time throughout the migration window. The IT team has full visibility into what mail arrived, where it went, and what is still queued — at all times during the cutover.
Dual Delivery During the Migration Window
StrataMail's dual delivery architecture means inbound mail captured during the migration window is simultaneously stored locally — in the continuity mailbox — and queued for relay to the new tenant. This gives users access to email throughout the migration through StrataMail's branded webmail portal.
Users who would otherwise lose email access during the cutover window can sign in to the continuity portal and continue reading and replying normally. They are never locked out of email — even if the old tenant is decommissioned before the new tenant's MX records have fully propagated. This addresses one of the most common migration complaints from end users: the hours or days where email simply does not work during a live cutover.
What the Engagement Includes
Microsoft 365 tenant migration email continuity is a professional services engagement, not a standard platform subscription. It begins with a paid assessment and typically runs across four phases:
| Phase | What We Do | Timing |
|---|---|---|
| Assessment & Scoping | Review migration plan, DNS configuration, mailbox count, cutover schedule. Deliver written migration brief and StrataMail configuration plan. | 1–2 weeks before cutover |
| Pre-Provisioning | Configure StrataMail for the domain(s), test MX routing, verify dual delivery to continuity webmail, confirm queue visibility in admin dashboard. | 24–48 hours before cutover |
| Cutover Support | Monitor StrataMail throughout the migration window, verify queue health, coordinate with the migration team on DNS timing and relay release. | During cutover window |
| Release & Deprovision | Verify all queued mail delivered to new tenant. Remove StrataMail from MX configuration. Final queue and event log review. | After cutover stabilizes |
Pricing
The engagement starts with a flat-fee assessment covering up to 5 hours of engineering time, with a written migration plan and cutover schedule delivered at the end. The assessment fee is credited in full toward the execution engagement if you proceed. Execution is priced per 100 mailboxes, and any work beyond the agreed scope is billed hourly at business-hours, after-hours, or emergency rates. Current prices for every line are published on the Microsoft 365 Migration Email Continuity page at Infinity Data Center.
StrataMail vs. BitTitan / Quest
StrataMail is not a replacement for BitTitan MigrationWiz, Quest On Demand Migration, or Microsoft's native cross-tenant migration tools. It is the safety net underneath them. Most migration projects use StrataMail alongside their existing migration tool — StrataMail handles the inbound mail protection problem, the migration tool handles the mailbox data movement problem.
If you are already scoped with BitTitan or Quest for an upcoming migration, adding StrataMail's assessment engagement gives you confidence that inbound mail is protected during the DNS propagation window — regardless of how long propagation takes, and regardless of what happens to the old tenant during cutover. MSPs can also provision migration coverage through the StrataMail partner program and bill their clients directly.