MigrationWiz - Advanced Options & General Options

When you created a project, you defined the Source, the Destination, and the items that need to be migrated. This can be mailboxes, documents, archives, etc. The MigrationWiz project also has Advanced Option features that will allow you to customize the project even more.

These are broken down into General Options and Advanced Options. Under Advanced Options, you may 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 Filtering Maintenance Licensing Performance
  • Send successful migration email notifications: Choose who to notify when a migration has been executed successfully.
  • Send failed migration email notifications to: Choose who to notify when a migration fails.
  • Customize Notification Email: Customize email for success, failure, and request for credentials. Use certain keywords as codes for certain data. OAuth 2.0 does not use customized email; it will only use the default.

You can use Markdown syntax to format your email. 

Specific Migration Type Options

Mailbox

Source Destination

  • Migrate From: Choose between migrating from Mailbox, Archive (only with archive project), or Recoverable items. If migrating from Recoverable items, we recommend you have a litigation hold on.
  • Use  Impersonation to Authenticate

Failing Items

Several options can impact whether certain items in a mailbox get migrated. Ensure these options are not blocking the items from migrating.

Project Level Item 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)

Advanced Options

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

Bulk Load

The Bulk Load feature is available as part of the Advanced Options for all Mailbox migration projects. This powerful feature allows you to upload up to 40,000 items related to any type of advanced options but you can mostly use it with:

  • Recipient mappings.
  • Folder mappings.
  • User mappings.
  • Additional project-specific Support Options for your scenario.

Once you create your project, you can import your support option under the Support tab of the Advanced Options by following the steps below.

Support Tab.png

  1. Click Import Multiple Support Options.
  2. Import your support options.
  3. Check your imported items.
  4. Validate and save your changes.

Import Your Support Options

You can import your support options in two ways, no matter which one you choose, consider the following points before importing them:

  • Review carefully the support options to import.
  • Consider that each line break or space between characters splits the command line, e.g.:
    If you add the Example =1 support option, it will be imported as
    Example
    =1
Import Via File Import Via Text

Keep in mind that if you want to import your support options via file, you can prepare a .TXT file beforehand. Any other format file is not supported.

To select your file:

Import Multiple Support Options.png

  1. Click Browse.
  2. Choose your file.
  3. Click Import Multiple Support Options.

Check your Imported Items

MigrationWiz offers powerful tools such as pagination and the search field to help you review your imported items.

Pagination Search

MigrationWiz allows you to easily review your imported options by grouping them in a set of options per page, avoiding overwhelming you with a bunch of data.

Pagination.png

You can perform the following actions by clicking:

  • > You go to the next page.
  • < You go backawards.
  • << You go to the beginning.
  • >> You go to the end.

Important

The number of visible options on each page is configurable, you can set it up in groups of 20, 40, or 60 items.

Validate and Save Your Changes

Once you review your imported list, it is time to validate it. To do so, click Validate.

This validation shows all the possible issues found in the imported list. MigrationWiz shows and addresses them at the top of the first-page list. Besides, at the bottom of the list find notifications of the validation process. The issues addressed can be related to:

  1. Duplicate key.
  2. Value errors.
  3. Sintax key errors.

After completing a successful validation the following message will be shown at the bottom of the page.

Sucessful Validation.png

You will notice that the Validate and Save buttons are active and clickable. Click Save to save your imported items, otherwise, you will lose your AO list.

Warning

MigrationWiz will not allow you to save your changes until you solve or erase all the addressed issues from your list.

In case MigrationWiz encounters issues but you think the validation is wrong, at the bottom of the list you will find the following notification:

Bulk Add-Errors Notification.png

If you click the notification link, you will be able to save your list. For more information about errors please refer to the Advanced Options Notifications article.

Consider that some fields won't be saved at any chance. For more information about this behavior please review the Validation Notifications section of the Advanced Options Notifications article.

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

You may perform a Mailbox-to-archive migration simply by setting the Edit/Project/Advanced Options (Source/Destination Tab) within a Mailbox migration project to “Migrate to: Archive”.

