Google Vault Migration Guide
- This is the complete onboarding task flow for setting up a Google Vault migration.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- At a high level, migrating Google Vault is a three-step process:
- Use BitTitan's 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 AZCopy 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.
Prerequisites for Google Vault Migrations
- Prepare the client computer to run the Googe Vault Extractor and store the exported files. Requirements for the client:
- Windows 7/Server 2008+
- At least enough free storage for hold the Google Vault export
- Ability to run a command prompt as Administrator
- .NET Framework version 4.6.1 or later must be installed. Note: To determine the .NET Framework version currently installed, follow theinstructions 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 AZCopy. To learn more and access the latest version of AZCopy 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 on 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
- From the client computer that was prepared in Step 1, using Internet Explorer, 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:
- 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.
Prepare the Destination Environment
Note: If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed.
- 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 AZCopy.
- 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 AZCopy example would upload the local directory C:\\GVE\\Export to a Blob named migrationwiz within the BitTitan Azure Storage Account: AzCopy /Source:C:\\GVE\\Export /Dest:https://BitTitan.blob.core.windows.net/migrationwiz /DestKey:xxxxxxxxxx /S
- Note: You have the option to upload these to a specific Azure data center. This is done by either using the UploaderWiz optional parameter of azurelocation=gov, ger or china; or by using AZCopy and specifying the URL (refer to this TechNet article for more information). KB004975
MSPComplete Steps (https://manage.bittitan.com/)
- Create the customer. KB005421
- Create the Source and Destination endpoints.
- For the Source endpoint:
- Click on 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 on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365> fill in the required fields.
- Set up the Project. Create project > Create a personal archive project > Name the project > Select MSPComplete customer >Select the Source endpoint > Select the Destination endpoint.
- 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 on 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
- 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: ^(?!Permanently Deleted$)
- 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 (fill in the preferred Destination folder for Google Vault Items): FolderMapping=”^Permanently Deleted->Google Vault Items”Note: This step is optional, but helps users to locate their Google Vault data. KB005017
- Set the value for the maximum number of licenses to consume per item, per pass. The default value is one license per user, which allows up to 10GB to be migrated per user. However, if a user has 28GB of data, the migration will pause at 10GB unless you have increased this value to a number of 3 or more. Note: The project will only consume the number of licenses for the amount of data migrated. For example, if this value is set to 5, and the user has 28GB of data, then only three licenses will be consumed, and two licenses will remain. KB004890
- Add PSTCustomEndpointSuffix=Azure URI under Support/Support options. KB005896
- 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 either using the UploaderWiz optional parameter of azurelocation=gov, ger or china; or by using AZCopy and specifying the URL (refer to this TechNet article for more information).
- The following can be deleted:
- On the Google Vault admin portal:
- Matter files that were created for each query
- Downloaded Matter files
- The Google Vault Extractor and directory
- 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
- Your Google Vault MigrationWiz project. Note: This is optional, because MigrationWiz has a 180-day autodelete policy. KB004624
- Endpoints that were created for this project
- If a separate account was created for the purpose of migrating the Google Vault items to Office 365 (e.g., firstname.lastname@example.org), this account can be deactivated and removed.