Sign in to Dropbox
Read-only access, approved on Dropbox's own consent screen. Nothing to register, no client secret to store, and no permission that could write to or delete from Dropbox.
ShareMaster V2
Dropbox to SharePoint migration without downloading it all first
Bring a Dropbox account, or an entire Dropbox team, into SharePoint libraries through Microsoft's own Migration API. Folder structure and modified dates come across, Paper documents are converted and reported rather than quietly changed, and a run that stops partway can be picked up where it left off.
Where this is up to. Dropbox to SharePoint is built and has been run end to end against a live tenant, and it lands in the next ShareMaster V2 beta drop. It is not in the build currently published, so if you install the beta today you will not find it yet. V2 updates itself, so the drop that carries it arrives on its own.
Moving off Dropbox now and want to talk the job through first? Get in touch and we will tell you honestly whether this fits.
How it works
Four decisions, then it runs
No PowerShell, no staging file share, and nothing to install on the Dropbox side. It runs on your Windows machine and talks to both services directly.
Choose what to read
A personal home folder, a team folder, the whole team space, or a member's home folder. Then tick the exact folders and files you want if you do not want all of it.
Choose where it lands
A SharePoint site, a library and a folder inside it. The Dropbox folder structure is rebuilt underneath, and folders that already exist are reused rather than duplicated.
Set the rules, then run
Which Dropbox timestamp becomes Modified, what happens to files already in the destination, and what to do with Paper documents. Then it runs, with live per-file progress and a report at the end.
Be clear before you start
What comes across, and what does not
Dropbox and SharePoint do not hold the same information about a file, so some things cannot survive the trip no matter which tool you use. Here is the honest list.
Comes across
- Files, and the full folder structure they sit in
- Modified dates, from whichever Dropbox timestamp you pick: the one the uploading client supplied, or the one Dropbox itself recorded
- Team content: the team space, team folders and member home folders, each as its own scope
- Paper and cloud-native files, converted to the format Dropbox offers and renamed to match, with every conversion listed in the report
- Files that are already in the destination, skipped, replaced, or replaced only if nobody has edited the SharePoint copy since
Does not
- Version history. The current copy of each file is what lands, and Dropbox keeps its own revisions
- Created dates and authorship. Dropbox does not expose who created a file or when, so Created is set to match Modified and SharePoint records the migrating account
- Shared links, folder permissions and team access. Content moves, access does not, and the destination library keeps the permissions it already has
- Deletions on a repeat pass. A file deleted in Dropbox after the first pass stays in SharePoint, which is deliberate: an import should not delete anything
- SharePoint back to Dropbox. This runs one way only
The awkward parts
Built for the migration that does not go smoothly
Copy it twice, cut over once
Do the bulk of the copy while people are still working, then run a second pass that picks up only what changed. You can catch changes since the last pass, or everything since the original baseline, so the cutover window is minutes rather than a weekend.
Rate limits are waited out, not failed
Dropbox throttles and so does Microsoft 365. Both are treated as a pause rather than an error, and anything whose bytes still did not arrive is retried in a sweep at the end of the run instead of being left for you to find in a log.
Stopping is not starting over
Every run records the exact selection it used, so a cancelled or failed one is resumed from the history list. Files already in the destination are skipped rather than copied a second time.
You choose which date wins
Dropbox keeps two timestamps: the one the uploading client claimed, and the one Dropbox observed. The first usually holds the real authoring date, the second is always true. Neither is right for everybody, so it is your call and it is stated on screen.
Nothing is overwritten by accident
Existing destination files are skipped by default. If you do want them replaced, you can still protect anything a person has edited in SharePoint since the last pass.
Compare the two sides afterwards
A comparison report checks what is in Dropbox against what landed in the library, by relative path and by size, so signing off the migration is a document rather than a feeling.
FAQ
Dropbox to SharePoint, common questions
How do I migrate from Dropbox to SharePoint?
Sign in to Dropbox from inside ShareMaster, choose the account, team folder or team space you want to read, pick the SharePoint site, library and folder it should land in, then choose how existing files and Paper documents are handled. ShareMaster stages the content and imports it through Microsoft's SharePoint Migration API, showing per-file progress while it works.
Do I have to register an app in Dropbox first?
No. ShareMaster is itself a registered Dropbox app, so there is nothing to create, no client secret to store and no developer console to visit. You sign in with the Dropbox account that can see the content and approve the access on Dropbox's own consent screen.
What access does it ask for in Dropbox?
Three read-only permissions: read file metadata, read file content, and read sharing information. A team migration adds read-only team information and member listing so it can enumerate team folders and member home folders. Nothing ShareMaster asks for can write to or delete from Dropbox.
Can it migrate a whole Dropbox team, not just one account?
Yes. A team sign-in exposes the team space, each team folder and each member's home folder as separate scopes, and you migrate them one scope at a time so each one can land in the site and library that suits it. A personal Dropbox account signs in the same way and exposes its own home folder.
Does version history come across?
No. The current copy of each file is what lands in SharePoint. Dropbox keeps its own revision history and it stays there, so keep the Dropbox account readable until you are satisfied with the destination.
What happens to Dropbox Paper and other cloud-native files?
Dropbox will not hand those over in their original form. You choose: export each one to the format Dropbox offers and migrate the converted file, renamed to match its new format, or leave them behind. Either way every single one is listed in the run report, because a silently converted file is a file nobody knows changed.
Are Dropbox shared links and permissions recreated in SharePoint?
No. This moves content, not access. Shared links, folder permissions and team member access stay in Dropbox, and the destination library keeps the permissions it already has, so nothing is quietly widened during the move.
Can I run it again to catch what changed?
Yes, and that is the point of running it before cutover rather than during it. A second pass can pick up only what Dropbox reports as changed since the first pass, or everything that has changed since the original baseline. Deletions are deliberately not carried across, so a file removed in Dropbox stays in SharePoint.
What happens if a run is interrupted?
It is resumable. Runs are recorded in the migration history with the exact selection they used, so a cancelled or failed run can be picked up rather than started again, and files already in the destination are skipped instead of copied twice.
Which licence includes it?
Clone Master, the same tier as SharePoint to SharePoint migration. The 14-day trial reaches it as well, with the usual trial limits applied.
Getting off Dropbox soon?
Tell us the shape of the job and we will tell you straight whether this fits, and when the drop that carries it lands.