Recipient Mappings

Recipient mapping is used in mailbox migrations to ensure that the user information maps properly from the Source to the Destination, particularly in cases where the user name or domain name has changed. Below is a table that lays out the properties that are converted for each item to be migrated:

Email Appointments

The migrated items for email are the following:

  • Sender
  • From
  • ToRecipients
  • CcRecipients
  • BccRecipients

Recipient mapping is useful in a variety of ways:

  • All emails remain responsive 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 the destination when performing a tenant-to-tenant migration, while keeping the same domain name or when changing domain names from Source to Destination.
  • A project is required for each Destination domain if you use a recipient mapping while migrating from one Source domain to multiple Destination domains.

Use cases:

  • When migrating from Microsoft 365 to Microsoft 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.

RecipientMapping="@sourcetenant.onmicrosoft.com->@destinationdomain.com"

  • When you are migrating over to a new domain name.
    • Source domain = Sourcedomain.com
    • Destination domain = Destinationdomain.com
    • Here is an example - Migrating James@Sourcedomain.com to james@Destinationdomain.com you want to make sure that any entries for james@Sourcedomain.com are renamed to james@Destinationdomain.com during migration.

RecipientMapping="@sourcetenant.onmicrosoft.com->@destinationdomain.com" RecipientMapping="@sourcedomain.com->@destinationdomain.com"

For Large Migrations

A large number of recipient mappings (5,000+) may cause huge migration performance loss. If you are performing a large migration, add UseHashMapRecipientMapping=1. This will address such problems.

Important

You can simplify migrations and avoid errors using a .TXT file for recipient mappings in MigrationWiz. For more information regarding this topic please review the Bulk Load section above.

By opening the collapsible tab, you can compare the use of this Advanced option.

Project Configuration and Expected Behavior

Below is a comparison of project configuration and expected behavior with/without this Advanced Option:

Project AO COnfigurations Remark

RecipientMapping="user01@source.com->user01@destination.com"
RecipientMapping="user02@source.com->user02@destination.com"
RecipientMapping="user03@source.com->user03@destination.com"
RecipientMapping="user04@source.com->user04@destination.com"
RecipientMapping="user05@source.com->user05@destination.com"
……
……
RecipientMapping="user5000@source.com->user5000@destination.com"

This uses the old way of processing recipient mappings.

In this case, 5000 mappings are configured. The migration should expect slowness during migration.

UseHashMapRecipientMapping=1
RecipientMapping="user01@source.com->user01@destination.com"
RecipientMapping="user02@source.com->user02@destination.com"
RecipientMapping="user03@source.com->user03@destination.com"
RecipientMapping="user04@source.com->user04@destination.com"
RecipientMapping="user05@source.com->user05@destination.com"
……
……
RecipientMapping="user5000@source.com->user5000@destination.com"

Same way of configuring recipient mappings, but with UseHashMapRecipientMapping AO added.

This will cause recipient mapping to be handled differently by MigrationWiz and will greatly increase the performance.

Important

With the new AO, MigrationWiz will identify each “RecipientMapping” item configured as a direct mapping item. Therefore the user has to make sure the mapping is correctly configured with the exact SMTP address, e.g.:

RecipientMapping="user01@source.com->user01@destination.com"

User Prefix Changes

If a user's SMTP address is changing during the migration, Recipient Mapping can be used to ensure that message headers are rewritten with the new prefix. An example is if john.doe@sourcedomain.com was changing to john.doe2@destinationdomain.com. This is common during mergers when migrating data to an existing Microsoft 365 tenant and there are user name conflicts.

The following explains how to add a user prefix Recipient Mappings to your project’s Advanced Options.

