Migrate e mail, calendars, and contacts from Google Workspace to Microsoft 365



Learn to use an automatic batch migration emigrate your Google Workspace consumer’s e mail, contacts, and calendars to Microsoft 365. The batch migration software is accessible within the Change admin middle.

For detailed info, see: https://be taught.microsoft.com/alternate/mailbox-migration/automated-migration-neweac

This movies is the third and final video of a playlist. The opposite movies within the playlist embrace:
Video 1: Overview of migrating e mail from Google Workspace to Microsoft 365 via an automatic batch migration – https://youtu.be/5gxXg_s8YL0
Video 2: Stipulations for migrating e mail from Google Workspace to Microsoft 365 via an automatic batch migration – https://youtu.be/BnZOGkSymgk

supply

21 thoughts on “Migrate e mail, calendars, and contacts from Google Workspace to Microsoft 365”

  1. When you get stuck because the JSON file does not show up: It's because your google account does not have the permission to generate a service account key, which would have been the JSON file.
    I think Google changed the default roles and permissions recently (better security by default).
    if you didn't have a cloud console account, this process might have established one (it did for me, and I only noticed when I got an email from 'Google Cloud'). Additionally, for each time you attempted this process and authorised the action through logging into the google account with the little pop up window, it creates a new project to complete the action.
    Find the most recent project in google cloud, usually called 'projectname[random]'

    Click to select the project/organization, click on "More Action" (the 3 points on the right side), Click on IAM/PERMISSIONS, Edit your user and add Roles: "Organization Policy Administrator" and "Organization Administrator". (Note that Organization Policy Administrator should be visible at this level, if you are at the project level, this policy won't be available in the list).

    Now with those 2 roles, click on "Organization Policies" under IAM & Admin or repeat points 2/3 above and then select "Organization Policies".

    Search for "Disable service account key creation" and you should be able to click on Edit Policy and change the rule.

    Now you should be able to generate the key yourself. In the same project, find the menu item "Service Accounts" and there should already be one there, usually called "AutoServiceAccount1" or something like that. click the dot menu for that account and select 'Manage Keys'.
    Here you should be able to generate a new JSON key by pressing 'Add Key'. If you get an error saying there is a permission issue, go back and try to get the permissions sorted like I described above.
    Now you've downloaded the key as JSON, go back to the Microsoft migration tool and enter it at the 02:54 part.
    Good luck and god speed.

    Reply
  2. Thanks for the great information and guidance but if we have many domains connected to Google Workspace with Associated email accounts, do we need to repeat the process for all the domains or just for the main primary domain associated with the admin account?

    Reply

Leave a Comment

Exit mobile version