G Suite to On-Premises Exchange Migration Guide

This is the complete onboarding task flow for migrating folders and documents from G Suite to On-Premises Exchange.

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

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)

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.

Migrated

  • 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.
  • Chat history - Chat messages are migrated to the destination as an email message (without subject) by using the support option MigrateChats=1

Exchange

Not Migrated in Any Instance

  • Inactive mailboxes

Exchange Server 2003 (Source Only)

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Post (when the destination is Exchange or Office 365)

Exchange Server 2007+

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • BCC Recipients
  • Post (when the destination is Exchange or Office 365)

Exchange Server 2010 SP1+

Migrated

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

Not Migrated in any Exchange Instance

  • Email templates
  • Email flags (if the destination is G Suite)
  • Safe Sender/Block Lists
  • Mail Settings
  • Standalone documents stored in Public Folders (Example: IPM.Document item types)
  • System Public Folders
  • Sticky Note folders

Not migrated in Exchange 2003: Public Folders, BCC recipients on email items or optional attendees of calendar entries (Microsoft Exchange Web DAV API does not return this information for items)

Not Migrated in Exchange 2007: Public Folder Permissions

Exchange Public Folders

Public Folders can only be migrated to other public folders or shared mailboxes. We do not migrate Public Folders to individual user mailboxes or O365 Group mailboxes or vice versa.

Exchange 2007

Migrated

  • Public Folders
  • Subfolders

Exchange 2010 SP1+ & Office 365

Migrated

  • Public Folders
  • Subfolders
  • User Permissions
  • Mail-Enabled Security Group Permissions (Default and Anonymous User Permissions are not supported)

Exchange Archive

Exchange Server 2003 and Exchange Server 2007+ archives are not supported

Exchange Server 2010 SP1+

Migrated

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

Step 1: Source & Destination Preparation

  1. Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0:
    Enable access to G Suite using OAuth 2.0

    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. For instructions on using the Gmail API endpoint, see  MigrationWiz - Mailbox Migration - Set up Google API for migrating mailboxes.
    • 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.

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

      New_Google_Admin_APP_Access_Control.JPG

      • 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
    6. Click MANAGE DOMAIN WIDE DELEGATION.
    7. Click Add New.
    8. Enter 113321175602709078332 into the Client ID field. 
    9. 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
      • 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
    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.

    • If you are migrating from multiple domains, repeat these steps for each domain.
    • OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts, G Suite Legacy free accounts, or Google Apps Legacy free accounts. Unfortunately, migrating any Google Legacy free accounts is not supported.
  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 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).
    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. See How do I ensure G Suite folders containing more than 1000 messages will be migrated?
    How do I ensure G Suite folders containing more than 1000 messages will be migrated?

    IMAP access for desktop clients such as Thunderbird or Outlook Express

    You can either enable or disable POP and IMAP for your users via the simple process below. POP access is automatically enabled for your users. However, note that this action will apply to all users in your domain. If IMAP is disabled, users can no longer access their POP/IMAP settings in the Gmail interface, nor will they be able to access their mail via POP/IMAP (such as through Google Desktop), even if previously enabled.

    1. Sign in to the Google Admin console.
    2. From the dashboard, go to Apps > G Suite > Gmail > Advanced settings.
    3. In the Organizations section, select the organizational unit for which you want to configure settings.
    4. Under POP and IMAP Access, select or clear the checkbox for Disable POP and IMAP access for all users in the domain.

    It may take 15-30 minutes for IMAP and POP changes to take effect. As long as the box is cleared, users can configure POP and IMAP access for a host of clients.

    Removing folder size limits on IMAP folders

    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.

    Follow these steps to see if this has been set by a user, and how to change it so that there is no limit set:

    1. Log in to the 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.

    Showing All Mail label and other labels in Gmail:

    1. Sign into your Gmail account.
    2. Click on the gear icon at the top right of the Gmail window.
    3. Click on Settings.
    4. Go to the Labels tab.
    5. Checkmark Show in IMAP for All Mail, and for any other label you want to include in an IMAP client, or migrate.

     

     

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

Prepare the Destination Environment

1. Set up the user accounts

  1. Create an admin account for migration that has full access permissions to all mailboxes. KB004725
    • In the PowerShell script above, change the -User account to match the name of the admin account that was set up for migration.
    • Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
      • Set up a remote PowerShell session with Exchange 2010+. KB005111
      • To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:
        Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz 
  1. Disable throttling against the admin account:
    Disable throttling policy on Exchange

    Option 1: Disable throttling against only the migrating account (if not using impersonation). This way, the admin account can migrate at a faster rate because it is not subjected to any throttling.

     

    • Use this option if not using impersonation during the migration, but instead using delegation.
    • If migrating using admin credentials, it is only necessary to disable throttling against the admin account, rather than all users.
    • If migrating mailboxes using administrative credentials at the Source, but not using impersonation, we recommend disabling throttling limits on this administrative account in order to improve the speed of migration.
    • We recommend the creation of a migration administrative account and disabling policy enforcement for this account.

    Exchange Server 2010:

    To disable all throttling parameters for an admin account called "MigrationWiz":

    1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
    2. Type the following command and press Enter.
      New-ThrottlingPolicy MigrationWizPolicy
    3. Type the following command and press Enter.
      Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null
    4. Type the following command and press Enter.
      Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

    Exchange Server 2013 or 2016:

    To disable all throttling parameters for an admin account called "MigrationWiz":

    1. Open the Exchange Management Shell.
    2. Type the following command and press Enter.

      New-ThrottlingPolicy MigrationWizPolicy

    3. Type the following command and press Enter.

      Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

    4. Type the following command and press Enter.

      Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

     

  2. Verify mailbox accessibility using EWS:
    Verify mailbox accessibility using EWS

     You can verify independently if a mailbox is accessible using EWS with the following steps:

    1. Go to https://testconnectivity.microsoft.com
    2. If using Office 365, click the Office 365 tab.
    3. Select Service Account Access (Developers) and click Next.
    4. Specify the target mailbox email address.
    5. Specify the service account user name. If using admin credentials on the connector, enter the exact same user name.
    6. Specify the service account password. If using admin credentials on the connector, enter the exact same password.
    7. Check Specify Exchange Web Services URL and specify the URL (example: https://server/EWS/Exchange.asmx).
    8. If using Exchange Server, do not check Use Exchange Impersonation. If you are using Office 365, and using impersonation, do check the box.
    9. Check Ignore Trust for SSL.
    10. Click Perform Test.
    11. Once results are displayed, check the overall result, and click Expand All.

    It may be necessary to first manage permissions.

  3. If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:
    • Increase message size limits. See Increasing Exchange Message Size:
      Increasing Exchange Message Size

      This article is relevant for Exchange 2007-2016.

      This is a two-step process. The reason for this is that if the message size limits of Exchange are increased, the IIS limits will also have to be increased to allow increased payloads. There are other non-standard settings that can also cause size restrictions for the IIS or EWS connections, but we are unable to troubleshoot or identify specific environment restrictions outside of these settings.

      Increase the Message Size Limits of Exchange

      To display current message size limits:​

      1. Open the Exchange Management Shell.
      2. Enter the following commands:

      Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
      Get-SendConnector | Format-List -Property Identity, MaxMessageSize
      Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
      Get-MailBox | Format-List -Property PrimarySmtpAddress, MaxSendSize, MaxReceiveSize

      To increase message size limits on the Exchange Server:​

      1. Open the Exchange Management Shell.
      2. ​Enter the following commands:​

      ​Set-TransportConfig -MaxReceiveSize 150MB -MaxSendSize 150MB
      Get-SendConnector | Set-SendConnector -MaxMessageSize 150MB
      Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 150MB
      Get-Mailbox | Set-Mailbox -MaxSendSize 150MB -MaxReceiveSize 150MB

       

      Increase IIS Limits to Allow Accepting Payloads

      There are three limits that should be increased in IIS:

      • maxRequestLength
      • maxAllowedContentLength
      • maxReceivedMessageSize

      Follow these steps to increase the Exchange message size limits on your client access server:

      1. OpenWindows Explorer.
      2. Navigate to %ExchangeInstallPath%FrontEnd\HttpProxy\ews\
      3. Open the file Web.Config in a text editor, such as Notepad.
      4. Find the XML tag starting with for each change.
      5. Change the existing value to maxRequestLength="200000"​ -- this occurs in one place in the Web.Config file.
      6. Change the existing values to maxAllowedContentLength="200000000"​ -- this occurs one place in the Web.Config file.
      7. Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
        For example:
        <httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Anonymous" maxBufferSize="81920" transferMode="Streamed" />
        <httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Basic" maxBufferSize="81920" transferMode="Streamed" />
        etc.
      8. If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
      9. Save the file.
      10. IIS Reset is not needed, web.config changes are picked up by the next conne​ction.

      ​​Follow these steps to increase the Exchange message size limits on your mailbox server:

      1. OpenWindows Explorer.
      2. Navigate to %ExchangeInstallPath%ClientAccess\exchweb\ews\
      3. Open the file Web.Config in a text editor, such as Notepad.
      4. Find the XML tag starting with for each change.
      5. Change the existing value to maxRequestLength="200000"​ -- this occurs in one place in the Web.Config file.
      6. Change the existing values to maxAllowedContentLength="200000000"​ -- this occurs one place in the Web.Config file.
      7. Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
      8. If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
      9. Save the file.
      10. IIS Reset is not needed, web.config changes are picked up by the next conne​ction.
    • Increase maximum accepted content length. See Increase the Maximum Accepted Content Length:
      Increase the Maximum Accepted Content Length

      You may increase the maximum accepted content length by following these directions:

      1. Open Windows Explorer.
      2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
      3. Open the file Web.Config in a text editor such as Notepad.
      4. Go to the end of the file.
      5. Insert or edit the following XML code before the </configuration> tag:

        <system.webServer>
        <security>
        <requestFiltering>
        <requestLimits maxAllowedContentLength="104857600" />
        </requestFiltering>
        </security>
        </system.webServer>

      If XML code is already present in the Web.Config file, edit it to match what is shown above.

      Sample Web.Config before changes:

      <configuration>
      <system.web>
      ...
      ...
      </system.web>
      </configuration>

      Sample Web.Config after changes:

      <configuration>
      <system.web>
      ...
      ...
      </system.web>
      <system.webServer>
      <security>
      <requestFiltering>
      <requestLimits maxAllowedContentLength="104857600" />
      </requestFiltering>
      </security>
      </system.webServer>
      </configuration>

       

    • Increase maximum receive message size. See Increasing Maximum Received Message Size:
      Increasing Maximum Received Message Size

      If you are running IIS7 and Windows 2008, you may need to increase WCF settings:

      1. Open Windows Explorer.
      2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
      3. Open the file Web.Config in a text editor like Notepad.
      4. Find all XML tags starting with maxReceivedMessageSize=
      5. Change existing values to maxReceivedMessageSize="104857600"
      6. Save the file.
      7. Open a Command Prompt (cmd.exe).
      8. Type: cd %windir%\system32\inetsrv
      9. Type: appcmd.exe set config "Default Web Site/ews" -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600
      10. Run: iisreset
    • Increase maximum accepted re​​​​quest length. This is only valid if your Destination server is running Exchange 2007. See Increase Maximum Accepted Request Length:
      Increase Maximum Accepted Request Length

      Exchange Server 2007 has a default maximum accepted request length of 13MB. You may increase the maximum accepted request length by performing the following:

      1. Open Windows Explorer .
      2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
      3. Open the file Web.Config in a text editor such as Notepad.
      4. Find the XML tag starting with maxRequestLength=
      5. Change the existing value to maxRequestLength="102400"
      6. Save the file.

        A value of 102400 represents 100 MBs in kilobytes.

      Sample Web.Config before changes:

      <configuration>
      <system.web>
      ...
      ...
      <httpRuntime maxRequestLength="13280" />
      </system.web>
      </configuration>

      Sample Web.Config after changes:

      <configuration>
      <system.web>
      ...
      ...
      <httpRuntime maxRequestLength="102400" />
      </system.web>
      </configuration>

MigrationWiz Steps

    1. Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
      How do I create a new migration project?

      To create a new migration project:

      1. Sign in to your MigrationWiz account.
      2. Click the Go To My Projects button.
      3. Click the Create Project button.
      4. Click on the type of project that you wish to create.
        • Collaboration: Collaboration projects are used to migrate a Microsoft Teams instance from one Microsoft tenant to another. Collaboration migrations migrate all Teams, Channels, files, and permissions.
        • Document: 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.
        • Feature Coming Soon: Hybrid Exchange: Hybrid Exchange projects are used when migrating an On-Premises Microsoft Exchange 2010+ organization to Office 365. Hybrid projects are usually done over longer periods of time and in batches.
        • Hybrid migrations have a different process than a standard migration and are processed on the Hybrid tab in MigrationWiz. 
        • Mailbox: Mailbox projects are used to migrate the contents of the primary user mailbox from the previous environment to the new environment. Most mailbox migrations can migrate email, calendars, and contacts.
        • Personal Archive: Personal Archive projects are used to migrate archive mailboxes or PST files from one environment to another.
        • Public Folder: Public Folder projects are used to migrate part or all of a Public Folder from one server to another. As with document migrations, the folder hierarchy is maintained from the source to the destination.
      5. Click Next Step.
      6. 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. For steps on creating customers, see View, Add, and Edit Your Customers.
      7. Click Next Step.
      8. Select a Source Endpoint from the Endpoint dropdown menu.
        • If you have not already added the endpoint to the customer in MSPComplete, you will need to click New to create the source endpoint. For more specifics on creating endpoints, see View, Add, and Edit Customer Endpoints.
        • If you are migrating from a Hosted Exchange provider, click the I know my service provider button. Select your service provider from the drop-down list. If it is not listed, select Exchange 2003+ as your Source and enter your OWA URL.
      9. Select a Destination Endpoint from the Endpoint dropdown menu. If you have not already added the endpoint to the customer in MSPComplete, you will need to click New to create the destination endpoint. For more specifics on creating endpoints, see View, Add, and Edit Customer Endpoints.
      10. Click Save and Go to Summary. If setting up a Tenant to Tenant Coexistence mailbox project, check the box for Enable Tenant to Tenant Coexistence. Otherwise, leave that box unchecked.
    2. Add the accounts (also referred to as "items") that will be migrated to the project. See How do I add items to my migration project?
      How do I add items to my migration project?

      Add the accounts that will be migrated, also referred to as items, to a project using one of the following options:

      • Add from MSPComplete: This option allows you to add items that have already been added in MSPComplete. For more information, refer to How do I add users to a customer in MSPComplete?
      • Quick Add: This option allows you to add items o​ne 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: This option allows you to add multiple items at once by copying and pasting from a spreadsheet or by importing a CSV file. For more information, refer to How do I import mailboxes into the system without entering them one at a time?
      • Autodiscover Items: MigrationWiz detects the mailboxes directly at the Source using Autodiscover. For more information, refer to How do I Autodiscover Items for my Migration.
        • For mailbox migrations, this feature is only supported when the Source is Exchange 2007 or later, when the Source is Office 365, or when the Source is G Suite.
        • This feature is not supported for in-place archive migration projects, even if the Source is Exchange 2007 or later.
      • The domain names at the Source and at the Destination might be different. Make sure to provide the right information in the project. If they are different, it's best to modify these in your CSV file, and then use the Bulk Add feature to import the users into the dashboard.

    3. Set the Project Advanced Options. See MigrationWiz: Options & Advanced Options FAQ:
      MigrationWiz: Options & Advanced Options FAQ

      When you create a project, you define the Source, Destination, and the items that need to be migrated. This can be mailboxes, documents, archives, etc. The MigrationWiz project has Advanced Option features that will allow further customization the project.

      These are broken down into General Options and Advanced Options. Under Advanced Options, you can also use Support Options to further configure your project. 

      To access your options: 

      1. Click Edit Project.
      2. Click Advanced Options.

      General Options

      These options are basic level configurations.

      Notifications

      • Send successful migration email notifications: Choose who to notify when a migration has been executed successfully.
      • Send failed migration email notifications: Choose who to notify when a migration fails.
      • Customize Notification Email: Customize emails for success, failure, and request credentials. Use specific keywords as codes for certain data. OAuth 2.0 does not use the customized email; it will only use the default.
      • You can use Markdown syntax to format your email. 

      Filtering

      The filtering tabs allow for specific ranges to be migrated. You can choose the By Date or By Folder filtering options.

      • Specify the earliest date from which to migrate: This will migrate everything that is newer than this date.
      • Specify the latest date from which to migrate: This will migrate everything that is older than this date. Any date filters that have been set will be overridden by the date filters that are set under Start/Pre-Stage migration.
      • Filter folders (RegEx): Define Regular Expressions commands to filter the folder to be migrated.  Find this option under the By Folder tab.

      Maintenance

      • Number of days after which this project will be auto-deleted if unused: Projects are only kept as long as necessary. When a project is not being used, it will be deleted after 180 days of inactivity unless otherwise defined in this parameter.
      • Log subjects of failed items: When an item was not migrated successfully, retry the errors with this option selected to retrieve the subject and path of the item if it is available.
      • Remigrate previously successful items: Remigrate all the items that were already successfully migrated. This will override the duplicate item check. 
        • This option is specifically for Support troubleshooting. This option should only be utilized as directed by Support. 
      • Remigrate previously failed items: Remigrate all the items that were already migrated but failed. This will override the duplicate item check. 
        • This option is specifically for Support troubleshooting. This option should only be utilized as directed by Support. 

      Licensing

      Licensing allows you to set up a maximum number of licenses to use per item.

      Performance

      • Preferred Data Center: Migrations run in multiple data centers all over the world. Choose which data center should run the migration. By default, the data center closest to the authenticated user running the migration will be selected.
      • Max. concurrent migrations: This parameter defines how many migrations to allow simultaneously. Submit as many migrations as you like. This will define how many migrations will be active concurrently.
      • Max. errors of migration: When an error occurs during the migration, we check to see if the number of errors that we received reaches this threshold. If it does, the migration will be considered a failure. Otherwise, we keep on going.

      Specific Migration Type Options

      Mailbox

      • Source:
        • Migrate From: Choose between migrating from Mailbox, Archive (only with archive project) or, Recoverable items. If migrating from Recoverable items, it is recommend that you have litigation hold on.
        • Use Impersonation to Authenticate.
      • Destination:
        • Migrate From: Choose between migrating to Mailbox, Archive, or Recoverable items.
        • If migrating to Recoverable items, it is recommend that you have litigation holds enabled.
        • Destination Mailbox Language.
        • Use Impersonation to Authenticate.

      Failing Items

      Several options can impact whether items in a mailbox get migrated. Ensure these options are not blocking the migration of items you have intended to migrate.

      Project Level

      Check to see if you have one or more of the following enabled under Advanced Options:

      • Folder filtering
      • Date filtering
      • Item type filtering (not migrating calendars, mail, contacts, etc)

      Item Level

      Check to see if you have one or more of the following enabled under Advanced Options​:

      • Folder filtering
      • Item type filtering​ (not migrating calendars, mail, contacts, etc)

      Advanced Options

       These options will further configure your migration and will allow for special processes.

      Migrate to Archive

      You may perform an archive-to-archive migration simply by setting the Destination Advanced Option within an Archive migration to “Migrate to: Archive”.

      Recipient Mappings

      Recipient mappings are a useful way to ensure that:

      • All email can be replied to post-migration, even after a Full (Delta) Migration has occurred when performing a tenant to tenant migration, while keeping the same domain name; or when changing domain names from Source to Destination.
      • Calendar ownership and display name match on destination when performing a tenant to tenant migration, while keeping the same domain name; or when changing domain names from Source to Destination.

        If you are using recipient mapping while migrating from one Source domain to multiple Destination domains, a project is required for each Destination domain.

      Use cases:

      • When migrating from Office 365 to Office 365 and keeping the same domain name, recipient mappings must be added to your project, as directed below. This is included in the migration guide for this scenario.
      • When migrating over to a new domain name:
        • Source domain = Sourcedomain.com
        • Destination domain = Destinationdomain.com
        • Example - Migrating James@Sourcedomain.com to james@Destinationdomain.com you want to ensure that any entries for james@Sourcedomain.com are renamed to james@Destinationdomain.com during migration.
      • The following options are the most valuable for this migration scenario:
      • Under Filtering, add: (^All Mail$|^All Mail/) G Suite All Mail Label Migration:
        G Suite All Mail Label Migration

        The best approach is to filter out the All Mail label until the very last pass. The reason for this is that Google has most items in individual labels, but also keeps a copy of all items in the All Mail label.

        Without adding this filter, MigrationWiz will have to index the AllMail items label before it can migrate. This will typically be very large, and consequently will take a very long time to index.

        We recomnend that you first filter out All Mail, and migrate all the other labels during the Pre-Stage and Delta passes. Then, perform one last Delta pass, having removed the All Mail filter, so that it indexes the All Mail label during this pass and migrates any additional non-labeled items.

        Here are the steps to follow to add the filter to your MigrationWiz project Advanced Options. This should be left in place for all passes, apart from the very last pass (where it is removed, as detailed at the bottom of this article).

        1. Log in to your MSPComplete dashboard.
        2. From the list of customers in the left hand navigation panel, select your customer.
        3. From the list of options in the top navigation bar, click on Projects.
        4. Click on the name of your Project in the list. This will launch the MigrationWiz portal for the selected project.
        5. In the top navigation bar, click on the Edit Project button.
        6. From the resulting drop-down list, select Advanced Options.
        7.  Under Filtering, add the following: (^All Mail$|^All Mail/). This will filter the All Mail folder and any subfolders of All Mail.
        8. Click Save.

        Here is a screen shot that shows how this will look under your MigrationWiz project Advanced Options:

        allmail.PNG

        You can now perform your migration by following the steps in the migration guide that matches your scenario.

        After you have completed all passes, you can perform one additional last pass, but with the filter removed. This pass can be performed after your users have already begun using the Destination account. Follow these steps to remove this filter for the very last pass:

        1. From your MigrationWiz project dashboard, in the top navigation bar, click on the Edit Project button.
        2. From the resulting drop-down list, select Advanced Options.
        3.  Under Filtering, remove the previously added filter.

        4. Click Save

        5. Now you can select the items for migration, click Start and select Full Migration, and follow the prompts to start your migration pass. This pass will migrate any additional items that are in the All Mail folder, but not in any other label. This is normally just a few deleted items, and archived items (that have no label). Normally the user is unaware of these items, but it is still best to migrate, for completeness.

          • This will filter out the All Mail label from your migration passes. It will 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.
        • Under Support/Support options, add:
    4. Run Verify Credentials. See How do I verify credentials?
    5. Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
    6. Pre-Stage pass: Select the users > Click 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 Start Migration. How do I start a migration?
    7. MX Record Cutover: Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.
      • If you are migrating in batches, you will not be cutting over the MX records until your final batch of users has been migrated.
    8. Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to the sample email for some sample text and screen shots that can be included in this email.
    9. Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration
    10. Run Retry Errors. For more information, see Retrying Failed Items.
    11. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
    12. If problems persist, contact Support. For more information on how to contact Support, see How do I get support for your products?
    13. If you are not using DeploymentPro, users must create new Outlook profiles.
    14. 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/) G Suite All Mail Label Migration.
      • Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. For more information, see:
How Do I Start a Migration?

How do I start a migration?

Answer:

  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.
    • Full - Requires a license. This migration selection will migrate all identified and supported items.   
    • Pre-Stage - Requires a license. This migration selection will migrate all identified and supported items before the selected date.  In the case of mailbox migrations, only email items will be migrated for this migration option.  This migration option requires a license of the appropriate type.
    • 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.
  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.
  • For more specific information on each type of migration, see Selecting Migration Options in MigrationWiz: Descriptions:
    Selecting Migration Options in MigrationWiz: Descriptions

    Once you have created and populated your migration project, MigrationWiz provides five migration options.

    The five allow you to test and verify your connections, complete the migration either in stages or in a single pass, and then allows you to capture and migrate items that may have failed to migrate the first time around.

    Following are descriptions of each migration option:

    1. Verify credentials: This process checks the credentials for migration at both the Source and the Destination. Verifying credentials will not migrate any data or consume any licenses. This process will perform the following actions:
      • It will check that the mailbox exists on the Source.
      • If using admin credentials at the Source (these are entered when creating the project), it will verify those credentials.
      • If not using admin credentials at the Source, and using user credentials for each mailbox, it will verify those credentials.
      • It will check that the mailbox exists on the Destination.
      • If using admin credentials at the Destination (these are entered when creating the project), it will verify those credentials.
      • If not using admin credentials at the Destination, and using user credentials for each mailbox instead, it will verify those credentials.
    2. Trial Migration: A Trial Migration will migrate a very small amount of data in order to test that the project has been created properly and that the mailboxes have been entered correctly. It is completely free and can be performed an unlimited number of times. Each Trial Migration will perform the following:
      • Trial migrations verify credentials at both the source and destination.
      • Trial mailbox migrations recreate the entire folder hierarchy on the destination, based on what is defined at the source.
      • Trial migrations migrate only up to ten items in each folder, and up to a total of 5MB of data.
      • For Public folder migrations, the Trial migration only migrates the current folder and does not scan sub-folders. No data is migrated, nor is an error message shown. Upon running behind the scenes, the trial migration on public folders will show a Success message.
    3. Pre-Stage Migration: A Pre-Stage Migration pre-fills a Destination mailbox with mail only migrated items, as defined by the Pre-Stage Migration settings selected. 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. It has no impact on the end users and is a highly recommended strategy to follow since the majority of data is migrated over prior to MX record cutover. Typically only mail items older than three months are included in the Pre-Stage Migration because these items are unlikely to change.
      • When performing a Pre-Stage Migration, it is important to understand that MigrationWiz is a migration solution and not a synchronization solution. With this in mind, it will not propagate updates, deletes, or moves of the items previously migrated in the first migration pass because we do not have “live” monitoring of changes (as with a sync agent), and we cannot handle scenarios like conflict resolution without user interaction.
      • Here is what would happen after a Full (Delta) Pass, if items previously migrated to Destination have been:
      • Deleted at the Source: The Destination will keep containing these deleted items. We cannot propagate deletes (e.g., if an item is archived at the Source, it will look like a delete and we can not delete the item at the Destination).
      • Moved from Folder A to another Folder B: These items will be duplicated at the Destination, they will be both in Folder A and in Folder B at the Destination.
      • Updated at the Source: These items will not be updated at the Destination. There is no process by which the calendars, contacts, tasks, etc., can be updated. This would require conflict resolution, which is only possible with a synchronization solution. Instead, MigrationWiz watermarks all migrated items so as to avoid remigrating any items in subsequent passes.
      • This multi-pass migration strategy typically follows an order of events similar to this:
        • First pass (Pre-Stage): Migrate ONLY mail items that are older than three months. The Pre-Stage migration is performed one to two weeks before MX record cutover (times vary, dependent upon the number of mailboxes being migrated and the size of the mailboxes). Perform the MX record cutover.
        • Second pass (Full or Delta): Migrate all items, with no date filters. This pass is performed after the TTL expires.
        • Changing MX records in DNS to point to the new system is not effective immediately, and is subject to replication delays. Wait for the TTL (aka Time To Live) to expire.
        • Optional Third pass (Full or Delta): Migrate all items, with no date filters. 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.
    4. Full/Delta Migration Both Full and Delta migrations have the same settings in MigrationWiz. With both migration types, the migration has no date filters, and all items are migrated.
      • With a Full Migration, everything is migrated in one pass. For example, a single pass migration (Big Bang) strategy will move the entire mailbox in one pass, after MX records are cut over. A typical scenario consists in cutting over on a Friday evening and migrating during the weekend.
      • With a Delta Migration, which is performed after a Pre-Stage Migration and is part of a multi-pass migration strategy, it is possible to resubmit a mailbox or mailboxes to perform a differential migration pass. MigrationWiz will automatically find items that haven't yet been migrated since the first pass and migrate only those. In other words, a Delta pass will find and migrate residual items. In most cases, a Delta pass will complete much faster than the initial pass.​ In a Delta pass, MigrationWiz will continue the migration from where it left off and cause no duplicates to be created at the Destination, which means that all items which were not migrated in the first pass or were created after/during the first pass will be migrated.
    5. Retry errors This is another attempt to migrate any items that previously failed to migrate. It will not migrate any successfully migrated items. It will not consume any more licenses. Only submit mailboxes in the Retry Errors mode if they satisfy both of the following conditions:
      • The last migration completed successfully.
      • The mailbox contains at least one error.
  • For specific license information, see Migration License Types
  • Prior to starting your migration, you must have already purchased the appropriate licenses as needed.
  • Prior to starting your migration, you can customize your migration by selecting Advanced Options.
  • In Public Folder migrations the Trial Migration only scans the current folder and does not scan sub-folders.  No data is migrated, nor is an error message shown.  Barring connectivity errors, the Trial Migration for Public Folder migrations will show a Completed status.
  1. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.

 

 

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