Google email migration
Migrate email to Google Workspace
IT Systems migrates business email from hosting mail, cPanel, Zimbra, Microsoft 365 or any IMAP system to Google Workspace, minimising send/receive disruption and preserving important mailbox data.
Old mail system
Hosting, cPanel, Zimbra, Microsoft 365.
Data sync
Mailboxes synced on a planned schedule.
Cutover
MX switch and email security configuration.
Google Workspace migration checklist
| Phase | What to check | Goal |
|---|---|---|
| Before migration | User list, mailboxes, storage, aliases/groups, admin rights and backup. | Understand the data and risks before moving. |
| Data sync | Choose the right migration method for the source, test sample mailboxes and verify data. | Reduce the risk of missing mail or wrong folders. |
| DNS cutover | Point MX to Google, configure SPF, DKIM, DMARC and test sending/receiving. | New mail flows through Google Workspace at the right moment. |
| After migration | Set up Gmail on devices, guide users, verify data and hand over. | Users work smoothly after the switch. |
Email sources we can migrate
Hosting mail/cPanel
Move mailboxes from common email hosting to business Gmail.
Zimbra/IMAP
Plan migration batches by mailbox size and the state of the old system.
Microsoft 365
Move from Exchange Online to Google Workspace when the business changes ecosystem.
6-step Google Workspace email migration process
Moving email to Google Workspace for an office of 10–100 people usually takes 1–3 weeks. Most of the risk lies in preparation and the MX switch timing, not in the migration tool itself.
| Step | Main tasks | Suggested time |
|---|---|---|
| 1. Assess the old system | List mailboxes, sizes, aliases, groups, forwards and synced devices; identify the source (hosting mail, Zimbra, Exchange, Microsoft 365) | 1–2 days |
| 2. Prepare domain and DNS | Verify the domain, lower MX TTL, prepare SPF, DKIM and DMARC | 1 day |
| 3. Create users and permissions | Create accounts, groups to replace shared mailboxes, enable 2-step verification, assign admin roles | 1 day |
| 4. Initial data migration | Run a migration tool (Data Migration Service or equivalent) for old email, calendars and contacts; pilot with 2–3 users first | 2–7 days depending on size |
| 5. Cutover | Switch MX after hours, run a delta sync for new mail, test sending and receiving internally and externally | One evening |
| 6. Handover and monitoring | Train users, set up phones, monitor spam placement and authentication errors for 7 days | 1 week |
Checklist before switching MX
- A complete list of mailboxes, aliases and forwards in use.
- MX TTL lowered at least 24 hours before cutover.
- A pilot migration for 2–3 users confirmed complete.
- Users know their new passwords and have 2-step verification on.
- The company, and key partners if needed, know the switch time.
What to check in the first 7 days after cutover
- Whether outgoing mail lands in spam (check SPF, DKIM, DMARC).
- Mail still arriving at the old system because of stale DNS or forwards.
- Devices, scan-to-email printers and accounting software sending via SMTP have been reconfigured.
- Keep the old system for about a month to cross-check before cancelling it.
Google Workspace migration FAQ
Will we lose email when moving to Google Workspace?
With a proper assessment and migration process, old data is synced on schedule and new mail arrives in Google after cutover.
Can large mailboxes be migrated?
Yes, but quota, connection speed, source limits and batch sizing need to be checked.
What do users need to do after migration?
Users sign in to Gmail/Google Workspace, set up their devices and check their data after the move.
Cutover plan that minimises disruption
Email migration is not just copying data. The key is choosing the cutover time, lowering DNS TTL, testing send/receive and preparing user guidance right after the switch.
| Timing | Tasks | Owner |
|---|---|---|
| 3–5 days before | Check admin rights, mailbox list, backup; lower DNS TTL if needed. | IT Systems + the company’s domain admin. |
| Before cutover | Sync data, test sample accounts, prepare Gmail sign-in guidance. | IT Systems. |
| At cutover | Point MX to Google, check SPF/DKIM/DMARC, test internal and external mail. | IT Systems. |
| After cutover | Support users, check for missing data, fix devices and hand over administration. | IT Systems + company contact. |
Need to move your email to Google Workspace?
Send us your current mail system, number of users, mailbox sizes and domain, and IT Systems will propose a suitable migration plan.
