Preparation is an important part of achieving a seamless migration process. The following information covers Access & Security, Throttling, and Archiving within the source and destination environments.

Access & Security

We support using a fully qualified domain name (FQDN) or an IP address. Regardless of whether you specify a FQDN or an IP address, both must be accessible via the internet by our migration servers.

MigrationWiz uses advanced logic in handling firewalls. We have tested our service against many different firewalls to ensure proper migration. As long as your server is accessible from the internet, MigrationWiz should be able to migrate your mailboxes without a problem.

If the APIs we connect to are protected by multi-factor authentication, we cannot connect to your server.

We suggest you create an exception policy on your firewall for migration that bypasses the multi-factor authentication layer.

We suggest you perform a free trial to guarantee it works for you. If you experience any problems, contact our technical support.

Data Security

When MigrationWiz migrates data,  the data is read from the source by the MigrationWiz servers. It is important for some security protocols that this data does not leave its region, e.g., Australia, Europe, etc.

In MigrationWiz you can define what Region of Destination Tenant you want us to use for Google Workspace, Hosted Exchange, and Dropbox endpoints when creating your project.

For Microsoft 365 mailbox and archive migration, MigrationWiz automatically detects it.

Throttling

Setting Throttling Limits

Throttling allows you to modify the volume of migration throughput to accommodate network bandwidth on the Source or Destination systems. In some cases, you may need to limit throughput, while in others you may be able to increase throughput.

In a low-bandwidth or low-performance environment, you may be required to cap the bandwidth used for migration to avoid any service disruptions.

We recommend the following:

• You can limit the number of concurrent connections on your project (we will only open one network connection per item).
• Many systems (like Exchange 2010 or later) allow you to configure throttling policies which can be used to control load.
• Many routers or firewalls allow you to configure rate limits by URL or originating IP.

In addition, note the following:

• In a low-bandwidth environment, we recommend pre-staging your data ahead of time.
• You may implement an IP lockdown for your migration If it is useful to know incoming IP addresses.
  

  Important

  IP LockDown does not work with BitTitan Autodiscover using MigrationWiz. To add Users to the project, use Bulk Add via a CSV file or add them manually.
• When submitting migrations, you can specify a delayed start (for example, start the migration at 1 AM on a Saturday).

You can find specific guidance on setting or removing throttling in the migration FAQs specific to your source or destination and it should be used in conjunction with your migration guide. 

Specifying the Number of Simultaneous Items

Specifying the number of simultaneous items to migrate controls the quantity of needed bandwidth. Submitting all of the mailboxes for migration, the system enforces the number of items that we perform simultaneously and automatically under the covers. We only open one network connection per item actively migrating.

​To specify the number of simultaneous item migrations:

The default value is 100. To prevent overwhelming the source server, set a lower value if there are bandwidth concerns, such as 15. This value may be modified while mailboxes are migrating. It may take a few minutes for the modified setting to take effect.

Increasing this number increases the number of simultaneous migrations instantly. For example, if the value is increased to five to 10, five additional items will begin to migrate.

Decreasing this number does not lower the number of items currently migrating. For example,​ if the value is decreased from 10 to five, five items currently being migrated will not be immediately stopped. Instead, all 10 items will continue to migrate, and only when the active migrations drop below 5, will additional items start migrating. To decrease the items in progress, stop the migrations that exceed the limit and resubmit them.​​

Archiving & Data Retention

MigrationWiz will preserve all dates associated with your email data, except for the creation date. As each item gets created at the Destination, the create date is set to the current time. Other properties such as the received date, the end date, etc., remain identical to what they were at the Source.

We find that most archiving and content policies do not evaluate the creation date, but do evaluate other dates, such as the received date. Therefore, it is likely that archiving and content policies will process migrated emails. You can learn more about how dates are evaluated here: http://technet.microsoft.com/en-us/library/bb430780.aspx.

If you are migrating to Office 365, note that default archiving policies will move items older than two years to the archive mailbox.