Fix a Disabled Cutover Migration Option for Exchange 2010 to Microsoft 365
Question details
Enable a cutover migration from Exchange 2010 to Microsoft 365 when the migration batch option is unavailable.

- Product
- Exchange Server 2010 and Microsoft 365
- Device & OS
- not provided
- Scenario
- An administrator is setting up a cross-forest migration and wants to create a cutover migration batch.
- Observed behavior
- The migration endpoint test succeeds but reports Support Cutover: False, and the Cutover Migration option is disabled.
Confirm that you have administrative access to Exchange 2010 and the Exchange admin center. Identify the Outlook Anywhere hostname and the migration endpoint used for the attempted batch.
Verify Outlook Anywhere and the cutover migration endpoint
Use this approach when the endpoint test succeeds but reports that cutover migration is not supported.
A successful connection test does not necessarily mean the endpoint meets the requirements for a cutover migration. Exchange 2010 cutover migration uses Outlook Anywhere to connect to the source server.
In the Exchange Management Console on the Exchange 2010 server, review the Outlook Anywhere configuration, including its external hostname and authentication settings. Confirm that the service is reachable from the internet.
In the Exchange Management Console, check the certificate assigned to the relevant Exchange services. Verify that it is valid, trusted by a public certification authority, and covers the Outlook Anywhere hostname.
In the Exchange admin center, open Migration and review the migration endpoints. Confirm that the endpoint is configured for Exchange Outlook Anywhere rather than a remote move or another migration type.
Test the corrected endpoint again in the Exchange admin center, then open Migration and start a new migration batch. Check whether Cutover Migration is available.

Review directory synchronization before a cutover migration
Check this prerequisite if directory synchronization is enabled or the cutover option remains unavailable after correcting the endpoint.
Work with Office files in WPS Office after your migration
WPS Office is a free, lightweight alternative with a familiar interface for working with Office files. Its format compatibility helps users move their document workflows smoothly, although it does not perform or repair Exchange mailbox migrations.

Frequently Asked Questions
Why does the endpoint test succeed while cutover migration is disabled?
The test may establish connectivity without confirming cutover support. Review the endpoint type, Outlook Anywhere configuration, certificate, and Microsoft 365 cutover prerequisites.
Which Exchange 2010 service does a cutover migration use?
A cutover migration uses Outlook Anywhere. Check its external hostname and authentication settings in the Exchange Management Console and verify that the service is reachable.
Does the Exchange certificate affect cutover migration?
Yes. Check the certificate assigned to the relevant Exchange services and confirm that it is valid, publicly trusted, and covers the Outlook Anywhere hostname.
Should I disable directory synchronization immediately?
Not without reviewing the impact. Check the tenant's synchronization status in the Microsoft 365 admin center, consult the current cutover prerequisites, and coordinate any required change with your identity administrator.
Can WPS Office fix the Exchange migration endpoint?
No. The endpoint and mailbox migration must be configured in Exchange and Microsoft 365. WPS Office can help users work with compatible Office documents separately.




