Skip Ribbon Commands
Skip to main content

G Suite to G Suite Migration Guide

Last Update: 7/21/2017 11:32 AM
This article has been moved to our new Help Center. Please update your bookmarks.

   G Suite to G Suite Migration Guide

Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To get to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, click the waffle icon (waffle.png) in the top navigation bar of MSPComplete, and select the appropriate migration product.

Introduction

  • This is the complete onboarding task flow for migrating mailboxes from G Suite to G Suite. 
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.
  • The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. This is an Agent which includes multiple modules - e.g.; for HealthCheck for Office 365 and DeploymentPro. It is not required to install DMA for this migration scenario. However, BitTitan will be adding several modules to DMA, and these will be important to power MSPComplete feeds (which will provide further information to you about upsell and cross-sell opportunities).

Prepare the Source Environment

  1. Grant MigrationWiz OAuth 2.0 access to G Suite. KB005019
    1. Notes:

      1. If you are migrating from multiple domains, repeat these steps for each domain.

      2. 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/

        Note: OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts. If a G Suite tenant is a G Suite for Business Legacy free account, end user credentials must be used. Refer to KB005124 for more information on migrating with end user credentials.

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

  3. Ensure the folder size limits on IMAP folders have been removed for all users. For each user, click on the gear icon > Settings > Forwarding and POP/IMAP tab > Folder Size Limits > Select the radio button for Do not limit the number of messages in an IMAP folder (default). Note: 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. KB005104

  4. Export mailboxes to CSV file(s). From the Google Admin portal > Click Users > Click on ⁝ (3 vertical dots) > Download Users > Download All Users >Click OK > Save.

Prepare the Destination Environment

  1. Create users on G Suite. Refer to the G Suite admin help article here.
  2. Grant MigrationWiz OAuth 2.0 access to G Suite. KB005019
    • Notes:
      • If you are migrating to multiple domains, repeat these steps for each domain.
      • 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

MSPComplete Steps

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427
    • For the Source endpoint:

      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.
      • It is necessary to add ALL domains that will be migrated from. This means that if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, then it is important to ensure that both of these are added under Your Domains when creating the endpoints. When you add a domain, you need to click on the "+" button.
      • Enter Administrative email address. Note: This is the account that has admin access level to the Google admin portal.
    • For the Destination endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.
      • It is necessary to add ALL domains that will be migrated to. This means that if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, then it is important to ensure that both of these are added under Your Domains when creating the endpoints. When you add a domain, you need to click on the "+" button.
      • Enter Administrative email address. Note: This is the account that has admin access level to the Google admin portal.
  3. Purchase licenses. From your MSPComplete dashboard, click on Purchase > Mailbox Migration > select MigrationWiz-Mailbox and enter the number of licenses you wish to purchase. Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro bundle or the MigrationWiz Mailbox and MigrationWiz Document bundle if also migrating Google Drive accounts).  KB004647
  4. Deploy DMA to users (optional). Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:
    • Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. ​KB005412  video
    • Via email. KB005411

MigrationWiz Steps 

Watch this video to see a walk-through of the steps below.

  1. Create the Mailbox Migration project. KB004380

    • Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
  2. Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
  3. Set the Project Advanced Options. KB004834
  4. The following options are the most valuable for this migration scenario:

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

        • Notes:

          • 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. Note: 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  KB005056                     

      • Under Support/Support options, add: StoreOverflowGooglePropertiesInNotesPrefix="enter your text here"  KB005056

      • Under Support/Support options, add: SuppressReminderDays=N  KB004203

  5. Run Verify Credentials. KB004511
  6. Notify users that a migration is occurring. Send email to all users, telling them the time and date of the migration.
  7. Pre-Stage pass: Select the users > Click on the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click on Start Migration. KB004938
  8. MX Record Cutover. Change over MX records on the DNS provider's portal. Also include the AutoDiscover (CName) setting.
      • Notes:
      • If you are migrating in batches, you will not be cutting over the MX records until your final batch of users has been migrated.
        • If mail coexistence is required, you must set up mail forwards against those user accounts that are in the migration batches. Options:
          • Manually set forwards during a migration on a per-user basis, from the individual users' portal. Note: This is only a valid option if there are a small number of users. KB004316
          • Manually set forwards during a migration on a per-user basis, from the admin portal. Note: This is a suitable option for small- to medium-sized projects. KB004374
          • Automate the setup of mail coexistence (forwards) for GoogleApps through the MigrationWiz management console tool. Note: This is the best option for large projects. KB005168
  9. Send email to end users tolet them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.
  10. Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
  11. Run Retry Errors. KB004658
  12. Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
  13. If problems persist, contact Support. KB004529
  14. If users will be using Microsoft Outlook with G Suite, they will need to follow instructions here, to download and install G Suite Sync for Outlook and create a new Outlook profile that connects to G Suite.
  15. Remove the All Mail filter from project Advanced Options, and run one final (Full) migration pass.
    • Under Project Advanced Options > Filtering section, delete:  (^All Mail$|^All Mail/).  KB005626
    • Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938        
  16. Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626