Migrating from Google Workspace (formerly G Suite) to Microsoft Office 365 is a significant shift for many organizations seeking better integration with Microsoft tools, improved compliance, or enhanced collaboration features. While tools like Microsoft’s native migration tool, Google Workspace Migrate can simplify the process, it’s not always seamless. One common challenge: skipped items during migration.
Skipped emails, files, folders, or calendar entries can lead to data loss, confusion, and post-migration headaches. Knowing how to identify these skipped items from migration logs is essential for a successful and auditable migration.
Why Items Get Skipped During Migration
Before diving into log analysis, it’s important to understand why items may be skipped:
- Corrupt or unsupported file formats
- Too large attachments exceeding platform limits
- Permissions errors (e.g., user doesn’t have rights to a folder or email label)
- Time-based filters (e.g., only emails after a certain date were selected)
- Label/folder conflicts between systems
- Rate limiting or throttling by Google or Microsoft
Step-by-Step: Identifying Skipped Items from Migration Logs
1. Use Built-in Reporting from Your Migration Tool
Most enterprise-grade migration tools provide downloadable migration reports. These typically include:
- Success status for each item
- Failure reasons
- Skipped item counts
Look for logs with fields like:
Status = SkippedReason = Unsupported item typeorAccess denied
Microsoft Migration Tool: Check logs in the Exchange Admin Center or download detailed CSVs
Tip: Export logs to Excel and use filters to analyze skipped items quickly.
2. Manually Review Microsoft 365 Import Logs
If you’re using PowerShell or Microsoft Exchange Admin Center (EAC):
- Go to Exchange Admin Center > Migration > Batch Details
- Click on the completed batch.
- Download the report CSV.
- Look for columns like:
StatusDetailErrorMessageSkippedItemCountFailureReason
For large batches, use Excel filters or Power BI for deeper analysis.
3. Review Google Workspace Audit and Vault Logs (Pre-Migration)
Compare what should have been migrated:
- Use Google Vault or Google Workspace Admin Audit logs to get:
- Number of emails per user
- File storage per user (via Drive Audit)
If there’s a significant difference post-migration, it may indicate skipped or incomplete transfers.
4. Use PowerShell for Deeper Investigation (Post-Migration)
For emails and calendar items in Office 365, PowerShell can help:
Get-MailboxStatistics -Identity user@domain.com | Select TotalItemSize, ItemCount
Compare this with Google Workspace data to find discrepancies.
5. Monitor Skipped Items Using Alerts or Logs Dashboards
For enterprise projects:
- Set up log dashboards using tools like:
- Power BI
- Google Data Studio
- Log Analytics in Azure
- Automate reporting on:
- Skipped items
- High failure rate mailboxes
- Users with zero migrated files (indicating permission or quota issues)
Common Skipped Item Types and How to Handle Them
| Skipped Item Type | Reason | Fix or Workaround |
|---|---|---|
| Google Docs/Sheets | Format not compatible | Convert to Microsoft format before migration |
| Large Emails/Attachments | Exceeds Office 365 limits | Split or compress attachments |
| Shared Drives | Not mapped correctly | Use dedicated Shared Drive migration tools |
| Calendar Recurrences | Complex recurrence rules | Manually recreate in Outlook if needed |
| Labels/Folders Conflicts | Gmail labels vs Outlook folders mapping | Customize label-folder mapping settings |
Perform a pilot migration before full-scale deployment to detect skipped item patterns early.
Communicate with end users: Let them know some items may not migrate perfectly.
Backup before migration: Always keep a backup of Google Workspace data (e.g., via Takeout or a backup solution).
Conclusion
Migration is more than a checklist—it’s a data integrity operation. Identifying skipped emails, files, and folders is vital to ensuring that no critical data is lost during your transition from Google Workspace to Office 365.
By understanding how to analyze and interpret migration logs, you can resolve issues proactively and ensure a smooth transition for your organization.