On This Page
| Table of Contents |
|---|
...
The Google Shared Drives connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files between your Google Shared Drives and cloud storage repositories and on-premise network file shares. The first step is to create the Google Shared Drives connection by providing the connection information required for DryvIQ to connect to the shared drives.
| Info |
|---|
Migrating documents from Google Workspace requires a Google Workspace service account with administrative privileges. The service account allows the DryvIQ Platform to act on behalf of users using the Google Workspace API. Refer to Creating a Google Workspace Service Account for instructions on how to create the service account. |
Creating a Connection
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Google Shared Drives as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Test the connection to ensure DryvIQ can connect using the information entered.
You will see a green "Connected” message on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)
Click Done.
Add connection modal for Google Shared Drives
...
Field | Description | Required |
|---|---|---|
Display as | Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. The maximum length is 255 characters. | Optional |
Service Account Email | Enter the email address created during the Service Account creation process. It will resemble | Required |
Private Key | Enter the private key required to access the drive. This is the value created when creating the new private key when creating a new Service Account in the Google IAM & admin Console. It will begin with " | Required |
Subject Email | Enter the email address for the root account containing the data to be transferred. | Required |
Domain | Enter the target domain name. For example, your-domain.com. If you do not include the domain for the Subject Email, you must include the domain in this field. This domain will then be used as the domain for the account. | Optional |
Token Uri | Enter the custom authentication URI. If not supplied, the default is used - https://accounts.google.com/o/oauth2/token. | Optional |
Preserve content type | Indicate if DryvIQ should try to preserve files in their original content type. This feature is mainly used for Google to Google transfers. The default value is No. This means that an upload content type is not specified. Most files will still preserve content types. However, Google native documents and Microsoft Office files will transfer as Microsoft Office files. Selecting Yes will preserve files in their original content type. Google native documents will transfer as Google native documents. Microsoft Office files will transfer as Microsoft Office files. | Optional |
Import as Google native documents | Indicate if DryvIQ should import Microsoft Office documents as Google documents. This feature is mainly used when transferring from any platform, such as Box to Google. The default value is No. This means Microsoft Office files will be preserved as their original content type. Selecting Yes will import all Microsoft Office files as Google native documents. | Optional |
Behavior when deleting items | Select the type of delete DryvIQ should perform when deleting items: Permanent or Soft. Soft delete is the default delete behavior; however, Permanent is the recommended behavior. A soft delete marks items as a deleted. You can still access them to restore or permanently delete the items. A permanent delete removes the items. This delete is not reversible. | Optional |
Allow file discovery | Indicate if files with shared links should be searchable. The default value is No. This means that only users with whom the file has been shared can find and access the file. Selecting Yes sets the "People can search for this file" setting in the file link settings to TRUE. This means any files with shared links can be found and accessed by any user through the search. | |
Use domain admin access | Indicate is you want to allow domain-level administrator access to all Google shared drives, regardless of membership. The default value is No. This means the connection can only access shared drives the administrator is a member of. Selecting Yes allows the connection to access all shared drives in the administrator's domain/enterprise. | Optional |
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
Supported | Not Supported | Other Features and Limitations |
|---|---|---|
File size maximum: 5 TB | ||
Author/Owner preservation | Path length maximum: None | |
Segment path length: 500 | ||
Restricted types | ||
Permission preservation | No leading spaces in file name/folder name | |
No trailing spaces before or after file extensions | ||
Author Preservation/Audit Trail Preservation
The Google Shared Drive connector uses per-request impersonation. When Google Drive is the source or destination connection, DryvIQ must make requests to the platform on behalf of the account owner, not the administrator. To ensure “Created By” and “Modified By” dates are preserved during migration, the destination connection must also impersonate the corresponding account owner.
DryvIQ supports author preservation in Shared Drives. It does this by impersonating the user that last modified the file when uploading the file. However, there are some limitations:
...
Sites, Forms, Fusion Tables, My Maps, and Google Workspace Marketplace are all files that are not transferable.
Comments in Docs, Sheets, and Slides are not transferable.
You cannot transfer permissions to folders other than the shared drive.
You cannot transfer demoting/deny permissions (disinheritance).
...
Documents
Native Google documents will be handled as indicated below.
Although some platforms such as Box and Dropbox support Google Docs, DryvIQ does not currently support transferring them to Google Shared Drives.
When transferring Google Docs from Google Shared Drives to another platform, DryvIQ will export the documents as Microsoft Office documents.
Google Docs convert to docx files.
Google Slides convert to pptx files.
Google Sheets convert to xlsx files.
Google Drawings converts to svg files.
Google Apps Script converts to json files.
Google Forms, Fusion Tables, Sites and My Maps are not available for download in Google Shared Drives. This means DryvIQ is prevented from transferring these items. Expected behavior is the item will be flagged with the error message "IO Violation and message:Downloading content is not supported for file...".
...
When transferring Microsoft Office documents to Google Shared Drives, you can choose to either keep their original format or import them as Google Docs when setting up the connection.
Google Shortcut Links
Google does not allow downloading of native link files that appear on the Google platforms. DryvIQ will filter these files out of the migration job and log the skipped reason for reference.
Root File Transfers
You cannot transfer files to the root of your Google Shared Drives connection. Folders transferred to the root of the Google Shared Drives connection will be created as Team Drives.
Versioning and Simulation
For Google native documents, only the size of the current version can be calculated from the API. When running a simulation job with versioning enabled, only the size of the current version of the file will be shown. The size of the other versions will not be calculated for these documents.