Planning a Google
Workspace migration.
Protect identity, mail flow and user productivity through the transition.
A Workspace migration starts with identity and data inventory. Count active users, shared addresses, aliases, groups, mail volumes, calendars, files, devices and applications that send email before selecting an edition or cutover plan.
Select the edition from requirements
Compare storage, meetings, retention, endpoint management, security investigation and administrative controls. Do not select only on headline price. Record which requirements are mandatory and which can be introduced later.
Inventory identities, data and dependencies
Document users, aliases, groups, shared mailboxes, calendars and file ownership. Identify scanners, websites, accounting systems and applications that send mail through the current provider. Confirm access to the domain registrar and DNS before scheduling migration.
Secure and support the cutover
Plan multi-factor authentication, administrator roles, recovery methods, sharing defaults and email authentication. Communicate what users must do on phones and desktop clients. Define how migrated data will be validated and who handles missing items or delivery issues.
Migration checklist
- Users, aliases, groups and shared addresses
- Mail, calendar and file data volumes
- Domain, DNS and registrar access
- Applications and devices that send email
- Security controls and administrator ownership
- Cutover, validation, user communication and support