Adding Accounts

Add from MSPComplete

This option allows you to add items already added in MSPComplete. 

Quick Add

This option allows you to add items one at a time. To do so, provide an email address if you entered administrative credentials when setting up the project. Otherwise, enter the following user information:

• An email address
• Login name
• Password
• Mailbox status

Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

1. Sign in to your MigrationWiz account.
2. Select the Project for which you want to perform the bulk import.
3. Click on Add.
4. Click on Bulk Add.
5. Follow the instructions on the page.  

Columns that are allowed within the import file:

Mailbox Flags

This table provides a list of possible flags that may be set. Specifying a flag value of zero (0) will not enable any flags.

Add the flag values together to enable multiple items. For example, to enable the following:

1. Send an email to the administrator (you) when migration is complete
2. Send an email to the administrator (you) if the migration fails
3. Remigrate previously failed items​

...you would calculate the flag as 1 + 2 + 2097152 = 2097155.

​Autodiscover

​The Autodiscover process within MigrationWiz can discover items from the Source environment to be imported into your projects.

There are a few requirements for this to work:

• The Source must be Exchange 2007 or later, Office 365, or G Suite (IMAP). If you are using Autodiscover from G Suite (IMAP), all G Suite (IMAP) domains must be added to the list of domains in the Endpoint.
• This feature is not supported for in-place archive migration projects, even if the Source is Exchange 2007 or later.
• The endpoint on the Source needs to use admin credentials.
• The admin account specified in the Source endpoint must have an associated mailbox for mailbox migration projects.
• The admin mailbox must be listed in the public Global Address List (GAL).
• The migration project type needs to be a Mailbox migration.
  Important
  For the exact steps to be followed during your migration check the relevant Migration Guide, which can be found on the Help Center site.
• The domain names at the Source and the Destination might be different. Make sure to provide the right information in the project. If they are different, it is best to modify these in your CSV file and then use the Bulk Add feature to import the users into the dashboard.

It is not possible to restrict the source IP addresses of the connection.  This means the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using one of the other available options.

Autodiscover of items will not work while using Modern Authentication

Which items can be discovered within MigrationWiz? 

Autodiscovery exposes the following items:

• For mailbox migration, autodiscovery will list all mailboxes at the Source.

Steps to Run Autodiscover

MigrationWiz

1. Navigate to the project you want to import users into.

2. Ensure that you have created an endpoint for the source project.

3. At the top navigation bar of the project, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.

4. Once discovered, click the Import button, to import the items into your MigrationWiz project.

Rediscover

MigrationWiz provides the customers with a downloadable CSV file with all the important data about the migration, such as email, login name, password, and status of the destination and source tenants.

Perform this feature by selecting the Rediscover Items operation during the migration. When the option opens, click the Download CSV button.

Consider that the download option only works when there is no migration or rediscover process.

Moving Items Between Projects

Use the Move tool on the dashboard to move items between projects, rather than importing users into a new project via CSV. This way, the licenses will move too, along with the statistics and the ability to resubmit Delta passes using the licenses previously consumed on each item.

Steps

1. Click on the checkbox next to the Source Email column to select all of the items, or click on the checkboxes next to the names of the items to select individual items.
2. Click on the Move​ icon on the dashboard. (The icon looks like a cross with arrows)
3. Click on the radio button next to the project name, where these items will move to.
4. Click on the Move Items button. 
5. There will be a confirmation on the screen for the number of all items that​ have been moved.​

Adding an Item to an Existing Mailbox

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

Preventing Duplicates

MigrationWiz uses a system of watermarks to track previously migrated items. There are several advantages to using watermarks instead of detecting items by their names, titles, or other properties.

How are watermarks created and stored for later use?

As items are migrated, a small watermark is embedded in the header of each item. This allows us to track it once it resides in the Destination. Watermarks also convey information such as the endpoint type specified in MigrationWiz. 

Additionally, a matching watermark is stored in one of our databases. We do not store any content data from the item, only the watermark data. The database holds the items that have been migrated and prevents items from being remigrated if they are deleted by users at the Destination.

Because watermarks are tracked in two different places, there is a double layer of protection against the creation of duplicates.

How does MigrationWiz use watermarks in additional migration passes?

When another migration pass begins, the Destination is scanned for watermarks so we will know what data has been migrated. The watermark database is also scanned to prevent the re-migration of deleted or moved items at the Destination between passes. This scanning process occurs at the beginning of every migration pass. The larger the quantity of data migrated, the longer this process will take. For example, a migration that previously transferred 20GB of data will take longer to scan for watermarks than a migration with 20MB transferred.​

Important

Watermarked items are not migrated a second time. Only items found without a watermark will be migrated.

What happens to items at the Source?

Data at the Source will not be modified. this includes watermarks.

How do I delete watermarks?

• If a user manually deletes a migrated item from the Destination, it will not be migrated because it will still be tracked on the back end.
• To delete our end of the watermarks database, check the box next to the migration you want to do this for, then click the circular Reset Items button on the toolbar at the top of the user list. This will only clear our end of the database.
• If you want to delete watermarks stored at the Destination, you must delete the items themselves, as the watermarks are embedded in the item headers. This is typically done only when restarting your migration from scratch. Deleting items at the Destination will only clear the Destination watermarks. Unless the watermarks are reset on our end, items deleted from the Destination will not be remigrated.

To learn more about resetting items and item statistics, see resetting item statistics.

Additional notes

• Due to our use of proprietary watermarks, we cannot detect items migrated by other means. For example, items forwarded from the Source to the Destination (also items migrated by other solutions) will not contain our watermarks. Therefore, we have no knowledge of them existing at the Destination. As a result, we will migrate these items even if they are already at the Destination.
• Since we store the endpoint type in the watermark, changing the Source or Destination endpoint type in between passes will void the watermark and all items will be migrated again. If this happens, a new watermark will be generated in each item based on the new Source or Destination endpoint type.
• If an item at the Source is moved in between passes, we cannot match the Source item with its Destination counterpart. As a result, the item will be migrated a second time. It will then exist in both locations.

We do not impose any limit on item/attachment sizes. However, large items/attachments can fail to migrate because of external factors.  There are two considerations:​

1. What is the maximum attachment size allowed by the Destination system? 
   • ​Most email systems impose size limits. For example, if the Destination system has a 30MB limit, any item/attachment larger than 30MB will fail to migrate.
2. What is the connection timeout for the Source and Destination system? 
   • ​​For security reasons, most email systems close opened connections after a predetermined amount of time. For example, if the Destination system only has 512Kbps of network bandwidth and closes connections after 30 seconds, we may be unable to transfer large items/attachments before the connection is closed.

MigrationWiz will automatically make multiple attempts to migrate large items. Upon completion of a migration, you may resubmit it in error retry mode to try to migrate failed items. This is always free of charge.

When migrating from or to Office 365, Change message size limits in Office 365.

Exchange migrations

When migrating from or to Exchange (2007 and later) using EWS, use PowerShell to increase the size limits. 

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. Other non-standard settings can also cause size restrictions for the IIS or EWS connections, but we cannot troubleshoot or identify specific environment restrictions outside of these settings.

Increase the Message Size Limits of the 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

Three limits 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 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 in one place on 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 connection.

​​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 each change.
5. Change the existing value to maxRequestLength="200000"​ -- this occurs in one place on the Web.Config file.
6. Change the existing values to maxAllowedContentLength="200000000"​ -- this occurs in one place on 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 connection.