Dropbox or Box to SharePoint and OneDrive: The Migration Playbook for Sharing Links, Team Folders, External Collaborators and Cutover

Microsoft's Migration Manager, in the SharePoint admin center, connects to a Box enterprise or a Dropbox team as an administrator, scans every account, and copies files and folders into OneDrive and SharePoint under a mapping you control. What it moves: files, the folder structure, and permissions for internal users it can match to Microsoft 365 accounts. What it does not move, from Microsoft's own FAQ pages for Box and Dropbox:

• Sharing links. External sharing links are not recreated. Every link in an email, a wiki page, a portal or a contract has to be replaced by hand, or it dies at cutover.
• External collaborators. Microsoft's tool does not share migrated content with external users, on purpose; they are re-invited in SharePoint after the move.
• Version history. Only the latest version of each file is transferred. Export the versions you need first.
• Comments. File comments in Box do not migrate to SharePoint.
• Box Notes are converted to Word documents, with elements such as the file preview, table of contents and annotations left out. Box bookmarks do not migrate.
• Dropbox Paper documents and Paper templates are not exported, because Dropbox does not allow the tool to export them.

None of this is a defect in the tool; every third-party tool has a similar list. The job is to find these categories in your own data before the copy starts, because each one is a decision, not a task.

Both products blur the line between personal and team data, and the migration is where the line gets redrawn.

Box: enterprise-owned folders become SharePoint sites or libraries; content under an individual user's root becomes that user's OneDrive. The trap is the "team" folder a departed manager created in her own account and shared with twelve people: Box reports it as personal, and migrating it to her OneDrive migrates it to nobody.

Dropbox: team folders map to SharePoint, member folders map to OneDrive. Shared folders that live in one member's account and are shared to the team are the same trap under a different name.

The rule we use: if more than three people edit it and it outlives any one of them, it is a SharePoint site or library. If one person owns it and shares it occasionally, it is OneDrive. The mapping has to come from an inventory of who actually uses each folder, not from where the vendor stores it.

