MigrationWiz facilitates several types of migrations from source to destination. This article gives a description of each type of migration as well as some basic expectations.
For migration guides, Select the desired migration type and Source environment from the Main Help Center. See also: Supported Migration Scenarios.
To decide what kind of license you need, see Migration License Types.
Collaboration migrations migrate a Microsoft Teams instance from one Office 365 tenant to another. All teams, channels, conversations, files, and permissions are migrated. If changes or updates are made to the Source during the migration, those changes will not be synced to the new folder, so we recommend that this be run when Teams is not being utilized. For more information and suggestions, see Collaboration Migration Best Practices.
Collaboration Migration requires a Global Administrator account to be used on both the Source and the Destination endpoints. This account must also have an Office 365 license applied that includes Teams. The MigrationWiz-Collaboration license is required for this type, as User Migration Bundles will not work.
Document migrations are used to move the contents of a File Server or user-specific Document drive from the source to the new account on the destination. These migrations include documents and files, but not the contents of mailboxes, Public Folders, or archives. Common environments include SharePoint, OneDrive for Business, Office 365, and Google Drive. One common situation that needs to be taken into consideration before running a Document migration is documents that are shared between users, specifically documents owned by one user inside a folder owned by a different user. This situation requires specific settings in MigrationWiz. Most of the Migration Guides do include the settings for this, but you can find out more information in How does MigrationWiz behave in the case of an owned document inside a non-owned folder?
Documents may be migrated all at once, or in batches. Because MigrationWiz is not a sync tool, any changes made during or after migration will not be synchronized. To learn more about how document migrations work, see Document Migration Best Practices.
Hybrid Exchange Migrations: (Feature Coming Soon)
Hybrid Exchange migrations are used when migrating an On-Premises Microsoft Exchange 2010+ organization to Office 365. This project creates user mailboxes on the destination and assigns Microsoft licenses to the users if the licenses have not been previously assigned. MigrationWiz allows management of users and batches within the project, as well as precise control of batch sync and finalization of the migration.
Hybrid Exchange migrations are usually done over longer time periods and often in batches. These projects require an Office 365 Global Administrator account on the Destination. The MigrationWiz-Hybrid license is required, User Migration Bundle licenses will not work. This migration type is specifically set up to accommodate the Hybrid Exchange management process and simplify the change to Office 365.
Mailbox migrations are used to migrate supported contents from a user mailbox on the Source to a user mailbox on the Destination. Supported contents vary depending on the Source and Destination environments and can include folders, email, contacts, calendars, tasks, journals, and notes. For details on what contents are supported for your specific migration, refer to What items are migrated with MigrationWiz?
Most mailbox migrations can use Admin credentials or supplied user credentials. There is also an option to have the user enter their credentials instead of having the credentials entered when the project is created. More information on having the user enter their own credentials, see What if I don’t know the credentials for the item I want to migrate?
Items in a migration can be added by Autodiscover (when supported), individually, or through a CSV. To add from a CSV, follow the instructions in How do I import mailboxes into the system without entering them one at a time?
Personal Archive Migrations:
Personal Archive migrations are used to migrate Personal Archive files, Archive mailboxes (In-Place Archives), or PST files from a File Server or a User account to the Destination. This type of migration is commonly used in conjunction with Mailbox migrations. Supported environments include G Suite, Office 365, Exchange, and EML. These archives may be migrated into an inbox or another archive. When migrating into an archive, we suggest checking on the size limitations of the destination archive before starting the migration. Not all archives will hold the same amount of data and some are created with smaller sizes but will expand. That expansion can take extra time that needs to be accounted for in the project.
Personal Archive Migrations do not support Autodiscover. Users will need to utilize MSPComplete or manual entries (via Quick Add or Bulk Add).
Public Folder Migrations:
Public Folder migrations are used to migrate Exchange or Office 365 Public Folders from the Source to the Destination. It is also possible to migrate from a Public Folder to a Shared Mailbox. You will need to obtain an estimate of the data to be migrated. If you do not already know the size, you can use either PowerShell by using the instructions in How do I find the size of Source Public Folders?, or the BitTitanSDK, which provides you with two components: the BitTitan PowerShell, and the BitTitan Management Console. The Management Console will run a diagnostic that lets you know how many licenses you will need, as described in How do I estimate the number of Public Folder migration licenses required?
Note: If your data to be migrated is greater than 20GB, you will need to follow slightly different steps during your migration than if it is less than 20GB. Please ensure, when choosing your migration guide, that you have chosen the correct one.