MigrationWiz - Mailbox Migrations

Mailbox migrations vary by source and destination but have a few things in common. The most commonly asked general questions are below. For specific steps and guidance based on your migration scenario, see our migration guides. 

Important

Mailboxes may be in use during migration on both the source and destination. If items are removed or moved on the source during the migration, errors or failures may occur. We recommend notifying users to avoid changes to data during the migration process. 

By design, the migration caches the Mailbox and Project settings once it starts and is assigned to a migration server

Workaround

In case you make changes to your Mailbox or Project after the migration stats, you should stop it and restart your process 

MigrationWiz does not have any limitations on the mailbox size to migrate. We have migrated mailboxes that contain hundreds of gigabytes (GB) of data.

​​​Email that already exists in a Destination mailbox is not changed or affected in any way during the migration process.  MigrationWiz does not delete, change, or move any items that exist in the Destination mailbox before running a migration.  

Supported Mailbox Types

Encrypted Email

For all Source email systems, any email sent or received using third-party encryption plugins does not migrate using MigrationWiz. This email needs to be decrypted before it can be migrated.

Flagged Email

The Follow-Up condition rule item will be displayed in the Inbox or For Follow-Up Search folder as default in the O365 Outlook as well as Exchange.

The rule will not be triggered with Flag-Follow Up with a specific folder neither in Outlook nor Exchange.

Migration between different domain suffixes

You may migrate data between email accounts that have different domain suffixes.

Automatic Replies (Out-of-Office Messages)

You can now migrate Out-of-Office messages from source mailboxes to destination mailboxes using different endpoints.

MigrationWiz supports this feature in the following source and destination endpoints:

  • Microsoft Exchange Server.
  • Microsoft 365.
  • Google/G-Suit.

Important

We strongly advise prioritizing the migration of Automatic Replies (Out-of-Office Messages) as the final step in any mailbox migration.

Permissions

With MigrationWiz you can automatically migrate mailbox folder permissions, allowing you to migrate folder, and calendar permissions for user and shared mailboxes. Avoiding manual re-application of permissions.

Important

Calendar Permissions

Consider the following behavior for Calendar Permissions:

  • MigrationWiz only supports exporting the content of mailboxes and folders to PST files. However, it does not support exporting other features like Folder and calendar permissions as PST files.
  • In Gmail/G-Suite migrations, MigrationWiz cannot migrate the following items:
    • Calendar Description.
    • Email User display name.

Folder Permissions

Folder permissions are migrated using the following approach:

  • First, MigrationWiz tries to match the source primary SMTP email address to the destination primary SMTP email address.
  • Next, MigrationWiz tries to match the source display name to the destination display name.

Important

If more than one match is found on the destination display name, a failure occurs and the permissions are not assigned to that particular UserID.

Mailbox Rules

With MigrationWiz you can migrate Mailbox Rules including Client-Side Rules from Outlook for specified conditions and actions. This works at the tenant level as well as regular (personal) mailbox settings.

Important

This feature is fully supported at the source and destination:

  • Microsoft Exchange
  • Server Microsoft 365
  • Google/G-Suite Gmail
Not Supported Client-Side Rules
  • Print.
  • Play a sound.
  • Desktop Alerts.
  • PintoTop. PintoTop action property exists in Outlook Wizard, but Service API doesn’t support it.
  • Display a specific message.
  • Alert window.
  • Clear the Message.
  • Permanently Delete.

Signatures

You can migrate signatures from source mailboxes to destination mailboxes using Google / G-Suite only within MigrationWiz.

Pre-existing Items

Email that already exists in a Destination mailbox is not changed or affected in any way during the migration process.  MigrationWiz does not delete, change, or move any items that exist in the Destination mailbox before running a migration.  

S/MIME Email

MigrationWiz can migrate S/MIME digitally signed messages with or without encryption.

Create a Mailbox Migration Project

  1. From the MigrationWiz dashboard, click Go To My Projects.

  2. Click Create Project.

  3. Select a Mailbox migration type. 

  4. Click Next Step.

  5. Enter a project name and select a Customer from the list.

    1. If the customer hasn’t already been created, you can do so here.

    2. To create a new customer, click New, provide the required details including primary email domain and company name, and click Save.

  6. Click Next Step.

Migrated Items

Certain mailbox items are always migrated, regardless of source or destination. 

