1. Migrating to Office 365 from Google mail and exchange

2. Introduction Session Objectives:
Show how to migrate from Google Mail (IMAP) and on-premises Exchange to a single Office 365 tenant while using:
Azure AD Sync
Hybrid Exchange environment
3rd Party IMAP Mail Migration product
1) Account Provisioning - understand the options and challenges
2) Mail Flow – how this works and what to be aware of during coexistence
3) Migrating Messaging data – both from Google Mail (IMAP) and Exchange
Takeaway:
Whatever environment(s) you are migrating from, getting to Office 365 is possible and can be relatively straight forward – with enough planning…

3. Background
Overview:
Project Goal - The company was looking to migrate all users to a single Cloud Messaging solution – in this case Office 365.
History – a section of the business had been migrated to Google Mail while keeping the ‘back office’ users on Exchange
Existing Pain Points:
Google Mail users were not able to:
View a complete company address book
Send s to on-premises Distribution Groups
Other issues – company specific:
Users across environments cannot view Availability information, schedule meeting rooms, etc.

4. High-level environment Overview
A single Google Apps tenant – using @gapps.company.com
A single AD domain / Exchange 2007 Organization
Multiple Exchange servers in Australia and across the APAC regional sites
Google Mail users exist as MailEnabled user objects in AD (with a target address of
Symantec Cloud use for mail delivery (and journaling)

5. Initial mail flow

6. Main challenges
Provisioning of Google Mail User Accounts into Office 365 – two options:
Use the 3rd Party Tool to provision the users into Office 365
Use AADSync to populate Office 365 with both the Google Mail User accounts and Exchange Mailbox users
Mail Flow – ensure mail delivery works during the coexistence phase between:
Google Mail tenant
On-premises Exchange Organization
Office 365 / Exchange Online
Migration of messaging data:
Google Mail (IMAP) = use a 3rd Party Migration Tool - (MigrationWiz)
Exchange = use a Hybrid environment and Migration Batches

7. Account provisioning options
Microsoft Office365
11/27/2018
Use the 3rd Party Tool provision IMAP (Google Mail) users into Office 365
These tools can provision users directly into Office 365 based on the IMAP (Google Mail) mailbox
Increases complexity if you want to use Microsoft’s Directory Sync tools long term.
Only option if there are not AD objects for the IMAP users. 1
Vendor Recommended
Use Azure AD Sync to provision only the Exchange Mailbox users into Office 365
Microsoft recommends to use their Directory Sync tools to provision accounts into Office 365.
It is possible to use a 3rd party tool such as MigrationWiz to provision and migrate Exchange users. 2
Vendor Recommended
Use Azure AD Sync to provision both the Google Mail & Exchange Mailbox users into Office 365
This is possible provided you understand the limitations and constrains of the 3rd party tools and
Microsoft’s Directory Synchronization tools and the Office 365 tenant in a Hybrid environment.
This can simplify account provision and account management during coexistence. 3
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Vendor Says…

9. 3rd party complexity… When following the vendors recommendations:
Required for a unified GAL in Office 365
Provision all Google Mail users via 3rd Party Tool (MigrationWiz)
Challenges around who is active and should be provisioned – 3rd party license is used
Filter out all Google Mail user accounts using ‘attribute filtering’
extensionAttributeX = ‘No-Sync’
Provision all Exchange mailbox user accounts using AADSync
Additional challenges
AD account for Google Mail users must come to be ‘in-scope’ of AADSync once migrated
AADSync must then perform a ‘soft-match’ of the AD account and existing Office 365 object

10. Keeping it ‘simple’
Use Azure AD Sync to provision all objects to Office 365 – both Exchange Mailbox users accounts and Google Mail ‘MailEnabled’ user accounts
MigrationWiz can still migrate data to existing objects in Office 365
What is the 3rd party vendor talking about???
3rd Party Migration tools can’t work with objects which have the “msExchMailboxGUID” attribute populated in AD and then synchronized to Office 365
Further reading:

11. Mail flow details
3rd Party solution or device provides mail routing options and control
If the MX records point directly to Google, forwarding can be configured post migration
Hybrid with Centralized Mail Routing configured
Best to keep the existing mail flow path until the migration is complete
Environment Specific’s
Symantec Cloud synchronized members of the ‘Google AD GroupX’ groups
s for members of these groups is delivered to the Google Mail tenant
All other s are delivered to on-premises Exchange
Journaling requirement to Symantec Cloud (Transport Rule in Office 365)
An additional ‘migration’ SMTP address required for Google Mail forwarding – added as an additional proxy address

12. Mail flow during coexistence

13. Migration details – Google mail
Use a 3rd party product – the default IMAP migration option only migrates (no contacts and calendar data)
MigrationWiz from BitTitan
Great web-interface for creating migration projects and monitoring/reporting/troubleshooting
.CSV file import to create large migration batches
Ability to automate the process using PowerShell Scripts (PS module available)
Environment Specific’s – scripted as part of the migration:
Add to proxyAddresses of the MailEnabled user object in AD
Remove the MailEnabled user account from ‘Google AD GroupX’ – changes inbound mail flow
Change targetAddress on MailEnabled user object to
Add as a forwarding address to the Google Mailbox
Other; Assign Office 365 license, set the –UsageLocation, -TimeZone, and -Language

14. Prep – before the Migration
Attribute changes
Starting State
Prep – before the Migration
Migration / Switch

15. Migration details – Google mail
Template headers for .CSV input file:
MigrationWiz PowerShell cmdlets to create source-target connectors:
New-MigrationWizMailboxConnectorSettingsGoogle
New-MigrationWizMailboxConnectorSettingsMicrosoftOffice365
Migration Throughput:
Averaging approx. 300 mailboxes per day
Max throughout attempted mailboxes in a day
Average Google Mailbox Size MB

16. Migration details – Exchange
Standard Hybrid Mailbox Moves – Migration Batches
Template headers for .CSV input file:
Environment Specific’s
Requirement to minimize WAN utilization and optimize the path for migration data using local internet links at the regional sites
Additional control available when using multiple Hybrid servers and Migration End-Points

17. MULTIPLE migration end-points

18. Summary – Questions???
Mail flow, mail flow, mail flow – plan this thoroughly before starting Where possible, use the Microsoft Directory Synchronization Tool – it will probably be your long-term synchronization tool. Directory Synchronization from Active Directory to Office 365 is required for ADFS. Use a 3rd Party Migration tool for IMAP migrations to migrate all messaging data (MigrationWiz works great) Remember - Follow standard Microsoft ‘best practice’ when implementing Directory Synchronization and the Hybrid environment: run IdFix, open the required ports, ensure Outlook Anywhere is configured correctly, run the ‘Remote Connectivity Analyzer’, etc.