1. BitTitan Help Center
  2. Perform a Migration
  3. Microsoft Migrations
  4. Exchange Online Mailbox Migrations using Graph API
  5. Mailbox Migrations Guides using Graph
  6. Google Workspace as Source

G Suite (IMAP) to Microsoft 365 using Graph API Migration Guide

Notes

  • Although present in the UI, BYO App using Client Certificate is currently unavailable. We are working on a resolution for this issue at this time.
  • GoDaddy-Hosted Office 365 is currently not supported with the Graph Endpoints at this time.
  • Due to Graph API limitations at this time, Archived Mailboxes migrations are not fully supported using the Graph API. If your migration involves Archived Mailboxes, you should use EWS (Google Workspace Migrations) to perform your migration project until the Graph limitations are resolved by Microsoft and we are able to extend support for this scenario using the Graph API.

This is the migration guide for a mailbox from G Suite, using the IMAP endpoint, to Microsoft 365 using Graph API. This guide contains all the steps needed for your migration. Other useful resources and information are also linked or included.  

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. 

First migration?

We have created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.

Prerequisites

It is important to highlight and meet the following prerequisites for a smooth migration project.

Licensing

We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit Which Migration License Do I Need?.

To use your license by following the next steps:

  1. Review Considerations.
  2. Purchase Licenses.
  3. Create a Customer.
  4. Apply Licenses.
ConsiderationsPurchase LicensesCreate a CustomerApply Licenses

Licenses are released once payment has been received:

  • Licenses are available immediately upon payment if you purchase via credit card.
  • If you purchase via wire transfer (100+ licenses), the licenses will be available once payment is received and accepted.
  • We do not accept purchase orders because of processing overhead.

In both cases, you will be notified by email that payment has been accepted and licenses are available in your account upon notification.

For more information on licensing, including coupon redemption and other licensing types, see our Which License Do I Need? guide.

Limitations

  • App password usage, MFA/2FA, SSO, and ADFS are not supported for the migration service accounts being used for this migration scenario.
  • Some item types are not migrated. Click the bar below to expand the full list of what item types are and are not migrated. We are constantly working to create a better migration experience for you, so these items may change.
  • Due to Microsoft limitations, using Delegate Permissions with Graph API is not supported at this time. Only Application Permissions can be used.
  • Pinned/Flagged Emails are migrated but not Pinned/Flagged in the destination environment.
  • Threading (email messages that belong to the same conversation) is not supported and will require Manual implementation. 
  • Delegate-level calendar access isn't supported by Microsoft Graph. It's automatically downgraded to Free/Busy-only.
  • Archive Mailbox as a destination is currently not supported. Support for this option is planned for a future release.

Besides, you should consider the following points when performing a G Suite (IMAP) to Microsoft 365 Migration: 

  • When migrating from G Suite as a source, contacts in Contact Groups (which look like subfolders of the Contacts folder) will migrate to the top-level contacts folder on the destination. Folders will be created for each group but the contacts will not be sorted into those folders.
  • Calendars can have multiple Owners. An Owner is anyone with "Make changes and manage sharing" permissions, so shared calendars will be migrated to users with these permissions by default.

Important

All accounts being migrated must be in Active status in the tenant. Users that are set to a status of Inactive accounts cannot fully migrate and fail in the project.

Migrated Items

Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.

Which items are migrated?

Always migrated

  • Inbox.
  • Folders/Labels.
  • Email.
  • Muted Email (as regular email).
  • Contacts.
  • Calendars (including links for Google Hangouts within calendar meetings).
  • Calendar Notifications.

Links for Google Hangouts are a new default feature added to Google Meetings. Microsoft 365 does not have the corresponding property to map. Therefore, when migrating to Microsoft 365, the links for Google Hangouts are added to the beginning of the meeting description body text on Microsoft 365.

What items are not migrated?

Not Migrated in Any Instance

  • Calendar Reminders.
  • Appointments.
  • Google Spaces.
  • Google Spaces Chats.
  • Chat message attachments.
  • Google Groups for Business (including forums and collaborative inboxes).

Not Migrated As Source

  • Calendar Attachments.
  • Calendar Reminders.
  • Tasks.
  • Chats and chat history.
  • Google Categories (i.e., the Google category flags: Social, Promotions, Updates, Forums).
  • Email attachments that are links to Google Drive.
  • Some calendar colors.
  • Personal Folder and Calendar Permissions.
  • Mailbox Rules.
  • Automatic Replies (Out of Office Messages).

Important

All color category meta tags are transferred over, but Microsoft 365 does not have direct color mappings from Google G Suite, so certain colors do not get mapped over, thus the colors are not displayed in Microsoft 365 for the calendar entries.

Not Migrated As Destination

  • Calendar Attachments.
  • Exceptions of recurring appointments.
  • Google Groups for Business (including forums and collaborative inboxes).

With Google API Endpoint at Source

With this endpoint, all items listed above migrate as before. However, utilizing the API endpoint enables migration of the following items as well. The following items are not migrated via the IMAP endpoint. 

  • Google Categories (Category flags, i.e. Social, Promotions, Updates, Forums).
  • Snoozed and Scheduled emails - these are migrated like regular emails to custom destination labels. Their properties are not migrated.

For additional features and limitations, please visit MigrationWiz: Migrated and Not Migrated Items.

Which is the migration mapping?

Relationship fields do not migrate fully from Gmail. The mapping is as follows: 

Google contact field

Mapping in O365

Remarks

Content.content

Contact body

Description in the body

Sensitivity

Sensitivity

 

Priority

Importance

 

Initials

Initials

 

Nickname

NickName

 

Name.FullName

Subject

 

Name.FullName

FileAs

 

Name.GivenName

GivenName

 

Name.FamilyName

Surname

 

Name.NameSuffix

Generation

 

Name.AdditionalName

MiddleName

 

Organization (primary)

CompanyName

Also stores name, department, title and job descriptions

Organizations (non-primary)

Companies

Also stores name, department, title and job descriptions

Emails

EmailAddresses

Only first 3 are stored. Rest are stored in overflow properties.

IMs

ImAddresses

Only first 3 are stored. Rest are stored in overflow properties.

Phone numbers

PhoneNumbers

Types:

  • home

  • home fax

  • mobile

  • pager

  • work

  • work fax

  • other

If any number is already set, we append to overflow contact properties

Postal Addresses

Physical Addresses

Types:

  • home

  • work

  • other

If any address is already set, we append to overflow contact properties.

Also stores city, country or region, postal code, state and street

Events

Wedding Anniversary (only for anniversary)

Rest are stored in overflow properties

Relations (value = "assistant")

AssistantName

 

Relations (value = "child")

Children

 

Relations (value = "domestic-partner")

SpouseName

 

Relations (value = "manager")

Manager

 

Relations (value = "partner")

SpouseName

 

Relations (value = "spouse")

SpouseName

 

Relations (value = others)

Others stored in overflow properties

 

Mileage

Mileage

 

ContactPhotoInBytes

Attachments

 

User defined fields

All stored in overflow properties

 

Name.GivenNamePhonetics + Name.AdditionalNamePhonetics

Stored as extended property

 

Name.FamilyNamePhonetics

Stored as extended property

 

contactEntry.Name.NamePrefix

Stored as extended property

 

Birthday

Stored as extended property

 

Websites

Stored as extended property

 

Prepare the Source Environment

Recommended Actions

The following sections are recommended to ensure that the migration of all data is possible and to prevent failures.

Mailbox migration projects require that a G Suite administrator grant access to the BitTitan client ID and scopes listed in this article. 

  • Enabling access is required for both G Suite mailbox and Google Drive document migration projects.
  • Mailbox migration projects require that a G Suite administrator grant access to the BitTitan client ID and scopes listed in this article.
  • Document migration projects require that a G Suite Super administrator grant access to the BitTitan client ID and scopes listed in this article and enable the API access. The steps to do this are included at the bottom of this article.

Grant MigrationWiz OAuth 2.0 access to G Suite

BitTitan products use OAuth 2.0 to authenticate to G Suite and utilize the G Suite (IMAP) endpoint in MigrationWiz. This applies to both mailbox and document migration projects. To configure the OAuth access within your G Suite environment, follow the directions in this article.

Enabling access is required for both G Suite mailbox and Google Drive document migration projects. In order to access your G Suite data, it is necessary to add specifically allowed API scopes to the MigrationWiz project. 

Steps in the G Suite Admin Console

Complete these steps to grant BitTitan client ID access to the appropriate scopes:

  1. Go to https://admin.google.com and authenticate as a Super Administrator.

  2. In the admin console, go to Menu Google_Menu.png > Click Security > Access and data control > API controls> Manage Domain Wide Delegation.

    Warning

    If you do not see the security icon on your admin console home page, your account does not have the necessary rights to make these changes. 
    Google limits settings access and configuration to only G Suite Super Administrator accounts.

  3. Click Add New.

  4. Enter 113321175602709078332 into the Client ID field. 

    Important

    Make sure there are no leading or trailing spaces, as this may cause the error "URL ends with an invalid top-level domain name."

  5. Enter  the following groups of scopes into the OAuth Scopes (comma-delimited) field:
    • G Suite as the Source (read-only scopes):
      https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/, https://www.googleapis.com/auth/gmail.settings.sharing, https://www.googleapis.com/auth/gmail.settings.basic,https://www.googleapis.com/auth/contacts.other.readonly 
  6. Click Authorize. 

The client's name is 113321175602709078332. This will grant BitTitan products access to the appropriate scopes.

Enable IMAP Access

Ensure IMAP access is enabled for all users. For details on how to check this, refer to the Google support article here.

Enable Folder Size Limits

Ensure the folder size limits on IMAP folders have been removed for all users. For each user:

  1. Click the gear icon.
  2. Click Settings.
  3. Select the Forwarding and POP/IMAP tab.
  4. Select Folder Size Limits.
  5. Select the radio button for Do not limit the number of messages in an IMAP folder (default).

This is an end-user setting, which can only be set on a per-user basis. Therefore, we recommend that you send instructions to your end users to check this setting. 

Sample Communication to End Users

Action Required - Due Date XX/XX/XX We are preparing to migrate your environment. To ensure a seamless migration, certain end-user settings must be verified. Follow the directions below to remove the folder limits on your account migration. Failure to do so on time may result in lost items. G Suite has a setting that can limit the number of messages in an IMAP folder. If this is configured, this will restrict MigrationWiz so that it can only retrieve and migrate that number of messages from each folder.

  1. Log in to your Gmail account.
  2. Click on the gear icon in the upper right-hand side of the window, and choose Settings.
  3. Click on the Forwarding and POP/IMAP tab.
  4. Under the IMAP Access heading, look for Folder Size Limits.
  5. Ensure that Do not limit the number of messages in an IMAP folder (default) is selected.

To further clarify the implications of this setting: If the limit has been set (e.g., to 1,000 as per the default suggestion), then if folders contain more than 1000 items, they will be truncated at 1000 items. This means that MigrationWiz will only be able to migrate 1000 emails from each folder. Thank you for your assistance. If you have any questions or concerns, please contact [Help Desk].

Export mailboxes to CSV file(s)

From the Google Admin portal:

  1. Click Users.
  2. Click ⁝ (3 vertical dots).
  3. Download Users.
  4. Download All Users.
  5. Click OK.
  6. Save.

Prepare the Destination Environment

Modern Authentication Requirements

The KBs listed in the Exchange Online Authentication options using Graph API section will help you configure the destination tenant when using Microsoft 365 with the Microsoft Graph API. A Global Administrator account is required to consent to the BT app or create and consent to the BYO app, since the Entra app's permission types require global admin approval.

Export the User List to a CSV File

This can be used when bulk-adding users to your MigrationWiz project later. You can copy and paste the user list into the Source and Destination Email columns within your MigrationWiz project dashboard under Add > Bulk Add.

To export the user list:

  1. Go to the Microsoft 365 admin portal.
  2. Click Users.
  3. Click Active Users.
  4. Click Export.
  5. Click Continue.

Be sure to save the CSV somewhere you can access it for upload later in the migration.

MigrationWiz Steps

Create a Mailbox Project

  1. Log in to MigrationWiz.
  2. Click the Go to My Projects button.
  3. Click the Create Project button.
  4. Select the Mailbox project type. 
  5. Click Next Step.
  6. Enter a Project name and select a Customer.
  7. Click Next Step.
  8. Select endpoints or follow the steps below to create new endpoints. 
  9. Click Save and Go to Summary.

Endpoints

Service Account Password

Before migrating, ensure that the service account password in the source does not contain any commas. If it does, update the password before starting the migration process.

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints or create new ones. 

Create your Endpoints

Please review the following tabs to create your destination and source endpoints.

Source Endpoint Destination Endpoint

Create your source endpoint by following the next steps:

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select G Suite (IMAP). 
  4. Enter the requested credentials.
  5. Click Add and Next Step.

Add Users

Add the user accounts that will be migrated to the project. MigrationWiz allows you to bulk import users into the system.

You may use Bulk Add, Quick Add, or add the accounts to the MSPComplete customer. 

Quick Add

This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:

  • An email address
  • Login name
  • Password
  • Mailbox status
Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add.
  5. Follow the instructions on the page.

Advanced Options

Advanced Options allow you to choose your notifications, filtering, maintenance, licensing, performance, and some configuration options.

Support Options are advanced configurations that make use of Powershell or code blocks to provide extra options or resources for your migration.

The following options are the most valuable for this migration scenario:

Support Tab

Recommended Options

The following options are most valuable for all G Suite migration scenarios:

  • InitializationTimeout=8 This increases the initialization timeout window to eight hours. This value is in hours, up to a maximum of 100 hours. Values above 100 are in milliseconds. For example:​
    • InitializationTimeout=2 will increase the timeout to 2 hours.
    • InitializationTimeout=8 will increase the timeout to 8 hours.
    • InitializationTimeout=14400000 will increase the timeout to 4 hours.
    • InitializationTimeout=21600000 will increase the timeout to 6 hours.
  • StoreOverflowGooglePropertiesInNotes=1 
  • StoreOverflowGooglePropertiesInNotesPrefix="enter your text here" Replace "enter your text here" with your message.
  • SuppressReminderDays=X Replace "X" with a value from 1 to 365.

Bulk Load

To upload a large list of Advanced Support options, see the Bulk Load - Advanced Options when Migrating Mailbox projects using Graph API for additional guidance.
 

Filtering Tab

  • Under Filtering, add: (^All Mail$|^All Mail/) 

Run Verify Credentials

  1. ​Sign in to your MigrationWiz account​.
  2. Open the Project containing items you wish to validate.
  3. Select the items you wish to validate.
  4. Click on the Start button in your dashboard.
  5. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration. 

Run Migration

In the MigrationWiz interface:

Pre-Stage pass

  1. Select the users you wish to migrate.
  2. Click the Start button from the top.
  3. Select Pre-Stage Migration.
  4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago.
  5. Click Start Migration.

MX Record Cutover

Once confirmed that the Pre-stage migration has been completed successfully. Log into the DNS provider's portal, and change the primary MX record to reflect the DNS settings for the destination M365 tenant.

Full pass

  1. Select the users.
  2. Click the Start button from the top.
  3. Select Full Migration.
  4. Click Start Migration.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Remove All Mail

  1. Remove the All Mail filter from Project Advanced Options, and run one final full migration pass.
  2. Under Project Advanced Options > Filtering section, delete: (^All Mail$|^All Mail/) 
  3. Select the users.
  4. Click the Start button from the top, and select Full Migration.
  5. Click Start Migration.

Final Steps

Users must create new Outlook profiles, set up their signatures again, and reattach any PST files attached to their previous profile.

Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. 

Related Topics

Was this article helpful?
0 out of 0 found this helpful

Articles in this section