An Exchange Migration is often one of the most critical phases of an organization’s transition to a modern messaging environment. Whether you’re migrating from on-premises Microsoft Exchange Server to Microsoft 365, moving between Exchange environments, or consolidating multiple tenants, administrators expect migration batches to progress steadily until completion.
However, one issue consistently frustrates IT teams: the migration appears to stop at 95%.
After hours—or sometimes days—of successful data transfer, the migration dashboard seems frozen. Mailboxes remain in a syncing state, users begin asking when they’ll receive access to their new environment, and administrators are left wondering whether the migration has failed or simply requires more time.
Fortunately, a migration that appears stuck at 95% does not always indicate a failure. In many cases, Exchange is performing final synchronization tasks, validating mailbox consistency, processing incremental changes, or waiting for administrative actions before marking the migration as complete.
Understanding why this occurs helps administrators avoid unnecessary interruptions, prevent data inconsistencies, and recover stalled migrations more efficiently.
This guide explains why Exchange Migration Software jobs become stuck at 95%, how to interpret migration logs correctly, the most common technical causes, and practical recovery methods. You’ll also learn best practices that reduce the likelihood of migration delays in future projects.
What Does It Mean When an Exchange Migration Software Is Stuck at 95%?
The migration percentage shown within Exchange Admin Center or Microsoft 365 does not always represent a simple copy operation. Instead, it reflects multiple stages involved in mailbox migration.
Typically, mailbox migration progresses through several phases:
- Initial mailbox discovery
- Mailbox validation
- Data transfer
- Incremental synchronization
- Folder verification
- Mailbox consistency checks
- Final synchronization
- Migration completion
Reaching 95% generally indicates that the majority of mailbox content has already been copied successfully. Rather than transferring large amounts of data, Exchange is usually completing background operations before marking the migration batch as finished.
These background activities may include:
- Synchronizing recently received emails
- Processing calendar updates
- Verifying mailbox integrity
- Applying mailbox permissions
- Confirming folder hierarchy
- Updating migration reports
- Waiting for administrator approval
- Completing final mailbox locking procedures
As a result, remaining at 95% for some time can be completely normal, especially when migrating large mailboxes or thousands of users.
However, if progress remains unchanged for many hours—or even several days—administrators should begin investigating potential issues.
Why Does Exchange Migration Software Commonly Stop at 95%?
The final stages of an Exchange migration require considerably more validation than earlier stages.
Unlike simply copying mailbox data, Exchange verifies whether:
- Every folder has been synchronized.
- No mailbox corruption exists.
- Incremental changes are fully replicated.
- Deleted items are synchronized.
- Mailbox permissions are transferred.
- Archive mailboxes are complete.
- User access can safely transition.
- Final consistency checks have succeeded.
Because these operations involve multiple background services, any delay within one component can temporarily prevent the migration from completing.
Several infrastructure components also influence this stage, including:
- Network latency
- Exchange Web Services (EWS)
- Microsoft 365 service responsiveness
- Storage performance
- Active Directory replication
- Authentication services
- Mailbox database health
- Migration endpoint availability
Even if data copying has finished successfully, delays in any of these services may leave the migration status at 95%.
Benefits of Understanding the 95% Exchange Migration Software Stage
Knowing what happens during the final stages of an Exchange migration offers several practical advantages for IT administrators and project teams.
Prevents Unnecessary Migration Cancellations
One of the most common mistakes is cancelling a migration simply because the progress appears frozen.
If Exchange is actively completing synchronization tasks, stopping the migration may actually increase recovery time and require additional resynchronization.
Understanding normal migration behavior helps administrators make informed decisions instead of reacting prematurely.
Improves Troubleshooting Efficiency
When administrators understand the migration workflow, they can quickly distinguish between:
- Normal synchronization delays
- Performance bottlenecks
- Authentication failures
- Mailbox corruption
- Service interruptions
- Configuration issues
This targeted troubleshooting approach minimizes downtime and accelerates issue resolution.
Reduces Business Disruption
Unexpected migration delays often affect:
- End-user productivity
- Helpdesk ticket volumes
- Project timelines
- Executive confidence
- Compliance deadlines
Identifying the root cause early allows organizations to communicate realistic expectations and reduce operational disruptions.
Supports Better Migration Planning
Knowledge gained from previous migrations helps improve future migration projects by identifying recurring bottlenecks, infrastructure limitations, and resource requirements.
Organizations can then schedule migrations during low-usage periods, optimize network capacity, and allocate sufficient time for final synchronization.
Common Scenarios Where Exchange Migration Software May Stall
Although every Exchange environment is unique, administrators frequently encounter the 95% issue in several common situations.
Large Mailboxes
Mailboxes exceeding several tens of gigabytes naturally require additional time for:
- Folder validation
- Calendar synchronization
- Search index verification
- Archive synchronization
- Incremental updates
The larger the mailbox, the longer Exchange may spend completing final consistency checks.
Hybrid Exchange Deployments
Hybrid environments introduce additional synchronization layers between on-premises Exchange Server and Exchange Online.
These environments rely on:
- Azure AD synchronization
- Exchange Hybrid Configuration
- Secure connectors
- OAuth authentication
- Exchange Web Services
A delay in any synchronization component can prevent the migration batch from completing promptly.
High User Activity During Migration
If users continue sending and receiving emails while migration is underway, Exchange must repeatedly synchronize new mailbox changes before finalizing the migration.
Continuous mailbox activity extends the final synchronization stage and may leave progress appearing fixed at 95%.
Network Instability
Even brief periods of packet loss, increased latency, or temporary connectivity interruptions can slow synchronization tasks, particularly during the final migration phase where mailbox verification depends on stable communication between source and destination environments.
Challenges and Risks When Exchange Migration Software Remains Stuck at 95%
While a migration paused at 95% is often part of the normal synchronization process, administrators should investigate if there is no progress for several hours or if migration reports indicate repeated retries. Understanding the underlying cause is essential to avoid extended downtime, incomplete mailbox transfers, or user disruption.
Below are the most common reasons an Exchange Migration remains stuck at 95% and the steps you can take to diagnose each issue.
Common Causes of Exchange Migration Stuck at 95%
1. Final Incremental Synchronization Is Still Running
This is the most common and least concerning scenario.
During the final migration stage, Exchange performs one last synchronization cycle to capture any mailbox changes that occurred while the initial data copy was in progress. These changes may include:
- Newly received emails
- Sent messages
- Calendar updates
- Contacts
- Tasks
- Deleted items
- Folder modifications
For active users, this synchronization may continue until the migration is finalized or the mailbox is locked for completion.
How to identify it
- Migration statistics continue updating.
- The amount of data remaining gradually decreases.
- No critical errors appear in migration reports.
- Mailbox synchronization timestamps continue changing.
Recommended action
Monitor the migration instead of cancelling it immediately. If synchronization continues to make progress, allowing it to complete is usually the safest approach.
2. Large Mailbox or Archive Mailbox Processing
Mailbox size significantly affects migration duration.
Although most mailbox content may already be copied, Exchange still performs validation on:
- Folder hierarchy
- Archive mailboxes
- Recoverable Items
- Calendar folders
- Permissions
- Search indexes
Organizations with mailboxes larger than 50–100 GB often notice that the last few percentage points require considerably more time than the initial transfer.
Best practice
Before migration:
- Remove obsolete emails.
- Empty Deleted Items.
- Archive inactive data.
- Identify oversized mailboxes.
- Schedule large mailbox migrations separately from smaller batches.
This reduces the workload during the final synchronization stage.
3. Network Latency or Connectivity Problems
An Exchange migration depends on continuous communication between the source and destination environments.
Common network-related issues include:
- High latency
- Packet loss
- VPN instability
- Firewall interruptions
- Proxy configuration issues
- Bandwidth limitations
Even if the data transfer completed successfully, intermittent connectivity can delay mailbox verification and completion tasks.
Signs to watch for
- Migration pauses intermittently.
- Retry attempts increase.
- Synchronization repeatedly resumes.
- Transfer speed fluctuates unexpectedly.
Recommended action
Verify:
- Network stability
- Firewall rules
- Exchange Online connectivity
- DNS resolution
- Internet bandwidth utilization
Monitoring tools can help identify whether the bottleneck lies within the network rather than the Exchange infrastructure itself.
4. Exchange Web Services (EWS) Issues
Exchange Web Services (EWS) is a critical component used by many migration solutions.
If EWS experiences authentication failures, throttling, or service interruptions, mailbox synchronization may pause during the final stages.
Typical causes include:
- Incorrect authentication settings
- Expired certificates
- Proxy misconfiguration
- Disabled EWS
- Service throttling policies
Diagnostic steps
Check whether:
- EWS endpoints are reachable.
- Authentication succeeds.
- SSL certificates are valid.
- Service accounts have appropriate permissions.
Resolving EWS issues often allows the migration to resume without restarting the entire batch.
5. Mailbox Corruption
Corrupted mailbox items are another common reason migrations appear to stall.
Examples include:
- Damaged calendar entries
- Corrupt attachments
- Invalid folder structures
- Broken permissions
- Corrupted Recoverable Items folders
Instead of skipping these objects immediately, Exchange attempts multiple retries before recording an error.
Symptoms
- The same mailbox repeatedly fails.
- One mailbox delays an entire migration batch.
- Migration reports reference corrupted items.
- Retry counters continue increasing.
Recommended approach
Review migration reports carefully to identify the affected mailbox. Repairing the mailbox before restarting the migration often produces better results than repeatedly retrying the entire batch.
6. Microsoft 365 Service Throttling
Exchange Online protects Microsoft 365 resources by limiting excessive migration activity.
Organizations migrating:
- Thousands of users
- Multiple large mailboxes
- Multiple migration batches simultaneously
may encounter service throttling.
Typical indicators include:
- Reduced migration throughput
- Temporary pauses
- Automatic retry attempts
- Longer synchronization cycles
Best practice
Rather than migrating every mailbox simultaneously:
- Divide users into batches.
- Schedule migrations during off-peak hours.
- Stagger large mailbox migrations.
- Monitor Microsoft 365 service health.
7. Active Directory Synchronization Delays
Hybrid Exchange deployments rely heavily on directory synchronization.
If Azure AD Connect has not synchronized recent user or mailbox changes, Exchange may delay migration completion.
Potential issues include:
- Unsynchronized mailbox attributes
- Incomplete user provisioning
- Duplicate objects
- Missing proxy addresses
- Outdated synchronization cycles
Ensuring directory synchronization completes successfully before migration reduces the likelihood of delays during the final migration phase.
Understanding Exchange Migration Logs
Migration logs are one of the most valuable troubleshooting resources available to Exchange administrators.
Instead of relying solely on the progress percentage, administrators should review detailed migration reports to determine exactly what Exchange is doing.
Migration logs commonly include information such as:
- Mailbox status
- Synchronization progress
- Data transferred
- Items skipped
- Retry attempts
- Error codes
- Warning messages
- Completion status
- Processing duration
These reports help distinguish between a migration that is actively processing and one that has genuinely stopped.
Important Log Information to Review
When investigating a migration stuck at 95%, focus on the following details.
Migration Status
Look for values such as:
- Syncing
- Completing
- Incremental Sync
- Synced
- Completed
- Failed
- Completion in Progress
A mailbox remaining in “Completing” for a reasonable period may still be functioning normally.
Retry Counts
Multiple retries do not always indicate failure.
Exchange automatically retries temporary issues caused by:
- Network interruptions
- Service throttling
- Authentication timeouts
- Temporary server unavailability
A steadily increasing retry count, however, warrants further investigation.
Error Messages
Common migration errors include:
- Authentication failures
- Network timeouts
- Mailbox corruption
- Permission issues
- Service unavailable errors
- Endpoint connectivity problems
Rather than focusing solely on the percentage displayed in the migration dashboard, use these error messages to identify the underlying cause.
Synchronization Time
Review the timestamp of the last successful synchronization.
If synchronization occurred only a few minutes ago, the migration is likely still progressing.
If there has been no update for several hours and no additional activity is recorded, further troubleshooting is appropriate.
Step-by-Step Recovery Methods
When an Exchange Migration remains at 95% longer than expected, avoid immediately cancelling the migration. Instead, follow a structured troubleshooting process.
Step 1 – Verify Migration Activity
Before taking corrective action:
- Review migration reports.
- Confirm synchronization timestamps.
- Check whether transferred data continues increasing.
- Identify whether retries are occurring.
If progress is still being made, allow the migration to continue.
Step 2 – Review Exchange Migration Logs
Carefully examine:
- Warning messages
- Failed mailbox items
- Authentication events
- Retry history
- Synchronization statistics
- Mailbox-specific errors
The logs often reveal the exact component responsible for the delay.
Step 3 – Validate Network Connectivity
Confirm that:
- Source Exchange servers are accessible.
- Microsoft 365 connectivity is stable.
- DNS resolution is functioning correctly.
- Firewall policies permit migration traffic.
- Proxy servers are not interrupting communication.
Even minor connectivity issues can significantly extend the final synchronization phase.
Step 4 – Check Mailbox Health
Identify mailboxes reporting repeated failures or excessive retries.
Investigate whether:
- Mailbox corruption exists.
- Folder structures are inconsistent.
- Archive mailboxes contain problematic items.
- Permissions are invalid.
Resolving mailbox-specific issues prevents them from delaying the remainder of the migration batch.
Step 5 – Resume Instead of Restarting
If the migration has paused due to a temporary issue, resuming the migration is generally preferable to deleting and recreating the migration batch.
Restarting from scratch may require Exchange to repeat synchronization tasks that were already completed successfully.
Real-World Example
Consider an organization migrating 450 mailboxes from Exchange Server to Microsoft 365 over a weekend. By Sunday morning, nearly every mailbox displays 95% completion, yet users report that new emails continue arriving in the source environment.
Rather than cancelling the migration, the IT team reviews the migration reports and confirms that incremental synchronization is still processing recent mailbox activity. They temporarily reduce user activity, verify stable network connectivity, and allow the migration batches to continue. Within a few hours, the remaining synchronization completes successfully without restarting any mailboxes.
This example illustrates why understanding migration behavior and reviewing logs is often more effective than reacting to the percentage indicator alone.
Best Practices to Prevent Exchange Migration from Getting Stuck at 95%
While not every migration delay can be avoided, careful planning and proactive monitoring significantly reduce the chances of an Exchange Migration stalling during its final stages. The following best practices are based on common enterprise migration experiences and Microsoft Exchange administration principles.
1. Assess Your Environment Before Starting
A successful migration begins with a thorough assessment of your Exchange environment. Review:
- Exchange Server health
- Mailbox database status
- Available storage
- Network bandwidth
- Active Directory health
- Microsoft 365 tenant readiness
- SSL certificates
- DNS configuration
Identifying infrastructure issues beforehand helps prevent interruptions later in the migration process.
2. Clean Up Mailboxes Before Migration
Migrating unnecessary or outdated data increases the overall migration time and may contribute to longer synchronization cycles.
Consider:
- Deleting obsolete emails
- Emptying Deleted Items folders
- Archiving inactive mailboxes
- Removing duplicate content
- Reducing oversized attachments where appropriate
A cleaner mailbox is generally faster to validate and synchronize.
3. Migrate in Manageable Batches
Instead of migrating every mailbox simultaneously, divide users into logical batches based on factors such as:
- Department
- Office location
- Mailbox size
- Business priority
- User activity
Smaller migration batches simplify troubleshooting and reduce the impact of unexpected issues.
4. Monitor Migration Progress Regularly
Avoid relying solely on the percentage displayed in the migration dashboard.
Review:
- Migration reports
- Synchronization timestamps
- Warning messages
- Retry counts
- Mailbox completion status
- Microsoft 365 service health
Continuous monitoring enables administrators to detect potential problems before they become critical.
5. Schedule Migrations During Low-Activity Periods
The final synchronization stage is often shorter when mailbox activity is minimal.
Whenever possible, perform migrations during:
- Evenings
- Weekends
- Public holidays
- Planned maintenance windows
Reducing user activity minimizes the number of new mailbox changes that must be synchronized before completion.
6. Validate Results After Migration
Completing a migration batch is only one part of the overall process. Administrators should verify that migrated mailboxes are functioning as expected.
Post-migration validation should include:
- Mailbox accessibility
- Email send and receive functionality
- Calendar synchronization
- Contacts and tasks
- Shared mailbox access
- Delegate permissions
- Archive mailbox availability
- Folder structure consistency
This helps ensure a smooth transition for end users and reduces post-migration support requests.
Why Choose EdbMails for Exchange Migration?
Selecting the right Exchange Migration Tool can simplify migration planning, reduce manual effort, and provide better visibility into migration progress.
EdbMails is designed to support organizations migrating between on-premises Exchange Server, Microsoft 365, Hosted Exchange, and hybrid environments. Its interface focuses on simplifying complex migration tasks while providing administrators with detailed migration status information.
Some of the capabilities that administrators commonly look for include:
- Support for Exchange Server to Microsoft 365 migrations
- Microsoft 365 tenant-to-tenant migration
- Exchange hybrid migration support
- Incremental migration to transfer only newly added items
- Automatic mailbox mapping options
- Selective mailbox migration
- Detailed migration reports
- Resume capability for interrupted migrations
- Filtering options for mailbox data
- Secure authentication using modern Microsoft protocols
For organizations managing multiple mailboxes, these features can help streamline migration projects while maintaining better control over migration progress.
As with any migration project, it’s still important to assess your environment, validate prerequisites, and test with a pilot migration before moving production workloads.
Frequently Asked Questions
1. Is it normal for an Exchange Migration to remain at 95%?
Yes. In many cases, the final 5% represents background operations such as incremental synchronization, mailbox validation, permission updates, and consistency checks. For larger mailboxes or highly active environments, this stage can take considerably longer than the initial data transfer.
2. How long should I wait before troubleshooting a migration stuck at 95%?
The answer depends on mailbox size, user activity, network performance, and the number of mailboxes being migrated. If migration reports continue showing synchronization activity, it’s generally best to allow the process to continue. If there has been no progress for several hours and logs indicate repeated failures or retries, further investigation is recommended.
3. Can I safely cancel a migration that’s stuck at 95%?
Cancelling should be considered only after confirming that the migration has genuinely stopped. If Exchange is still performing incremental synchronization or validation tasks, cancelling the migration may increase recovery time and require additional synchronization later.
4. Which logs should I review during Exchange Migration troubleshooting?
Administrators should review migration reports, synchronization status, retry counts, warning messages, mailbox-specific errors, authentication events, and connectivity-related logs. These details provide more accurate insights than relying solely on the migration progress percentage.
5. Does mailbox size affect the final migration stage?
Yes. Larger mailboxes generally require more time for folder validation, archive synchronization, consistency checks, and incremental synchronization. This often explains why migrations involving very large mailboxes appear to pause near completion.
6. Can network issues cause Exchange Migration to stall at 95%?
Yes. Network latency, intermittent connectivity, firewall restrictions, proxy interruptions, or bandwidth limitations can all delay communication between the source and destination environments, affecting the final synchronization stage.
7. How can I reduce the chances of migration delays?
Some recommended practices include:
- Assess the Exchange environment before migration.
- Clean up unnecessary mailbox data.
- Migrate users in manageable batches.
- Monitor migration reports regularly.
- Schedule migrations during periods of low user activity.
- Validate migrated mailboxes after completion.
These steps help reduce risks and improve the overall migration experience.
Conclusion
An Exchange Migration appearing to stop at 95% can be concerning, but it doesn’t always indicate a failed migration. In many situations, Exchange is completing essential background tasks such as incremental synchronization, mailbox validation, or consistency checks before marking the migration as complete.
The key to resolving these situations is understanding what the migration process is doing behind the scenes. By reviewing migration logs, monitoring synchronization activity, checking network connectivity, and investigating mailbox-specific issues, administrators can distinguish between normal processing and genuine migration problems.
Careful planning, routine monitoring, and following established migration best practices can significantly reduce delays and improve migration outcomes. Performing pilot migrations, validating prerequisites, and scheduling migrations during low-activity periods further contribute to a smoother transition.
For organizations looking for a reliable Exchange Migration Software, EdbMails provides features such as incremental migration, detailed reporting, mailbox mapping, resume capability, and support for multiple Exchange migration scenarios. When combined with proper planning and testing, these capabilities can help administrators manage Exchange migration projects with greater confidence and efficiency.
