Migrate G-Suite to Exchange Online: 5-7 Wks Impl.

Extended explanation: In the first step, adjustments are made to the source and target systems. The creation of administrative service users in G-Suite and Exchange Online as well as authorization assignments on various Google APIs create the necessary prerequisites for coexistence and migration. After that, the coexistence is set up technically, i.e. routing domains, alias addresses, MX records, etc. are created and tested. This is followed by the setup of the migration endpoint on Exchange Online, through which the data migration will take place later. During the Exchange migration, which takes place in freely definable batches, data (mail, contacts, calendars) is migrated from G-Suite to Exchange Online, whereby the user:in continues to work under G-Suite. At the (manual) end of the migration, the actual conversion takes place, from which the user no longer works productively with G-Suite, but with Exchange Online. Note: there are technical limitations during data migration. The following data cannot be migrated:

• E-mails: out-of-office settings, automatic replies, filter rules or otherwise. Regulate
• Meeting rooms: no migration possible
• Calendars: shared calendars, Hangout links, appointment colors
• Contacts: entries beyond three email addresses per contact, Gmail tags, contact URLs, custom tags

The migration of Groups (if not used as a distribution list, but as a collective mailbox) is done manually, because there is no automatic migration path here. After all users have been migrated, the migration and coexistence environment is dismantled in a controlled manner. This includes eliminating service users, revving permissions, and changing central MX records. Furthermore, the SPF record is adapted and exchange online protection (EOP) is activated and set up.

Agenda

• Prep for Mail Migration
• Coex. G-Suite/ExO
• Exchange Migration
• Offboard G-Mail
• Hypercare-Support Exchange/Outlook
• Exchange Online Protection