
—
Enterprises move from Dropbox to SharePoint to keep their data and applications, like files, emails, Teams, and Office apps, in a single place.
For this migration, Microsoft offers a free migration tool called the Migration Manager. It does its intended job. However, it does not move everything. By everything, we mean that it does not migrate version history, external sharing links, and guest access.
Microsoft confirms all these limits in its official documentation.
This blog post explains what actually moves in a Dropbox to SharePoint migration and what gets left behind. By choosing the right cloud migration solution, you’ll also find out how to migrate from Dropbox to SharePoint without losing data or permissions.
Key Takeaways
- Microsoft’s free tool transfers only the most recent version of each Dropbox file.
- External sharing links are not recreated and must be rebuilt at the destination.
- Permissions re-share automatically, but only after you map identities correctly.
- Renaming folders during the project duplicates everything below the renamed folder.
- CloudFuze carries versions, shared links, and permissions in one pass, including external shares.
What You Can Move from Dropbox to SharePoint?
The table shows what moves and what doesn’t, when you migrate from Dropbox to SharePoint.
| Item | Native Migration Manager |
| Files and folder structure | Carried |
| Internal permissions | Re-shared after identity mapping |
| Metadata | Carried when identities are mapped |
| Version history | Most recent version only |
| External sharing links | Not recreated |
| External collaborator access | Excluded by policy |
Microsoft clearly says that the Migration Manager only moves the most recent file version. It does not recreate external sharing links. External collaborators do not get access to the migrated content.
It is critical to plan and address these limits of the native tool if you want to migrate data from Dropbox to SharePoint .
How Microsoft’s Migration Manager Moves Files from Dropbox to SharePoint?
Microsoft’s Migration Manager moves files from Dropbox to SharePoint in the following way:
- Connect to Dropbox, using credentials with Read access to every account in scope.
- Scan and assess, then clear the blockers the report names.
- Copy ready accounts to the migrations list.
- Review destination paths, because matching paths map automatically.
- Map identities across domains, groups, and users.
- Migrate, monitor, and run a delta pass before cutover.
Your destination account must have one of three roles. These are Migration Administrator, SharePoint Administrator, or Global Administrator.
How Identity Mapping Affects File Permissions?
Pay attention to step five in Migration Manager’s workflow. It decides whether users retain their file access post-migration. Microsoft explains how this works.
When each user identity is correctly mapped, files are automatically shared again after migration. Users retain their earlier access. In case the identities are not mapped, files are not shared again.
To prevent this issue, check for these things:
- Map domains before mapping individual users.
- Check that User Principal Names match in both systems.
- Plan how to handle external collaborators before migration.
How CloudFuze Handles Identity Mapping?
CloudFuze maps user identities in three ways.
- Auto-mapping matches users automatically when their names match.
- CSV-based mapping lets you match users manually.
- Folder display mapping is for when the other two methods do not work.
CloudFuze maps guest users along with internal users. It also migrates external sharing permissions. Thus, external users keep their existing access.
Many Dropbox projects move content to two Microsoft platforms. Team files migrate to SharePoint and personal files go to OneDrive.
The process is the same for both. CloudFuze matches each user by email alias. This makes sure a Dropbox to OneDrive migration moves files to the correct account.
Plan Data Loss Prevention (DLP) Before Moving Your Files
Before migration, it is crucial to know where to apply Data Loss Prevention (DLP) policies. Files shared in Dropbox will migrate to SharePoint. Here, Microsoft Purview policies are applicable.
You must identify each and every SharePoint site that will store sensitive or regulated files. This will enable you to apply the right policies post-migration.
It’s also essential to review the security and compliance of both platforms. Microsoft Purview offers better Data Loss Prevention (DLP), sensitivity labels, and data retention policies than standard Dropbox plans.
We recommend against keeping old sharing permissions. A wise course of action would be to review and set up file access carefully.
How to Move What the Native Tool Leaves Behind?
A dedicated Dropbox to SharePoint migration tool like CloudFuze moves the data that Microsoft’s native tool does not. The table explains how it handles each item.
| What the native tool drops? | How CloudFuze handles it? |
| Version history, latest only | All versions, or a selected number per file |
| External sharing links | Link types preserved, including view and edit access |
| External collaborator access | Folder and file permissions carried with external shares |
| Dropbox Paper documents | Converted to .docx in SharePoint Online |
| Changes during a long project | One-time pass plus delta before cutover |
During migration to SharePoint, many teams overlook embedded links or links inside files. Almost every document, such as Word, Excel, PowerPoint, and PDF files, usually contains links to Dropbox locations. These stops working after migration.
CloudFuze migrates files from Dropbox to SharePoint without breaking links. The enterprise cloud migration platform automatically replaces unsupported characters with supported ones. It also creates shortcuts for long file paths instead of letting them cause migration failure.
CloudFuze effectively handles numerous large-scale enterprise migrations. It moved Estée Lauder’s over 1,000 users and more than 100 TB of data from Dropbox to SharePoint Online and OneDrive.
CloudFuze is most suitable in the following cases:
- You need to keep file versions for legal or retention requirements.
- External collaborators need access immediately after migration.
- Dropbox Paper documents must remain editable.
- You need to move terabytes of data in stages.
CloudFuze is SOC 2 Type 2, ISO 27001, and GDPR compliant. Authentication runs through OAuth, so user passwords are never handled.
Decide What Has to Survive First
Choose your migration tool based on what you need to move. First, list everything you want to keep intact during migration.
Microsoft’s Migration Manager can be adequate if you only need to move files and internal access permissions. But if you also need version history, guest access, or links inside files, consider a third-party migration platform like CloudFuze.
In either case, identify any migration gaps before starting. Talk to a migration specialist if you need to preserve file permissions or version history.
Frequently Asked Questions
1. Does Migration Manager Keep Dropbox Version History?
No, Microsoft mentions in its official documentation that the Migration Manager only migrates the latest version of each file. All versions older than the most recent one stay in Dropbox. Projects under retention or legal hold require a migration tool that carries version history across.
2. Will Dropbox Shared Links Still Work After the Move?
No, Microsoft does not recreate external sharing links. You need to rebuild every link again at the destination. This task is quite time- and effort-intensive. A wise option is to use a migration platform that preserves link types, including view and edit access.
3. Can Dropbox Paper Documents Move to SharePoint?
Yes, Dropbox documents can move to SharePoint, but not through the native route. A third-party tool like CloudFuze converts Dropbox Paper files into .docx documents in SharePoint Online. They then open and edit normally in Word.
4. What Happens If I Reorganize Folders Mid-Migration?
Microsoft considers a renamed file or folder a completely new object. Everything below the renamed folder can duplicate at the destination. It’s important to make structural changes before the project starts, or after it finishes.
—