Which items are migrated?
  • Date/Time.
  • Subject.
  • Body.
  • Importance.
  • Sensitivity.
  • Size.
  • Item Class.
  • Exceptions to recurring meetings.
  • Linked mailbox data (if accessible via EWS).
  • Pictures are included in the migration in migration scenarios with high fidelity, e.g., for Exchange to Microsoft 365, and Microsoft 365 to Microsoft 365.
  • Calendar folder permissions (Exception for Exchange sources outlined below).
  • Mailbox folder permissions
  • Client-side mailbox rules (from Outlook clients).
  • Server-side mailbox rules
Which items are not 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 notifications

    Important

    Folder and calendar permissions are not supported.
  • Modified description text and 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).
  • Bounce notifications.
  • RSS feeds Mailbox sharing settings (aliases; client settings; delegates e.g. SendAs and SendOnBehalf rights).
  • Personal Messaging Resource Management (MRM).
  • Tags.
  • Outlook Quick Steps.
  • Custom color coding for categories.
  • Pictures added within a Business Card, under Contacts.
  • Server-based and dynamic distribution lists.
IPM and Report Mailbox Items Migrated
The following item types and message categories are exported from the source during migration.
  • IPM.Appointment
  • IPM.Contact
  • IPM.Note
  • IPM.Note.CommVault.Galaxy.Stub
  • IPM.Note.GroupMailbox.WelcomeEmail
  • IPM.Note.Microsoft.Conversation
  • IPM.Note.Microsoft.Conversation.Archive
  • IPM.Note.Microsoft.Conversation.Voice
  • IPM.Note.Microsoft.Missed
  • IPM.Note.Reminder.Event.2
  • IPM.Note.Rules.OofTemplate.Microsoft
  • IPM.Note.SMIME.MultipartSigned
  • IPM.Note.Receipt
  • IPM.Schedule.Inquiry
  • IPM.Schedule.Meeting.Notification.Forward
  • IPM.StickyNote
  • IPM.Task
  • REPORT.IPM.Note.CommVault.Galaxy.Stub.IPNNRN
  • REPORT.IPM.Note.Delayed.DR
  • REPORT.IPM.Note.DR
  • REPORT.IPM.Note.IPNNRN
  • REPORT.IPM.Note.IPNRN
  • REPORT.IPM.Note.NDR
  • REPORT.IPM.Note.Relayed.DR
IPM and Report Mailbox Items Not Migrated

The following item types and message categories are not exported from the source during migration.

  • IPM.AbchPerson
  • IPM.CalendarSharing.CalendarUpdate
  • IPM.CalendarSharing.EventDelete
  • IPM.CalendarSharing.EventUpdate
  • IPM.ControlFlowMessage
  • IPM.ControlFlowMessage.DocumentAnalyticsPropagation
  • IPM.ControlFlowMessage.GraphTransactionMessage
  • IPM.ControlFlowMessage.ModifyActionPropagation
  • IPM.ControlFlowMessage.SharePointItemMaintenance
  • IPM.ControlFlowMessage.SharePointItemRevokeAccess
  • IPM.ControlFlowMessage.SharePointItemSecurityUpdate
  • IPM.ControlFlowMessage.UserSubscriptionPropagation
  • IPM.DistList IPM.Document.Word.Document.12
  • IPM.File
  • IPM.File.Document
  • IPM.GroupMailbox.AddMemberRequest
  • IPM.GroupMailbox.JoinRequest
  • IPM.Outlook.Recall
  • IPM.Recall.Report.Failure
  • IPM.Recall.Report.Success
  • IPM.Schedule.Meeting.Canceled
  • IPM.Schedule.Meeting.Request
  • IPM.Schedule.Meeting.Request.AttendeeListReplication
  • IPM.Schedule.Meeting.Resp.Neg
  • IPM.Schedule.Meeting.Resp.Pos
  • IPM.Schedule.Meeting.Resp.Pos.SilentResponse
  • IPM.Schedule.Meeting.Resp.Tent
  • IPM.Sharing
  • IPM.TaskRequest
  • REPORT.IPM.Schedule.Meeting.Canceled.NDR
  • REPORT.IPM.Schedule.Meeting.Request.IPNRN
  • REPORT.IPM.Schedule.Meeting.Request.NDR
  • REPORT.IPM.Schedule.Meeting.Resp.Pos.IPNNRN
  • REPORT.REPORT.IPM.Note.IPNNRN.NDR
