GOOGLE VAULT MAIL Migration
1. Migrate Google Vault overview
For more information about security, please refer to this article.
For more information about migration performance, please refer to this article.
4. Mail Migration Scope
5. Pre-migration configuration
5.1. Before you start
Before you start, you will need to ensure you have the details outlined in the following table. In each case, we recommend you create an account especially for migration (we provide steps for each system), which you can delete upon completion of migration. This ensures full security and simplicity.
|Stores details and provides communication between the systems you already use.
|Our extensive help center is always accessible, with videos, troubleshooting tools, samples & more.
|Google Admin console
|This is where administrators manage Google services for people in an organization.
|Target: Office 365 account
|Optional. Used by the Cloudiway support to connect and troubleshoot issues.
6. Migrate Google Vault : Steps
The following steps are required to migrate a Google Vault:
- Create a Google Vault source connector
- Create a PST Import Service target connector
- From the Cloudiway archive user list, define an archive to migrate with the Vault connector as the source and the PST Import connector as the target.
6.1. Create your connectors
For Cloudiway to migrate your Vault archives, it needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors. You will need to set up a connector for each source tenant and each target tenant. Please refer to this page to configure your connectors.
For large projects, it’s possible to create multiple connectors that will be used in parallel. Please contact Cloudiway consulting services if you need to set up such configuration.
Note: you can enable the checkbox in the Migration Settings during the Connector Configuration to migrate all Google Chats and Hangouts:
Click on Import, then click on New import Job.
Give your job a name and click next.
Then select Upload your Data and click next:
Click on Show Azure SAS URL, copy its value.
Paste it in your target PST Import connector in the Cloudiway platform.
Click on the UPLOAD button
If you see any error messages, check your CSV file, and try uploading again.
Once the CSV file format is correct, you will see a confirmation message.
Refresh the screen to see when the user list has been updated.
Option 2: Single user creation details
Many of our customers create a single user for testing. This lets you watch the migration process without affecting all users. Single users can also be created for migrations affecting just a few users.
Click on Manage then Create User to display the pop-up screen:
Notice on this page, that you can choose in the “Target Recipient Type” field between “Standard” or “Archive” type.
Both of these types can have user mailboxes or shared mailboxes as target emails.
If you choose the “Standard” type, all the migrated emails will be placed in the root of the target user or shared mailbox. If you choose the “Archive” type, all the migrated emails will be placed in the archive folder of the target user or shared mailbox.
Fill in all details for a new user, then click OK to add the new user to the Archive Migration / User List. Repeat the process for any more users you’d like to create.
6.3. Start the Migration
The migration will extract the archive from Vault into a PST File and upload it to the Blob storage used by the Microsoft import service
From the archive user list, select the users, click on MIGRATION then Start
Once your Cloudiway migration jobs are done, which means that your Google Vault PST Exports were uploaded successfully into the Azure Blob Storage, you can trigger the Microsoft Import job.
First, generate the mapping file. In the Cloudiway Archive list, click on MANAGE, then Download PST List.
Download regardless of the PST Process status is an option that permits to regenerate entirely the mapping file or only the delta (the list of PST files that have not been processed yet by the Microsoft Import Service)
Note: the mapping file generated by the platform migrates to the Office 365 mailbox by default (column isArchive=FALSE). You can change the destination by editing the mapping file. For example, you may prefer to migrate to the online archive (column isArchive=TRUE) or evenly to a specific folder (column TargetRootFolder=/FolderName). You can refer to the Microsoft documentation for the exact syntax of the mapping file.
A common scenario is to migrate Google Vault Permanently Deleted Items (in the connector specify Migrate Deleted Items) to the Recoverable Items Folder so the users do not have access to the data in the active mailboxes. If you are migrating into the Recoverable Items Folder of the user’s mailboxes (column TargetRootFolder=/Recoverable Items/Deletions)., the users must be on Litigation Hold in Microsoft 365. If not, the data will be automatically deleted in Microsoft 365. To place the mailboxes on Litigation Hold: TechNet article.
Once you have the file, you can submit the Microsoft Import job.
Come back to the Microsoft Import job service page and start the job. When requested to provide the mapping file, use the file generated above
Check on I’m done uploading my files and I have access to the mapping file
Click on Next and then Submit.
Once you reach this step, you will have to wait for Office365 to finish the job. Once done, the status will show “Import Completed”.
Check the job and then click on Import to Office 365
Click on “No, I want to import everything.” And then click Next
To verify the Vault Export status, log in to vault.google.com
Navigate to Matters.
Open the matter of the user, click on EXPORTS, and verify the export status.