Dropbox & Box to OneDrive:
What Actually Breaks

Shared links stop working — and nobody notices until it matters

Both Dropbox and Box generate shareable links tied to the specific location and platform where a file lives. When a file moves to OneDrive, its Dropbox or Box link doesn't redirect or update — it simply stops resolving to the file. Every link that's been sent in an email, embedded in a document, saved in a bookmark, or stored in a third-party system referencing the old location breaks silently at the moment of migration.

This is rarely caught during the migration itself, because the migration tooling reports success based on the files being copied, not on whether external references to those files still function. The practical mitigation is identifying high-value shared content ahead of time — files that are widely linked externally — and proactively communicating new OneDrive links for those specific items rather than expecting every recipient to notice and ask.

Folder-level and file-level permissions don't map directly

Dropbox and Box both support granular sharing at the individual file or folder level, often built up organically over years by many different users independently sharing content with clients, partners, and colleagues. OneDrive's permission model is broadly similar in capability but structurally different enough that a direct one-to-one migration of every existing share often isn't possible, or isn't advisable even where it is technically possible.

The realistic approach is treating migration as an opportunity to consolidate and simplify sharing, rather than attempting to perfectly replicate years of accumulated individual shares. This requires a decision, made deliberately rather than left to migration tooling defaults, about which shares are actually still needed and which have simply never been cleaned up.

Sync client conflicts and duplicate files

Users who have both the old platform's sync client and OneDrive's sync client running during a transition period frequently end up with duplicate files, sync conflicts, or confusingly named conflict copies (files renamed with the user's name and a date, a common outcome when two sync clients modify the same file). This is more common than it should be, because uninstalling the old sync client is easy to forget as a discrete migration step, particularly when migration is handled centrally by IT but the sync client removal depends on individual user machines.

A clean migration includes explicit steps to disable or uninstall the old sync client on every affected device, not just an assumption that users will do it themselves once told the migration is complete.

Version history doesn't carry over

Dropbox and Box both maintain file version history, and in both cases, that history is generally not preserved when files are copied to OneDrive through most migration methods — only the current version of each file typically migrates. For organisations where version history serves as an informal audit trail or safety net for accidental changes, this is a real loss that isn't obvious until someone specifically needs an old version and discovers it's gone.

Where version history matters for specific content, it needs to be identified and either exported separately before migration or explicitly accepted as a limitation, rather than assumed to transfer automatically.

File and folder naming conventions that OneDrive rejects

OneDrive (and SharePoint, which shares the same underlying platform) enforces restrictions on certain characters in file and folder names, as well as path length limits, that Dropbox and Box either don't enforce or enforce differently. Files with characters like #, %, or trailing periods, or folder structures with very long nested paths, can fail to migrate or get silently renamed. Running a pre-migration scan for naming and path-length issues, and resolving them before the migration rather than discovering failures partway through, avoids a frustrating mid-migration cleanup exercise.

Shared team folders need a deliberate ownership decision

Both Dropbox and Box support team or shared folders that don't map to a single individual owner in the same way personal storage does. Migrating this content into OneDrive — which is fundamentally built around individual user storage, with SharePoint as the shared-content equivalent — often means a decision needs to be made about whether shared folders should actually land in SharePoint Online rather than OneDrive, which is frequently the more appropriate destination for genuinely shared team content.

Planning around these specific risks

None of these issues are reasons to avoid the migration — they're reasons to plan for them specifically rather than treating this as a generic file transfer. A pre-migration audit covering shared links, naming conventions, and shared-vs-personal content classification catches the majority of these issues before they become post-migration support tickets.

CloudyNex's cloud storage migration service is built around exactly this kind of pre-migration assessment for Dropbox, Box, and Google Drive migrations to OneDrive and SharePoint. If your migration includes a broader move to Microsoft 365, our OneDrive migration service covers the personal storage side specifically, including sync client management and naming remediation.