The destination may affect which items may be migrated. Not all item types will migrate to all destinations. For such special cases, read the migration guide for details on management.

Special cases in email migrations

Hidden Folders

If a system folder exists on both the source and the destination, MigrationWiz detects it and migrates items to that location.

For example, Exchange stores attachments in a hidden system folder called 'Files'. If the destination also has this folded, MigrationWiz automatically migrates the items. As these are hidden, it may appear they did not migrate.

If the content needs to migrate to a different folder, use folder mapping to specify the new destination folder. 

Encrypted Content

We migrate MIME content in an as-is state. S/MIME messages can be migrated and remain encrypted at the destination. Viewing them on the destination requires the same certificate used to encrypt them, including their corresponding private key. 

Messages with Azure Information Protection are migrated, but not viewable at the destination, as the source tenant policies are not available on the destination.
You can migrate them in a viewable format, by decrypting these messages on the source and migrating the decrypted emails.

If you need to encrypt them at the destination (this is optional), simply recreate the security policies on the destination and then reapply the policies to the migrated messages.

Our data retention and security policies can be reviewed on our BitTitan Data Security and Privacy Policy page.

Color Categories

The default colors are maintained during migration. However, if additional color categories have been defined at the Source, other than those supported at the destination, they are not migrated. Instead, they are converted to the default calendar color at the destination.

For example, Google supports more calendar colors than Microsoft 365. Any calendar colors on Google that are not any of the six (6) default colors on Microsoft 365 (blue, orange, green, purple, red, yellow) will be converted to the default color on Microsoft 365 (light red).

Calendar Meeting Links

Lync, Skype, or Teams events are migrated but do not usually work in the destination because the links are for the source environment. These events need to be recreated at the destination. There are exceptions to this rule, but they are not consistent.

Mailbox Migration FAQ

Licensing Large Items

You are limited to 50 GB of data transfer per license that you purchase.

If you have a mailbox requiring over 50 GB of data transfer and you have purchased a mailbox license, your migration will stop automatically after transferring 50 GB.

However, you can restart the migration from where it left off by purchasing another mailbox license and resubmitting it for a new migration.​

Assign M365 Licenses to Individual Users or a Group of Users

MigrationWiz improved its functionality to allow license management and assignment for users and groups for Microsoft 365 mailboxes during regular mailbox migrations. This feature can be accessed within your mailbox project by simply navigating to the mailbox project created and selecting the 'Apply Microsoft 365 Licenses' option.

Important

In the past, license management and assignment were only available during coexistence migration. The process for assigning an O365 license now mirrors that of the T2T project behavior.

Apply Licenses.png

With this enhanced functionality, MigrationWiz customers can seamlessly incorporate license assignments into their regular mailbox migrations, granting them finer control over the backend processes during migration. Customers retain the flexibility to revisit and modify the default license type selection at any time. Furthermore, they can make decisions regarding future license applications during the discovery phase.

To access this feature, follow the steps below.

  1. Navigate to the Source/Destination section of the Advanced Options.
  2. Select the Apply Licenses to Target Mailboxes during the Pre-Stage Process checkbox in the Destination section.
  3. Navigate to the mailbox project and select Apply Microsoft 365 Licenses to enable license assignment.

Important

This feature is only available with Microsoft 365 mailboxes.

Shared Mailboxes

Shared mailboxes migrate similarly to a regular mailbox migration.

  • Migration with administrative credentials
    From the MigrationWiz dashboard, click on the Quick Add button and enter the email address of the shared mailbox at the Source, and the email address of the shared mailbox at the Destination.

    When the migration is performed, it migrates with the administrative credentials added when creating the project. The administrator account must have full access permissions to the shared mailbox to perform the migration.

    If you perform a Bulk Add of users, simply include the shared mailboxes in the CSV file that is used to import the mailboxes into the MigrationWiz dashboard.
  • Migration without administrative credentials
    From the MigrationWiz dashboard, click on the Quick Add button and enter the email address of the shared mailbox at the Source, and then the login name and password of either the owner of that shared mailbox or an account that has full access permissions to the shared mailbox.

    Also, enter the email address of the shared mailbox at the Destination, and then the login name and password of either the owner of that shared mailbox or an account that has full access permissions to the shared mailbox.

The screenshot below using the fictitious acme.com provides an example of how to add the shared mailbox into the MigrationWiz dashboard, for the Destination.

