Dropbox to Microsoft OneDrive,
without the manual swap.

Run a free dry run. Connect Dropbox and OneDrive, and Mover walks the source, counts every file, sums the bytes, and returns the exact file count and price before you commit. Buy the matching usage pack, launch, and Mover handles the transfer — re-running later moves only what changed or failed.

Folder hierarchy is preserved. File modification timestamps are preserved where the destination supports it; OneDrive accepts the original modified-time on upload, so the metadata you care about stays intact.

Mover migrates file content. Sharing and permission models differ between Dropbox and OneDrive, so permissions do not transfer 1:1 — they have to be re-established on the destination side, typically via Entra groups and SharePoint sharing. The data is what Mover moves; permissions are what M365 owns.

Yes. After connecting both sides, you can pick the specific folders or accounts to include. Filters and date ranges let you narrow it further — useful for staged cutovers where you migrate one team at a time.

It depends on the size and on Dropbox and OneDrive API rate limits, which Mover respects automatically. The dry run gives you a size estimate; for planning purposes, multi-TB migrations typically complete inside a single business day, with the option to run overnight.

Transient failures are retried automatically. Anything that cannot be transferred — typically because of an unsupported character in the filename or a path that exceeds OneDrive limits — is logged and reported, so you can review and remediate before declaring the migration done.

Yes. Mover reads from Dropbox via OAuth while the migration runs, then writes to OneDrive. You typically cancel the Dropbox plan after the migration is verified, not before.