Google Workspace Domain Migration Guide
Know what you’re moving before you migrate.
Moving users and data is only part of a successful Google Workspace migration. You also need to account for ownership, permissions, external sharing, Groups, Shared Drives, suspended users, and files your organization may not actually own.
This practical guide helps Google Workspace administrators audit the source environment, plan the migration, validate the destination, and identify what could be left behind.
Why Google Admins
Need This Guide?
A migration can technically complete while leaving access problems behind. A file may arrive with the wrong owner. Group-based permissions can stop working when identities change. Users may depend on files owned by external collaborators or personal Gmail accounts. Suspended accounts can contain data that still needs to be retained.
- Identify users, OUs, Groups, ownership, external sharing, Shared Drives, inactive accounts, suspended users, and sensitive data.
- Plan for Gmail, My Drive, Shared Drives, Calendar, Contacts, users, Groups, permissions, and other Workspace data.
- Decide how users, Groups, file ownership, Shared Drive membership, and permissions should work in the destination.
- Find business content owned by partners, contractors, former employees, or personal Gmail accounts before source accounts are retired.
- Validate the migration and review after cutover