Migration
Google Workspace Email Migration Checklist
Quick Answer
A safe Google Workspace migration provisions all user accounts first, migrates mailbox data while the old MX records are still active, and only switches MX records to Google once data migration is confirmed complete.
The most common migration mistakes come from doing things in the wrong order - especially switching DNS before data has finished moving, which can create a gap where mail is neither in the old system nor the new one.
Common Causes
- MX records switched before mailbox data finished migrating.
- User accounts not fully provisioned before migration starts.
- No overlap period kept with the old provider in case something was missed.
- Calendar and contacts overlooked in a plan focused only on email.
Safe Troubleshooting Steps
- Inventory everything that needs to move: mail, contacts, calendar, shared mailboxes, aliases.
- Provision all Workspace user accounts before starting data migration.
- Migrate mailbox data while old MX records remain active.
- Verify migration completeness before switching MX records to Google Workspace.
- Keep the old provider active briefly as a safety net after cutover.
What to Verify
- All user accounts exist in Workspace before migration starts.
- Migration is confirmed complete before MX records change.
- A brief overlap period is planned after cutover.
When Professional Help May Be Useful
Migrations involving many mailboxes, large historical data, or multiple domains benefit from a written sequence reviewed in advance, since mistakes here are harder to reverse once DNS has switched.