migratesharedmailbox.png

The login name and password can only be added if the MigrationWiz project is created without administrative credentials.

Refer to the Create a Shared Mailbox article from Microsoft for more information about how to create and use shared mailboxes in Office 365.

As with a regular mailbox migration, it is necessary to purchase mailbox migration licenses or User Migration Bundle licenses to perform the migration.

Shared mailboxes make it easy for a specific group of people to monitor and send emails from a common account, like public email addresses, such as info@mining88.com or contact@mining88.com. When a person in the group replies to a message sent to the shared mailbox, the email appears to be from the shared mailbox, not from the individual user.

Shared mailboxes are a great way to handle customer email queries because several people in an organization can share the responsibility of monitoring the mailbox and responding to queries. The customer queries get quicker answers, and related emails are all stored in one mailbox.

Shared mailboxes are also ideal for storing the mailbox contents of terminated employees.

It is not necessary to assign licenses to shared mailboxes in Office 365, except when they are over their storage quota of 50GB.

In the back end, shared mailboxes are identical to user mailboxes. Look at the user list; there will be a user created for the shared mailbox.

Mailbox Size

There is a relationship between mailbox size and data transferred but they can be quite different and cannot be compared directly.​ The size statistics shown on the mailbox statistics page indicate the amount of data transferred over the wire. This typically differs from your mailbox size (as reported by your Source email system) for different reasons including:

  • Size calculation: Your Source email system calculates and reports mailbox sizes using proprietary formulas and methods.
  • Content conversion: The same data may be encoded using different formats at the Destination (i.e., plain text + HTML MIME parts).
  • Protocol overhead: Data, as read from the Source, often includes protocol data such as headers, flags, IDs, and more.
  • Data encryption: Unless you configure your connection to use non-SSL endpoints, all data will be encrypted.
  • Data compression: Data may be compressed or decompressed during storage or transmission.
  • Data encoding: Many communication protocols will encode data (like Base64 encoding, and SOAP encapsulation).

Also, some items may not be migrated or may fail to migrate, depending on the error count specified on your project.

If you are trying to compare mailbox sizes because you are looking for missing items, click here.

Add Mailbox to Existing Project

  1. Sign in to your Migratio​nWiz account.
  2. If you do not see your projects listed, click on the Projects​ section.
  3. Click on the name of your Project in the list. 
  4. Click on the Add button.​​

Sent Items Migrated to the Wrong Location

This article applies to mailboxes whose Source "Sent Items" folder was successfully migrated, but whose location at the Destination is different from the expected one.

The IMAP protocol only identifies the "Inbox" folder as a system folder. There is no clear identification of other system folders such as "Sent Items", "Deleted Items", and others.

For example, a "Sent Items" folder may be labeled as “Sent Items”, “My Sent Items”, “Sent”, “Sent emails”, “Courrier Envoye”, ”Sendte emails”, and so forth. There is no reliable way for us to detect if a specific folder is a Sent Items folder. For this reason, we map folders by name.

​​However, we support folder remapping as an advanced feature. To implement specific folder mappings:

  1. Go to Advanced Options. To enter Advanced Options within the new MigrationWiz interface, select your project name, then click on Edit Project at the top left, then click on Advanced Options at the bottom right.
  2. ​Within the Support Options section, specify the following:
    FolderMapping="^SourceFolder->DestinationFolder"
    Example:
    FolderMapping="^My Sent Emails->Sent Items"
  3. ​​Click on Save Options.
  4. Click on Save Project.

The expressions on the left and the right are regular expressions.

Migrating Permissions

Folder permissions are migrated using the following approach:

  • First, MigrationWiz tries to match the source primary SMTP email address to the destination primary SMTP email address.
  • Next, MigrationWiz tries to match the source display name to the destination display name. If more than one match is found on the destination display name, a failure occurs and the permissions are not assigned to that particular UserID.

By default, MigrationWiz only migrates Mailbox Folder Permissions for System folders. To migrate permissions on folders that were created by users, the Advanced Option must be set to MustMigrateAllPermissions=1 in your project.

This setting is an option because it is not a best practice and scanning for permissions slows down the migration.
We do not migrate any permissions for the Default or Anonymous user accounts.

Merging Mailboxes

If you intend to merge several email accounts that you have been managing separately into a single email account, you can do it via MigrationWiz, by migrating all Source mailboxes at the Destination where they are mixed. Consider that you need to purchase as many licenses as Source mailboxes you want to merge.​

