how to

How to Migrate Your Files Between Cloud Storage Providers

· 3 min read cloud-migrationrclonecloud-storagedata-transfer

Switching providers — Dropbox to OneDrive after a price change, Google Drive to a privacy-focused host — goes wrong when people drag folders through the web interface and lose timestamps, sharing links, or half the files silently. A clean migration uses a transfer tool that copies server-to-server, verifies checksums, and keeps the old account alive as a fallback until the new one is proven. Plan for a weekend, not an afternoon.

What you need

  • Accounts on both old and new providers with enough free quota on the destination
  • rclone installed (free, all platforms) or the destination's built-in migration tool (OneDrive's Mover, Dropbox's Google importer)
  • A computer with stable internet; server-side copy means bandwidth is mostly metadata
  • An inventory of shares, apps, and integrations pointing at old paths

Step by step

  1. Audit the old account first. List top-level folder sizes (rclone size dropbox:), note files shared with other people, and record connected apps (editors, backup tools, phone auto-upload) that will need re-pointing.
  2. Clean before copying. Delete duplicates, empty trash, and consolidate scattered folders. Migrating junk doubles your effort and cost.
  3. Configure rclone for both providers: run rclone config, add each remote, and name them clearly (old-dropbox, new-gdrive). For Google Drive, create your own OAuth client ID to avoid shared-quota rate limits during large transfers.
  4. Run a pilot copy of one small folder: rclone copy old-dropbox:Projects new-gdrive:Migrated/Projects -P --checksum. Check that file counts match and spot-open several documents in the new provider's preview.
  5. Run the full transfer off-peak with --transfers 8 --checkers 16 for parallelism. Large libraries take hours to days; rclone resumes cleanly if interrupted, so do not restart from scratch on failure.
  6. Verify exhaustively: rclone check old-dropbox: new-gdrive: --download compares actual content, not just names. Confirm total count and byte totals match exactly.
  7. Re-create what does not migrate automatically: sharing permissions, third-party app connections, offline pins, and version history (providers do not carry it over). Notify collaborators of new locations and update any embedded links.
  8. Keep the old account read-only for at least one full month. Cancel its paid plan only after a month of daily work has happened entirely inside the new provider.

Common mistakes

  • Deleting the source immediately after the copy finishes. Hidden breakage (missing shares, failed special files) surfaces days later; keep the original until proven otherwise.
  • Copying through a local disk when both providers support server-side moves — it triples time and risks corruption on disconnects.
  • Forgetting mobile camera-roll uploads pointed at the old provider; phones keep uploading there for months, splitting your data across two accounts.

Related guides

The month-long overlap period works best when you already follow [[setup-3-2-1-backup-rule]] so the old account is not your only fallback. After migrating, rebuild offline availability per [[set-up-offline-cloud-access]], and encrypt sensitive folders first per [[encrypt-files-before-upload]]. If transfers produce duplicate copies mid-flight, [[prevent-cloud-sync-conflicts]] explains why and how to dedupe.

← All guides