Mailbox migration from on-prem to cloud FailedStuck

Question

I have an on-prem Exchange mailbox that is in a FailedStuck status and then reverts to an InitialSeeding status. It repeats over continuously for a number of days, but never manages to sync to Office365 I dont find too many articles explaining what the FailedStuck status refers to and how to resolve. Any pointers would be great!

Answer 1

Hi @Patr_UK ,

FailedStuck status is a status in the process of Exchange mailbox migration. It usually means that errors or problems occur during migration, resulting in the migration cannot continue. This status may be caused by network connection problems, Exchange server problems, or other reasons.

As Andy said, in some cases, using new move requests may help solve the problem of migration failure. And it is understood that when you delete the original move request and re-create a new request, the system will continue to move from the position of the last failure.

Besides, you may be able to try other fault exclusion steps, such as checking if there are any errors in the server log or other instructions that may cause problems. In addition, you could try to restart the Exchange server. There may also be a problem with the network connection between the local Exchange server and the Office 365. You may need to check your network configuration and ensure that all the necessary ports have been opened, and there are no firewalls or other security measures to prevent connections.

Hope that the above information can help you solve the problem!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread.