G Suite (IMAP) to G Suite (IMAP) Migration Guide

Let's Get Started

This is the complete onboarding task flow for migrating folders and documents from G Suite (IMAP) to G Suite (IMAP).

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices. If you have never performed a migration before, we suggest reading that before beginning the steps outlined in this 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.

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.

Migrated Items

G Suite

Migrated - IMAP or G Suite (Gmail API) endpoints

  • 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 Meeting. Microsoft Office 365 doesn't have the corresponding property to map. Therefore, when migrating to Office 365, the links for Google Hangouts are added to the beginning of the meeting description body text on Office 365.

Not Migrated in Any Instance

  • Calendar Reminders
  • Appointments
  • Chat message attachments

Not Migrated As Source

  • Calendar Attachments
  • Calendar Reminders
  • Tasks
  • Chats and chat history
  • Google Groups for Business (including forums and collaborative inboxes)
  • Google Categories (i.e., the Google category flags: Social, Promotions, Updates, Forums)
  • Email attachments that are links to Google Drive
  • Some calendar colors

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

Not Migrated As Destination

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

Step 1: Source & Destination Preparation

Prepare the Source Environment

G Suite requires the use of OAuth 2.0 for migrations. The steps to set this up are explained below for Source preparation. OAuth 2.0 OR Google API may be used for the Destination.

Grant MigrationWiz OAuth 2.0 access to G Suite

Grant MigrationWiz OAuth 2.0 access to G Suite. If you are migrating to multiple domains, repeat these steps for each domain.

BitTitan products use OAuth 2.0 to authenticate to G Suite  and utilize the G Suite (IMAP) endpoint in MigrationWiz. This is applicable to both mailbox and document migration projects. In order to obtain access to your G Suite data, it is necessary to add specifically allowed API scopes to the MigrationWiz project. 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.

1: Create users on G Suite

Google provides clear, step-by-step guidance for this project. Follow these steps and then move to the next step listed below.

2: Set Authentication

OAuth 2.0 Steps

BitTitan products use OAuth 2.0 to authenticate to G Suite  and utilize the G Suite (IMAP) endpoint in MigrationWiz. This is applicable to both mailbox and document migration projects. In order to obtain access to your G Suite data, it is necessary to add specifically allowed API scopes to the MigrationWiz project.

  • These steps must be followed whenever there is a migration project either to or from G Suite that will utilize the G Suite (IMAP) endpoint. This is currently required for all Google as Source projects. 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.

3: 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. Click Security. If you do not see the security icon on your admin console home page, you do not have the necessary rights on your account to make these changes. Request Super Administrator access from the customer to implement these changes.
  3. Click Advanced settings. Google limits accessing and changing this setting to only G Suite Super Administrator accounts.
  4. You will now have one of two options, depending on whether your tenant has been updated to the new Google API or not. 
  5. Classic Google UI New Google UI:

    1. Go to the G Suite admin page at google.com.
    2. Click on Security.
    3. Click on Advanced Settings.
    4. Click Manage API Client Access.

    Or If your account shows the latest UI updates from Google, as shown below:mceclip1.png

    1. Go to the G Suite admin page at google.com.
    2. Click on Security.
    3. Click Advanced Settings.
    4. Under ‘Domain-wide delegation’, click Manage domain-wide delegation.
    5. On the Manage domain-wide delegation page, click Add new.
  7. Click Add New.
  8. Enter 113321175602709078332 into the Client ID field. 
  9. Enter the following groups of scopes into the OAuth Scopes (comma-delimited) field. Note that these scopes are for the source only. The destination scopes are found below.

    • 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/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

10. Click Authorize. The client name is 113321175602709078332 (make sure there are no leading or trailing spaces, as this may cause the error "URL ends with an invalid top-level domain name."). This will grant BitTitan products access to the appropriate scopes.

4: Enable IMAP

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

5: Enable Folder Size Limits

  1. Ensure the folder size limits on IMAP folders have been removed for all users. For each user:
  2. Click the gear icon.
  3. Click Settings.
  4. Select Forwarding and POP/IMAP tab.
  5. Select Folder Size Limits.
  6. 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. Expand the following section for sample communication and instructions:

>Removing Folder Limit

6: 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. Click Save.

Prepare the Destination Environment

The steps for preparing the destination are identical to the steps for preparing the source, with the exception of the scopes. Follow the directions above to set up your destination, but substitute the following block of scopes for the source scopes above, then continue setting up your destination according to the Prepare the Source instructions. 

G Suite as the Destination (full scopes):

https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, 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

Set up Migration

Purchase and Apply UMB Licenses

Licenses are required to run a migration project in MigrationWiz. To obtain license pricing information, or to purchase licenses, click the Purchase button in the top of your MSPComplete or MigrationWiz dashboard.

  • Payment: We accept credit cards, and wire transfer in certain situations.  
  • When purchasing with a credit card, payment is immediately processed during checkout. If successful, licenses are granted to your account instantly.
  • Wire transfers are available for purchases of 100 or more licenses. If you are purchasing at least 100 licenses, you will be presented an option to purchase via wire transfer during checkout. A wire transfer checkout will generate an invoice with wiring information for your accounts payable department and bank. Once the funds are received by our system, the licenses are granted to your account immediately. 

For this project type it is recommended to use our User Migration Bundle licenses. 

  • These licenses enable you to perform multiple migrations of User mailboxes, documents, and in-place archives, and allows the use of DeploymentPro to perform post-migration Outlook email profile configuration.
  • Further information on User Migration Bundle Licenses:
    • User Migration Bundle Licenses have unlimited data available per license.
    • User Migration Bundle Licenses are applied to the customer's users, for whom you'll be performing migrations, and are valid for one year.
    • Read the MigrationWiz Licenses article for more information about how to apply the licenses to Users for migrations.

2: Set the Endpoints

This is done in the MigrationWiz dashboard. You may either select existing endpoints or create new ones.

To select existing endpoints, choose G Suite (IMAP) for both source and destination. 

To create new endpoints, select New and fill in the requested fields. The endpoint type will be G Suite (IMAP)

Once the endpoint has been saved in the project, it will automatically be assigned to the customer that was selected in the Project Information tab when creating the project.

Step 2: Set the Advanced and Support Options

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

  • Under Filtering, add: (^All Mail$|^All Mail/)
    • This will filter out the All Mail label from your migration passes. It will also speed up your migration passes.
    • You will remove this folder filter before performing your final migration pass. These steps are included later in this section.
  • Set the Maximum concurrent migrations value. The default value is 100. For cloud to cloud migrations, this value can be set to a very high number, such as 500, because both the Source and Destination environments can handle a large number of concurrent migrations.
  • Under Support/Support options, add:
    • StoreOverflowGooglePropertiesInNotes=1 
    • StoreOverflowGooglePropertiesInNotesPrefix="enter your text here"  

Step 3: Run Migration

Perform the migration, using one of the following strategies. More information on each strategy is included in the Migration Planning and Strategy Guide linked in the beginning of this guide. 

  • Full Migration strategy. For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration, and requires licenses. This migration selection will migrate all identified and supported items.  
  • Pre-Stage Migration Strategy: This strategy includes a Pre-Stage pass and a Full (Delta) pass. This migration selection will migrate all identified and supported items before the selected date. This migration option requires a license of the appropriate type.

Additional Migration Types

  • Trial - Free migration pass. This migration selection is used to test the migration server.  It will migrate up to 10 items per folder or up to 5 MB of data per mailbox. A full migration with a license will pick up where the trial left off. 
  • Verify Credentials - Free migration pass. This migration selection will test to make sure that the credentials being used for migration are correct and will allow a successful connection. No data is migrated.
  • Pre-Stage Pass. A Pre-Stage Migration is typically part of a multi-pass migration strategy. It occurs before the MX record cutover and is a great way to pre-fill the majority of the end users' data into their future Destination mailboxes while they are still using their old email system.
  • MX Record Cutover. This migration is used for email delivery by SMTP.
  • Run Full (Delta) Pass Migration. This pass is performed two or three days after the MX record cutover. This picks up any residual mail that was still delivered to the old mail system after the MX record cutover, due to slow DNS internet propagation.
  • Retry Errors - Free migration pass. Once a Full or Pre-Stage migration has completed successfully, Retry Errors can be run to retry only failed items.

For large migration projects that are more than 50 users, we recommend a Pre-Stage Migration strategy. This is a multiple-pass migration.

Once you have chosen your migration strategy: 

  1. Click on the name of the Project you want to run.
  2. Select one or more items to migrate by checking the box next to the item name. If you want to select all the items, click the checkbox to the left of Source Email.
  3. Click on the Start button and select the type of migration to run.
  4. If you want to delay your migration, then select the checkbox marked "Automatically start the migration at", and enter the date and time to have the migration start. To start a migration immediately, you do not need to select the scheduling option.
  5. Click Start Migration.

Notify Users

Send out the final notification that the migration is beginning. Include when the migration will start, expected duration, any usage instructions during migration, and any expected steps or notifications for the post-migration timeline.

Request Statistics

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

Post-Migration Steps

  1. Notify users once the migration has completed. If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon completion of the migration.
  2. Assist users with setting up access to their G Suite (IMAP) accounts.
  3. Provide training to end users on G Suite. 
Was this article helpful?
0 out of 2 found this helpful