> 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/cloud-content-platforms/sharepoint.md).

# SharePoint

## Connections

Adding a <code class="expression">page.vars.VENDOR\_NAME</code> connection is a two-step process. First, you save a new connection. After the connection is saved, you log into <code class="expression">page.vars.VENDOR\_NAME</code> to grant Mover access to your files.

Create a new connection and select <code class="expression">page.vars.VENDOR\_NAME</code> 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.

## Migration Destination

When SharePoint is the destination, select a document library or a folder inside one. A destination such as `companyname.sharepoint.com/sites/MySite/Shared Documents` selects the site's default document library; `companyname.sharepoint.com/sites/MySite/Shared Documents/Incoming` selects a folder within it. The default library appears as `Shared Documents` in the path even when SharePoint displays it as *Documents*.

The connection root and site levels let you browse to libraries; they cannot receive files. The migration's *Destination Path* is required for SharePoint, and Mover rejects an empty destination path when creating or editing a migration. A site path by itself, such as `companyname.sharepoint.com/sites/MySite`, is also not a writable file destination. A nonempty path still needs to identify a library or folder where the connected account can upload files; accepting the path does not confirm write permission.

The connection root can be used as a migration source. A [OneDrive](/connections/cloud-content-platforms/onedrive.md) connection points directly to a drive and supports a root destination.

## <code class="expression">page.vars.VENDOR\_NAME</code> is Not 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.

## SharePoint Changes to Uploaded Files

SharePoint can add metadata to an uploaded Office file, changing its contents and size after Mover delivers it. When a migration keeps source files, Mover detects the size change and copies the complete SharePoint-modified file back to the source. This remote resync replaces the original source file so both copies match under Mover's [file-matching rules](/migration-behavior/file-matching-and-data-integrity.md), preventing later runs from repeatedly transferring the same file.

A successful resync appears in the [migration log](/migration-guide/results-and-reruns.md#migration-log) with the message "Re-synced file back to source because destination modified it on upload."

Each resynced file requires another transfer, from SharePoint back to the source. That transfer adds time to the migration and is subject to provider rate limits on both sides. Remote resync does not consume your [usage pack](/billing-and-usage-packs.md#how-data-transfer-is-calculated), and Mover does not charge for it. The successful transfer into SharePoint still counts toward usage.

This is the one situation in which a migration configured to keep source files can still write to the source. The source connection must have permission to overwrite the affected files. If that permission is missing, the resync fails and the failure appears in the migration log. Correct the source permissions before rerunning. Until the resync succeeds, later runs can transfer the same file into SharePoint again because the sizes still differ; those successful transfers consume usage.

Files that are checked out, open in Microsoft Office Online, or otherwise locked in SharePoint cannot be migrated until the lock is released.

## Rate Limiting

[Microsoft applies throttling limits to SharePoint Online](https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online), and the applicable limit can depend on the Microsoft 365 license plan. A migration with many files can reach the limit whether SharePoint is the source or destination.

Mover automatically reduces parallel work and retries recognized throttling responses with increasing delays. If SharePoint continues rejecting an item after those retries, the run records a failure that can be retried by running the migration again. Mover does not expose a SharePoint concurrency setting, so use smaller, non-overlapping batches and run them one at a time. See [Performance and Rate Limits](/migration-behavior/performance-and-rate-limits.md).