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. 
    Note: OAuth 2.0 does not use the customized email; it will only use the default.

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

    Note: 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.
Was this article helpful?
0 out of 3 found this helpful