g suite migration pre-requisites · [email protected]...
TRANSCRIPT
All steps Performed by:
Abdul Farooque Arian (MCT&MCSE)
G Suite migration pre-requisites G Suite to O365 Migration provides the pre-requisite steps on for G Suite migration. Read it to learn
how to migrate mailboxes from G Suite to Office 365. You must be a global admin in Office 365 to
complete the migration steps.
The following list contains the migration tasks given in the order in which you should complete them
for G Suite to O365 migration
• Create service account in G Suite: Login as super admin in G Suite and create a project
a.Login>https://console.developers.google.com/iam-admin/serviceaccounts
I have already a Project> But Create a new one for this Guide. Click New Project
b, Name Your Project > Browse and Select your Parent Organizational Unit (Initial Domain)and Click
Create
C. Now Create Service Account in this New Project
D. Name this service Account>Click Create>
E. On the Service account permissions (optional) screen, click Continue.
F. Under Create key (optional) click Create Key.
Under Key type, make sure JSON is selected, and then click Create.
G. Keep track of the JSON keyfile that is automatically downloaded, as you will need its filename
during the steps under Create a migration endpoint in Office 365. Click Done.
F.
Click on the Email for the Service Account you just created to enter the details page.
Alternately, you can click the dots under the Actions column and click on the Edit action.
On the Service account details page, note the Unique ID. This is the ClientId that you will
provide later in the instructions for Grant access to the service account for your Google
tenant.
104754753970230334661
G.
If you see an area that says Show Domain-Wide Delegation, click to expand that
section. Then, enable the checkbox for Enable G Suite Domain-wide Delegation, and
then click Save.
At This Point Save May Not Work and you will get an error>
Correct the Highlighted Fields.
H. Click > Configure Consent Screen
I.
Click Internal on Next screen and Click Create>
J. On Next Page>Name the App and >Click Add Scope and Select all scopes
Click Save at the End of the Page> and save the Consent Screen.
This will be the final Look of the OAuth Consent screen
K. Go back to the Service Account>
https://console.developers.google.com/iam-admin/serviceaccounts
And Save the Account details now.
Now Migration Admin Account has been created.
• Finish and save the private key and delegate domain-wide access to the service account
• Take note of the client ID that was generated
• Enable mail, calendar and contact API access to the service account
• Enable API usage in your project
• Go to the Developer page for API Library and sign in as the Google user you used
above in Create a Google Service Account.
• Select the project that you used above.
• Search for the following APIs, and then for each one, if necessary, click Enable to
enable them for your project:
o Gmail API
o Google Calendar API
o Contacts API
Grant access to the service account for your Google
tenant
1. Go to the G Suite Admin page and sign in as G Suite admin for your tenant.
2. Click Security, then click Advanced settings, and then click Manage API client
access.
3. In Client Name, type the ClientId for the service account you created in the Create
a Google Service Account section above.
4. In API Scopes add the required scopes
(https://mail.google.com/,https://www.googleapis.com/auth/calendar,https://www.
google.com/m8/feeds/,https://www.googleapis.com/auth/gmail.settings.sharing).
The scopes need to be entered in comma-separated format, with no spaces in
between. If the API Scopes are entered incorrectly, the resulting list won't match
and the migration process will fail later, after you start the migration batch.
5. Click Authorize. Verify that the resulting list shows "Email (Read/Write/Send)",
"Calendar (Read-Write)", "Contacts (Read/Write)", and
"https://www.googleapis.com/auth/gmail.settings.sharing".
• Add a sub-domain for mail routing during batched migrations
Create a sub-domain for mail routing to Office 365
1. Go to the G Suite Admin page and sign in as a G Suite admin for your tenant.
2. Click Domains, and then click Add a domain or a domain alias.
3. Select Add another domain. Enter the domain that you will use for routing mails
to Office 365. A sub-domain of your primary domain is recommended (such as
"o365.freelearningforall.com" when "freelearningforall.com" is your primary
domain) so that it will be automatically verified. Keep track of the name of the
domain you enter because you will need it for the following steps, and later in the
instructions as the Target Delivery Domain when you Create a migration batch in
Office 365.
1. Click Skip Google MX setup, and then click I use another mail server. This other
mail server will be Office 365.
2. Log into your DNS provider and update your DNS records so that you have an MX
record at the domain you created above , pointing to Office 365. Ensure that this
domain that you created above is an accepted domain in Office 365. Follow the
instructions in Add a domain to Office 365 to add the Office 365 routing domain
("o365.freelearningforall.com") to your organization and to configure DNS to route
mail to Office 365.
At Gsuite the domain will be active as below:
After you create MX records at Domain Provider> (Pointe MX to EXO) in office 365.
Create a sub-domain for mail routing to your G Suite
domain
1. Go to the G Suite Admin page and sign in as a G Suite admin for your tenant.
2. Click Domains, and then click Add a domain or a domain alias.
3. Select Add a domain alias of... your domain. Enter the domain that you will use
for routing mails to G Suite. A sub-domain of your primary domain is
recommended (such as "gsuite.freelearning.com" when "freelearning.com" is your
primary domain) so that it will be automatically verified.
Click Set up Google MX records, and then follow the instructions that are listed for
your DNS provider.
Create All MX Records provided by Google at your DNS Provider
It may take up to 24 hours for Google to propagate this setting to all of the users in
your organization.
Once your Records are Propagated the gsuite.freelearning.com sub domain will be active.
Provision users in O365 Please Follow the Instructions from : https://docs.microsoft.com/en-us/exchange/recipients-in-
exchange-online/manage-mail-users
I have TWO users in Gsuite with details as:
1.Mail user should have Three Email addresses
a. [email protected] as Primary to forward emails to Gsuite
b. [email protected] as Alias for the migration (Primary domain at Gsuite)
c. [email protected] Alias for email back to Office 365
1.Add your Primary domain freelearningforall.com in office 365 and verify it.
2.Create mail user
Mail user will look like this:
An Example of Mail user is:
On G- Suite Side:
If you did not add your primary domain in office 365 which is at G suite than you can also provision a
user like below:
User id: [email protected] (sub domain pointing to office 365)
External Email ID : [email protected] (sub domain pointing to gsuite)
Also add smtp as [email protected] (Primary domain which will be migrated to office365)
Start a G Suite migration batch with the Exchange
admin center (EAC)
1. Create TXT file with below Format:
EmailAddress [email protected]
2.Click the link below and go to Migrations options in Exchange Admin center
Click Batch> New migration batch.
You can also start the migration from classic Exchange Admin Center
Name the Migration batch> Select Migration to Exchange Online
Select G Suite
Set Endpoint
Name Your Endpoint
Enter the settings related to service account you created:
My service Account email id is
Click Import Jason and browse to the Jason file you downloaded in first step.
Once the Endpoint is configured>
Browse to txt/csv file and start your batch
Set Limits and target delivery domain…this should be your sub-domain pointing to Exchange Online
Final step to choose an account for migration completion notification.
Click Done to finish and start your batch.
Once the batches are 100% synched>Select the batch and click>Complete Batch.
Final Steps are to Select the Batch and > Complete the batch. Wait until it is
completed > Remove the batch and assign the licenses to migrated users.
Remove the batch once it is successfully “Completed”.
Good Luck.
This Document is written by Abdul Farooque Arian
Referenced:
https://docs.microsoft.com/en-us/exchange/mailbox-migration/perform-g-suite-migration
Thanks
Friday, 27th 2019.