> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/connections/object-storage.md).

# Object Storage

Object storage connections are designed for bucket or container services. They generally handle large migrations more efficiently than collaboration platforms because they expose direct storage APIs without the same document-collaboration layer.

Mover provides dedicated connections for:

* [Amazon S3](/connections/object-storage/amazon-s3.md)
* [Azure Blob Storage](/connections/object-storage/azure-blob-storage.md), including containers that use Azure Data Lake Storage Gen2 hierarchical namespaces
* [Google Cloud Storage](/connections/object-storage/google-cloud-storage.md)

Use [S3-Compatible Storage](/connections/object-storage/s3-compatible-storage.md) for another service that implements the S3 protocol. Mover also provides named S3-compatible connection forms for [Akamai Linode](/connections/object-storage/s3-compatible-storage/akamai-linode.md), [Backblaze B2](/connections/object-storage/s3-compatible-storage/backblaze-b2.md), [Cloudflare R2](/connections/object-storage/s3-compatible-storage/cloudflare-r2.md), [Filebase](/connections/object-storage/s3-compatible-storage/filebase.md), and [Wasabi](/connections/object-storage/s3-compatible-storage/wasabi.md).

Object storage connections require a bucket or container and provider credentials. Prefer credentials scoped to the migration's required paths and actions. A source-only connection can use read-only access; a destination must allow object creation, and source deletion requires delete permission.

Amazon S3, Azure Blob Storage, and Google Cloud Storage sources support additional detection when a source object changes during a run. See [File Matching and Data Integrity](/migration-behavior/file-matching-and-data-integrity.md).