Fix Google Workspace to Microsoft 365 Migration Stuck on Starting
Question details
A migration batch from Google Workspace to Microsoft 365 is stuck in the Starting status after a restart, previously showing a missing subscription error for one user.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating email, contacts, and calendar data from Google Workspace to Microsoft 365 via the Exchange admin center.
- Observed behavior
- The migration batch remains stuck on Starting indefinitely and fails to progress to the Syncing phase.
Ensure that every user included in the migration batch has an active and properly assigned Microsoft 365 subscription with an Exchange Online license before proceeding.
Allow Time for Syncing and Unlock Gmail Accounts
Sometimes large mailboxes or Google's bandwidth limits cause delays. Giving it time and ensuring the Gmail account isn't locked can resolve the stall.
Google Workspace imposes strict bandwidth limits on data exports. If these limits are reached, the migration batch may pause at the starting phase until the quota resets.
Give the migration batch up to 24 hours. It may automatically transition from Starting to Syncing once Google's bandwidth throttling passes.
Log in to your Google Workspace admin console to review the status of the specific users in the batch.
Check the affected user's account status. If the account is locked for security reasons or exceeding limits, unlock it from the user details page.
Ensure that IMAP access is fully enabled for the affected Gmail accounts so Microsoft 365 can pull the data.

Restart Migration via Classic EAC or PowerShell
If the modern Exchange admin center interface is unresponsive to the batch, using the classic EAC or PowerShell commands can force the process to start.
Migrate Data Using PST Export and Import
When server-side automated migration fails completely due to persistent errors, manually exporting and importing PST files is a reliable fallback.
Enhance Team Productivity with WPS Office
While resolving complex email migration issues in Microsoft 365, ensure your team stays productive with WPS Office. It's a lightweight, free, and highly compatible productivity suite that seamlessly handles Word, Excel, and PowerPoint files without the need for expensive subscriptions.

Frequently Asked Questions
Why does a Google Workspace migration batch stay on Starting?
This usually happens due to Google's bandwidth limits throttling the connection, a missing Microsoft 365 subscription for a target user, or a locked source Gmail account preventing data access.
How long should I wait for a migration batch to change to Syncing?
Depending on the mailbox size and Google's IMAP bandwidth restrictions, it can take anywhere from a few hours to 24 hours. If it remains stuck beyond a day, manual intervention or restarting the batch is recommended.
Does a missing Microsoft 365 license stop the entire batch?
Yes. If a user included in the migration batch does not have a valid Exchange Online license assigned, the batch may fail to start or halt entirely on the Starting phase until the license issue is resolved.
Can I migrate just the failed user using a PST file?
Yes. If a single user is causing the batch to hang, you can remove them from the batch, let the rest of the accounts sync, and manually export and import that individual user's data using a PST file.




