This is the complete onboarding task flow for setting up a Google Vault migration.
Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
At a high level, migrating Google Vault is a three-step process:
- Use the BitTitan Google Vault Extractor to programmatically export email into individual user files. Each user's export will contain three (3) files; a .zip file containing the mail, a metadata file containing mail header info, and a .done or .fail file representing the success of the export. These files will be downloaded to the machine running Exporter.
- Use UploaderWiz to upload the locally stored files to Azure Blob storage.
- Use MigrationWiz to migrate mail from the Azure Blob to the Destination of choice. Common Destinations are an Office 365 archive mailbox, recoverable items, or the primary mailbox.
Before migration, we recommend that you review the Google Vault Best Practices Guide. KB005235
Data from Google Vault accounts that are suspended in G Suite can still be migrated.
Note: As a best practice, Google recommends suspending user accounts instead of deleting them. For instructions on how to migrate suspended accounts, refer to KB005850.
MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because we do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.
MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.
Prerequisites for Google Vault Migrations
- Prepare the client computer to run the Google Vault Extractor and store the exported files. Requirements for the client:
- Windows 7/Server 2008+
- At least enough free storage to hold the Google Vault export
- The ability to run a command prompt as Administrator
- .NET Framework version 4.6.1 or later installed.
Note: To determine the .NET Framework version currently installed, follow the instructions provided by Microsoft: How to: Determine Which .NET Framework Versions Are Installed.
- Download and install the Google Vault Extractor from here. More detailed information about the Google Vault Extractor can be found in KB004975.
- Download and install UploaderWiz. To learn more and access the latest version of UploaderWiz for download, click here.
- Buy an Azure subscription. KB004996
- Create an Azure storage account.
Note: This information will be entered when creating your MSPComplete Destination Endpoint. KB004832
- To obtain your Access Key: Log on to the Azure portal > Dashboard > All Resources > All subscriptions > Click Storage Account name > Settings > Access Key.
Note: Make a note of the Storage Account Name and the Primary Access Key. These will need to be entered when creating your MSPComplete Destination Endpoint.
- Create an Azure public blob container named migrationwiz. Confirm that the blob container is empty and accessible. KB008059
Important: A Vault administrator account or G Suite super administrator for your organization is required in order to perform this migration. More information can be found here.
- Delete any duplicate Matters.
- Delete any Matters that were created by previous extractions. These can be identified by the unique ID attached to the Matter name.
Note: This step is optional.
- From the client computer that was prepared in Step 1, using any browser, log in to Google Vault from here.
- Confirm that all necessary users are licensed for Google Vault. This can be confirmed in the G Suite admin panel.
- Prepare Matters for migration:
Prepare the Destination Environment
Note: These steps may have already been completed during a previous migration project.
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
- Set up accounts on Office 365 and assign licenses. These can be created in several ways:
- Manually, one at a time.
- By bulk import, via CSV file. Microsoft instructions
- By PowerShell script. TechNet article
- By DirSync, AAD Sync or AAD Connect. KB004336
Export, Extract, and Upload Files to Azure by running the Google Vault Extractor, followed by UploaderWiz
- From the client computer, run the Google Vault Extractor to export the items in the Google Vault.
- Initiate the Exporter. From the client computer that was set up in Step 1 in the Prerequisites for Google Vault Migrations section of this guide, open an administrative command prompt, navigate to your install directory, and run the upload command. Example command:
C:\\Users\\USERPROFILE\\Desktop>GoogleVaultExport.lnk -process-start-args "COMMAND"
Important: Refer to the following Knowledge Base article for more details on the syntax of this command: KB004975.
- For example, this UploaderWiz example would upload the local directory
C:\\GVE\\Exportto a Blob named migrationwiz within the BitTitan Azure Storage Account:
UploaderWiz -type azureblobs -accesskey yourAccount -secretkey xxxxxxxxxx -container migrationwiz -rootPath "C:\GVE\Export"
Note: You have the option to upload these to a specific Azure data center. This is done by using the UploaderWiz optional parameter of azurelocation=gov, ger or china. KB004975
- Create the customer. KB005421
- Create the Source and Destination Endpoints.
- For the Source Endpoint:
- Click Endpoints >Add Endpoint > Enter Endpoint name > For Endpoint type, select Google Vault.
- Enter Storage Account Name and Access Key in the fields provided.
- For the Destination Endpoint:
- Click Endpoints > Add Endpoint > Enter Endpoint name > For Endpoint type, select Office 365> fill in the required fields.
- For the Source Endpoint:
- Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:
- Set up the Project. Read the How do I create a new migration project? article for more information.
- Add items to MigrationWiz project. We recommend that you use the AutoDiscover items feature to import all the items from the Azure blob container. Select Add > Autodiscover Items.
- Edit Destination email addresses as needed to set the Destination mailbox to ingest each file into. Click the Edit Item (pencil icon) to the right of the row. Under the Destination Email Address field, enter the mailbox that this file will be ingested into. KB004937
- Set the Project Advanced Options. KB004834
- Note: The Azure URI needs to be changed to one of the following values:
- core.chinacloudapi.cn (China)
- core.cloudapi.de (Germany)
- core.usgovcloudapi.de (government)
- Important: This Advanced Option only needs to be added if you are uploading your Google Vault files to a specific Azure data center. This is done by using the UploaderWiz optional parameter of azurelocation=gov, ger or china.
- Set the Destination to migrate data into. DESTINATION: MICROSOFT OFFICE 365 > Migrate to: Mailbox or Archive or Recoverable Items. Note: The default setting is mailbox.
- Filter Folders:
- This inclusion filter means that only the items in the Permanently Deleted folder will be migrated. KB004670
- This inclusion filter is only required when migrating Google Vault data from active mailboxes. If a user is in suspended mode, then this filter is not required, since you will be migrating all data.
- Support Options (replace "Google Vault Items" with your preferred Destination folder name):
FolderMapping="^Permanently Deleted->Google Vault Items"
Note: This step is optional, but helps users to locate their Google Vault data. KB005017
PSTCustomEndpointSuffix=Azure URIunder Support/Support options. KB005896
- Set the value for the maximum number of licenses to consume per item, per pass.
Note: Delta migrations are not supported for Google Vault migrations. Google Vault migrations only require a single Full Migration pass. KB004938
The following can be deleted:
- On the Google Vault admin portal:
- Matter files that were created for each query
- Downloaded Matter files
- On the client computer being used to run the Google Vault Extractor:
- The Google Vault Extractor and directory
- On Azure:
- Azure storage containers used for uploading the extracted matter files into
- The Azure storage account, if it was set up just for the purpose of the Google Vault project
- On MigrationWiz:
- Your Google Vault MigrationWiz project.
Note: This is optional because MigrationWiz has a 180-day autodelete policy. For more information, see How do I extend the unused period of my Project?
- Your Google Vault MigrationWiz project.
- On Office 365:
- Endpoints that were created for this project
- If a separate account was created for migrating the Google Vault items to Office 365 (e.g., firstname.lastname@example.org), this account can be deactivated and removed.