Office 365 Migration Network Requirements

Migrating mailboxes to Office 365 involves transferring large volumes of business data over the internet. A successful migration depends on a properly configured network infrastructure. While selecting the right migration method is important, the network infrastructure plays an equally critical role in determining migration speed, reliability, and overall success. Insufficient bandwidth, restrictive firewall or proxy settings, and network latency can lead to migration delays, connection interruptions, Microsoft throttling, and extended project timelines.

Before starting an Office 365 migration, administrators should review network capacity, bandwidth availability, firewall rules, proxy settings, and Microsoft 365 connectivity requirements, and verify that the network infrastructure and security policies meet Microsoft's recommended prerequisites. Proper preparation helps avoid connection failures and unexpected migration delays. The exact requirements vary with mailbox size, the number of users, the migration method, the source environment, and the Microsoft 365 tenant configuration.

Why Network Planning Matters for Office 365 Migration

Every mailbox, archive, attachment, calendar, and contact is transferred through your organisation's network connection to Office 365. The quality of your network directly affects how efficiently this data is migrated.

A well-planned network provides several benefits, including better migration planning, reduced troubleshooting, lower risk of interrupted data transfers, better utilisation of available bandwidth, and less impact on business users during migration.

Evaluating the network before migration allows administrators to identify potential network limitations and optimize performance before transferring production data.

Network readiness is one part of overall migration planning. For the complete planning and migration workflow, see the Office 365 migration guide.

Office 365 Migration Network Requirements

Before starting an Office 365 migration project, verify that your environment meets the essential network requirements.

1. Reliable Internet Connectivity
   

   A stable and high-speed internet connection is essential for transferring mailbox data to Office 365. Frequent network interruptions or unstable connections can increase migration time and may require migration jobs to be restarted.

2. Sufficient Bandwidth
   

   Bandwidth planning is one of the most important aspects of a successful migration. Even with a fast internet connection, transferring very large mailboxes requires sufficient upload capacity and proper scheduling. The required bandwidth depends on factors such as the number of mailboxes, average mailbox size, number of concurrent migration jobs, available upload speed, and Microsoft service throttling.

3. Low Network Latency
   

   Latency measures the time required for data to travel between the source environment and Office 365. Lower latency helps maintain consistent communication with Microsoft services and improves migration efficiency.

4. Firewall Configuration
   

   Ensure that outbound communication to Office 365 services is allowed through the firewall. Incorrect firewall policies may block migration traffic or interrupt communication with Exchange Online.

5. Secure Network Protocols
   

   Office 365 migration uses encrypted communication to protect mailbox data during transmission. Verify that your network supports secure HTTPS connections and that TLS is enabled according to Microsoft's recommendations.

Bandwidth Requirements for Office 365 Migration

Microsoft does not publish a fixed bandwidth requirement for mailbox migration. The bandwidth you need depends on the total data volume, the time available for the migration, and the capacity that can be given to migration traffic without affecting business users.

To estimate the minimum transfer time, divide the total data volume by the effective upload throughput. For example, 500 GB of mailbox data (4,000,000 megabits) sent over a sustained 100 Mbps connection takes about 40,000 seconds, or roughly 11 hours. This is a theoretical figure: protocol overhead, Microsoft throttling, source server performance, and other network traffic extend the actual migration time.

• Upload capacity: Migration to Office 365 depends mainly on the upload bandwidth available from the source environment. Measure the upload speed that is actually available during the planned migration window.
• Download capacity: When the migration tool runs on a local machine, mailbox data is downloaded from the source and uploaded to the target through that machine's connection, so both directions must be considered, for example in tenant-to-tenant migrations.
• Shared usage: Migration traffic shares the connection with users and other services. Schedule large batches outside business hours or reserve capacity for migration traffic.

Firewall and Port Requirements

Migration traffic to Microsoft 365 uses encrypted HTTPS connections. Allow the following outbound traffic from the machine or server that runs the migration:

Microsoft recommends allowing Microsoft 365 service URLs rather than maintaining static IP address allow lists, because the IP ranges change. Use the Microsoft 365 URLs and IP address ranges list (aka.ms/m365endpoints) or the Microsoft 365 endpoints web service to keep firewall rules current. If the source is an on-premises Exchange server, the migration machine also needs access to the source server, for example over port 443 for Exchange Web Services.

Proxy and VPN Considerations

Proxies and VPNs add processing and routing steps between the migration machine and Microsoft 365. These steps can increase latency and limit throughput.

• Proxy bypass: Microsoft recommends bypassing TLS decryption, traffic interception, and deep packet inspection for Microsoft 365 domains. If migration traffic must pass through a proxy, confirm that the proxy allows outbound HTTPS, supports modern authentication, and does not modify Microsoft certificates.
• VPN routing: Sending migration traffic through a VPN to a central location before it reaches the internet (a network hairpin) adds latency and limits throughput to the capacity of the VPN. Where possible, run the migration from a machine with direct internet egress, or use split tunneling so that Microsoft 365 traffic bypasses the VPN.

Microsoft 365 Connectivity Requirements

The migration machine must be able to reach the Microsoft 365 services that handle authentication and mailbox access:

• Authentication: Microsoft Entra ID sign-in endpoints (login.microsoftonline.com) for modern authentication.
• Mailbox access: Exchange Online endpoints (outlook.office365.com) for Exchange Web Services, and Microsoft Graph (graph.microsoft.com).
• DNS resolution: Resolve Microsoft 365 hostnames through DNS servers close to the network egress point, so that connections use the nearest Microsoft 365 entry point.
• Connectivity test: Run the Microsoft 365 network connectivity test (aka.ms/netonboard) from the migration machine before the migration starts.

Factors That Affect Migration Speed

Network bandwidth is one of several factors. Migration speed also depends on:

• Mailbox size and item count: Larger mailboxes and mailboxes with many items take longer to process.
• Concurrent migrations: Migrating more mailboxes in parallel increases throughput until bandwidth, source server capacity, or Microsoft throttling becomes the limit.
• Microsoft service limits: Exchange Online applies service protection limits that can temporarily reduce throughput during large migrations.
• Network latency: Each request to Microsoft 365 waits for a network round trip, so higher latency reduces the throughput of every connection, particularly for mailboxes with many small items. Microsoft identifies minimising round-trip time to the Microsoft Global Network as the primary goal of Microsoft 365 network design.
• Batch size: Size each migration batch so that its data volume can transfer within the planned migration window at the measured throughput, using the transfer-time estimate in the bandwidth section above.
• Source server performance: CPU, disk, and workload on the source mail server affect how quickly data can be read.
• Migration machine resources: CPU, memory, and disk on the machine running the migration tool affect how many mailboxes can be processed at the same time.

Office 365 Migration Best Practices for Network Optimisation

Preparing the network before migration helps avoid unnecessary delays and improves migration performance.

1. Assess Current Network Capacity
   

   Measure available upload bandwidth and evaluate current network utilisation before starting the migration.

2. Perform Pilot Migrations
   

   Run a small pilot migration to estimate migration speed, identify configuration issues, and validate the migration process before migrating all users.

3. Schedule Migration during Off-peak Hours
   

   Running migration jobs outside business hours minimises the impact on employee productivity while allowing more bandwidth for migration traffic.

4. Use batch migration
   

   Migrating users in manageable batches reduces network congestion and simplifies troubleshooting if any issues occur.

5. Monitor Migration Progress
   

   Continuously monitor migration reports, bandwidth usage, and network performance to quickly identify connectivity issues and resolve them before they affect the overall migration.

Network Checklist Before Starting Office 365 Migration

Confirm the following before you migrate production mailboxes. For the complete pre-migration task list beyond the network, use the Office 365 migration checklist.

