For the complete documentation index, see llms.txt. This page is also available as Markdown.

Google Cloud Storage

Connections

Create a new connection and choose Google Cloud Storage as its type.

Provide a Connection Label so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.

Bucket Details

Enter the name of the bucket to use for the connection.

The Project ID is the unique identifier for your Google Cloud project. Mover uses it to identify which project's resources to interact with.

Credentials

Provide the JSON key for a Google Cloud service account that can access the bucket. Create and download the key from Google Cloud; see Google's service account key documentation.

Advanced Settings

If your credentials do not have access to the entire bucket, or are restricted to specific subfolders only, then Mover may not be able to verify connection to the bucket.

When you do not have access to the entire bucket, use the advanced setting for Can these credentials access the root of this remote or are they restricted to a subfolder? to specify a subfolder that can be used instead.

Google Cloud Storage 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.

Last updated