Cloud storage migration
Dropbox → SharePoint
Migration Manager copies Dropbox Business accounts into SharePoint, OneDrive, or Teams. You map identities first. A destination path cannot be edited after that task starts.
Typical timeline2 to 6 weeks20 to 50 hours active work
This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.
Before you migrate
Should you make this move?
Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.
Current platform
Dropbox
Reasons to stay
- Fast, dependable desktop synchronization keeps file-based collaboration simple
- Managed sync, sharing, version history, and access controls reduce file-server work
Reasons to leave
- Knowledge, office-suite, and governance workflows are less integrated than broader suites
- Shared links, permissions, comments, and ownership models do not map cleanly
New platform
SharePoint
What gets better
- Microsoft 365 content, identity, compliance, and intranet capabilities are deeply integrated
- Managed sync, sharing, version history, and access controls reduce file-server work
What gets worse
- Sites, libraries, permissions, and sync behavior create a complex migration surface
- Shared links, permissions, comments, and ownership models do not map cleanly
Best of the move
SharePoint: Microsoft 365 content, identity, compliance, and intranet capabilities are deeply integrated. This removes a major source-side concern: Knowledge, office-suite, and governance workflows are less integrated than broader suites.
Worst of the move
What you lose: Fast, dependable desktop synchronization keeps file-based collaboration simple. What you inherit: Sites, libraries, permissions, and sync behavior create a complex migration surface.
Jump to a section
Know the shape of the move.
Clean0
Partial4
Manual5
Lost3
SourceDropbox10 mapped fields
Automatic1
Transform3
Manual5
Unsupported1
DestinationSharePoint9 supported paths
This timeline assumes
- The source is Dropbox Business. Connect asks for a Dropbox Business administrator. A personal Dropbox account is not this project.
- The destination is a Microsoft 365 tenant. The site already documents Dropbox → OneDrive, Dropbox → Google Drive, and OneDrive → SharePoint.
- You can sign in as Microsoft 365 Migration Administrator, SharePoint Administrator, or Global Administrator. Microsoft says to use the fewest of those.
- Users and groups already exist in Microsoft 365 before you map them.
- Dropbox stays licensed until a sample of files opens in SharePoint with the right people.
What survives the move.
“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.
| Item | Outcome | Impact | What happens | Mitigation |
|---|---|---|---|---|
| The project | manual | critical | In Microsoft 365 admin center, go to Setup, then Migration and imports, and create a Dropbox project. You then connect, scan, add folders to the migration list, review paths, map identities, and migrate. | Scan and read the reports before you add a folder to the migration list. |
| Source access | manual | critical | The connect wizard signs in to a Dropbox Business admin and asks you to Allow the listed individual and team permissions. Microsoft also says the account needs Read access to every Dropbox user you will migrate. | Use an admin who can see the accounts on the list. A member token is not the documented path. |
| Scan findings | partial | high | After the scan you download reports of issues that can block a migration. The overview says Migration Manager has file size limits and unsupported files, and points at a separate note. This playbook does not invent those numbers. | Read the scan report and the limits article Microsoft links before you start a task. |
| Destination path | manual | critical | A task cannot run without a destination. Once content is migrating to a destination, that path cannot be modified. Exact matches are filled in for you. A SharePoint path looks like https://contoso.sharepoint.com/sites/sitecollection/Shared Documents or that URL plus a folder. | Fix paths in the panel or with the destinations CSV before you start the task. |
| OneDrive targets | manual | high | If the destination is OneDrive, Microsoft says to pre-provision OneDrive. Otherwise validation fails. The path can be a UPN such as [email protected], or a personal URL under /personal/. | Provision OneDrive before you upload the destinations file. |
| Identity map | manual | critical | Automap matches names exactly. Microsoft says that usually does not map everyone. You can edit a row or import a file. Domains, users, and groups must already exist on the Microsoft side, and every required source identity must be mapped before migration. If they are not, people lose access and file metadata is wrong. | Create the accounts first. Then finish the map. Do not start on automap alone. |
| Folder permissions | partial | critical | Permissions migrate with the files only when identity mapping is already done. The default copies folder permissions. File permissions are off, and files inherit the parent folder. Turning file permissions on makes the migration slower. In a delta, permissions move only when the related files move. | Decide folder-only or file permissions before the first task. |
| Dropbox roles | partial | high | Microsoft's table maps Dropbox Owner to Owner, Editor to Can edit, and Viewer to Can view. | Check one editor and one viewer after the pilot. Do not expect a longer Dropbox role list. |
| Library root | partial | high | If the destination is the document library itself, root folder permissions from the source are not migrated. Microsoft says to create a folder in the library and use that folder as the destination. | Put the Dropbox account in a folder under Shared Documents, not on the library root, when those permissions matter. |
| Path edits after start | lost | critical | Microsoft says the destination cannot be modified once migration to it has started. A wrong site is a new task, not an edit. | Validate the CSV. Empty destination rows are skipped during validation, which can hide a folder you forgot. |
| Shared links and comments | lost | high | The pages above describe files, destinations, identities, and the Owner, Editor, and Viewer roles. They do not say Dropbox comments or public shared links are recreated. | Export a list of links you still need and recreate them in SharePoint. |
| Personal Dropbox | lost | high | The connect article is a Dropbox Business administrator sign-in. This project does not start from a personal login. | Use a different copy method for a personal account. Do not force it through this wizard. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Dropbox Business team | Migration Manager Dropbox project | manual | Created under Setup, Migration and imports. |
| Admin sign-in | Allow on the Dropbox consent screen | manual | Needs read access to the users you will scan. |
| Scanned folder | Migration task | manual | Add it only after the scan report is reviewed. |
| Account path | SharePoint, OneDrive, or Teams path | transform | Locked once the task starts. SharePoint example includes /Shared Documents and an optional folder. |
| OneDrive user | Pre-provisioned OneDrive | manual | Validation fails if OneDrive does not exist yet. |
| Dropbox user or group | Microsoft 365 identity | manual | Automap is exact name match. Finish the rest by hand. |
| Folder permission | Folder permission | automatic | On by default, after identities are mapped. |
| File permission | Inherited from the folder, unless you enable file permissions | transform | Enabling it slows the copy. |
| Owner, Editor, Viewer | Owner, Can edit, Can view | transform | Microsoft's Dropbox role table. |
| Comment or shared link | No destination | unsupported | Not described as part of this migration. |
Make the move recoverable.
Create the source-of-truth backup
Keep Dropbox readable until SharePoint permissions match the map.
- List the Dropbox accounts and the SharePoint sites they should land in.
- Confirm each Microsoft user exists.
- Download the scan reports.
- Export current shared links you still depend on.
- Leave Dropbox licenses on.
Proof to capture: A destination CSV you validated, a scan report, and Dropbox still opening the same files.
Scan and paths
Choose a destination you will not need to edit later.
- Connect the Business admin and finish the quick settings wizard.
- Scan, download the reports, and fix blockers.
- Add ready folders to the migration list.
- Upload a destinations CSV if the panel cannot see a site. Empty paths are skipped.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Identities and permissions
Copy access with the files.
- Create missing users and groups in Microsoft 365.
- Map every required Dropbox identity. Do not trust automap alone.
- Leave file permissions off unless you accept the slower copy.
- If you need the source root permissions, destination a folder inside the library, not the library root.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
The things most likely to hurt.
These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.
Cutover
The task starts on the wrong site
criticalpossible likelihood
A path was close enough to pass a glance, and the task is running.
- Consequence
- Microsoft says you cannot change that destination afterward.
- Mitigation
- Validate the CSV and migrate one account first.
Stop if: Any required path is empty or unverified.
Design
Automap left people unmapped
criticallikely likelihood
The map looks finished because some names matched.
- Consequence
- Those users lose access, and metadata is wrong. Microsoft states both outcomes.
- Mitigation
- Compare the Dropbox user list with the map.
Stop if: A person who must open the files has no Microsoft identity.
Pilot
File permissions were left at the default
highpossible likelihood
A file was shared more narrowly than its folder, and you did not enable file permissions.
- Consequence
- The file inherits the folder. Viewers of the folder can see it.
- Mitigation
- Test one file that is not shared with the whole folder.
Stop if: That file is visible to someone who could not open it in Dropbox, and you needed the old rule.
Do the work in this order.
Estimate forA Dropbox Business team moving into SharePoint libraries
Total elapsed2 to 6 weeks
Active work20 to 50 hours
BufferAdd time for scan exceptions, OneDrive provisioning, and a second pass for file permissions.
01
Days 1 to 4Accounts and sites2 to 4 days
02
Days 4 to 6Scan1 to 3 days
03
Days 6 to 12One account3 to 6 days
04
Days 12 to 20Remaining accounts4 to 8 days
05
Days 20 to 30Keep Dropbox1 to 2 weeks
- Days 1 to 4 · inventory
Accounts and sites
6 to 12 hours active2 to 4 days elapsedSite owners waiting- List Dropbox accounts and target sites.
- Confirm the Microsoft users exist.
Depends on: Dropbox Business admin, SharePoint admin
Stop / go checkpointConnect Migration Manager?
Go when: Every account has a proposed path and a Microsoft user.
Stop when: The source is a personal Dropbox.
- Days 4 to 6 · backup
Scan
3 to 8 hours active1 to 3 days elapsedScan time waiting- Connect and scan.
- Download the reports.
- Save shared links you must recreate.
Depends on: Admin consent
Stop / go checkpointAdd folders to the list?
Go when: Blockers in the scan report have an owner.
Stop when: A report has not been downloaded.
- Days 6 to 12 · pilot
One account
6 to 14 hours active3 to 6 days elapsedCopy waiting- Map identities for the pilot.
- Migrate one account into a folder, not the library root.
- Check Owner, Editor, and Viewer.
Depends on: Validated destination
Stop / go checkpointMigrate the rest?
Go when: The pilot user can open the file, and a non-user cannot.
Stop when: The path was wrong and you cannot edit it.
- Days 12 to 20 · cutover
Remaining accounts
4 to 10 hours active4 to 8 days elapsedCopy and deltas waiting- Start the rest only with mapped identities.
- Run a delta.
- Recreate shared links that did not come across.
Depends on: Pilot accepted
Stop / go checkpointSend people to SharePoint?
Go when: A sample from each site opens for the mapped user.
Stop when: An unmapped group still owns access.
- Days 20 to 30 · observe
Keep Dropbox
3 to 6 hours active1 to 2 weeks elapsedPeople using the new sites waiting- Watch missing-file reports.
- Leave Dropbox licensed.
- Fix links you still see in old mail.
Depends on: SharePoint in use
Stop / go checkpointRemove Dropbox?
Go when: You can still open Dropbox if a file is wrong.
Stop when: A library root is missing the permissions you needed.
Cut over with a way back.
Cutover
Copy the remaining accounts after one destination has been proven.
- Finish identity mapping.
- Validate destinations, using a folder inside the library when root permissions matter.
- Start the tasks.
- Run the delta Microsoft describes, knowing permissions move with the files that move.
- Ask a mapped editor and a mapped viewer to open a file.
- Leave Dropbox in place.
Proof to capture: The sample users see the expected files in SharePoint, and Dropbox still has them.
Rollback
Send people back to Dropbox. You cannot retarget a task that already started.
- Tell people to use Dropbox for the accounts that are wrong.
- Leave the SharePoint copy. Do not delete it until you know which files were edited there.
- Create a new task if a later attempt needs a different path.
- Fix the identity map before that new task.
- Write down the path that was locked in.
Proof to capture: Dropbox is still the place people are told to work, and the bad destination is known.
Rollback immediately when
- A destination path is wrong after the task starts
- A required user is unmapped
- A file is visible because only folder permissions were copied
- OneDrive validation failed because it was not provisioned
- The scan report was never read
Prove the migration worked.
Every blocking check must pass. Capture the evidence before cleanup begins.
| Pass | ID | Check | Method | Expected result | Evidence |
|---|---|---|---|---|---|
V-01Blocking | Business admin | Confirm the connect account is a Dropbox Business admin with read access. | The wizard reaches Allow and the scan list. | Project screenshot. | |
V-02Blocking | Reports downloaded | Open the scan reports before adding tasks. | Each blocker has a decision. | Scan file. | |
V-03Blocking | CSV validation | Upload destinations and read the validation report. | Every task you will run has a path. Empty rows are skipped, so look for them. | Validation report. | |
V-04Blocking | Map complete | Compare Dropbox users and groups with the map. | Each required identity has a Microsoft account that already exists. | Map export. | |
V-05Blocking | Editor and viewer | Open one file as each. | Editor can edit. Viewer can view. The Microsoft table is Owner, Can edit, Can view. | Access check. | |
V-06Blocking | Library folder | If you needed source root permissions, confirm the destination is a folder inside the library. | It is not the bare library. | Path note. | |
V-07 | A changed file | Edit a Dropbox file and run the delta. | The new bytes arrive. Permissions on unchanged files are not the delta's job. | Delta log. | |
V-08Blocking | Dropbox still licensed | Open the same file in Dropbox. | You can send people back. | Dropbox check. |
Remove the scaffolding safely.
Safe after: Mapped users have worked in SharePoint and Dropbox is still available for a miss.
- Archive the scan report, the destination CSV, and the identity map.
- Recreate shared links that the migration did not carry.
- Leave file-permission settings documented.
- Remove Dropbox licenses only after the sample still looks right.
- Do not edit a destination that already ran. Start a new task.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- Microsoft: migrate Dropbox with Migration ManagerAccessed 2026-11-02
- Microsoft: connect to DropboxAccessed 2026-11-02
- Microsoft: review Dropbox destination pathsAccessed 2026-11-02
- Microsoft: map Dropbox identitiesAccessed 2026-11-02
- Microsoft: Migration Manager permissionsAccessed 2026-11-02