Overview
DryvIQ connections to Google Drive require OAuth 2.0 access. A client application configuration is required. DryvIQ provides a preconfigured, default client application; alternatively, users can create a custom client application if preferred. Refer to Google’s API-specific authorization and authentication information documentation to learn more.
This connection is for personal Google Drive accounts. If you are looking to migrate content for your Google Business Drives, you will need to use the Google Workspace or Google Shared Drives connectors.
Two-factor Authentication
Two-factor authentication is supported for Google Drive accounts. When testing the connection, you will be guided through the same two-factor authentication flow used when signing into Google Drive.
Creating a Connection
- Expand the Manage section in the left navigation menu.
- Click Connections.
- Click Add connection.
- Select Google Drive as the platform on the Add Connection modal.
- Enter the connection information. Reference the table below for details about each field.
- Click Sign in with Google Drive.
- On the Sign in with Google modal, enter the email Address for the account you are using for the connection and click Next.
- Enter the password required to log in to the Google Drive account and click Next.
- Click Allow when prompted to allow DryvIQ to access your account.
- You will see a green "Connected” message at the bottom of the modal when DryvIQ establishes the connection. (If the connection fails, verify the information you entered.)
- Click Done to create the connection.
| 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.
If you do not add a display name, the connection will automatically be named using the account owner's name. For example, Google Drive (John Doe). If it will be helpful for you to reference the connection by account, you should use the default name. |
Optional |
| Platform API client credentials | Required | |
| Use the system default client credentials |
Select this option to use the default DryvIQ client application. This is the default selection. | |
| Use custom client credentials |
Select this option to create an administrator connection. If you choose to use your own application credentials, two additional options will be displayed. Refer to Google’s API-specific authorization and authentication information documentation to learn more. | |
| Client ID |
This field displays only when you select Use custom client credentials. Your administrator will provide this value. Refer to Google’s API-specific authorization and authentication information documentation to learn more. | Required when using custom credentials |
| Client Secret |
This field displays only when you select Use custom client credentials. Your administrator will provide this value. Refer to Google’s API-specific authorization and authentication information documentation to learn more. | Required when using custom credentials |
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
| Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
| Version Preservation | Author/Owner Preservation | Invalid Characters: / |
| Timestamp Preservation | File Lock Propagation | File Size Maximum: 5 TB |
| Metadata Map |
Mirror Lock Ownership |
Path Length Maximum: N/A See below for more information. |
|
See below for more information. |
Segment Path Length: 500 See below for more information. |
|
| Account Map | ||
| Group Map | ||
| Permission Preservation | ||
| User Impersonation | ||
| Tags Map |
Path Lengths
Google Drive does not impose restrictions on the total path length; however, segment path lengths are limited to 500 characters. Segments are delimited by a forward slash (/). For example, <max 500 characters>/<max 500 characters>.
Slashes in Folder Name
Forward slashes (/) are invalid characters; however, DryvIQ allows “/“ in folder names only when manually building the path for the job or scan in the user interface. When creating the job or scan, it will fail to run if you copy and paste the root path with a “/“ in a folder name. Also, you cannot include a slash in a folder name when creating a job or scan using the DryvIQ REST API.
Restricted Types
Native Google Docs
Although Box supports Google Docs, Google Workspace does not support exporting Google Docs in its native format. Consequently, you cannot transfer Google Docs from Google Workspace to Box without the files being converted to the Microsoft equivalent during the transfer process. However, a Google Doc created in Box can be transferred to Google Workspace and retain its original format. DryvIQ exports Google native documents in the following formats:
- Google Docs converts to DOCX files.
- Google Slides converts to PPTX files.
- Google Sheets converts to XLSX files.
- Google Drawings converts to SVG files.
- Google Apps Script converts to JSON files.
Non-transferable Items
Sites, Forms, Fusion Tables, My Maps, and the Google Workspace Marketplace are proprietary Google formats and are not available for download in Google Workspace/Google Drive. This means DryvIQ is prevented from transferring these items. The expected behavior is that the item will be flagged with the error message "IO Violation and message: Downloading content is not supported for file: /"
Comments in Docs, Sheets, and Slides are also not transferable.
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 reason for skipping them for reference.
Versioning and Simulation
For Google-native documents, only the size of the current version can be calculated using the API. When running a simulation job with versioning enabled, only the size of the current version of the file is displayed. The size of the other versions will not be calculated for these documents.