Large Mailbox Migration Best Practices
Large mailbox migrations require more planning than standard mailbox migrations because they involve transferring a significant amount of mailbox data between Exchange Server, Exchange Online, Microsoft 365 tenants, or hybrid environments. As mailbox sizes continue to grow due to years of accumulated email, attachments, calendars, contacts, tasks, and other Outlook items, administrators must carefully prepare every stage of the migration to maintain efficiency and minimize disruption.
Whether an organization is moving to Microsoft 365, upgrading from an older Exchange Server, consolidating multiple tenants, or modernizing its messaging infrastructure, large mailbox migrations present unique operational challenges. Factors such as available bandwidth, migration concurrency, Microsoft 365 throttling policies, synchronization time, and mailbox activity all influence the overall migration duration.
Using a professional solution such as the EdbMails Office 365 Migration Tool simplifies large mailbox migrations by supporting direct mailbox migration between supported Exchange Server versions, Microsoft 365 tenants, and hosted Exchange environments. The software includes features such as incremental migration, concurrent mailbox migration, automatic connection retry, migration filtering, and detailed migration reports that help administrators efficiently manage projects of various sizes.
Unlike smaller mailbox migrations, transferring large mailboxes often requires phased execution, careful scheduling, and continuous monitoring. Proper preparation before the migration begins helps reduce delays, improves migration performance, and provides a smoother experience for administrators and end users.
Why Large Mailboxes Require Special Planning
Greater data volume
Large mailboxes contain more mailbox content, including emails, attachments, calendars, contacts, journals, notes, tasks, and folder structures. Since more data must be processed and transferred, migration jobs generally require more time than smaller mailbox migrations.
Network bandwidth affects migration speed
Migration performance depends heavily on the available upload bandwidth between the source and destination environments. Limited bandwidth can increase the overall migration duration, especially when multiple mailboxes are being migrated simultaneously. Organizations should evaluate their available network capacity before scheduling large mailbox migration projects.
Microsoft 365 throttling
Microsoft 365 applies throttling policies to protect service availability. During large migrations, administrators may experience reduced throughput if too many migration requests are processed simultaneously. Solutions such as EdbMails are designed to work within Microsoft 365 service limits while providing options for concurrent mailbox migration and automatic retry mechanisms when temporary interruptions occur.
Ongoing mailbox activity
Users often continue sending and receiving email while the migration is running. Changes made after the initial mailbox copy are synchronized during incremental migration, helping administrators migrate only newly added or modified mailbox items instead of copying the entire mailbox again.
Longer migration windows
Large mailbox migrations frequently require additional migration time compared to smaller mailboxes. Scheduling migrations during planned maintenance periods or lower business activity can help reduce the impact on users while allowing administrators to monitor migration progress more effectively.
Best Practices for Large Mailbox Migration
Assess mailbox size before migration
A successful large mailbox migration begins with understanding the amount of data that needs to be transferred. Before creating migration batches, administrators should review mailbox sizes across the Exchange Server or Microsoft 365 environment to identify larger mailboxes that may require additional migration time. This assessment should also consider archive mailbox requirements (where applicable), the overall migration scope, and the number of mailboxes assigned to each migration batch. Organizing mailboxes based on size provides better visibility into the expected workload, helps estimate migration duration more accurately, and enables administrators to create balanced migration batches for a smoother migration process.
Remove unnecessary mailbox content
Reducing unnecessary mailbox content before migration can decrease the amount of data that must be transferred, helping improve overall migration efficiency. Organizations may encourage users to remove obsolete information such as Deleted Items, Junk Email, outdated mailbox folders, and temporary content that is no longer required for business purposes. In addition, EdbMails provides folder selection and migration filtering options, allowing administrators to choose the mailbox content that should be migrated when appropriate, further optimizing the migration process.
Use migration filters when appropriate
Not every migration requires transferring every mailbox item. When business requirements allow, administrators can use migration filters to migrate specific mailbox content instead of the entire mailbox. Filtering data can reduce migration time while allowing organizations to focus on the information that users actually need. EdbMails supports filtering options that help administrators control the migration scope during supported migration scenarios.
Plan mailbox migration batches
Rather than migrating all mailboxes simultaneously, administrators should divide the project into manageable migration batches. Mailboxes can be grouped based on factors such as mailbox size, business department, geographic location, business unit, or migration priority. Organizing migrations into smaller batches makes the project easier to monitor, simplifies troubleshooting, and reduces the operational impact if an issue occurs during the migration.
Evaluate available bandwidth
Network bandwidth directly affects mailbox migration performance. Before beginning a large migration, estimate the total amount of mailbox data that will be transferred and compare it with the available upload bandwidth. This helps administrators estimate migration duration and determine whether additional migration windows may be required. For example, migrating several hundred gigabytes or multiple terabytes of mailbox data over a limited internet connection will naturally require more time than migrating the same data over a high-speed enterprise connection.
Schedule migrations during lower activity periods
Large mailbox migrations often perform more efficiently when scheduled outside normal business hours. Running migration jobs during evenings, weekends, or planned maintenance periods can reduce competition for available network resources while minimizing the impact on end users. This approach also gives administrators additional time to monitor migration progress and address any issues before users resume normal business operations.
Use concurrent mailbox migration appropriately
Migrating multiple mailboxes simultaneously can significantly improve migration efficiency when sufficient system resources and network bandwidth are available. However, configuring too many concurrent migrations may increase resource utilization and reduce overall migration performance. EdbMails supports concurrent mailbox migration, enabling administrators to migrate multiple mailboxes in parallel. The optimal level of concurrency depends on factors such as available bandwidth, source server performance, Microsoft 365 service limits, migration workstation resources, and the overall migration workload. Selecting an appropriate concurrency level helps maintain stable migration performance throughout the project.
Monitor migration progress regularly
Continuous monitoring allows administrators to identify and resolve migration issues before they affect a larger number of mailboxes. Throughout the migration, administrators should regularly review the overall migration progress, completed mailboxes, mailboxes currently being processed, failed migration attempts, retry operations, and the time required for individual mailbox migrations. EdbMails provides detailed migration reports that help track migration status and review completed operations. Regularly monitoring these reports enables administrators to detect issues early and simplifies troubleshooting when additional attention is required.
Be aware of Microsoft 365 throttling
Microsoft 365 applies throttling policies to maintain the stability and performance of its services. During large mailbox migrations, these policies may temporarily reduce migration throughput when service limits are reached. Although throttling cannot be completely avoided, its impact can be minimized by planning migration batches carefully, avoiding excessive simultaneous migration requests, scheduling migrations during lower activity periods, and continuously monitoring migration progress. EdbMails is designed to operate within Microsoft 365 migration limits and includes automatic retry functionality that helps continue migration operations after temporary interruptions.
Verify migration prerequisites
Before starting any migration batch, administrators should verify that the migration environment has been properly configured. Following a structured Office 365 migration guide before beginning production migrations can help administrators prepare the source and destination environments more effectively. This includes confirming that source mailboxes are accessible, destination mailboxes are available, required administrative permissions have been assigned, authentication requirements have been satisfied, and migration endpoints are correctly configured for the selected migration scenario. Completing these prerequisite checks before migration begins helps reduce avoidable interruptions and contributes to a smoother migration process.
Perform incremental migration before final cutover
One of the key features of EdbMails is its support for incremental migration. After the initial mailbox migration has been completed, users may continue sending and receiving email in their source mailboxes. Before the final migration cutover, administrators can perform an incremental migration to transfer only newly added or modified mailbox items. This approach avoids duplicate mailbox items, transfers only recent changes, reduces synchronization time, keeps source and destination mailboxes aligned, and simplifies the final migration process. Incremental migration is particularly beneficial for phased migration projects where users continue working until the final transition to the new environment.
Tips for Improving Migration Efficiency
The following recommendations can help improve the overall efficiency of large mailbox migration projects:
- Create organized migration batches instead of migrating every mailbox simultaneously.
- Schedule large migration jobs during lower business activity whenever possible.
- Monitor migration reports throughout the project.
- Use incremental migration before final cutover.
- Review available bandwidth before scheduling migration windows.
- Keep migration software updated.
- Verify administrative permissions before starting migration.
- Inform users about the planned migration schedule to reduce unexpected interruptions.
Following these practices helps administrators maintain better visibility throughout the migration while minimizing delays and improving overall project organization.
Common Challenges During Large Mailbox Migration
Although modern migration solutions simplify mailbox transfers, administrators may still encounter challenges when migrating large mailboxes. Proper planning and continuous monitoring can help reduce these issues and keep the migration project on schedule.
Limited network bandwidth: Available network bandwidth plays a significant role in migration performance. If bandwidth is limited or shared with normal business operations, large mailbox migrations may take longer than expected. Planning migration windows during periods of lower network usage can help maximize available bandwidth.
Microsoft 365 throttling: Microsoft 365 may temporarily limit migration activity to maintain service stability. During periods of high migration activity, administrators may notice slower transfer rates. Using organized migration batches and monitoring migration progress helps minimize the operational impact of throttling.
Large data volume: Mailboxes containing years of email communication naturally require more time to migrate than smaller mailboxes. Organizations should account for total mailbox size when estimating project timelines.
Ongoing mailbox activity: Users often continue working while mailbox migration is in progress. New emails, calendar updates, contacts, and other mailbox changes created after the initial migration can be synchronized later by using EdbMails' incremental migration feature.
Temporary connectivity interruptions: Internet interruptions or temporary service availability issues may occasionally occur during long-running migration projects.
EdbMails includes automatic connection retry functionality that helps resume migration operations after temporary connection interruptions, reducing the need for manual intervention.
Pre-Migration Checklist
Before beginning a large mailbox migration, verify that the migration environment has been properly prepared.
Migration Planning Checklist
- Review the overall migration scope.
- Assess mailbox sizes.
- Verify source and destination connectivity.
- Confirm administrator permissions.
- Ensure destination mailboxes are available.
- Evaluate available network bandwidth.
- Organize mailbox migration batches.
- Configure migration filters if required.
- Schedule migration during an appropriate maintenance window.
- Inform end users about the migration schedule.
- Verify authentication requirements.
- Confirm sufficient system resources for the migration workstation.
- Perform a small pilot migration if appropriate.
- Enable migration logging and reporting.
Completing these tasks before the migration begins helps reduce avoidable delays and provides greater visibility throughout the migration process.
Post-Migration Validation
Completing the mailbox migration is only one part of the overall project. After migration, administrators should verify that mailbox data has been transferred successfully and that users can continue working without interruption.
Post-migration validation helps identify any issues that require attention before the migration project is considered complete.
Verify migrated mailbox content
Review migrated mailboxes to confirm that mailbox data has been transferred successfully.
Verify items such as:
- Email messages
- Folder structure
- Calendar items
- Contacts
- Tasks
- Notes
- Archive mailbox content (if migrated)
Verify user access
Confirm that users can successfully access their migrated mailboxes using supported Outlook clients and Outlook on the web after the migration is complete.
Administrators should verify that users can:
- Open their mailbox
- Browse mailbox folders
- Send and receive email
- Access recently migrated mailbox content
Review migration reports
EdbMails generates detailed migration reports that provide administrators with information about completed migrations, skipped items, retries, and any issues encountered during the migration process.
Reviewing these reports helps confirm successful mailbox transfers and assists with troubleshooting if additional migration activity is required.
Perform incremental synchronization if needed
If users continued working in their source mailboxes after the initial migration, run an incremental migration before the final migration cutover.
Incremental migration copies only newly added or modified mailbox items while preventing duplicate data, helping ensure that the destination mailbox remains up to date.
Performance Considerations
Several technical factors influence the performance of large mailbox migrations. Understanding these variables allows administrators to estimate migration duration more accurately and optimize project planning.
| Factor | Impact on Migration |
| Network bandwidth | Higher bandwidth generally allows faster data transfer. |
| Microsoft 365 throttling | May temporarily reduce migration throughput during heavy activity. |
| Concurrent mailbox migration | Running multiple migrations simultaneously can improve efficiency when properly configured. |
| Mailbox size | Larger mailboxes generally require more migration time. |
| Attachment volume | Mailboxes containing many or large attachments typically take longer to migrate. |
| Source server performance | Server responsiveness can influence migration speed. |
| Incremental migration | Synchronizes only newly added or modified mailbox items after the initial migration. |
| Migration batch size | Well-balanced batches simplify monitoring and project management. |
Because every environment differs, migration duration varies depending on available infrastructure, internet connectivity, source server performance, Microsoft 365 service conditions, and the total amount of mailbox data being transferred.
Conclusion
Large mailbox migrations require careful planning, realistic scheduling, and continuous monitoring to achieve a successful outcome. Factors such as mailbox size, available bandwidth, Microsoft 365 throttling, migration batches, and ongoing mailbox activity all influence migration performance and overall project duration.
By following established large mailbox migration best practices and a structured Office 365 mailbox migration strategy, organizations can improve migration efficiency, reduce administrative effort, and minimize disruption to end users.
The EdbMails Office 365 Migration Tool supports organizations throughout the migration process with features such as concurrent mailbox migration, incremental migration, migration filtering, automatic connection retry, and detailed migration reports. These capabilities help administrators manage large mailbox migration projects more efficiently while maintaining data integrity and reducing migration complexity.
Frequently Asked Questions
What is a large mailbox migration?
Does EdbMails support large mailbox migration?
Why is migration planning important for large mailboxes?
How does incremental migration help?
What should administrators verify after migration?
For additional migration questions, see our Office 365 Migration FAQ
