Microsoft 365 Tenant-to-Tenant Cutover Email Migration — No Downtime or Bounced Email

This service plans, designs, and performs an email migration from one Microsoft 365 tenant to another, typically for mergers, acquisitions, or moves to a different geographic region. It is an advanced tenant-to-tenant cutover migration designed to avoid bounced emails, NDRs, and downtime for incoming mail during the domain transfer.

This service is for organizations moving Exchange Online email from a source Microsoft 365 tenant to a destination Microsoft 365 tenant. It is especially relevant for mergers, acquisitions, divestitures, tenant consolidations, or relocations where business email continuity during domain transfer is important.

IT Partner sets up proxy services to receive incoming email during the domain transfer, because the email domain cannot normally be active in two Microsoft 365 tenants at the same time. This approach is designed to prevent incoming message loss, bounced emails, and NDRs while the domain and MX records are moved to the destination tenant.

The service is designed to avoid downtime for incoming mail during the domain transfer, but mail receipt may be delayed for about 3–5 minutes depending on the volume of incoming emails. Users should also expect planned changes such as new Outlook profiles if they use the desktop version of Outlook.

The stated success criteria for this service include no incoming message loss during the migration process. IT Partner uses proxy services during the domain transfer to receive incoming mail, but the exact behavior should still be confirmed during planning based on the customer’s environment and mail flow requirements.

The service includes exporting mail-enabled resources from the source tenant, importing resources into the destination tenant, pre-staging older email, setting up proxy services for incoming mail during domain transfer, performing the final mailbox migration, and changing required domain zone records. It also includes a project closeout report with final project status, acceptance evidence, outstanding issues if any, and final budget information.

The service includes a pre-stage migration for emails and email folders older than 30 days, followed by a final mailbox migration. The final migration includes calendars, contacts, rules, and other mailbox data within the stated scope of the service.

Yes, IT Partner exports resources from the source tenant, including mailbox-enabled users, contacts, groups, and similar mail-enabled resources. These resources are then imported to the destination tenant using AD Connect or CSV import, depending on the agreed migration approach.

The actual plan may vary depending on the customer’s needs, environment readiness, mailbox sizes, DNS access, and availability of required administrative access.

You must provide global admin level access to both the source Microsoft 365 tenant and the destination Microsoft 365 tenant. The destination tenant must have available Exchange Online licenses, and you must also have access to the DNS zone for the email domain being migrated.

The engagement typically includes a kickoff meeting, a source system health check, user creation or AD Connect configuration, migration start, migration verification, MX record change to the new Microsoft 365 tenant, final email migration, and post-migration tasks. These milestones may be adjusted based on the customer’s specific requirements.

IT Partner changes records in domain zones to accommodate the migration needs as part of its stated responsibilities, but the client must provide access to the email domain DNS zone and perform internal and external DNS changes as required. If a third-party DNS provider is involved, the client is responsible for coordinating that vendor and schedule.

IT Partner is responsible for exporting source tenant resources, importing resources to the destination tenant via AD Connect or CSV import, pre-staging older email, setting up proxy services, performing the final mailbox migration, and changing domain zone records needed for the migration. IT Partner also verifies migration results and provides a project closeout report.

The client must provide a dedicated point of contact, coordinate outside vendors, provide required admin and DNS access, configure network equipment if needed, and inform users about upcoming changes. The client is also responsible for deploying desktop email software if used, assisting with high-risk user identification, and recreating Outlook profiles on client workstations when the desktop version of Outlook is used.

No, informing users about upcoming changes is not included in the service. The client is responsible for user communications and for providing users with the necessary information about migration-related changes.

No, desktop software settings are not included, and the client is responsible for recreating new Outlook profiles on workstations if the desktop version of Outlook is used. IT Partner’s migration scope focuses on the tenant-to-tenant email service migration rather than workstation configuration.

No, migration of corporate documents to SharePoint Online is not included in this service. IT Partner notes that SharePoint Online document migration can be added as an additional service.

After completion, IT Partner performs post-migration tasks and provides a project closeout report. The report indicates final project status, evidence matching the acceptance criteria, any outstanding issues, and the final budget.

This advanced service includes proxy services to receive incoming email during domain transfer, because it is designed to avoid bounced messages, NDRs, and incoming mail downtime. If short-term downtime and the possibility of losing some emails is acceptable, IT Partner offers a separate Microsoft 365 Tenant-to-Tenant Cutover Email Migration service.