How to Verify a Successful Google Workspace to Microsoft 365 Migration

Why Migration Verification Matters

Gmail uses labels, and a single message can carry several at once. Microsoft 365 uses a strict folder hierarchy, where each item lives in exactly one folder. Every migration tool translates one structure into the other, and that translation is where item counts drift or folders land in the wrong place. A "migration complete" message only confirms the process ran to the end, not that every mailbox came through intact.

What Counts as a Successful Migration

Three conditions need to be met together: item counts match within an explainable margin, folder and label structure maps correctly, and metadata such as read status, timestamps, and sender information carries over intact. Matching counts with a broken folder structure is not a successful migration, even if the summary screen looks clean.

Common Verification Problems

1. Missing or Incomplete Items

   Symptom: item counts on the destination fall noticeably short of the source for specific mailboxes.

   Cause: usually throttling limits on the Google or Microsoft side interrupting a batch mid-transfer, or a permission scope that didn't cover every mailbox at runtime.

   Resolution: re-run the migration for the affected mailboxes only, not the entire batch.

2. Duplicate Items After Multiple Migration Passes

   Symptom: users see the same email or calendar event appear twice after a second migration run.

   Cause: re-running a migration without incremental tracking, so items that already transferred get copied again.

   Resolution: use a tool with incremental migration support, such as EdbMails, which tracks what's already been moved and transfers only new or changed items on later passes.

3. Folder or Label Mismatches

   Symptom: labels appear flattened, missing, or nested incorrectly in the destination mailbox.

   Cause: usually nested labels or labels containing special characters that didn't translate cleanly.

   Resolution: correct the mapping and re-run the affected folders. Manually moving items inside the destination mailbox risks further inconsistency and should be avoided.

Frequently Asked Questions

1. How long should verification take for a large migration?

   It scales with mailbox count and how deep you sample, not with total data volume. A batch of a few hundred mailboxes typically needs a few hours for report review plus manual spot checks, not a full re-review of every account.

2. What if item counts match but users still report missing emails?

   Check spam or junk folder filtering rules on the Microsoft 365 side first. A message can migrate successfully but land somewhere the user isn't checking.

3. Is a second full migration pass ever necessary after failed verification?

   Rarely. Most verification failures affect a subset of mailboxes or folders. Re-running only the affected scope, ideally through an incremental pass, avoids duplicating data that already transferred correctly.

4. Should verification happen before or after MX record cutover?

   Before. Verifying while the source system is still live and unchanged gives you a stable comparison baseline. Verifying after cutover means the source may already have new mail that was never in scope for the migration.