A business team drowning in shared links and duplicate folders does not have a storage problem, it has an ownership problem, and OneDrive changes who owns what. Files that lived in personal Dropbox accounts move into a structure where the business controls access, retention, and offboarding. This guide shows how to migrate Dropbox to OneDrive business team by business team, starting with an audit of who actually owns the files, because the migration is only as clean as the folder map it starts from.
The audit is the unglamorous part and the part that decides everything. Shared folders with ex employees, files owned by personal accounts, and links sent to clients all need a decision before a single file moves. Teams that skip the audit spend months after the move untangling permissions that a week of preparation would have prevented.
Why Teams Make This Move Now
Teams usually reach this decision after months of small frustrations rather than one dramatic failure. The old tool still works, but every workaround added to it makes the next change harder, and the team slowly spends more time managing the tool than doing the work it was bought for. That slow drift is easy to ignore, because no single week looks bad enough to justify a project, yet the total cost across a year is often larger than the migration itself.
The second reason teams move is control. A business team that can explain its own structure, its sharing rules and its review dates keeps the benefit of any tool long after the initial enthusiasm fades. A team that relies on memory or on one enthusiastic person loses it when that person is busy or leaves. Written standards are dull, but they are what turn a good week into a good year, and they cost almost nothing to create compared with redoing work that was never recorded.
Timing matters as much as tool choice. Starting during a quiet period, with a small pilot and a clear review date, gives the team room to fix problems without pressure. Starting during the busiest period, with everything moving at once, turns small mapping errors into visible failures. Choose the pilot carefully, protect the review date, and let the pilot result decide the pace of the wider rollout rather than a calendar deadline set before anyone saw the real data.
How to migrate Dropbox to OneDrive business team Without Losing Live Work
There are several ways to carry out the work, and the right one depends on size, data quality and how much time the team can give it. The table below compares the realistic options, including what each one suits best. Judge each option against your own volume and skill, not against a sales claim, and run the cheapest option that still passes a trial with real work. A method that works on a sample but fails on real data is not a method, it is a demo.
| Option | What it involves | Best for |
|---|---|---|
| Built in or native importer | Microsoft Migration Manager in the SharePoint admin center, which replaced the retired Mover tool | A team with a standard Dropbox setup |
| CSV export and manual import | A manual export cleaned in a spreadsheet before import, giving control over assignment | A team that needs to restructure during the move |
| Assisted or third party migration | A specialist service that handles mapping, batches and validation | A team with compliance, volume or deadline pressure |
Check the current plan details on dropbox.com and microsoft.com before you commit, since pricing, limits and importer availability change. Vendor pages are the only reliable source for prices at decision time, and any figure quoted elsewhere, including in this guide, should be treated as a prompt to verify, not as a quote.
The honest limit to name early is this. Dropbox Paper documents, external sharing links, detailed permission mappings and some version history do not transfer cleanly. They must be converted, recreated or reviewed by hand, and external collaborators need new links rather than expecting old ones to keep working. Accepting that limit in week one lets you schedule the rebuild work properly, while discovering it in launch week turns it into a crisis. Put the rebuild items on the project plan with owners and dates, and treat them as launch criteria, not as follow up tasks.
What Moves, What Breaks and What Must Be Rebuilt
Work through the table below row by row as you migrate Dropbox to OneDrive business team with your own data, and mark each row as moves cleanly, needs rebuilding or needs a decision. Rows marked needs a decision are the ones to resolve before import, since deciding them afterwards means rework. Keep the completed table as the project record, because it answers most questions the team will ask during rollout, and it prevents the same decision being debated three times by three different people.
| Item | Where it goes | What to check |
|---|---|---|
| Personal Dropbox folders | OneDrive personal libraries | Map each user by email before migration |
| Team folders | SharePoint document libraries | Create team sites in advance, then map each folder |
| Shared folders | SharePoint libraries with groups | Recreate membership through Microsoft 365 groups |
| File versions | Version history where supported | Verify version counts on key documents |
| External sharing links | New sharing links | Recreate external links, since old links do not carry over |
| Dropbox Paper docs | Converted Office docs or exports | Convert or export Paper docs before migration |
| File comments | No direct equivalent | Export valued comments or accept their loss |
| Shortcuts and starred files | OneDrive shortcuts and favourites | Rebuild shortcuts after migration |
Two rows in that table usually cause the most trouble, and they are worth naming plainly. The first is anything involving permissions or sharing, since a wrong share can expose sensitive work or block a colleague at a critical moment. The second is anything involving history, since history that arrives flattened or unattributed looks complete but misleads anyone who relies on it. Test both rows in the pilot with real examples, and do not accept a vendor assurance in place of a test result.
Once the mapping is settled, the order of work matters as much as the mapping itself. Move the smallest meaningful slice first, verify it completely, and only then widen the move. That order limits the damage from any error, gives the team confidence from a real success, and creates a repeatable routine for the remaining slices. Teams that move everything at once rarely get that confidence, and they often spend the savings from speed on fixing errors that a pilot would have caught.
The Workflow Step by Step
Follow the steps below in order, because each one builds on a finished earlier step. Skipping ahead to the import before the mapping is settled creates work that has to be redone, while following the order means the import itself is the easy part. Print the list for migrate Dropbox to OneDrive business team, tick each step off, and do not move on until the current step works with real data from the team.
- Audit storage and clean up first. Measure total storage, identify owners, and delete or archive redundant, obsolete and trivial files. Migration Manager charges nothing extra for the tool itself, but every gigabyte of clutter you move costs time and confuses the new structure, so clean first.
- Create SharePoint sites and OneDrive accounts. Create the destination team sites and confirm every user has a Microsoft 365 account with enough storage. Sites are not auto created from folders, so each team folder needs a destination site agreed in advance.
- Map identities by CSV. Map Dropbox users and groups to Microsoft 365 identities in a CSV, and verify email matches before running anything. Identity mapping decides whether permissions and metadata land correctly, so a sloppy map produces a tidy looking migration with wrong access.
- Scan and fix blocking issues. Run Migration Manager scans, download the reports, and fix long paths, unsupported files and permission problems the scan flags. SharePoint path limits bite deep folder structures, so shorten paths before migration rather than during it.
- Pilot one team end to end. Migrate one team completely, then check files, folders, permissions and version history against Dropbox. The pilot proves the mapping, the tool settings and the validation method before the wider rollout.
- Migrate in batches with delta sync. Migrate remaining teams in batches, then run delta sync to pick up files changed since the first pass. Delta sync is what makes a phased migration safe, since teams keep working in Dropbox until their batch cutover.
- Recreate sharing and external links. Recreate external sharing links and review group memberships in SharePoint, since old links do not carry over and external access often breaks. Tell external collaborators the new links explicitly, rather than letting them discover dead links.
- Cut over team by team and monitor. Switch each team to OneDrive and SharePoint on its own date, monitor migration reports for failures, and keep Dropbox read only for a fixed reference period. Team by team cutover keeps support load manageable and gives each team a clean go live day.
The Checklist to Run Before Cutover
Use this checklist as the gate before you complete migrate Dropbox to OneDrive business team, not as an afterthought. Every item should have a name beside it and a date, since a checklist without owners is a wish list. Run through it with the people who will live with the result, not only with the person who set it up, because the people who use the system daily spot problems that the setup person cannot see. If an item fails, fix it and rerun the checklist, rather than waiving it under time pressure.
| Check | What good looks like |
|---|---|
| Storage measured and cleaned | Redundant files removed, totals known |
| Destination sites created | Every team folder has an agreed SharePoint library |
| Identity map verified | User and group matches checked by email |
| Pilot team validated | Files, permissions and versions checked |
| Delta sync completed | Changes since first pass picked up |
| External links recreated | Collaborators told about new links |
The rollback note deserves emphasis, because it is the item most plans skip. A rollback plan is not pessimism, it is professionalism. It states what triggers a pause, who decides, how the team returns to the old system, and how long that return stays possible. Writing it before cutover costs an hour. Needing it without having written it costs days of confusion, and it is usually needed on the one migration where nobody expected trouble.
Trade Offs and Costs to Weigh Honestly
OneDrive for business is included in Microsoft 365 plans, so compare the full Microsoft 365 subscription against Dropbox Business pricing for your headcount and storage needs. Check current plan pages before deciding, since storage caps and per user limits change, including a 5 terabyte per user cap noted in recent guidance.
Also price the cleanup and support time. Migration Manager itself is free, but audit, path shortening, permission review and first month support take real hours. A migration quoted as free on tooling alone understates the project, so budget staff time per team and staff the pilot team go live properly.
Also check what happens when you stop paying. Your data, your history and your templates should stay yours in a usable form, and the export route should be tested before you depend on it. A system that holds data hostage is not a bargain at any price, and the time to discover that is before migration, not during an exit years later when the data matters most. When you migrate Dropbox to OneDrive business team, you are choosing a home for work that will outlive the project itself, so exit terms deserve the same attention as entry price.
Mistakes That Quietly Undo the Work
The mistakes below are common because each one feels reasonable at the time. Read the list with the team, agree which mistake your setup is most likely to make, and put one guard in place against it, since a named mistake is far easier to avoid than a vague warning to be careful. The team that can name its likely mistake before starting has already avoided half of it, and the guard you put in place now is cheaper than the fix you will need later when you migrate Dropbox to OneDrive business team under deadline pressure.
- Assuming sites auto create from folders. Migration Manager does not auto create SharePoint sites from Dropbox folders. Create sites first, map folders to libraries, and verify each mapping before running the batch.
- Skipping the scan reports. Scan reports flag path length, permission and file problems that fail silently mid migration. Read them, fix the flagged items, and rescan before the real run.
- Trusting external links to survive. External sharing links do not carry over. Recreate them, notify collaborators, and check the most shared documents first after migration.
- Migrating Paper docs as an afterthought. Dropbox Paper documents do not migrate as native files. Convert or export them before migration, or accept losing their collaborative format.
- Moving everyone on one day. A single day cutover overwhelms support and hides batch failures. Cut over team by team, with delta sync and a monitoring window per team.
How to Tell Whether It Is Working
Pick four numbers and track them monthly, because evidence beats feeling when judging whether migrate Dropbox to OneDrive business team is working. Choose numbers you can collect without extra admin, such as time saved, errors, completion rates or satisfaction, and record them in one place on the same day each month. A trend over three months tells you far more than a single good or bad week, which may reflect holidays, deadlines or one unusual event.
Compare the new numbers with the baseline recorded before the change, and be honest about what they say. If a number improves, keep doing what caused it and say so to the team, since people repeat work that is praised. If a number gets worse, change one thing, not five, so you can tell what helped. Changing five things at once leaves you guessing, even when the numbers improve.
Set a review date now, ninety days from launch, and put it in the calendar with the name of the person who owns the review. Without a named owner and a date, reviews slip, and a slipped review means a system that slowly stops matching the work. The review itself need not take long, since one hour with the four numbers and the user answers is enough to decide what to keep, what to change and what to stop.
One more consideration is how the team handles exceptions, because every workflow meets a case that does not fit the template. Decide in advance what happens then, whether the exception is handled by hand, escalated to a named person, or logged for a later template change. A workflow without an exception rule either breaks on the first odd case or gets quietly bypassed, and bypassed workflows teach people that the routine is optional. Write the exception rule beside the template, keep it to two sentences, and review it when exceptions start to repeat, since a repeated exception is really a missing step.
Training deserves a note of its own, because a workflow is only as good as the least confident person using it. Train in short sessions with real examples from your own work, let people practise with a colleague before they face a real task, and write the three most common questions and answers where everyone can see them. People who feel confident use the system, while people who feel unsure avoid it and fall back on old habits, which quietly recreates the very problem the workflow was meant to solve.
The First Two Weeks After Cutover
The first two weeks after cutover decide whether the new system sticks or quietly loses to old habits. Staff will hit the first unfamiliar screen, the first missing shortcut and the first report that looks different, and each of those moments is a small decision point. If help is quick and the answer is written down, the new habit forms. If help is slow and the answer lives only in one person’s head, the old habit returns, and it returns without anyone announcing it. Plan the first two weeks as carefully as the migration itself, with named helpers, office hours and a visible list of known issues.
Start with a daily check in for the first five working days, kept to fifteen minutes and focused on blockers only. Ask each team what failed, what felt slow and what they worked around, and fix the workarounds first, since a workaround that survives a week becomes a permanent shadow process. Log every issue with its fix, and share the log where the whole team can read it, because the same question asked by five people costs five times as much as the same question answered once in public. Close each check in with one decision, even a small one, so the team sees progress rather than a growing list.
- Watch the first real task end to end in the new tool, not a demo task, and note every click that felt unnecessary or confusing.
- Check the most used report, queue or dashboard daily for the first week, and compare it with the old system until the numbers agree.
- Ask new joiners and occasional users first, since confident daily users hide problems that occasional users hit immediately.
- Review permissions and access requests weekly at first, because access problems are the fastest way to lose trust in a new system.
- Record every workaround the team invents, and turn the repeated ones into proper fixes or documented steps within the fortnight.
By the end of the second week, the questions should change character. Early questions are about where things live and how to do familiar tasks, while later questions are about edge cases, reporting and improvements. That shift is the signal that adoption is working, and it is worth naming in the review, since teams that expect questions to vanish entirely misread normal learning as failure. If questions have not shifted by week three, the problem is usually training or mapping, not attitude, and it deserves a focused fix rather than a reminder to try harder.
The ninety day review should then judge the move on the numbers chosen before launch, not on how people felt in launch week. Bring the four tracked numbers, the issue log and the list of rebuild items that were deferred, and decide what to keep, what to change and what to stop. Deferred rebuild items need dates at this review, or they drift forever, and the team should hear explicitly which deferred items are being dropped and why. A review that ends with dated decisions is a project closed properly, while a review that ends with general satisfaction is a project that will be reopened the next time someone asks why a report looks odd.
Support coverage during those first weeks deserves its own rota, not just good intentions. Name two people who can answer questions each day, rotate the role so it does not burn out one enthusiast, and give the rota holders time in their week to actually help. A rota that exists only on paper helps nobody, while a rota with protected time turns early confusion into quick answers and quick answers into confidence. Thank the rota holders publicly at the review, since visible thanks is what makes people volunteer for the next change.
Measure support volume as well as task outcomes during the first fortnight, since a falling question count with steady output is a better sign than either number alone. If questions stay high while output falls, the team is stuck rather than learning, and that pattern calls for more training or a mapping fix. If questions fall but output also falls, the team may have quietly stopped using the new tool, and that pattern calls for a direct conversation, not another tutorial. Numbers do not replace talking to people, but they tell you which conversations to have first.
Finally, write the one page handover that the next person will need. It should name the system owner, the review date, the mapping decisions that matter, the known gaps and where the exports and backups live. One page is enough, and one page will actually be read, while a long manual will not. Keep it beside the system, not in a personal drive, and update it at each review. That single habit is what turns a migration project into a system that survives staff changes, busy periods and the next tool decision, whenever that comes.
More Reading on Stratilyze
For the systems around this one, Stratilyze also covers a related Stratilyze guide a related Stratilyze guide a related Stratilyze guide Read the guide that matches your next bottleneck first, because fixing the biggest bottleneck next gives a larger gain than polishing a part of the work that already runs well.
Communication around the change matters as much as the setup itself. Tell the team what is changing, why it is changing, when it takes effect and where to get help, and say it in the channel they already read rather than in a new tool they have not adopted yet. A change announced once in one place will be missed by half the audience, so repeat the message at the pilot, at cutover and at the first review, and keep the wording consistent each time.
Finally, resist the urge to add features in the first month. The first month is for proving the core workflow with real work, fixing the mapping errors the pilot missed, and letting habits form. New features added during that period confuse the measurement, since you can no longer tell whether a change in the numbers came from the workflow or from the feature. Freeze the scope for ninety days, log feature requests for the review, and judge them then against the numbers rather than against enthusiasm.
Frequently Asked Questions
What tool migrates Dropbox to OneDrive now?
Microsoft Migration Manager, built into the SharePoint admin center, is the current free tool, after Mover was retired for admin led migrations in 2024. It moves files, folders and basic sharing, while Paper docs, detailed permission mapping and some version history need separate handling.
Do Dropbox permissions transfer fully?
Only partially. Migration Manager migrates file level permissions where identities map correctly, but external access often breaks and sharing settings may need manual reconfiguration in SharePoint. Verify permissions on the pilot team before the wider rollout.
What happens to Dropbox Paper documents?
Paper documents do not migrate as native files. Convert them to Office documents or export them before migration, and check formatting after conversion, since collaborative comments and structure can shift.
Is there a storage limit to watch?
Yes. Recent guidance notes a 5 terabyte per user cap on OneDrive, ending older higher request options, so check total Dropbox volume against destination limits before planning. Teams over the cap need a SharePoint library strategy, not a single user library.
How long does a business migration take?
A small team can move in one to two weeks, while a larger business with many team folders usually needs four to eight weeks including scans, pilot, batches and delta sync. The scan and pilot results give the honest timeline.
Do external sharing links keep working?
No. Old Dropbox links do not carry over to OneDrive or SharePoint, so recreate links for shared documents and tell external collaborators directly. Check the most shared files first, since those are the links people actually click.
The Bottom Line
Start with the mapping table and the pilot, then the checklist, then the closure date, and do those three things before any wider rollout, because a wider rollout without them is how a promising move becomes a lingering parallel system. The team that runs a simple, written routine well will get more from the new tool than a team with a fancier setup and no routine, and that advantage grows every month the routine runs.
Pick the first step today, test it with real work tomorrow, and let the numbers over the next ninety days tell you what to improve next. That disciplined approach is what makes this kind of change pay, rather than becoming another project that starts with enthusiasm and fades within a month.
