Migration software
Google Workspace Migration for Microsoft Exchange
Suggested in 2 of our migration playbooks, mainly for Email and domains. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What it handles
The limits of the built-in tools that Google Workspace Migration for Microsoft Exchange gets around, as covered in our playbooks.
cPanel email to Google Workspace migration
- Plan imports in groups of 100 usersMigrates IMAP mailboxes listed in a user CSV, up to 1,000 users per file. Each row holds the source login and password.
- Check the certificate and firewall before import dayGoogle's recommended IMAP migration tool when the server has no trusted certificate or is not reachable from Google services.
- Data import tool: one import holds up to 100 IMAP users, and you must exit it (which deletes its reports) before starting the next.Google's installable tool. Takes up to 1,000 IMAP users per CSV file, and runs on a Windows computer you provide.
- Data import tool: it connects from Google's servers, so it fails if the certificate is not trusted or the host blocks Google.Google's recommended tool when the server has no trusted certificate or Google cannot reach it. Moves email and labels only.
IMAP email to Google Workspace migration
- Work in waves of 100 users and keep the reportsMigrates IMAP mailboxes listed in a user CSV, up to 1,000 users per file. Each row holds the source login and password.
- The data import tool needs a server Google can reach, with a trusted certificate and email-address sign-ins.Google's recommended tool for servers without a trusted certificate, on internal networks or using plain usernames.
- Data import tool: one import holds up to 100 users, and you must exit it (which deletes its reports) before starting the next.Google's installable tool. Takes up to 1,000 IMAP users per CSV file, and runs on a Windows computer you provide.
How it handles key settings
From the settings checklists in our playbooks: what Google Workspace Migration for Microsoft Exchange carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| What the import moves, and what it leaves behind | Also moves email and labels only from an IMAP server. | cPanel email to Google Workspace migration |
| Users per import, and the reports | Takes up to 1,000 IMAP users per CSV file, on a Windows computer you provide. | cPanel email to Google Workspace migration |
| Mailbox passwords and IMAP access | Google recommends it when the old server signs in with plain usernames instead of email addresses. | cPanel email to Google Workspace migration |
| Whether Google can reach the old server | Google's choice for servers with no trusted certificate or on an internal network. It runs on a Windows computer you provide. | cPanel email to Google Workspace migration |
| What the import moves, and what it leaves behind | Also moves email and labels only from an IMAP server. | IMAP email to Google Workspace migration |
| Users per import, and the reports | Takes up to 1,000 IMAP users per CSV file, on a Windows computer you provide. | IMAP email to Google Workspace migration |
| Mailbox passwords and IMAP access | Google recommends it when the old server signs in with plain usernames instead of email addresses. | IMAP email to Google Workspace migration |
| Whether Google can reach the old server | Google's choice for servers with no trusted certificate or on an internal network. It runs on a Windows computer you provide. | IMAP email to Google Workspace migration |
Tools for the same jobs
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.