• Upload and download throughput measured during the planned migration window
• Estimated transfer time calculated for the total data volume
• Outbound TCP 443 and DNS allowed from the migration machine
• IMAP ports (143 or 993) open to the source server for IMAP migrations
• Microsoft 365 URLs allowed, and TLS inspection bypassed for Microsoft 365 domains
• Proxy settings verified for outbound HTTPS and modern authentication
• VPN hairpin avoided, or split tunneling configured for Microsoft 365 traffic
• Microsoft 365 network connectivity test completed from the migration machine
• Pilot migration completed to measure actual throughput

Troubleshooting Common Network Issues During Migration

Several network-related issues can affect migration performance if they are not addressed in advance.

1. Limited Upload Bandwidth
   

   Insufficient upload capacity significantly increases migration duration, particularly when migrating large mailboxes.

   Resolution: Move large mailboxes to off-peak windows, reduce the number of jobs sharing the connection, or run the migration from a location with more upload capacity.

2. Microsoft Throttling
   

   Microsoft automatically regulates service requests to maintain platform stability. Excessive concurrent migration requests may temporarily reduce migration throughput.

   Resolution: Reduce the number of concurrent migrations and allow the migration to continue after the throttling period ends.

3. Network Interruptions
   

   Unstable internet connections can interrupt active migration sessions and extend project completion times.

   Resolution: Use a stable, wired connection for the migration machine and resume the batch with incremental migration so that completed items are not transferred again.

4. Firewall Restrictions
   

   Blocked Office 365 endpoints or incorrectly configured firewall rules may prevent successful mailbox connections.

   Resolution: Check firewall and proxy logs for blocked Microsoft 365 hostnames, then allow the required URLs and outbound port 443.

5. High Latency
   

   Long network response times reduce migration efficiency and may increase synchronisation delays between the source and destination environments.

   Resolution: Check for VPN or proxy hairpins and use local DNS resolution and internet egress for Microsoft 365 traffic.

Proper network assessment before migration helps address most of these issues before production migration begins.

How EdbMails Optimises Network Performance During Office 365 Migration

Office 365 enforces service protection limits that regulate mailbox migration activity. Large-scale migrations may experience temporary throttling based on tenant workload, concurrent connections, and service utilisation.

1. Automatic Throttling Management
   

   EdbMails automatically detects Office 365 throttling responses. The migration resumes once throttling limits are lifted, reducing the need for administrator intervention.

2. Concurrent Mailbox Migration
   

   EdbMails supports concurrent mailbox migration by distributing workloads across multiple threads while remaining within Microsoft 365 service protection limits. Administrators can configure the level of parallel processing based on available CPU resources and network bandwidth to maximise migration throughput.

3. Incremental Migration
   

   Following the initial migration, EdbMails identifies and transfers only newly created or modified mailbox items. Incremental Migration minimises bandwidth utilisation and prevents duplicate mailbox data from being written to the destination.

4. Mailbox Access During Migration
   

   EdbMails supports zero downtime migration by allowing users to continue accessing their mailboxes while data is migrated in the background. After the initial migration, incremental migration synchronises only new or modified items, and completes the migration with minimal business disruption.

EdbMails also maintains mailbox integrity, preserves folder hierarchy, and supports secure modern authentication for Microsoft 365 environments. These capabilities help organisations complete Office 365 migrations with minimal disruption while making efficient use of available network bandwidth.

Conclusion

Meeting the Office 365 migration network requirements is essential for achieving a successful migration. Proper bandwidth planning, stable internet connectivity, optimised firewall settings, and careful migration scheduling all contribute to more efficient data transfer and reduced business disruption.

By evaluating the network infrastructure before migration and using EdbMails for Microsoft 365 Migration, organisations can simplify mailbox migration projects, reduce troubleshooting, and plan a more predictable transition to Office 365.

---

Additional resources:

• Office 365 Migration Tool
• Office 365 migration best practices
• Office 365 tenant to tenant migration
• Exchange to Office 365 migration