Google Workspace Migration

Fix Google Workspace to Microsoft 365 Migration Stuck on Starting

Khadija KhanKhadija Khan Nov 2, 2026 869 views

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.

How to Fix Google Workspace to Microsoft 365 Migration Batch Stuck on Starting
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.
Before you start

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.

Solution 1Recommended

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.

1
Wait for bandwidth limits to reset

Give the migration batch up to 24 hours. It may automatically transition from Starting to Syncing once Google's bandwidth throttling passes.

2
Access Google Admin console

Log in to your Google Workspace admin console to review the status of the specific users in the batch.

3
Unlock the Gmail account

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.

4
Verify IMAP settings

Ensure that IMAP access is fully enabled for the affected Gmail accounts so Microsoft 365 can pull the data.

Allow Time for Syncing and Unlock Gmail Accounts
Data Throttling: Google typically limits IMAP bandwidth to 2.5 GB per day for downloads. If a mailbox is exceptionally large, the batch may appear stuck while waiting for the daily limit to refresh.
Free Microsoft Office alternative

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.

Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Free to download and use core features with no mandatory subscriptionLightweight design ensures smooth performance on all devicesFamiliar user interface reduces team onboarding and training time
microsoft office alternative - wps office

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.