You need to perform the following steps:

  1. Create a Project, and add a mailbox to migrate from the first Source mailbox to the single Destination mailbox.
  2. Submit the migration from the first mailbox to the Destination mailbox.
  3. Wait until the migration has been completed.
  4. Add a mailbox to migrate from the second mailbox to the same Destination.
  5. Open Advanced Options.
  6. Under Support, checkmark the Do not search destination for duplicates button.
  7. Submit to migrate from the second mailbox to the single Destination mailbox.
  8. Wait for completion.

    Important

    If you have more than two accounts, repeat Steps 4 through 8. Requiring two or more licenses, one for each Source mailbox.

Important

If you have duplicate email messages across Source mailboxes, you will encounter duplicate ones at the Destination mailbox.

You can also migrate the Source mailboxes into individual subfolders at the Destination as described in Folder Filtering and Mapping.

Migrating Suggested Contacts and Autocomplete Lists

It is important to understand the difference between Autocomplete Lists and Suggested Contacts.

Autocomplete Lists

When email addresses are typed in, Outlook remembers them and can offer autocompletion when adding recipients to a new email message. The Autocomplete List stores email addresses in a server-side hidden file. Therefore, those contacts remain accessible when a user has multiple computers running Outlook 2010 or later.

If you are using the DeploymentPro product to automate the configuration of Outlook profiles, Autocomplete Lists are migrated over to the new profile, as part of the process. The DeploymentPro Guide provides more information on the steps to follow to run DeploymentPro projects. If you are using DeploymentPro, you do not have to manually migrate these.

Suggested Contacts

Suggested Contacts is a special contact folder introduced with Exchange 2010 and was removed in Exchange 2013. This folder creates contacts for each new address a user sends an email to.

Summary

This table shows which type of contacts are supported by Outlook/Exchange, depending on the version.

Type

2010

2013

Autocomplete List (mailbox data)

 x 

 x 

Suggested Contacts

 x 

 ​​

  • Autocomplete Lists:
    • From Exchange Server 2003 / 2007 (.Nk2 file): MigrationWiz does not migrate these. This process must be done manually.
    • From Exchange Server 2010 / 2013 / 2016 (server-side file): MigrationWiz does not migrate these. The DeploymentPro product migrates these. If you are not using DeploymentPro, the process must be completed manually.
  • Suggested Contacts:
    • From Exchange Server 2003 / 2007 / 2013 / 2016: Not applicable.
    • From Exchange Server 2010: Are migrated by MigrationWiz.

Autocomplete Lists and Suggested Contacts cannot be migrated if the Source Exchange server is unavailable.

Finding Large Items 

The size item limit on the Destination may be lower than the Source. This results in migration failures for those items that are larger than the limit on the Destination.

Before you start a migration, it is possible to identify the items that will fail to migrate by doing a mailbox search for large items on the Source.

  • This is an end-user approach, which requires each end user to perform these steps. 
  • This article includes instructions for Outlook clients and G Suite webmail clients. Refer to the option that matches your client.

Option 1: Using Outlook Client

  1. Create a new search folder.
  2. In the resulting dropdown list, scroll down, select Large mail, and click Choose...
  3. Change the number to the item size limit on the Destination (e.g., 25000) and click OK twice.

You have a new folder under Search Folders, that displays all the emails that are larger than the selected size.

Option 2: Using G Suite webmail client

  1. Access the G Suite Gmail website.
  2. On the Search box, type the item size limit on the Destination (e.g., 25000000) and click the search icon.

The value entered in the search box must be in Bytes.

Configure Users Who No Longer Exist in the Source Tenant

MigrationWiz allows customers, with long-running projects, to quickly tag inactive accounts on the source tenant and remove them (if needed) with just one click, to ensure the accuracy of their user lists.

This option is available for all mailbox migrations in the Quick Add and Bulk Add options, allowing you to choose the mailbox status as Active or Inactive

Use the Quick Add option when adding one mailbox item at a time. To configure the status, scroll down to the Mailbox Status Options section and select the Active or Inactive status from the dropdown list.

Quick Add.png

Otherwise, use the Bulk Add Items to import and configure more than one mailbox at a time using a CSV file. After selecting the CSV file, set the mailbox status in the User Status column by choosing the Active or Inactive status from the dropdown list.

Bulk Add - Status Column.png

Also, the Bulk Add Items feature allows you to choose the items to migrate from your database.

You can check the checkbox next to them or apply any of the following rules:

  • Only newly detected active mailboxes will be migrated, if you want to migrate only the active mailboxes in the CSV file.
  • All newly detected mailboxes will be migrated, if you require to migrate all the new mailboxes regardless of status in the imported CSV file.
  • Old and new detected mailboxes will be migrated, if you want the entire data from the imported CSV file.

    Important

    In this case, the already migrated existing mailboxes on the destination tenant are overridden with the current updated information.

Rediscover Items

MigrationWiz provides you with a new brand feature that allows you to detect additional mailboxes that were added to their Microsoft Entra ID scoping group all the mailboxes at the source tenant, besides providing you with a downloadable CSV file with all the important data about the migration, such as email, login name, and status of source accounts in the tenant.

Important

The Rediscover Items option is exclusively designed for O365 T2T (Tenant-to-Tenant)with Coexistance enabled scenarios. Rediscover Items helps identify items added to Microsoft Entra scoping groups and synchronizes the distribution of item lists. The Sync Distribution of Items List option is specifically tailored for use in T2T coexistence projects.

Performing Rediscover Items
Start Rediscover Download CSV

Perform this feature following the steps below:

  1. Select the Rediscover Items operation during the migration.
  2. Wait until the process is over.

Bulk Address Change

Domain Name

There are two ways you can bulk update the domain name in the email addresses of migration mailboxes:

  • You can use the Change Domains button in MigrationWiz.
  • You can download and run the Change-MW_ExportAddresses and Change-MW_ImportAddresses PowerShell scripts attached at the bottom of this article. 

Why might it be necessary to change the Source or Destination address of all your Users on a MigrationWiz Project? 

  • If you are performing a tenant-to-tenant migration while keeping the same domain name, and you started the migration using the vanity domain on the Source addresses, we recommend using .onmicrosoft.com addresses for both Source and Destination addresses to avoid this.
  • If you just ran Autodiscover on MigrationWiz to discover all your Source mailboxes, and you are migrating into a different Destination email domain.

These examples are two among others that might make it necessary to have to change those addresses.

Use the Change Domains button

MigrationWiz now provides the option of doing a bulk update of email addresses on both the Source and Destination computers, where the change is of the address domain.

When you click on the Change Domains button, the box opens to allow you to bulk change the domain associated with mailboxes on the Source or Destination.

Full Addresses 

Use the BitTitan SDK PowerShell Script

  • If the BitTitan SDK is not installed on your computer, the first step is to download and install it. Our SDK includes the PowerShell and the Management Console modules. The pre-requisites and download link for the SDK can be found here: Install the BitTitan SDK
  • Download the PowerShell script(s) required to make the bulk changes. Links for downloading the scripts can be found at the bottom of this KB: 
    • The Change-MW_ImportAddresses script changes all Destination addresses
    • The Change-MW_ExportAddresses script changes all Source addresses.
  • Both scripts make changes based on a CSV file, that needs two columns, as shown below:
  • You must name column A as "UserPrincipalName" and column B as "NewUPN", because those are the names hard-coded in the script.
    • List all the current addresses in the project in column A.
    • List all the new addresses, with the new domain name, in column B.

You can obtain those addresses by exporting them via PowerShell when connected to the Source or Destination system (i.e., via the On-Premises Exchange or the Exchange Online PowerShell).

Follow these steps to run the PowerShell scripts:

  1. Once you run the script, enter your MigrationWiz credentials in the prompt.
  2. Enter the MigrationWiz project name and the location of your CSV file.
  3. Let the script run and change all the Source or Destination addresses, as defined in the CSV file.

"Sent Items" Folder

This information applies to mailboxes whose Source "Sent Items" folder was successfully migrated, but whose location at the Destination is different from the expected one.

The IMAP protocol only identifies the "Inbox" folder as a system folder. There is no clear identification of other system folders such as "Sent Items", "Deleted Items", etc.

For example, a "Sent Items" folder may be labeled as “Sent Items”, “My Sent Items”, “Sent”, “Sent emails”, “Courrier Envoye”, ”Sendte emails”, etc. There is no reliable way for us to detect if a specific folder is a Sent Items folder. For this reason, we map folders by name.

