Google Workspace migration guide for UK SMEs
A practical sequence for moving email, files and users to Google Workspace without turning Monday into an outage post-mortem.
1. Discovery (week 0–1)
- Inventory mailboxes, aliases, shared mailboxes and mailing lists
- Map Drive / OneDrive / file-server shares and who owns what
- List DNS domains, MX, SPF/DKIM/DMARC and any third-party mail filters
- Identify blockers: legacy apps, printers using SMTP, finance tools tied to Outlook
- Agree success criteria: cutover window, training depth, rollback rules
2. Design & pilot
- Choose Workspace edition and OU / group structure
- Pilot with 5–10 users covering admin, finance and a power collaborator
- Test mail routing (dual delivery if needed), Drive sync and mobile
- Document leavers/joiners and MFA from day one
3. Cutover
- Freeze risky changes (new shared drives, major DNS edits) in the freeze window
- Final mailbox / Drive sync pass
- Update MX and verify inbound/outbound mail
- Communicate “where is my mail / Drive” with screenshots, not essays
- Watch queues for the first business day
4. Hypercare (2–4 weeks)
Expect calendar quirks, shared-drive permissions and “how do I attach from Drive?” tickets. Hypercare is intentional support density — not a surprise bill. Then move to steady-state Workspace admin and IT support.
See an anonymised outcome: professional services migration case study. Compare platforms: M365 vs Workspace.
Migration FAQs
Often 2–6 weeks end-to-end depending on mailbox volume, file estates and how many legacy apps need rewiring. Cutover itself is usually a short planned window.
Not always. Many firms migrate recent mail and archive the rest. Legal/compliance needs drive the decision — we make that explicit before cutover.