Cross Tenant Mailbox Migration: A Scoping Guide for IT Teams
Cross tenant mailbox migration is one of the most crucial processes in mergers, acquisitions, consolidation of tenants, and corporate restructuring operations. But migrating mailboxes from Microsoft 365 or Google Workspace accounts to another tenant includes a lot more than just transferring email data. User accounts, permissions, calendars, contacts, compliance policies, and shared mailboxes need to be properly scoped as well.
This blog post provides information about the most important dependencies that should be considered during the scoping process of Outlook to Outlook and Gmail to Gmail cross tenant mailbox migrations.
Key Takeaways:
Why Scoping Is Important for Cross Tenant Mailbox Migrations
Many business leaders think that scoping is the same as scheduling the migration process. It is not. Scheduling deals with setting timeframes and deadlines for moving particular mailboxes, whereas scoping deals with what needs to be done before the migration process can begin.
Each enterprise tenant has its own peculiarities. Some companies have tens of thousands of standard user mailboxes; other companies use a lot of shared, archive, and delegate mailboxes. Not understanding those dependencies, IT departments will get incorrect migration estimations and possible problems during the migration process.
A well-executed scoping assessment typically evaluates the following areas:
| Scoping Area | Why It Matters |
|---|---|
| Identity Infrastructure | Ensures users can authenticate after migration |
| Mailbox Inventory | Determines project size and migration batches |
| Permissions | Preserves delegated and shared mailbox access |
| Compliance | Maintains retention and legal hold requirements |
| Collaboration | Prevents disruption to calendars and shared resources |
Rather than treating every mailbox equally, enterprise IT teams should classify users based on mailbox complexity, business criticality, and migration risk. This allows larger projects to be executed in manageable phases instead of attempting a single large-scale cutover.
Scoping an Outlook-to-Outlook Cross Tenant Mailbox Migration
Migrating mailbox from Office 365 tenant to another require much more than just Exchange Online. User mailboxes are tightly coupled with Microsoft Entra ID, Microsoft Teams, SharePoint Online, OneDrive, Microsoft 365 Groups, and organizational security policies. Therefore, an Exchange mailbox should not be analyzed independently from these components.
Exchange Online Environment Assessment
The initial task is to understand how identities are configured within both tenants. This includes reviewing UPNs, SMTP addresses, accepted domains, proxy addresses, synchronization mechanisms, and other identity settings before planning the migration.
Organizations using hybrid Exchange environments should also determine whether user identities are managed through on-premises Active Directory or Microsoft Entra Connect. This directly affects mailbox provisioning, authentication, and mail flow after migration.
Validating identity configurations early help prevent common issues such as duplicate SMTP addresses, failed mailbox provisioning, and authentication conflicts during cutover.
In addition to identity assessment, IT teams should perform a complete inventory of the Exchange Online environment. At a minimum, the assessment should include:
- Total mailbox count
- Mailbox size distribution
- Archive mailbox sizes
- Shared mailboxes
- Litigation holds status
Focus on Mailbox Distribution Instead of Number of Users
Most companies use user numbers to gauge the migration difficulty. It should be noted that mailbox size has a more significant effect on the migration schedule than mailbox count.
For instance, it may take more effort to migrate 500 users with 150 GB mailboxes than to migrate 2,000 users with 8 GB mailboxes.
Mailbox distribution analysis will help you calculate migration batches, required bandwidth, and project length.
| Average Mailbox Size | Planning Consideration |
|---|---|
| Under 20 GB | Standard migration batches |
| 20–100 GB | Extended migration windows |
| Over 100 GB | Dedicated migration scheduling |
Large mailboxes also increase the likelihood of API throttling and require additional delta synchronization before production cutover.
Identify Dependence on Shared Mailboxes
Shared mailboxes are one of the most important elements in enterprise mailbox migrations.
Departments like Finance, Human Resources, Legal, and Customer Service may use shared mailboxes on a regular basis. While the migration of mailbox data is quite easy, the recreation of delegations will require some preparation.
The IT team should determine who has permissions of Full Access, Send As, and Send on Behalf type before migration starts. All these delegations need to be recreated immediately after the migration, to not interrupt communications with customers and internal processes.
Review Compliance Needs
Most companies adhere to regulations like GDPR, FINRA, SEC, ISO 27001, and SOC 2; thus, compliance is one of the crucial considerations in cross-tenant mailbox migrations. Prior to any migration process, it is essential to analyze Litigation Hold, eDiscovery, retention policies and labels, email journaling, Google Vault retention, and legal holds to ensure that protected mailboxes remain compliant. It is important to take into account such considerations at the very beginning of the process.
Scoping a Gmail-to-Gmail Cross Tenant Mailbox Migration
Migrations for Google Workspace tenants involve a different approach when compared to Microsoft 365 tenant migrations. The overall goal of moving mailbox data between tenants is the same, but the architecture and services involved are different.
It is essential to consider organizational structure, labeling, groups, aliases, and policies while performing a successful Gmail to Gmail migration.
Consider Google Workspace Architecture
Google Workspace groups users into Organizational Units (OUs), groups, domains, and various policies.
Before beginning the migration process, admins should assess how users are structured in the source tenant and whether the destination tenant has the same structure. Differences in Organizational Units or secondary domains can affect policy inheritance, user provisioning, and administrative controls after migration.
In case multiple acquired organizations are being migrated, IT teams should assess the naming convention, aliases, and domain structure to avoid user account conflicts.
Understand Gmail’s Label-Based Structure
Unlike Microsoft Outlook, Gmail does not group emails in folders.
Instead, Gmail labels are assigned to emails, making it possible for one email to belong to multiple labels at once.
Organizations relying on legacy IMAP migration methods often discover that labels are converted into folders, changing how users access email after migration.
API-based migration preserves native Gmail label hierarchies because labels, conversations, and email states remain the same.
In case of enterprises with sophisticated mailboxes organization, this makes a real difference for users experience after migration.
Google Workspace APIs Evaluation
Migration performance in Google Workspace depends greatly on the way API works instead of pure network capacity.
There are quotas and rate limits which define the speed of migration of mailbox data. The big project with thousands of users needs to consider this factor when planning the migration schedule.
Migrations of enterprise Gmail mailboxes do not imply simultaneous migration of all users but rather migration of users in migration waves to balance API usage and minimize the risk of throttling.
Delta migration is also one of the crucial factors because it ensures that newly arrived emails will be migrated between the first migration and cutover.
Mailbox Components to Include in Migration Scope
Before estimating timelines, IT teams should identify the mailbox components to be preserved. While Microsoft 365 and Google Workspace organize mailbox data differently, these components in the migration scope are important.
| Outlook-to-Outlook (Microsoft 365) | Gmail-to-Gmail (Google Workspace) |
|---|---|
| Emails | Emails |
| Folder hierarchy | Labels |
| Read/unread status | Folder structure (mapped from labels) |
| Categories | Read/unread status |
| Conversation threads | Starred emails |
| Calendar events | Important markers |
| Contacts | Calendar events |
| Tasks | Contacts |
| Attachments | Conversation threads |
| Internet message headers | Attachments |
| Mailbox permissions | Drafts |
| Shared mailbox memberships | Spam |
| Delegate access | Trash |
| Mail rules (where supported) | Gmail delegation and Send As aliases (where supported) |
Estimation of Migration Performance
The most common mistake when planning migration is estimating migration efforts on the basis of the number of mailboxes only.
A more reliable approach is calculating the total volume of mailbox data that must be transferred.
For example:
| Users | Average Mailbox | Total Data |
|---|---|---|
| 2,000 | 18 GB | 36 TB |
| 5,000 | 24 GB | 120 TB |
| 10,000 | 30 GB | 300 TB |
This approach provides a more realistic estimate of migration duration because it accounts for mailbox size rather than assuming every user generates the same amount of data.
Migration throughput is also influenced by factors such as API throttling, attachment sizes, concurrent migration threads, regional latency, and retry operations. Understanding these variables allows IT teams to build practical migration timelines instead of relying on optimistic assumptions
Validation and Delta Migration Planning
Mailbox migration is not a one-time process once you finish your first step.
Users will still be creating emails during your migration process, making delta synchronization a key component in the enterprise environment.
Typical migration steps involve initial sync, one or more delta syncs, validation, and finally, the production cutover.
Your validation step should ensure not only that the number of items in the mailbox is the same, but also that calendars, contacts, attachments, read/unread status, and permissions in the mailbox are preserved.
This last step ensures a lower number of support requests from users after the migration and increases their confidence.
Scoping Mistakes IT Departments Should Avoid
Do not make these common mistakes when planning your migration:
- Not accounting for archive mailboxes
- Forgetting shared mailbox permissions
- Overlooking API throttling
- Migrating unnecessary users
- Forgetting about distribution lists
- Not taking care of compliance policies
- Not conducting a pilot migration
- Not scoping out delta synchronization
- Not validating mailbox counts
Cross Tenant Mailbox Migration Scoping Best Practices for Enterprises
Here are some best practices that you need to adhere to for a large-scale project:
- Conduct a complete mailbox inventory before any migration strategy is drafted.
- Categorize the users on the basis of their mailbox size.
- Validate identity mapping before the transfer process begins.
- Migrate using API based migration and not the traditional IMAP migration method which preserves the mailbox metadata.
- Conduct a test run migration using different sample groups.
- Conduct several delta synchronization sessions before the actual cut-over migration.
- Immediately restore the mailbox permissions, delegates, and shared access post migration.
- Ensure that item counts, calendar, contact list and mail flow is validated prior to the closure of the project.
- Monitor API throttling and adjust migration concurrency to maintain performance.
- Maintain detailed migration logs and audit reports for compliance and troubleshooting.
Comprehensive Scoping & Execution: Why CloudFuze Leads Cross-Tenant Mailbox Migration
A successful cross-tenant mailbox migration begins with precise scoping. CloudFuze provides robust pre-migration scoping capabilities across both Exchange Online (Outlook to Outlook) and Google Workspace (Gmail to Gmail) environments. By conducting automated pre-migration audits, CloudFuze helps IT teams analyze mailbox sizes, item counts, folder hierarchies, delegate permissions, and API quota limits before a single byte is moved. This eliminates surprises and sets accurate project timelines.
Leveraging direct cloud APIs, CloudFuze transfers complete mailbox ecosystems including emails, calendar events, contacts, active conversations, read/unread flags, mailbox attributes, and inline attachments without the manual risk or data loss associated with legacy tools.
Built for high-volume enterprise transitions, CloudFuze combines scoping insights with automated user mapping, parallel batch processing, phased migration waves, and delta synchronization to ensure zero business disruption during cutover. Comprehensive real-time reporting and granular audit logs provide complete end-to-end visibility, allowing IT leadership to scope, execute, and verify the migration of thousands of users across global divisions.
Get the Best Custom Scoping Session with CloudFuze Experts!
Regardless of whether you are migrating mailboxes within Microsoft 365 or Google Workspace tenants, a properly executed scoping process is important to mitigate risks, enhance migration accuracy, and set realistic timelines for your project. When used alongside an API-based migration solution and execution process, scoping creates a good basis for a successful enterprise mailbox migration.
Work directly with our migration architects to map out your user data, identify potential bottlenecks, and ensure a seamless cutover. Request a custom scoping session.
Frequently Asked Questions
1. What should be considered when planning cross-tenant mailbox migration?
For cross-tenant mailbox migration to succeed, there is a need for complete inventory of mailboxes, identity mapping, domain validation, appropriate administrative permissions, API, license and a migration tool that can preserve metadata, permissions, and support incremental synchronization.
2. Why is cross-tenant mailbox migration important for organizations?
Organizations go for cross-tenant mailbox migration during mergers, acquisitions, divestitures, tenant consolidations, and restructuring projects. It helps centralize communication, simplify IT management, improve security, and maintain business continuity during organizational changes.
3. How does cross-tenant mailbox migration differ from single-tenant mailbox migration?
Single-tenant migrations involve moving mailboxes within the same environment, while cross-tenant migrations transfer data between separate tenants with different identities, domains, security policies, and administrative controls, making planning and validation more complex.
4. What are the steps required for successful cross-tenant mailbox migration?
It involves an assessment of the source and destination environments, user mapping, domain and identity validation, performing pilot migration, batch migration of mailboxes, delta synchronization, validation of migrated mailboxes, and cutover of migrated mailboxes.
5. What are the best tools for cross-tenant mailbox migration?
CloudFuze Migrate is the best tool for cross-tenant mailbox migration and offers advanced capabilities including metadata preservation, delta migration, automation, and reporting. It is one of the best options for migration from Outlook to Outlook and Gmail to Gmail.
About the Author: Aayushi Raj