​​However, we support folder remapping as an advanced feature. To implement specific folder mappings:
  1. Go to Advanced Options. To enter Advanced Options within the new MigrationWiz interface, select your project name, click  Edit Project at the top left, and then click Advanced Options at the bottom right.
  2. ​Within the Support Options section, specify the following:
    FolderMapping="^SourceFolder->DestinationFolder"

    Example:

     FolderMapping="^My Sent Emails->Sent Items"
  3. Click on Save Options.
  4. Click on Save Project.

The expressions on the left and the right are regular expressions.

Changing MX Records During Migration

MigrationWiz uses the information you specify on your Project (hostname, URL, and more), in conjunction with email addresses or other credentials, to connect to Source and Destination items. We do not use MX record information to connect to Source and Destination items. The MX record for your domain may point to the Source or Destination system. MX record information controls where email gets delivered, but we never use MX record information to log in to the Source, or the Destination.

Only incorrectly changing A records may affect the URL or hostname you specify on your Project. If you need to update A records in DNS, note that we accept URLs and host names in IP format.

Calendars 

Recurring appointments

In some cases, you may find a migrated recurring series with a yearly recurrence when the Source used a different recurrence pattern (for example, every two weeks). This is incorrect but done as a way to address the limitations of the Source system.

​This happens when migrating from Source systems that do not return the recurrence pattern via their API. Instead, those Source systems return individual (expanded) recurring appointments. For example, if the recurrence pattern occurs every two days, the Source system may return:

Instance #1 - 6 PM on January 1st 2014
Instance #2 - 6 PM on January 3rd 2014
... more instances (some customized, some not) ...
Instance #50 - 9 PM on August 1st 2014 (customized instance)

In those cases, we do not have access to the recurrence pattern from the Source system, so set a default recurrence (yearly recurrence). We then make each instance part of the same series and position it at the correct time. Even though the recurrence pattern is incorrect, all instances are positioned correctly and the recurring series can be managed as a whole (i.e., can cancel the entire series instead of having to manage each instance separately).

Suppressing calendar reminders

When a calendar item has a reminder on it, we migrate the calendar item and its reminder settings. When a reminder is dismissed, the fact that it was dismissed may be stored locally on the email client. For example, Gmail/G Suite does not store whether an appointment has been dismissed or not on the server.

Therefore, when items are migrated from the Source mail system to a new Destination mailbox, previously dismissed reminders may be reactivated. In most cases, a one-click action is sufficient to dismiss all reminders. However, OWA may struggle to dismiss thousands of reminders and "hang".

To suppress reminders for old appointments, before migration, set the following Advanced Option:  SuppressReminderDays=X

Steps:

  1. Click on Edit Project.​​
  2. Click on Advanced Options.
  3. In Support Only options, set: SuppressReminderDays=X
    • The value of X must be between 1 and 365 (inclusive).
    • Setting a value of X will mean that appointments whose end date is before [date of migration - X days] will have their reminders suppressed. 
    • Advanced Options are case-sensitive. The entry should be entered exactly as above (but change the "X" to a numerical value).

Archive Migrations

A note on root migrations

Exchange migrations do not migrate from the root, as EWS only sees and migrates items contained in folders. To migrate items at the root, create a folder for these items, drag and drop the items into the folder, and then migrate as usual. 

Mailbox and archive migration options

Perform a standard mailbox-to-mailbox migration

This is considered a mailbox migration project.
Leave the Advanced Options at their default options, i.e., "migrate to mailbox" for Source and "migrate to mailbox" for Destination. When migrating, you specify the Source and the Destination mailboxes.
Once the migration is complete, you could set Office 365 archiving rules so that mail will be moved to the archive mailbox, but that all occur post-migration.

Perform a mailbox to archive migration

We support migrating directly to an archive mailbox. In this case, you would enter Advanced Options for your project and select archives as the Destination, as in the screenshot below. You would then save these settings and run your migration following normal procedure.

This would still be considered a mailbox migration. Therefore you would create a mailbox migration project and purchase mailbox migration licenses or User Migration Bundle licenses.

Perform an in-place archive to mailbox migration

When creating a project, choose an in-place archive migration project.

In this case, you would leave the Advanced Options at their default destination setting, Migrate to Mailbox.

This requires User Migration Bundle licenses.
 

Perform an archive-to-archive migration

This is also considered an archive migration project.

In this case, you would change the Advanced Option for Destination to Migrate to: Archive.
This requires archive licenses, rather than mailbox migration licenses.

 

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