Under Support/Support Options:

  • Recipient Mapping should be added to each project under Advanced Options/Support Options.
    • RecipientMapping="john.doe@abc.com->john.doe2@xyz.com"
  • Note that Recipient Mapping changes are made according to the order in which the mappings are added to the Support Options. Ensure that the prefix mappings are at the top of the Advanced Options list so they are performed first and not superseded by the action of a domain-level recipient mapping option, e.g., RecipientMapping="@abc.com->@xyz.com". Changes are made based on mappings added from the top down. Therefore, ensure that Recipient Mappings are noted in the correct order you wish them to be performed. 
  • If you have multiple projects in progress for the same migration (e.g., batches), make sure that these mappings are also in the other project.  
  • MigrationWiz performs the SMTP rewrite during the migration process. The Source and Destination SMTP addresses for the mailboxes in the project are simply to define the Source and Destination matching. It does not correlate to any changes to email headers during the migration. This is why recipient mapping is mandatory, it ensures responsivity.

Destination Language

The spelling of both 'Calendar' and 'Contacts' must also reflect the language of the folder name at the Destination mailbox, e.g., 'Calendar' will be 'Calendrier' in French and 'Contacts' will 'Contactpersonen' in Dutch.

G Suite (GMail API) Limitations

For ‘GSuite (Gmail API) to GSuite (Gmail API)’ migrations only:

If you want to map multiple source labels into a single label on the destination, then the parent destination label must be created before starting the migration.

Example: If you wish to map three Source labels ('ABC', 'PQR', and 'XYZ') into one parent label ('DestinationLabel') at the destination then you must create the parent label ('DestinationLabel') at the destination mailbox before running the migration.

Enable Auto Remapping for Migrating Users

MigrationWiz has an Advanced Option available which can be added at either the project level or the individual item level, which remaps the Source email address over to the new Destination email address.

To set this, add the following flag under the Support options/support field:

AutoRemapMigratingUser=1

There are a couple of examples where this is useful:

Considerations

  • MigrationWiz does not auto-remap the migrating user unless this option is set.
  • We do not set this by default since we do not want to modify any content during migration, unless our Partners deem this as necessary, by adding this as an Advanced Option.
  • An alternative, and preferred, methodology for such remappings is to use the Advanced Option "Recipient Mappings".

Here is a breakdown of the exact functional behavior patterns, when adding this option:

  • It will auto-remap:
  • For:
    • Mail (sender + receiver  + extra entries such as CC and BCC addresses).
    • Calendar (organizer + attendees  + extra entries in the calendar item, such as resource rooms, and optional attendees).
  • Including:
    • ItemAttachment (for any attachment to items).
    • Recurrence exception (for calendar recurring meetings).

This Advanced Option has the following limitations:

  • We do not support recipient mapping for the actual MIME content, so email mime content-based migrations, such as Zimbra, won't have a remapping for email.
    • Further explanation: the MIME content is the information listed under Show Details, for a message, for most email systems.

Here is a breakdown of migration scenarios, to specify which scenarios support this Advanced Option:

Supported Not Supported
  • Exchange 2003+, or Microsoft 365 as a Source

    Important

    Exchange 2003 will migrate using WebDAV. Exchange 2007 can migrate using WebDAV or EWS, Exchange 2010+ will migrate using EWS.

  • GoogleApps as a Source
    • Limitations: Calendar entries do support this option. Email entries will not support this option because migrations are based on MIME content.
  • Zimbra as a Source
    • Limitations: Calendar entries do support this option. Email entries will not support this option because migrations are based on MIME content.
  • Lotus Notes as a Source

    Important

    Consider the following points:

    • Lotus' recipients are extracted inside the local LotusExtractor as an Attribute of LotusWebServiceItem instead of MIME content.
    • The customer's email addresses on the Domino/Lotus server are in X400 format instead of SMTP, so inside LotusExtractor, we have a translator that translates and maps these email addresses.

Refer to the Help Center article How do I add support options to a project or to a single item? for exact instructions on how to add this support option: AutoRemapMigratingUser=1

Important

The flag is case-sensitive, so be sure to add the flag exactly as indicated above.

Email Notification Customization

You can customize the notification emails that MigrationWiz sends for successful migrations, and failed migrations, or to verify credentials from the customer’s users.

Complete these steps to customize notification emails in MigrationWiz:

  1. Sign in to MSPComplete.
  2. In the MigrationWiz Project Details section of the Getting Started page, click Go To My Projects.
  3. In the top left corner of the page, select the appropriate workgroup.
  4. Click the project for which you want to customize email notifications.
  5. Click Edit Project in the top menu bar and click Advanced Options.
  6. In the Customize Notification Email section, select one of the following tabs:
    • To customize the notification email for a successful migration, select Success and add a checkmark next to Customize "successful migration" email.
    • To customize the notification email for a failed migration, select Failed and add a checkmark next to Customize "failed migration" email.
    • To customize the notification email for requesting credentials from users, select Credentials and add a checkmark next to the Customize "request credentials" email.
  7. Type your edits into the Subject or Message text boxes. At this time, the notification emails only support simple text customization.
  8. The following parameters can be used to customize the notification email even further. These parameters pull information from MigrationWiz and the configured project.
  9. Click Save when you have finished editing the notification email.

MigrationWiz notification emails originate from support@migrationwiz.com on behalf of your BitTitan user account. This cannot be changed; this feature was designed to prevent potential abuse.

Parameters
Project Type: The type of migration project (mailbox migration, document migration, etc.).

  • SourceSystem: The source environment (Hosted Exchange, G Suite, Microsoft 365, etc.).
  • SourceIdentifier: The source account (user@domain.com).
  • DestinationSystem: The destination environment (Hosted Exchange, G Suite, Microsoft 365, etc.)
  • DestinationIdentifier: The destination account (user@domain.com).
  • AdminFullName: The full display name of the MigrationWiz administrator (John Doe).
  • AdminEmailAddress: The email address of the MigrationWiz administrator (user@domain.com)
  • FailureMessage: The error message for a failed migration. (Reason: Your migration failed to check source credentials.). This parameter is recommended only for the failed notification email.
  • CredentialsUrl: The URL where users can enter their credentials (https://migrationwiz.bittitan.com/user-credentials/input?i=xxxxxx). This parameter is recommended only for the credential notification email.

Folder Max Length

Even though SharePoint and OneDrive support the folder path length is 400, we have to keep in mind that it's a whole path with extra root folders (SharePoint/OneDrive specific folders and Site URL) which can not be on the source, in case of Google Drive or can be shorter, in case of SharePoint/OneDrive.

Currently, MigrationWiz accepts the ShrinkFoldersMaxLength=n values from 50 to 350, where n is equal to the desired number of characters in the folder path. The base of 50 symbols is to keep space for a filename and specific SharePoint/OneDrive root folder extensions. There is a table with path differences below. Bold text indicates the change in the path from the Source to the Destination.

Source
Destination

Changes in the path

Google Drive
SharePoint

Folder1/Folder2
sites/Sitename/DocumentLibrary/Folder1/Folder2

Google Drive
OneDrive

Folder1/Folder2
personal/username_tenantname_onmicrosoft_com/Documents/Folder1/Folder2

SharePoint
SharePoint

sites/Site/DocLib/Folder1/Folder2
sites/LongSitename/LongDocumentLibrary/Folder1/Folder2

SharePoint
OneDrive

sites/Site/DocLib/Folder1/Folder2
personal/username_tenantname_onmicrosoft_com/Documents/Folder1/Folder2

OneDrive
SharePoint

personal/username_tenantname_onmicrosoft_com/Documents/Folder1/Folder2
sites/Sitename/DocumentLibrary/Folder1/Folder2

OneDrive
OneDrive

personal/username_tenantname_onmicrosoft_com/Documents/Folder1/Folder2
personal/longusername_longtenantname_onmicrosoft_com/Documents/Folder1/Folder2

Troubleshooting

If no Tags are Present in Advanced Options (AO), by Default Tags=null are Added 

In case no Tags are present in Advanced Options (AO), by default Tags=null are added in Support Options. However, projects with Tags=XXXXXX do not have any impact i.e. no Tags=null if Tags=XXXXXX is already present in AO.

Was this article helpful?
2 out of 15 found this helpful