Naming is part of the mapping. Dropbox and Box tolerate characters and lengths SharePoint rejects (the characters " * : < > ? / \ and |, and paths over 400 characters), and a decade of client folder names will fail the scan. Rename at the source; the scan report lists every offender.

The destination sites follow the same design as a file server migration: one site per permission boundary, one library per working set, and the storage pool sized for the result. File Server to SharePoint and OneDrive covers that design, and SharePoint Storage Limits covers the pool.

Start with an export: both admin consoles list shared links and external collaborators per folder, and that export is the work list for the two things the tool will not do.

Sharing links. Sort them by where they are used. Links in signed contracts and public web pages are rebuilt in SharePoint with the same audience (specific people, or anyone with the link if policy allows) and the old URL is updated wherever it lives. Links nobody can trace are allowed to die. Set the tenant and site external sharing settings first, because the default link type and expiration you choose there is what every user gets.

External collaborators. Each becomes a guest in Entra ID and is re-invited to the specific site or folder. Guests do not need a license for most SharePoint and OneDrive access; Guest and External Users in Microsoft 365 covers the cases where they do. The invitation is also the moment to prune former contractors, former customers and staff's personal mailboxes.

A typical 60-user professional firm after five years on Dropbox has well over a thousand shared links and a couple of hundred external collaborators; checked against the project list, only a small fraction is still in use, and retiring the rest turns the migration from "impossible" into a two-week job.

Two systems running for a few weeks is normal and should be planned, not feared.

• Week 0: identity. Every Box or Dropbox account maps to a Microsoft 365 account by email address; mismatches (personal addresses, aliases, departed users) are resolved in the mapping file first. Users need their licenses assigned before their OneDrive exists.
• Week 1: pilot. One team folder and five personal accounts. Check permissions, names and one rebuilt sharing link.
• Weeks 1 to 3: seed. Migration Manager copies everything while users keep working in the old system, and later passes pick up changes, so the copy can run for days without a freeze.
• Cutover weekend: freeze the source (Box: change collaborators to viewer; Dropbox: set team folders to view-only), run the final pass, verify counts, and switch the desktop clients: remove Box Drive or the Dropbox client through Intune, sign in the OneDrive client, turn on Known Folder Move, sync the libraries each team needs.
• Weeks 4 to 8: read-only tail. The old tenant stays readable while people find what the inventory missed. Then export whatever legal wants kept and close it.

The timeline scales with size and file count, not head count: 40 users with 8 TB of video take longer to seed than 200 users with 1 TB of documents. Our migration estimator prices it from the admin console's storage report.

Both vendors sell annual plans that renew unless notice is given; read the notice and refund terms in your agreement before you set a cutover date, because the migration should land before the renewal, not a week after it. We do not quote their prices; check the current terms with the vendor.

Before cancellation: export the admin reports (users, storage, shared links, external collaborators, audit log) and keep them with the project record; confirm that no application integration (e-signature, CRM, accounting) still writes to the old storage. After cancellation, the desktop clients go from every device, and the old sync folders on laptops are deleted.

On the Microsoft side there is nothing new to buy for most customers: OneDrive and SharePoint are in Microsoft 365 Business Basic, Business Standard and Business Premium, which at Microsoft list price, September 2026 price list, are $84.00, $168.00 and $264.00 per user per year on an annual commitment ($7.00, $14.00 and $22.00 per month). The next Microsoft renewal is the time to check whether any licenses bought for the migration can go, which is what License Cleanup Before Renewal is for.

Our Box, Dropbox and Google Drive to OneDrive for Business Document Migration moves personal accounts to OneDrive at $7 per user plus a $1,500 tenant fee, in five days: mapping, pilot, seed, cutover and the read-only tail. Team folders that belong in SharePoint sites are scoped like a file share: SharePoint Online Migration from File Share As-Is is $4,500 per source (one Box or Dropbox folder tree treated as one server), one week. The sharing-link and guest work is quoted from the export, and the price is fixed before anything is billed.

Does a Dropbox to SharePoint migration keep sharing links?

No. Microsoft's Migration Manager does not recreate external sharing links; they are rebuilt in SharePoint after the move. Export the link list from the Dropbox admin console first and decide which ones are still in use.

Can I migrate Box to OneDrive with Microsoft's own tool?

Yes. Migration Manager in the SharePoint admin center connects to Box, Dropbox and Google Workspace with no extra software. It moves files, folders and internal permissions, not sharing links, comments, earlier versions, Box bookmarks or Dropbox Paper.

Do external collaborators come across?

No. Microsoft's tool deliberately does not share migrated content with external users. They are re-invited as guests in Entra ID to the specific site or folder.

How long does a Dropbox or Box to Microsoft 365 migration take?

Personal accounts for a 20-to-200-user organization: five days of engagement across a two-to-three-week window that includes seeding and a cutover weekend. Team folders add a week per source tree.

What happens to file versions and comments?

Only the latest version of each file is transferred, and comments are not migrated. Export the versions and comments that matter before cutover.

• Microsoft Learn, "Migration Manager Box FAQs", "Overview: Migrate Box using Migration Manager" and "Migration Manager Dropbox FAQs": sharing links not recreated, content not shared with external collaborators, comments not migrated, latest version only, Box Notes converted to .docx with preview, table of contents and annotations omitted, bookmarks not migrated; "Unsupported files in Migration Manager": Dropbox Paper files and templates not exported; Microsoft Support, "Restrictions and limitations in OneDrive and SharePoint": invalid characters and the 400-character path. Not opened from this environment; as reported by sharegate.com and search excerpts on 27 September 2026; verify on Microsoft Learn.
• IT Partner blog articles linked above: Google Workspace migration, guest and external user licensing, SharePoint storage limits, license cleanup before renewal, file server to SharePoint and OneDrive
• IT Partner price sheet, Commercial segment, September 2026 US price list; IT Partner service pages and engineering notes, September 2026