What should I try when a Google Workspace to Office 365 migration keeps failing?

November 17, 2026 5 answers
Asked by +8c!glimfob~

The built-in migration tool keeps failing on one user's files and a large shared folder. Excluding failed folders gets it further, but leaves me unsure what actually moved.

There's also a mailbox with around 100,000 messages, many of them automatic replies. Are there other tools or approaches worth trying without making a mess of the partially migrated data?

Answers

Tivloro-6p

I'd stop excluding folders for a bit and work from the failure reports. A completed run with exclusions isn't a complete migration. Make an inventory of what's excluded, then check the error details for a few representative failures before retrying just those folders.

Look at path lengths, folder depth and names that might not be accepted at the destination. Don't assume every failure has the same cause, though. Compare the source and destination after each retry so you have a record of what is still missing.

Reply to this answer
p.738+brindlevisor

MigrationWiz is worth evaluating for the problem mailbox and share. Rclone is another option to test for files. Neither should be pointed at the whole destination blindly just because part of the job is already there.

Try a small, representative folder first. Check how the tool handles files that already exist, and verify the result before expanding the scope. A local download and upload could also be an option for the share, but check the existing destination first and allow for the size of the transfer.

+8c!glimfob~:

Would you test against a separate destination first, or use the existing folder?

!6r~weldpiston:

A separate test destination is a safer way to learn the tool's behavior. Then test its handling of existing files on a small subset before touching the main destination.

Reply to this answer
_k49~weldmixer.6

For the mailbox, get approval to remove the unwanted automatic replies at the source if they really aren't needed. The item count is a problem even when the messages are small. Check whether your chosen tool can migrate in smaller batches, and keep track of which batches have been verified.

Also review the destination mailbox's archive policies before the move. Policies that act during migration can make it harder to reconcile where messages ended up.

Reply to this answer
Kex

Don't forget the stuff outside mail and files. Check which applications use Google for single sign-on and plan how those users will authenticate after the switch. GAM can help identify active SSO bindings for review.

Reply to this answer
MEXLARO+7c

If the built-in file tool is failing without useful diagnostics, open a support case and include the reports and error details. In parallel, test another tool on a limited set rather than waiting on repeated full retries. Email and files may need different migration approaches.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions