G Suite (IMAP) to Office 365 Migration Guide

This is the complete onboarding task flow for migrating folders and documents from from G Suite to Office 365 via the Gmail IMAP endpoint. 

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.

Items and folders in "Shared with Me" will not be migrated. Only items in "My Drive" will be migrated. To migrate "Shared with Me" items, they must be added to "My Drive".

We are not able to support migrations with two-factor or multifactor authentication. 

Migrated Items

 

Always Migrated

  • Date/Time
  • Subject
  • Body
  • Importance
  • Sensitivity
  • Size
  • Item Class
  • Exceptions to recurring meetings
  • Linked mailbox data (if accessible via EWS)

Never Migrated

  • Items that do not match folder types, i.e. calendar responses within a mail folder. Important: If an item type is migrated into a folder of a different type at the destination, the item will not be visible.
  • Custom items that do not inherit from the core system types
  • InfoPath Forms
  • Calendar permissions (Exception for Exchange sources outlined below)
  • Calendar notifications
  • Modified description text & modified attendee lists for exceptions to recurring meetings
  • User-defined/custom fields for Contact items
  • Acceptance status for meeting participants
  • Personal distribution lists ("Contact groups" in Office 365)
  • Server-based and dynamic distribution lists
  • Bounce notifications
  • RSS feeds
  • Mailbox sharing settings (aliases; delegates; client settings)
  • Mailbox rules and folder permission settings (these are only supported from Exchange Server 2010 SP1+ and later to Exchange Server 2010 SP1+ and later)
  • Personal Messaging Resource Management (MRM) Tags
  • Outlook Quick Steps
  • Client-side rule
  • Color-coding for categories
  • Pictures that have been added within a Business Card, under Contacts.
  • Calendar meeting links: Lync, Skype or Teams events will be migrated but will usually not work in the destination because the links are for the source environment. These events will need to be recreated at the destination. There are exceptions to this rule, but they are not consistent.
  • Encrypted Emails: For all Source email systems, any email sent or received using encryption methods will not migrate using MigrationWiz. The emails will need to be decrypted before they can be migrated.

Pictures are included in the migration in migration scenarios with high fidelity, e.g., for Exchange to Office 365, and Office 365 to Office 365.

If Exchange is the Source, and an account exists in the Destination that matches the UPN prefix of an account with Calendar Permissions in the Source prior to submitting a migration, Calendar Permissions will be migrated, except for Resource Calendars. Resource Calendars permissions are not migrated.

If Exchange is the Source, and an account does not exist in the Destination that matches the UPN prefix of an account with Calendar Permissions in the Source prior to submitting a migration, Calendar Permissions will not be migrated.

Office 365

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Server-Side Rules
  • Folder Permissions
  • Post (when the destination is Exchange or Office 365)
  • Calendar acceptance status emails

Not Migrated

  • Safe Sender/Block Lists

Groups

Not Migrated

  • Notebooks

Planner

Not Migrated

  • Data

Office 365 Archive

Migrated

  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Server-Side Rules
  • Folder Permissions
  • BCC Recipients

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)

IMAP & POP

Migrated:

  • Inbox
  • Folders
  • Email

Step 1: Source & Destination Preparation

Prepare the Source Environment

Source Endpoint: G Suite IMAP (Own Service Account) Endpoint 

This endpoint requires your tenant service account to be set up and Google APIs be enabled. Follow the steps below to set up your environment for this endpoint. 

Prerequisites:

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

1: Set up API scopes with OAuth

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.

Step 2: Migrating with Google API

Prerequisites:

  • Subscription to Google Cloud Platform.
  • Google Super Administrator account.
  • Ability to set up a service account on the G Suite tenant.
  • Service account must be set up before the MigrationWiz project is created.

Step 1: Create a Google Project:

  1. Go to the Google Cloud Platform (GCP) Console and sign in as a super administrator. Choose one of the options below:

    • If you haven't used the Google Cloud Platform Console before, agree to the Terms of Service and click Create Project.

    • If you have used Google Cloud Platform Console before, at the top of the screen next to your most recent project name, click Down to open your projects list. Then, click New Project.

  2. Enter a project name and click Create.

  3. When the new project creation completes, at the top of the screen next to current project name, click Down icon and select the newly created project name from the list.

Step 2: Enable APIs for Service Account

  1. From the Google Cloud Platform Console, click Menu > APIs & Services > Library.

  2. Enable the following APIs by selecting the specific API and clicking Enable.
    Repeat for each API listed below:

  3. API:
    • Google Drive API
    • Google Calendar API
    • Gmail API
    • Contacts API
    • Admin SDK
    • Make sure that the Gmail, Calendar, and Contacts services are enabled within the Google tenant. You can control services for your users using the instructions on this page: Control who can access G Suite and Google Services.

Step 3: Create Customer Tenant Service Account

  1. From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.

  2. Click + Create Service Account at the top middle of the screen and enter a name.

  3. Click Create.

  4. Assign the role of Owner to the new Service Account by selecting Owner from the Role drop down menu.

  5. Click Continue to move to the next step, then click the Done button.

  6. You will now be returned to the "Service Accounts" page. 
  7. On ‘Service accounts' page, click vertical ellipsis under 'Actions’ column for the service account created above.
  8. Click Create key.

  9. Make sure that JSON is selected as "Key Type."
  10. Click Create.

  11. Click Close.

Make sure that you download the key as a JSON file and make a note of the name and location of the file. This JSON file will be used when setting up the migration endpoint in the Mailbox Migration project.

The JSON file must contain information in the following fields: “type”, “private key”, and “client email”. If these mandatory fields are empty the file upload during endpoint creation will fail.

Step 4: Setting the Scopes for the migration

From the Google Cloud Platform Console:

    1. Click Menu
    2. Click IAM & Admin
    3. Click Service Accounts
    4. Find the service account that was set up in Step 3: Create Customer Tenant Account.
    5. Find and copy the service accounts Unique ID number. This is the Client ID number that will be used in a later step.
      • This field often needs to be added to the view. Click on the Column display options button and add a checkmark to Unique ID, then click OK.
      • This Client ID should be considered similar to Administrator account passwords and handled securely.
    6. You will now have one of two options, depending on if the Google UI has been updated in your tenant. 
    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.

     Once these steps are complete:

    1. In the Client ID field, paste the Unique ID copied above.
    2. In the OAuth scopes (comma-delimited) field, paste all scopes listed below:
      1. For source endpoint :
        https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive.readonly
    3. Click Authorize.

     You should now see your specific Unique ID and the associate scopes listed.

Step 5: Set up the Google API endpoint during project creation

1. During the project creation process, click New for the Endpoint.
2. From the dropdown menu, select G Suite (Gmail API).
3. Click Select File.
4. Navigate to and select the JSON file that contains the Google Service Account key that was saved during the service account setup process.
5. Enter the super administrator email address.
6. Click Add.

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

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

Old Google Tenant:

  • Go to the G Suite admin page at google.com
  • Click on Security
  • Click on Advanced Settings
  • Click Manage API Client Access. or If your account shows the latest UI updates from Google, as shown below:mceclip1.png
  • Go to the G Suite admin page at google.com
  • Click on Security
  • Click Advanced Settings
  • Under ‘Domain-wide delegation’, click Manage domain-wide delegation
  • On the Manage domain-wide delegation page, click Add new
  1. Click MANAGE DOMAIN WIDE DELEGATION.
  2. Click Add New.
  3. Enter 113321175602709078332 into the Client ID field. 
  4. Enter one of the following groups of scopes into the OAuth Scopes (comma-delimited) field, depending on whether G Suite is the Source or Destination.

    • 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
  5. 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.

7: 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.

8: 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).

9: Export mailboxes to CSV file(s)

From the Google Admin portal:

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

Prepare the Destination Environment

1: Create an Administrator Account

Create a Global Administrator or a delegated admin with full access rights or permissions account in Office 365 to be used for migration or use the Global Administrator or delegated admin with full access rights or permissions account for the tenant. In order to have administrative permissions to migrate mailbox data, grant the account permissions on each mailbox.

  • Having administrative access to the Microsoft Office 365 control panel to manage users does not mean the same account has permissions to access all mailboxes for migration.
  • Having delegated admin access to accounts does not provide enough access.

Enabling an administrative account the ability to access Office 365 user mailboxes can be performed by adding the Impersonation role or Full Access mailbox permissions.  The below steps will explain how to configure the permissions access for both options.

2: Impersonation

To enable the admin account to impersonate users, run the below PowerShell command:

$cred = Get-Credential

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic -AllowRedirection

Import-PSSession $session

Enable-OrganizationCustomization

New-ManagementRoleAssi​gnment -Role ApplicationImpersonation -User <admin_user_name>

Remove-PSSession $session

  • More information about this PowerShell command can be found here.
  • MigrationWiz uses delegation by default to log in to individual user mailboxes using administrative credentials specified on the connector.
  • It is highly recommended to use impersonation when migrating from or to Office 365.

3: Full Access

To manually grant administrative access for migration, execute the following remote PowerShell commands: 

$cred = Get-Credential

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic -AllowRedirection

Import-PSSession $session

Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz

Remove-PSSession $session

  • The command needs to be applied each time a new mailbox is created since permissions are set directly on each mailbox. The administrative account will not have access until the permissions are applied.
  • In the script above, the username "MigrationWiz" should be replaced with the name of the administrative account that was set up, by following the instructions in this Knowledge Base article.
  • This username is the Administrative Username that needs to be entered under the project's Source or Destination settings, within MigrationWiz, when checking the box labeled Use Administrative Login.

 4: Create and License User Accounts

 Set up accounts on Office 365 and assign licenses. These can be created in several ways:

  • Manually, one at a time. Read the Add users individually or in bulk to Office 365 article from Microsoft for more information.
  • By bulk import, via CSV file. Read the Add several users at the same time to Office 365 article from Microsoft for more information.
  • By PowerShell script. Read the Create user accounts with Office 365 PowerShell from Microsoft for more information.
  • How do I synchronize my Azure Active Directory objects to Office 365?

    The recommended approach is as follows:

    Use this article from Microsoft for the most up-to-date information: Set up Directory Synchronization

    1. Download and install AAD Sync or AAD Connect (if you need support for federation).
    2. Set msExchMailbxoGuid to Null by first running the Synchronization Rules Editor as an administrator. Next, cick In from AD – User Exchange to edit the Inbound Rule Type. Then, Select Transformations. Find the msExchMailboxGuid attribute and change it to: Expression - msExchMailboxGuid - NULL - Checkmark Apply Once - Click Update. Enable AADSync or AAD Connect and perform a full synchronization.
    3. Configure filtering to define which objects are synced. Read the Azure AD Connect sync: Configure filtering article from Microsoft for more information.
    4. Use Microsoft AAD Sync or AAD Connect to create and synchronize the accounts from the On-premises environment to Office 365.
    5. Assign Office 365 licenses to accounts on Office 365.
    6. Remove the null attribute from the msExchMailboxGuid, using the Synchronization Rules Editor.
    7. Perform another synchronization, using AAD Connect (or AAD Sync).
    8. Migrate, using MigrationWiz. This step can also be initiated after Step 4, once the licenses have been assigned.By DirSync, AAD Sync or AAD connect. Read the How do I synchronize my Azure Active Directory objects to Office 365? article for more information.
    • If the local Active Directory (AD) schema has not been extended to support Exchange, then the steps above to set msExchGuid attribute to null are not needed. Synchronization can be run in the normal manner.
    • If you have previously used DirSync from an environment where the local AD supports Exchange, you cannot set the msExchangeMailboxGUID to null, because this is not supported by DirSync. Therefore, we recommend that you instead use AAD Sync or AAD Connect to rectify this problem, by following the steps outlined above.
    • If you do not set the msExchMailboxGuid to null, before running a synchronization from an environment where the local AD supports Exchange, all of the On-Premises Exchange attributes for each user will be synchronized, including the MailboxGuid attribute. If users are created in this state on Office 365, an Exchange Online license cannot be activated unless Mailbox Replication Services (MRS) is used to perform the mailbox move, or the steps above are followed to rectify this problem.
    • Once the users have been created on Office 365, and the licenses have been activated, then you can start using DirSync, AAD Sync, or AAD Connect in the normal manner. The problem is limited to the user creation and license enablement (when the local AD supports Exchange).
    • If the mailboxes are on an Exchange Server in the local AD, Office 365 accounts can be created using one of the following methodologies.
    • Licenses will also need to be assigned to the users, once they have been created.
      • AAD Sync or AAD Connect. Follow the instructions detailed in the recommended approach above.
      • Manually, one at a time.
      • By bulk import, via CSV file.
      • BitTitan DirSync tool.

 

Step 3: Licensing

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 Apply User Migration Bundle Licenses to the Customer's Users article for more information about how to apply the licenses to Users for migrations.

Step 4: Set up MigrationWiz 

The following steps will guide you through setting up your migration project in MigrationWiz. For all endpoints in this process, select or create the G Suite IMAP (Own Service Account) endpoint.

Create New Project

  1. To create a new migration project:

      1. Click the Go To My Projects button.
      2. Click the Create Project button.
      3. Under Project Type, select Document Project. Document projects are used to migrate document drives from one cloud storage to another. Document migrations will maintain the folder hierarchy from the source to the destination.
      4. Enter a Project name and select a Customer. If you have not already added the customer into MSPComplete, you will need to click New to create the Customer.
      5. Click Next Step.
      6. Select the source endpoint from the Endpoint dropdown list, or create a new source G Suite IMAP (Own Service Account) endpoint.
      7. Click Next Step.
      8. Select the destination Office 365 endpoint from the Endpoint dropdown list, or create a new Office 365 endpoint.
      9. Click Save and Go to Summary.
      10. On the Authorization page, click the Request Access Token button to open the Office 365 authorization page.
      11. Enter the email address and password for the Office 365 admin account and click the Sign In button. This generates the access token required by MigrationWiz for the MigrationWiz project and redirects back to the Authorization page of the MigrationWiz project.
      12. Click the Save Project button.

     

    Add Items

    Add the accounts (also referred to as "items") that will be migrated to the project. There are several ways to do this. 

    Quick Add
    This option allows you to add items one at a time. You have to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.
    Bulk Add

    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.
    Autodiscover

    The Autodiscover process within MigrationWiz can be used to discover items from the Source environment, so that they can be imported into your projects.

    There are few requirements in order for this to work:

    • The Source has to be Exchange 2007 or later, or Office 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
    • The endpoint on the Source needs to use admin credentials.
    • For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
    • The admin mailbox must be listed in the public Global Address List (GAL).
    • The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.

    One additional item to note here is that there is not a way to restrict the IP addresses that the connection will come from.  This means that the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using on of the other available options.

    Autodiscover of items will not work while using Modern Authentication

    Autodiscovery exposes the following items:

    • For mailbox migration, autodiscovery will list all mailboxes at the Source.

     

    Steps to Run Autodiscover

    1. Navigate to the project you want to import users into.

    2. Ensure that you have created an endpoint for the source project.

    3. Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.

    4. Once discovered, click on the Import button, to import the items into your MigrationWiz project.

     

    Set Advanced Options

    Set the Project Advanced Options. These are customization options which help MigrationWiz perform within specific environments. 

    Under Support/Support Options add:

    • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. 
    • RemoveExistingPermissionsWhenUnspecified=1 There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.

    Set the Advanced Option to send a notification to end users after the migration pass completes:

    • Notifications > Send successful migration and notification to: > Source email address (if users are still using G suite Gmail) or Destination email address (if users have already migrated from the G Suite gmail platform).
    • Customize the notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
    • Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-stage migration strategy, only set this up prior to the final Full (Delta) pass.

Run Verify Credentials

You may verify the credentials of items in MigrationWiz without migrating data or consuming any licenses.

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click on the Start button in your dashboard.
  4. 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. During this time, they should not modify any documents in their G Suite (IMAP) accounts, because any modifications will not be included in the migration.

Step 5: 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.
  • 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.

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. To prevent users from inadvertently logging in and using their G Suite accounts, decommission the G suite user accounts, or change their passwords.
  2. 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. Assist them with setting up access to their Office 365 accounts.
  3. Provide training to end users on Office 365.

 

 

 

Was this article helpful?
8 out of 12 found this helpful