Steps to Migrate G Suite to Office 365 Account

The G Suite to Office 365 migration guide is drafted for users who seek an arranged and feasible migration of G Suite content to Cloud destination.

Office 365 cloud platform is high in demand due to its secure, professional, scalable and robust infrastructure. Even G Suite users feel need to migrate to the cloud platform at some point of time. Check out this complete and detailed G Suite to Office 365 migration guide with all important stages and steps.

Manual G Suite to Office 365 Migration

Preparations for Migration

  • Creating a Google Service Account and JSON Key
    1. Visit this link in your Chrome browser and sign in using the G Suite admin credentials.
    2. Add a new project name and click CREATE option.
    3. Now, go to IAM & Admin>Service Accounts>Select Project>Create Service Account. Add any Service account name and click CREATE option.
    4. Click Continue and Done on the next two continual pages.
    5. Next, click Email for the Service account and then click Edit option.
    6. From the Service account details page, note down the unique ID on a separate location for further use in migration.
    7. On the next page, expand the section Show Domain Wide Delegation and select the checkbox saying Enable G Suite Domain-wide Delegation. Add the product name for the consent screen and click Save.
    8. On the Keys page, click on Add Key option and select Create key.
    9. Select the key type as JSON and click CREATE.
    10. The JSON key will be created to download. Keep a track of this file for further use.
  • Enabling Gmail, Contacts, Calendar APIs
    1. Go to this link and sign in with G Suite admin credentials.
    2. Select the project created earlier.
    3. Search APIs – Gmail, Google Calendar and Contacts and click Enable option against each of them.
  • Assigning access permission of service account for Google tenant
    1. Open the G Suite admin page and navigate to Security>API Controls>Manage Domain Wide Delegation.
    2. Click Add new option against the API Clients list.
    3. On the Add a new Client ID page, enter the client ID created in the Service Account stage.
    4. Enter the following scopes as it is in the Oauth scopes section.,,,
    5. Click on Authorize for verification of the scopes.
  • Creating sub domains for mail routing to Office 365 & G Suite
    To Office 365
    1. Open the G Suite admin page and go to Domains>Manage domain>Add a domain.
    2. Provide the domain name and click Continue and verify domain ownership option.
    3. Keep a track of this domain for use in migration.
    4. Login to DNS provider and update the records.
    5. Follow the same steps for creating sub domain for mail routing to G Suite. Navigate to Domains>Manage domain>Add a domain alias. In this follow this link – to set up MX records for G Suite Gmail.
  • Adding users in Office 365
    Provide or create Mail Users for every user in the organization listed for migration to Office 365.

Migration Process with Exchange Admin Center

Once all the above preparations are fulfilled or completed, follow this process to perform G Suite to Office 365 migration through synchronization process using the Exchange Admin Center.

  1. Open the Exchange Admin Center with administrator credentials.
  2. Go to recipients > migration.
  3. Now, click on the New or plus icon and then select Migrate to Exchange Online option.
  4. On the new migration batch page, select G Suite (Gmail) migration option and click Next.Select G Suite (Gmail) migration option
  5. Users are required to create a source CSV file before the next step with the Email address (primary email address of Office 365 mailbox) and Username (primary email address of Gmail) headers.
  6. Now, click on the Choose file option to browse and add the created CSV file as described in the previous step. Add the file and click Next to continue.
  7. On the G Suite (Gmail Configuration) page, provide the G Suite admin email address and test connection between Office 365 and G Suite accounts. Click on Choose File option to browse and add the JSON file (contains private key for service account) downloaded when the service account was created. Then click Next.
  8. On the Move configuration page, provide the migration batch name, target delivery domain (domain created to route emails from G Suite to Office 365) and click Next.Provide the migration batch name, target delivery domain
  9. On Start the batch page, browse and add the recipient to send the report, select the options to start and complete the batch. Then click new.Browse and add the recipient to send the report
  10. The batch synchronization will start. Wait till the status changes from Syncing to Syncd.The batch synchronization will start
  11. This synchronization follows incremented migration and ensures migration of newly received emails from G Suite to respective Office 365 mailboxes.

With Exchange Online PowerShell

  1. First users need to connect to the Exchange Online PowerShell.
  2. Test connectivity between Office 365 and G Suite accounts using this command.
    Test-MigrationServerAvailability -Gmail -ServiceAccountKeyFileData $([System.IO.File]::ReadAllBytes(“C:\\somepath\\yourkeyfile.json”)) -EmailAddress
  3. If the test is successful, run the next command to create the migration endpoint.
    New-MigrationEndpoint -Gmail -ServiceAccountKeyFileData $([System.IO.File]::ReadAllBytes(“C:\\somepath\\yourkeyfile.json”)) -EmailAddress -Name gmailEndpoint
  4. Next, run this command to create the migration batch.
    New-MigrationBatch -SourceEndpoint gmailEndpoint -Name gmailBatch -CSVData $([System.IO.File]::ReadAllBytes(“C:\\somepath\\gmail.csv”)) -TargetDeliveryDomain “”

    Enter the path of the CSV file created at the specified space in the above command.

  5. The batch migration will be started.

Is this native way of migration OK to you?

The above migration process to move G Suite to Office 365 is multi-staged and includes various steps. The user or administrator performing this migration – via Exchange Admin Center or Exchange Online PowerShell should be technically sound to avoid any sort of mistake causing the whole process to start again or creating the data loss condition. These data cannot be migrated using the native solutions – Calendar Reminders, Appointments, Chat message attachments, Calendar Attachments, Tasks, Chats and chat history, Google Groups for Business, Google Categories (i.e., the Google category flags: Social, Promotions, Updates, Forums), Email attachments that are links to Google Drive, etc. Also, a certain amount of patience and time are the primary requirements to complete the process without issues.

So, if you feel these challenging conditions comfortable, then have a try. For other users, we have easier and quicker migration solution for G Suite to Office 365.

Get the best alternative here

The G Suite to Office 365 migration becomes an easy operation if you choose the automated or professional way. We got you the best of all – G Suite to Office 365 Migrator tool that includes minimum steps to achieve instant and efficient migration of complete G Suite content with facility of advanced filters and options along with a smart interface.

Download Now

About Elias Macclure

Elias has a sleek writing style, and the reader may find that the extensive nuances of the material are covered in the article. He changes the writing style according to the platform and writes fine for Office 365 and SharePoint. He is an active reader and reads books by renowned writers including Charles Dickens, Sidney Sheldon and Agatha Christie.

Leave a Reply

Your email address will not be published. Required fields are marked *

  +  20  =  28