Google Drive

Connections

Create a new connection and select Google Drive as its type.

Provide a Connection Label so you can identify the connection in a list.

Mover uses OAuth to connect to this service. Save the connection, then select Connect Your Account and sign in directly with the provider. Mover receives an authorization token and does not store your provider password.

Mover can access the connected account's personal drive, Shared Drives, and folders that other Google Drive users have shared with the account.

Migration Destination

When Google Drive is the destination, select My Drive, a writable Shared Drive, or a folder within a drive, such as My Drive/Incoming. The top level of the connection lists drives and shared content; it is a browsing level and cannot receive files.

The migration's Destination Path is required for Google Drive. Leaving it blank selects the read-only connection root, which Mover rejects when creating or editing a migration. Selecting a path does not establish write permission: the connected Google account must be able to upload files to the selected drive or folder. The connection root can still be used as a migration source.

Google Workspace Files

Google Docs, Sheets, and Slides are not stored as ordinary downloadable files. Mover exports them to Microsoft Office formats during migration: Docs become .docx, Sheets become .xlsx, and Slides become .pptx.

When migrating between two Google Drive accounts, Mover uses an internal .google-apps marker while processing the converted file and removes that marker before uploading it to the destination. A source Google Sheet named Budget therefore arrives as Budget.xlsx. It is not converted back into a native Google Sheet.

Duplicate and Unsupported Names

Google Drive permits several files in one folder to have the same name. A filesystem migration cannot represent those files as distinct paths, so Mover skips case-insensitive duplicate names and records the conflict in the run log. Rename the files in Google Drive before rerunning the migration.

Google Drive also permits / and \ in filenames, but Mover treats those characters as path separators or invalid path characters. Rename files containing either character before migration.

Rate Limiting and Listing Speed

Google Drive can rate-limit migrations in either direction. It also does not use filenames as unique identifiers, so Mover must list an entire folder to resolve a file by name. Large folder trees can therefore take a long time to scan even when only a small amount of data needs to move.

Mover automatically reduces parallel work and retries recognized rate-limit responses with increasing delays. Mover does not expose a Google Drive concurrency setting. Divide large migrations into non-overlapping source paths or include-pattern batches and run them one at a time. See Performance and Rate Limits.

Google Drive is Case Sensitive

Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, MyFile.txt and myfile.txt can be two different files. A case-insensitive system treats those names as the same file.

Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.