01 / PLANNING NOTE
Separate users, domains, and tenants
Record the number of users, the domains they use, and the separate environments that administrators manage. Those are different counts. If ownership is unclear, identify who can confirm it before planning changes.
02 / PLANNING NOTE
Describe the intended destination
A new business may need a new environment. An existing business may need better management of its current tenant. An acquisition may need consolidation, continued separation, or a staged transition. Make the desired business result explicit.
03 / PLANNING NOTE
Inventory workloads before choosing a route
Microsoft's migration documentation separates different sources and workloads. Email, files, shared collaboration, identity, and connected applications can have different requirements. Google's migration guidance also describes supported approaches for moving into Workspace. Verify the relevant workload support with the project team.
04 / PLANNING NOTE
Plan for people and dependencies
Identify shared mailboxes, service accounts, integrations, device management, and external collaborators. Agree how changes will be communicated and how essential business workflows will be tested.
05 / PLANNING NOTE
Make completion measurable
Define the validation checks, exception owners, handover information, and support arrangements. A completed transfer job is one piece of evidence; the business also needs its users and workflows operating as agreed.
Reference material
Microsoft migration documentation
Confirm current provider requirements during scoping.