Google has a 3-phase deployment methodology for Google Workspace, starting with Core IT where a small group pilots the deployment by creating the technical design and testing setup options. Early Adopters involves rolling out the deployment to 5-10% of the workforce to validate the migration approach and test change management plan. Global Go-Live is the final stage.
When planning for a Google Workspace deployment, it's essential to consider migrating and syncing resources such as groups and calendars. Several options include individually, bulk via CSV or using Google Cloud Directory Sync (GCDS).
GCDS is a one-way process and requires installing and configuring the tool. Password Sync is another tool specifically designed for passwords, installed on each Domain Controller to push new passwords to their managed Google Account.
Google Workspace has three different types of groups - admin-managed, user-managed, and personal. Admin-managed groups can be synced via GCDS while user-managed and personal groups are not.
During the deployment process, there are three different mail delivery scenarios, including legacy mail forwarding to Google, routing messages from unknown users to a special mailbox or external server, and Direct, Dual, or Split Delivery.
There are two main approaches to data migration during a Google Workspace deployment - server-side migration and client-side migration. The best approach depends on the data's location and how much migration control is required.
Coexistence refers to when an organization has both Google Workspace and a legacy platform running at the same time. There are different types of coexistence, including short-term and long-term. Long-term coexistence is complex and not recommended.
Options for user migration during the first two phases include migrating nothing, minimal migration, or complete migration. The best option depends on the organization's needs, with migrating nothing considered the best practice.
GWMME is a server-side migration tool that migrates mail, calendar, and contacts from Exchange. Best practices include co-locating migration servers with mail servers for improved performance and actively monitoring for migration failures.
During the data migration strategy, determine what data will be migrated at each deployment phase to save time and reduce issues. The choice may include partial or complete migration of mail, calendars, and contacts.