Dropbox

Connections

Create a new connection and select Dropbox 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.

Dropbox 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.

Rate Limiting

Dropbox throttles requests from external integrations. A migration can be rate-limited when Dropbox is either the source or destination because Mover uses the Dropbox API to list, inspect, download, and upload items. Upload-heavy migrations are especially likely to be constrained by the rate Dropbox accepts.

Mover automatically reduces parallel work and retries recognized rate-limit responses with increasing delays. If Dropbox 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 Dropbox concurrency setting, so use smaller, non-overlapping batches and run them one at a time. See Performance and Rate Limits.

Dropbox also restricts some filenames and file types. Run a dry run and rename or exclude unsupported items before the live migration.