Office 365 Tenant-to-Tenant Cutover Email Migration — Microsoft 365 Mailbox Move
Office 365 / Microsoft 365 Tenant-to-Tenant Cutover Email Migration moves an organization's email environment from one Microsoft 365 tenant to another during mergers, acquisitions, rebranding, restructuring, tenant consolidation, company splits, or divestitures. The service covers mailboxes — emails, folders, calendars, contacts — plus mailbox-enabled users, distribution groups, permissions, DNS/MX and domain transition, and post-migration verification. Where both tenants meet Microsoft's requirements, IT Partner uses Exchange Online's native cross-tenant mailbox migration (with the required per-user Cross-Tenant User Data Migration licenses); otherwise established third-party migration tools (such as BitTitan or AvePoint) carry the data. Priced at $27.00 per mailbox over a 30-day engagement.
What this engagement is
This service moves an organization's email environment from one Microsoft 365 tenant to another using a cutover migration approach: historical data is pre-staged in advance, then mail flow switches to the destination tenant in a planned window — typically a weekend or overnight — followed by a final synchronization. Two migration paths exist, and IT Partner selects per project. Exchange Online's native cross-tenant mailbox migration moves mailboxes between tenants through Microsoft's Mailbox Replication Service; it requires cross-tenant setup (application registrations and organization relationships) and a Cross-Tenant User Data Migration add-on license per migrating user. Microsoft has also released a Cross-Tenant Orchestrated User Data Migration that bundles Exchange, OneDrive, and Teams chats in one workflow — in public preview since December 2025, and treated with appropriate caution. Where the native path's prerequisites or preview status do not fit, established third-party migration tools (such as BitTitan or AvePoint) carry the mailbox data with integrity verification. Either way, IT Partner handles planning and execution end to end: identity preparation, resource export/import, pre-stage synchronization, DNS configuration, permissions, cutover, and post-migration checks. IT Partner has been a Microsoft partner since 2006 and currently holds Microsoft Solutions Partner designations, with delivery expertise across Exchange Online and Microsoft Entra ID.
Success criteria
What you receive
How the work unfolds
Discovery of the source environment and pre-migration health checks.
Creating users in the target tenant or configuring AD Connect tools.
Migrating historical data older than 30 days before the cutover date.
Pointing MX records to the new tenant followed by the final data sync.
Verifying mail flow and assisting users with Outlook and mobile settings.
Prerequisites
Who does what
IT Partner
- Handle the end-to-end process of moving email services.
- Full Mailbox Migration including emails, folders, calendars, and contacts.
- Resource Export/Import of mailbox-enabled users, distribution groups, and contacts.
- Pre-stage Migration to move historical data in advance and minimize the final cutover window.
- DNS Configuration to manage MX records and domain transitions seamlessly across tenants.
- Security & Permissions migration for inbox rules, delegated access, and mailbox settings.
- Discovery of the source environment and pre-migration health checks.
- Creating users in the target tenant or configuring AD Connect tools.
- Migrating historical data older than 30 days before the cutover date.
- Pointing MX records to the new tenant followed by the final data sync.
- Verifying mail flow and assisting users with Outlook and mobile settings.
- Post-migration support to resolve any connectivity or desktop sync issues.
- End-to-end support: scoping → design → deployment → training.
Your team
- Assign a business owner, technical contact, and cutover approver who can make timely decisions during planning and the cutover window.
- Provide or approve Global Admin-level access, Privileged Identity Management activation, MFA approvals, or delegated partner access for both source and destination Microsoft 365 tenants as required for the engagement.
- Provide the migration inventory, including users, shared mailboxes, resource mailboxes, aliases, distribution groups, contacts, mailbox sizes, VIP users, and any exclusions.
- Confirm user identity mapping between source and destination tenants, including UPNs, primary SMTP addresses, aliases, and any planned domain or branding changes.
- Ensure required Microsoft 365 licensing is available and assigned in the destination tenant before migration and cutover activities that require active mailboxes.
- Provide access to DNS hosting or the DNS registrar, or have an authorized DNS administrator available to make approved MX, domain-transition, Autodiscover, and related mail-flow changes included in the final migration plan during the cutover window.
- Coordinate internal communications so users know the migration schedule, expected impact, sign-in changes, Outlook/mobile reconfiguration steps, and support process.
- Support endpoint readiness by ensuring users can sign in to Microsoft 365, update passwords or MFA methods if required, and make Outlook/mobile devices available for post-cutover validation.
- Provide source-environment information needed for discovery, such as accepted domains, Exchange configuration, mail flow connectors, transport rules, shared mailbox ownership, and delegated access requirements.
- Maintain any required business backups, legal hold, retention, compliance, or archive requirements that are outside the standard mailbox cutover scope unless separately included.
- Participate in validation after migration and provide timely feedback or sign-off for migrated mailboxes, mail flow, calendars, contacts, and user access.
What's not included
Limitations & technical notes
Frequently asked questions
What is Office 365 Tenant-to-Tenant Cutover Email Migration?
An IT Partner service that moves an organization's email environment from one Microsoft 365 tenant to another — commonly during mergers, acquisitions, rebranding, restructuring, tenant consolidation, company splits, or divestitures — with pre-staged data, a planned cutover, and post-migration verification.
How does email actually move between Microsoft 365 tenants?
Two ways. Exchange Online's native cross-tenant mailbox migration moves mailboxes through Microsoft's Mailbox Replication Service, after cross-tenant setup and with a Cross-Tenant User Data Migration add-on license per migrating user. Where those prerequisites do not fit, IT Partner uses established third-party migration tools (such as BitTitan or AvePoint). The path is selected during assessment and stated in the plan.
What does IT Partner migrate in this service?
Mailboxes with emails, folders, calendars, and contacts; mailbox-enabled users, distribution groups, and contacts (export/import); inbox rules, delegated access, and mailbox settings; folder structures, metadata, and permissions within the selected path's capabilities; and the MX/domain transition with post-migration mail-flow verification.
Is this a cutover migration or a staged migration?
Cutover: users switch to the destination tenant at a planned point, typically over a weekend or overnight. Historical mailbox data is pre-staged before the cutover date so the final window stays small. Organizations needing long-running coexistence should consider a staged approach, scoped separately.
How much does the migration cost, and how long does it take?
The service is priced at $27.00 per mailbox as a 30-day engagement, quoted in writing before work begins. Microsoft licensing — including Cross-Tenant User Data Migration add-on licenses where the native path is used — is purchased separately by the client.
What access is required before the migration can begin?
Global Admin-level access to both the source and destination Microsoft 365 tenants, so IT Partner can assess the environments, prepare identities, configure the migration, and manage the tenant-to-tenant mail flow changes.
How much downtime should we expect?
The design goal is minimal downtime: data is pre-staged, and the cutover runs over a weekend or overnight. The main risk window is domain transfer and DNS propagation, which varies by DNS provider and sender behavior — the plan sequences MX and domain moves to keep it short, but no zero-downtime guarantee is made.
Will calendars, contacts, permissions, and inbox rules be preserved?
Calendar appointments, recurring meetings, and contact lists are migrated, and folder structures, metadata, permissions, inbox rules, and delegated access are preserved within the capabilities of the selected migration path — the assessment states any path-specific limits before execution, and validation confirms the results.
What happens during the final cutover?
IT Partner points MX records to the destination tenant, sequences the domain transition (a domain can be verified in only one tenant at a time), runs the final data synchronization, and then verifies inbound and outbound mail flow in the destination tenant.
Will users need help reconfiguring Outlook or mobile devices after migration?
Usually yes — a tenant change means Outlook profiles and mobile accounts reconnect to the destination tenant. User assistance with Outlook and mobile settings is included, and post-migration support addresses connectivity and desktop sync issues during the validation window.
Does this service migrate OneDrive, SharePoint, or Teams content?
No — this is the email migration. OneDrive, SharePoint, Teams structure, and Teams private chats move under their own IT Partner services, typically sequenced with this one; Microsoft's orchestrated cross-tenant migration (in preview) can bundle Exchange, OneDrive, and Teams chats where its prerequisites fit, and that option is assessed per project.
What is not included in this migration service?
Non-Exchange workloads (OneDrive, SharePoint, Teams, Planner, Power Platform, Intune, Azure subscriptions), long-term tenant coexistence and cross-tenant GAL/free-busy sharing, identity consolidation beyond migration needs, public folders and third-party archives, large-scale desktop or device deployment, third-party application reconfiguration, licensing and registrar fees, security/compliance redesign, and custom training programs — each available as separate scope.