A successful Exchange-to-Google Workspace move needs staged copying, checks, and a rollback plan. Do not rush the MX change.
Map the process and prevent split mail
Build the runbook before production. Include inventory, a pilot, historical migration, delta syncs, a final sync, MX cutover, and reconciliation.
A safe MX change is the last routing step. It is not the first migration step. Keep Microsoft Exchange available until Gmail delivery and mailbox checks meet written acceptance rules.
Choose the migration model
Use a staged approach when users must work during the move. Reserve a full cutover for very small tenants with limited history and an acceptable outage.
Changing MX records after only a partial copy splits new mail. Mail then lands in Exchange and Gmail, creating a rushed cleanup project.
| Approach | Best fit | Mail interruption | Main risk |
|---|
| Staged with delta syncs | 10+ mailboxes or active teams | Usually 15 to 60 minutes | Poor validation |
| Weekend cutover | Very small, simple tenant | Several hours possible | Missed late-arriving mail |
| Long coexistence | Complex apps or phased teams | Low, but longer project | Routing loops and duplicates |
Set measurable acceptance rules
Create one acceptance row for each mailbox. Cover message count, oldest and newest dates, calendars, contacts, failed items, exceptions, and one accountable owner.
Critical executive, finance, legal, and shared mailboxes need zero unexplained errors. That rule makes the final go or no-go decision clear.
Prepare identities, access, and pilot data
Create destination accounts first. Then prove source access before the production batch.
Inventory special objects first
Export user, shared, and archive mailboxes. Also export aliases, groups, delegation, rules, public folders, and PST files.
Map each source address to a Google Workspace user, group, alias, or written exception. Flag large attachments, encrypted mail, legal holds, journaling, and retention rules.
The common mistake is missing shared mailboxes and old PST files. These items often surface after the MX change.
Test the right tool on real mail
Use Google Data for simple mail transfers. Use GWMME for Exchange mail, calendars, and contacts.
Assess Google Workspace Migrate or third-party tools for PSTs, archives, detailed reports, or complex retries. Pilot three to five representative mailboxes before you commit.
| Tool path | Typical scope | Cost pattern | Use it when |
|---|
| Google Data | Basic mail transfer | Included with Workspace | Low volume and simple mailboxes |
| GWMME | Exchange mail, contacts, calendars | Google-administered path | Exchange-specific move with pilot testing |
| MigrationWiz or similar | Complex batches and reporting | Per-user license, often $10 to $20+ | PST, archives, support, detailed retries |
For an Exchange to Google Workspace move, split the source checklist by platform. For Exchange Online, check the migration account permissions.
Check modern authentication support and Exchange Web Services access. Also check approved Conditional Access exclusions for the migration window.
For Exchange Server on-premises, check the EWS virtual directory. Check for a trusted TLS certificate and DNS resolution from the migration host.
Check firewall rules for required endpoints only. Use a service account with the least access needed.
Test one standard mailbox, one large mailbox, and one shared mailbox before you set the production date.
A successful login is not enough: the pilot must prove access to real mail, calendars, and contacts without access-denied or throttling errors.
Run deltas, cut over, and prove delivery
Start the historical migration while Exchange remains the mail authority. Then run incremental syncs until the cutover window.
Freeze changes for the final delta
Lower MX TTL to 300 seconds at least 24 hours before cutover, where possible.
During the final delta, pause mailbox moves and delegation changes. Pause inbox-rule edits and bulk imports too.
Keep Exchange available until checks are complete. This avoids losing late changes.
Change mail flow and validate it
Change MX records only when the final delta has no unexplained high-risk errors. Test inbound and outbound external mail.
Test aliases, SPF, DKIM, DMARC, and TLS. Compare Exchange and Gmail counts by folder and date range.
Check attachments, sent dates, recipients, calendars, contacts, shared mailboxes, and groups. Do not rely on a single recent-message test.
Keep rollback ready for 48 hours
Define rollback triggers before the window. Triggers include inbound failure, priority-mail gaps, identity failures, and too many unresolved exceptions.
Keep Exchange Online or Exchange Server available for 48 to 72 hours. Avoid untested dual delivery.
Estimate the project from measured transfer speed. Do not estimate from mailbox count alone.
Record total source size and mailbox count. Record the largest archive and the pilot transfer rate.
Include Exchange throttling, concurrent jobs, failed-item retries, and available bandwidth. A 2 TB tenant at 20 GB per hour needs at least 100 transfer hours.
That estimate excludes retries and the final delta sync. Lower concurrency can improve reliability, but it extends the window.
Schedule historical copying well before cutover. Reserve separate time for the final delta sync and mailbox checks.
Recalculate after the pilot. Mailboxes with many attachments and archives often move much slower than the tenant average.
Turn mailbox checks into a signed, repeatable record. Do not use a visual spot check alone.
For each priority mailbox, capture source and destination message counts. Capture oldest and newest message dates too.
Record folder-to-label mapping and attachment samples. Record calendar and contact migration results.
Set tolerances before the move. For example, allow zero unexplained missing messages in executive, finance, legal, and shared mailboxes.
Set an agreed failed-item limit for standard users. Do not leave this limit undefined.
Sample several date ranges, including recent mail and old archives. A latest-date check can miss old gaps.
Your acceptance rules should name the reviewer and exception owner. They should also show retry results and the final approval date.
What people ask
Can I migrate Exchange with no lost email?
You can greatly reduce risk with pre-stage copies, delta syncs, a freeze, and reconciliation. No method proves zero loss without source and destination checks.
How long does Exchange to Google take?
Small tenants may finish in 2 to 7 days. Large archives can take weeks.
Should I change MX before migration?
No, change MX only after historical and final delta checks pass. Keep Exchange online during the validation period.
Does Gmail keep Exchange folder structure?
Gmail converts most folders into labels. The visual structure can differ.
Can shared mailboxes migrate to Google Workspace?
Yes, but recreate delegated access, send-as rights, and group behavior separately. Test each shared address before cutover.
What causes missing messages after migration?
Common causes include throttling, permissions, corrupt items, size limits, skipped folders, and late mail. Pilot logs usually show which cause applies.
How much does an email migration cost?
Basic Google options may be included. Third-party licenses often start around $10 to $20 per mailbox.
Can I roll back after changing MX records?
Yes, if Exchange remains online and you restore the previous MX records. Keep the source available for 48 to 72 hours.
Close the project only after reconciliation
Close only when each critical mailbox meets its acceptance row. Each exception also needs a written disposition.
Keep migration reports, DNS records, and source-access evidence. These records support later checks and audits.
Do not use this runbook alone for Health Insurance Portability and Accountability Act, General Data Protection Regulation, or legal-hold records. Confirm retention, eDiscovery, archive access, and chain-of-custody controls before moving or deleting source data.
A verified Exchange-to-Google Workspace move ends with evidence. It does not end with a DNS update.
Keep the source intact until data checks, mail-flow tests, and the rollback period end.
Learn more
Here are some additional resources on this subject:
