The following sections will guide you through setting up and launching your migration. Each header is one step, with its component steps below. Follow these steps in order, and read the notes for important information about dependencies or best practices.
Run Verify Credentials
- Open the Project containing items you wish to validate.
- Select the items you wish to validate.
- Click on the Start button in your dashboard.
- Select Verify Credentials from the drop-down list.
- Once complete, the results of the verification will be shown in the Status section.
Run an assessment to calculate the number of licenses required for your migration. This must occur after the project is created.
- Add Users.
- Select the Users that need assessment. You can select All Users.
- The sender of this email will be: firstname.lastname@example.org and the subject header will be: Migration Statistics for Project: "your project name".
- This email will contain three (3) .zip file attachments. Unzip the attachment with the name: ProjectStats.zip.
- Once unzipped, open the file named ProjectStats.csv.
- The total size of the mailbox and the count of the folders are reflected in the columns labeled "Mailbox Size (bytes)" and "Folder Count" respectively. Note: The column is labeled "Mailbox Size (bytes)" even if the project is a project type other than a Mailbox migration.
- You can ignore the other columns which are only populated after the project items have migrated.
- Convert this number to GB by dividing this number by 1024*1024*1024.
- Now you can calculate the number of licenses per user.
The size calculations may be different from those that are reported in the Google Admin portal. Some possible reasons for this are:
- The MigrationWiz Assessment tool will index the entire Source data, and then convert it to the Destination format. The size calculations will be based on the converted data.
- If migrating from G Suite to Office 365, and converting labels to folders (which is the default, and recommended selection), then the size calculation will take into account the fact that labels need to be converted to folders on Office 365. This can result in an increase in size for the mailbox, at the Destination.
- If migrating from Google Drive to Microsoft OneDrive for Business, then the size calculation will be based on the converted sizes for each document.
- If you have date filters under the MigrationWiz project Advanced Options, then the MigrationWiz assessment will take this into account, too. This means that if you have a date filter to migrate just the last 30 days of data, then the assessment will be calculating how much data is in the Source Google Drive accounts for ONLY the last 30 days.
- GoogleDrive admin portal is reporting on all data for the user. This includes data in their My Drive and the Shared With Me folder. MigrationWiz assessment is based on what will be migrated because MigrationWiz will only migrate what is in the My Drive.
- If you want to migrate data in the "Shared With Me" folder too, then the following steps are required:
- Instruct Users to go into the Shared With Me folder and redirect everything into their own My Drive (they will need to right-click on each folder and then select Add To My rive). Note: This does not move the data. It adds a link so that it can be accessed from their My Drive.
- Add the Advanced Option DocumentBrowsingMode=Moderate to your MigrationWiz Project Advanced Options, under Support only options.
- Rerun the assessment.
- Purchase User Migration Bundle licenses and assign to each user to be migrated. These licenses include both the Mailbox migration and Document migrations.
Send out the final notification that the migration is beginning. Include when the migration will start, expected duration, any usage instructions during migration, and any expected steps or notifications for the post-migration timeline. Remind them to avoid modifying any documents at the Source, as this may cause corrupt data or and incomplete migration.
Perform the Migration
Perform the migration, using one of the following strategies:
- Full Migration strategy – Recommended for projects with fewer than 50 users:
- For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.
- Pre-Stage Migration Strategy – Recommended for projects with more than 50 users
- Pre-Stage pass.
- Full (Delta) pass.
Launch the Migration
- Click on the name of the Project you want to run.
- Select one or more items to migrate by checking the box next to the item name.
Note: If you want to select all the items, click the checkbox to the left of Source Email.
- Click on the Start button and select the type of migration to run.
- Full - Requires a license.This migration selection will migrate all identified and supported items.
- Pre-Stage - Requires a license. This migration selection will migrate all identified and supported items before the selected date. In the case of mailbox migrations, only email items will be migrated for this migration option. This migration option requires a license of the appropriate type.
- Trial - Free migration pass. This migration selection is used to test the migration server. It will migrate up to 10 items per folder or up to 5 MB of data per mailbox. A full migration with a license will pick up where the trial left off.
- Verify Credentials - Free migration pass. This migration selection will test to make sure that the credentials being used for migration are correct and will allow a successful connection. No data is migrated.
- Retry Errors - Free migration pass. Once a Full or Pre-Stage migration has completed successfully, Retry Errors can be run to retry only failed items.
- If you want to delay your migration, then select the checkbox marked "Automatically start the migration at", and enter the date and time to have the migration start.
Note: To start a migration immediately, you do not need to select the scheduling option.
- Click Start Migration.