Overview
- Google Chat is used by organizations for internal communications. Google Chat data carries important conversations and documents which need to be frequently archived.
- Using the LegacyFlo Googlechat-Vaultastic4 request type, you can now archive Google Chat conversations into emails which are saved on the Vaultastic Active Store.
Step 1: Getting access to the Google Chat data
This is a one-time process, in which you generate the API access key and register with LegacyFlo.
Follow the steps given here.
Step 2: Prepare the Vaults on the Active Store
- Each LegacyFlo request will upload data from a data file to a target vault on the Active Store
- Using the Admin Panel,
- Create the vaults, if not present
- Change the target vault access to Self Service (Make sure that you remove the access after the migration is over to avoid extra charges)
- Set the password for the vault.
Step 3: Submitting LegacyFlo requests
Once the preparation is done, you can start the migration by submitting migration requests to LegacyFlo.
The request type to be used is Googlechat-Vaultastic4.
The source parameters for the request are as follows:
Source Information
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| User ID | User id on M365 domain whose data needs to be retrieved (Note: The id should not contain the domain name.) | "john" |
| Domain | Source domain on M365 | "baya.com" |
| Operation Type | There are two options to choose from 1. Direct Message 2. Space If you choose Direct Message, all the Google Chat one on one chats for the user will be retrieved. If you choose Space, all the Google chats for the user in the Spaces will be retrieved. | Space |
| Include JSON Response | By default, all chat communications are converted to email in the HTML format and any documents shared are attached to the mail. The Include JSON Response option should be enabled if you wish to add the RAW JSON returned by the API as an additional attachment. |
Filter Information
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| Since (DD-MMM-YYYY) | If this field is left blank, all the communications of the user till one day before the date specified in the Before field will be retrieved. If this field has a valid input, then all communications since the date specified will be retrieved. | "31-JAN-2022" |
| Before(DD-MMM-YYYY) | If this field is left blank, all the communications from the date specified in the Since field till the date prior to the date when the execution starts will be retrieved. If the field has a valid input, all communications till a day prior to the date specified will be retrieved. | "31-MAR-2022" |
Destination Information
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| User ID | The user id on the destination Vaultastic 4 server. (Note: The id should not contain the domain name.) | "john.smith" (To upload data to john.smith@baya-com.vaultastic.com) |
| Domain | Destination domain on Vaultastic 4 | "baya-com.vaultastic.com" |
| Password | Password of the user on Vaultastic 4 | Note: Passwords cannot contain special characters mentioned in the list given here. Update the password before submitting the request. |
| Server | Hostname for the domain on Vaultastic 4 | "baya-com.vaultastic.com" |
Step 4 (optional): Submitting multiple LegacyFlo requests to backup data for multiple users
To upload multiple jobs using a CSV, create a CSV file with a list of all the users and other details required to upload data.