- IMAP server
- mail.example.com
- Port
- 993 · SSL/TLS
- Username
- full address
- Password
- mailbox password
Exchange Server → Google Workspace
Migrate Exchange Server to Google Workspace
On-premise Exchange to Google Workspace runs over IMAP, which sets the boundary up front: messages and folders move, calendars, tasks and public folders do not — they live outside the protocol.
- IMAP server
- imap.gmail.com
- Port
- 993 · SSL/TLS
- Username
- full address
- Password
- app password
What breaks on this particular pair
- IMAP is disabled by default on Exchange Server; the Microsoft Exchange IMAP4 service must be started and configured.
- Internal Exchange certificates are often issued for an internal name — enable accepting unverified certificates.
- Public folders are not reachable over IMAP and need a dedicated migration tool.
- Calendars, tasks and contacts export separately and import into Google by hand.
- Google Workspace quota is shared with Drive — total the volume in advance.
FAQ
Common questions
Do Exchange public folders migrate?
No. Public folders are not user IMAP mailboxes and the protocol cannot reach them. Use Microsoft tooling or a PST export instead.
How do I move a hundred mailboxes?
With a CSV batch: one row per user, jobs run through a queue, and you get a consolidated report with per-mailbox message counts.
Related routes
Other directions
Find out how big your mailbox is. It costs nothing.
Connect two servers, look at the size and decide. Or take the client and keep everything on your side.
Code on GitHub · built on imapsync · no sign-up