Roughly a third of business file migrations run into trouble at the same point, and it is not the copying. It is permissions. A folder tree that has grown organically for years carries ad hoc shares, forgotten external collaborators, and links that nobody owns, and copying that tree without redesigning it simply reproduces the mess on a new platform. Box appeals to teams that need stronger admin controls, compliance features, and content governance, while Dropbox remains the simpler sync-first choice. When you switch Dropbox to Box business team leaders should therefore treat the move as a permissions redesign with a file copy attached, not the other way round.
This guide maps shared folders to Box folders, audits who can see what, and sequences the move so the team never loses access to live work.
Why teams choose Box over Dropbox, and when they should not
Dropbox team folders versus Box folders
Choosing between staying and moving is a decision about the next two years, not about this week’s annoyance. Write down the three frustrations that pushed you to consider the move and check whether the new platform genuinely solves all three or merely replaces them with different ones. Read recent reviews from teams of a similar size, because a tool that shines for a solo user can strain under a team, and the reverse is also true. If only one of the three frustrations is solved, the move may still be worth it, but say so plainly and price the remaining two into the decision. A move made with open eyes lasts.
A move made on a single impressive demo usually ends with a second move a year later.
Box admin controls for business teams
Price is usually the trigger, but it is rarely the whole reason to move. When you compare the two bills side by side, look past the headline monthly figure and count what each plan actually includes for the people who will use it every day. A cheaper plan that forces you to buy a second tool for something the old plan included is not cheaper at all. switch Dropbox to Box business team deserves a simple spreadsheet before anyone cancels anything. List every seat, every add-on, and every integration you pay for today, then price the same setup on the new platform.
Add the cost of running both platforms side by side for one or two months, because that overlap is the honest price of a careful move. Most small teams find the saving is real but smaller than the marketing pages suggest, and the real win is a better fit for how the team works now rather than a dramatic cut to the bill.
How to switch Dropbox to Box business team leaders audit first
Permissions are the part of a move most likely to surprise a team, because sharing rules rarely transfer exactly. Before you move anything, list who can see what today, including outside collaborators and anyone with a link. Decide which of those people should keep access in the new system and which should be re-invited deliberately. Shared items deserve a second pass after the import. Open the sharing panel on a sample of moved items and confirm the right people still have access and nobody unexpected does. Pay special attention to items that were shared by link, since links from the old platform stop working once the old account closes.
Re-creating those shares on the new platform is a small job if it is planned, and an embarrassing scramble if it is discovered by a client.
A migration is the best excuse a team will ever get to clean up years of accumulated clutter, and the cleanup should happen before the move, not after. Archive what nobody has opened in a year, delete duplicates, and rename the folders whose names only made sense to one person who left long ago. Moving clutter costs time twice, once to copy it and once to sort it on the other side. It also makes the new workspace feel stale on its first day, which is the opposite of the fresh start a move should feel like. Be careful with deletions, though.
Archive rather than delete anything that might matter for tax, legal, or client history, and keep a short note of where the archive lives so it can be found again.
Start the audit at least two weeks before the copy. List every team folder, every external collaborator, and every active shared link, then decide what survives. switch Dropbox to Box business team gets easier with every stale share removed now, because each one removed is one re-invite you will not have to send later.
Mapping is the unglamorous work that decides whether the new workspace feels familiar or foreign. Before importing, write down what each old container becomes in the new world and keep that sheet open during the whole import. Names matter more than people expect. A folder or list called Clients in the old tool should still be called Clients in the new one, or people will spend weeks hunting for things they used to find by habit. Do the same for labels, tags, and groups. Where the new tool has no exact match for an old concept, decide the closest fit in advance and note it on the mapping sheet so nobody invents a different answer mid-import.
After the import, spot check ten items from different parts of the archive and confirm each one landed where the sheet said it would.
This table is the migration contract. No folder moves unless its destination row exists here and its owner has signed it off. switch Dropbox to Box business team stays auditable when the mapping sheet, not memory, decides where each folder lands.
| Dropbox item | Box destination | What to check after import |
|---|---|---|
| Team folder | Box folder owned by the team | Members and access levels match the audit |
| Personal folder | Box personal folder per user | Owner can find files and folder structure is intact |
| Shared folder with external users | Box folder with re-invited collaborators | External users confirm access after re-invite |
| Shared link | New Box shared link | Old link recipients receive the replacement link |
| File with version history | Box file with versions where supported | Current version opens and key older versions exist |
| Paper document | Box Note or converted document | Content is readable and editable by the right people |
| File comments | Box comments where supported | Key approval comments preserved or archived separately |
Running the copy with a migration tool
Dropbox Business connection for migration
Exports are where migrations quietly succeed or fail, so treat the export as a deliverable in its own right. Run the export from the desktop app or the admin console rather than a phone, because desktop exports expose the full options for format, attachments, and folder structure. Keep the original export files untouched in a clearly named folder, and work only on copies. That way a bad import can be repeated without going back to the source and re-exporting everything. Check the size of each export before you import it. A file that is far smaller than expected usually means attachments or a whole section were left out.
A file far larger than expected may contain duplicates from an earlier partial export. Either way, stop and look before you import, because importing twice creates the duplicate mess that takes longest to clean up.
Box for Business destination setup
The small details are where a migration earns its reputation inside a team. Dropbox file version history in Box deserves a dedicated test during the pilot, because it is used daily and any breakage shows up immediately. Run through it with the person who uses it most and watch where they pause. A pause usually means a label changed, a default changed, or a step moved, and each of those is fixable in minutes once spotted. Write the fix into the team guide the same day. Small details also include the things nobody owns, like shared templates, saved searches, and default views. Assign an owner to each one before the move.
An unowned detail is a detail that will be discovered broken at the worst possible moment.
Permissions, versions, and links after the copy
Box folder permissions for external collaborators
Every migration leaves something behind, and naming those gaps early prevents disappointment later. Some features have no direct equivalent, some history is stored in a format the new tool cannot read, and some automations have to be rebuilt by hand. Make a short list of the three things your team would miss most if they vanished, and test each one during the pilot. If a gap turns out to be a deal breaker, you want to learn that while the old platform is still running, not after it is cancelled. For gaps you can live with, write a one-paragraph workaround and put it where people will find it.
Teams accept a missing feature far more easily when someone has already explained the replacement than when they discover the loss on their own during a busy day.
A second detail worth the same attention is Box retention and admin console settings, which tends to be set up once and then forgotten. Because it is forgotten, it is also the thing most likely to be configured differently on the new platform without anyone noticing. Compare the old and new settings side by side during the pilot and screenshot both so the comparison can be repeated after the full import. If the new platform offers a stronger or simpler version of the same setting, adopt it deliberately and tell the team what changed. Quiet improvements are fine, but quiet changes that nobody was told about feel like bugs.
A short message explaining the change turns a potential complaint into a small welcome improvement.
Permission audit checklist for cutover week
Testing after a move should follow real tasks, not a generic checklist copied from a help page. Pick the five things your team does most often and run each one on the new platform with real data. Send a message, share a file, find an old item by searching, open the workspace on a phone, and undo a mistake. Time each task loosely and note where anyone hesitates. Hesitation is useful information. It points to the exact spot where a short guide, a renamed folder, or a different default setting would help. Repeat the same five tasks a week later. If the second run is faster and nobody asks for help, the move has landed.
If the same task still stalls, that task owns your next fix, not some other feature nobody uses.
Run this audit after the copy and before telling the team the move is done. A migration is not complete when files arrive. It is complete when the right people, and only the right people, can open them. switch Dropbox to Box business team is judged on this checklist more than on transfer speed.
- [ ] List every team folder, its members, and each member’s access level, and have folder owners confirm the list.
- [ ] Identify every external collaborator and decide who is re-invited, who loses access, and who is told why.
- [ ] Inventory all active shared links and note which clients or partners depend on each one.
- [ ] Confirm that no folder contains files larger than the destination platform’s per-file limit.
- [ ] Run a pilot copy of one team folder and verify structure, permissions, and version history before the full copy.
- [ ] After the full copy, open a sample of folders as a viewer, an editor, and an admin to confirm each role behaves correctly.
- [ ] Re-invite external collaborators on Box and collect a confirmation from each one that they can open shared items.
- [ ] Replace shared links in client documents, wikis, and email templates with the new Box links.
- [ ] Run a delta copy so files changed during the main copy are not left behind in Dropbox.
- [ ] Set Dropbox folders to read-only for two weeks, then archive or delete them only after the audit passes.
Timing, licences, and device rollout
Box Drive on team laptops
Timing a move well is mostly about avoiding the worst week, not finding a perfect one. Look at the calendar for deadlines, launches, holidays, and the days when the person who knows the old system best will be away. Then pick a quiet stretch and work backwards. Exports and pilot batches happen in the first week, the full import in the second, and verification in the third. Tell everyone the dates early, including clients who share files with you, so nobody is surprised by a changed link or a new invite. If a deadline moves into your migration window, pause the move rather than rushing it. A migration delayed by a week costs little.
A migration rushed through a deadline week costs trust, and trust is harder to rebuild than any folder.
Billing overlap is the part of a migration budget that people forget until the invoice arrives. Plan to pay for both platforms for at least one full billing cycle, and two if the team is large or the data is messy. Downgrade the old plan before cancelling it outright if the vendor allows it, since a cheaper read-only tier keeps the safety net while cutting the cost. Watch renewal dates on both sides. A move that finishes three days after an annual renewal has effectively paid for a year of a platform nobody uses.
Set a calendar reminder for the cancellation date on the day the move starts, not the day you hope it ends, so the reminder survives even if the project slips by a week or two.
Mobile behaviour decides whether a migration feels like an upgrade or a downgrade, because most people check the new tool on a phone before they ever sit at a desk. Install the new app on every phone and tablet the team uses, sign in, and confirm that offline access, search, and sharing all work the way people expect. Phones also expose the gaps fastest. A note, file, or message that looks fine on a computer but renders badly on a small screen will be reported within hours. Fix mobile display issues before the full rollout, even if that means adjusting a template or renaming a long folder. The desktop experience can wait.
The phone experience is the one people judge first.
Verification, training, and retiring Dropbox
Box search and version history after migration
Verification is a job with an owner and a deadline, not a vague hope that someone will notice problems. Assign one person to own the post-move check and give them a written list of what to confirm. Counts come first. Compare the number of items before and after, and investigate any gap larger than a rounding difference. Then check quality on a sample. Open items from the start, middle, and end of the archive and confirm attachments, images, and formatting survived. Finally, check access. Confirm that the people who should see shared items can still see them and that former collaborators cannot. When all three checks pass, write a short note saying so.
That note is what lets the team cancel the old plan without a lingering worry.
Training for a migration works best in short, task-shaped pieces rather than one long session. Nobody remembers a forty minute tour of every menu. People remember being shown how to do the three things they do every morning. Record a short screen video for each of those tasks, keep each one under three minutes, and link them from the top of the new workspace. Then hold one live session where people bring their own questions and their own messy examples. Answer with their data on screen, not with a demo account. After the session, keep a single page of answers to the questions that came up twice.
That page becomes the real manual, because it was written from the questions people actually asked.
History is what makes an archive valuable, and it is also what migrations handle worst. Creation dates, edit history, comments, and version history often transfer partially or not at all. Decide which history actually matters before you move. For most teams, the content and the current version matter far more than every past edit. Where history does matter, such as client approvals or contract drafts, export a dated copy in a stable format and store it alongside the new item with a clear name. Tell the team plainly what history will look different after the move so nobody panics when an old item shows the import date instead of its original date. Honesty about history beats a surprise every time.
Keeping Box tidy after the migration
The habits in this section decide whether you switch Dropbox to Box business team successfully or merely completely.
The first month on the new platform sets habits that last for years, so treat it as part of the migration rather than after it. Keep the mapping sheet and the team guide linked from the top of the new workspace for at least thirty days, because people will still look for old names and old locations while the new ones become familiar. Resist the urge to reorganise everything again immediately. A second reorganisation on top of a migration confuses people who have just learned the new layout, and it destroys the before-and-after comparison that tells you whether the move actually helped. Instead, collect small complaints in one shared document and review them together at the end of the month.
Patterns in that document point to genuine fixes, while one-off grumbles usually resolve themselves once the new routine settles. The goal of the first month is not perfection. It is a team that can do everyday work without thinking about the platform at all, which is the quietest sign that a migration has succeeded.
Measuring a migration after the fact is worth doing properly, because the next tool decision will lean on whatever story this one leaves behind. Pick three measures before the old platform closes and record them while you still can. The first is time on everyday tasks, measured loosely by asking the team how long the five most common tasks take now compared with before. The second is cost, including seats, add-ons, and the overlapping months, compared with the old bill for the same period. The third is friction, counted as support questions about the new platform per week, which should fall steadily after the first fortnight.
If all three move in the right direction, the move was a success and the numbers prove it. If one measure stalls, that measure names the next improvement project. Either way, the team ends up with evidence instead of opinions, and the next migration starts from a stronger position than this one did.
Every platform decision deserves a revisit date, set while the memory of the move is still fresh. Put a reminder twelve months out to ask whether the new platform still fits how the team works, whether the pricing still makes sense at the current size, and whether any feature that was missing at migration time has since appeared. A revisit is not a plan to move again. It is protection against the slow drift that made the last platform feel wrong, where pricing crept up, features went unused, and workarounds piled up until switching felt urgent.
Teams that review annually tend to make smaller, calmer adjustments, such as dropping unused seats or adopting one new feature, instead of another full migration. Write the revisit questions down now, while you can still remember what frustrated you about the old setup, and let that memory keep the new setup honest.
More Reading on Stratilyze
Teams finishing this migration often read next about cloud storage security for business, setting file naming conventions, and managing external sharing safely, since those habits decide whether the new Box setup stays clean or drifts back into the same sprawl. Anyone planning to switch Dropbox to Box business team should start with the mapping table above.
Frequently Asked Questions
Do Dropbox permissions transfer automatically to Box?
Migration tools can preserve many permissions, but not every Dropbox sharing model has an exact Box equivalent. Treat permission transfer as a starting point, not a guarantee. Audit a sample of folders after the copy, re-invite external collaborators deliberately, and recreate shared links by hand. The audit takes a day for most teams and prevents the far worse discovery that a client lost access, or that a former contractor kept it.
Shared links are tied to the platform that created them, so Dropbox links stop being useful once the team moves and the old account closes. Inventory the links that clients and partners actually use, create Box equivalents, and send the replacements with a short explanation. Links buried in old documents will still break, so search shared wikis and templates for Dropbox links during cutover week.
Is there a file size limit to worry about?
Migration guides for Dropbox to Box moves commonly note a per-file ceiling around fifty gigabytes for uploads through some tools, with a cap on files per folder in certain connectors. Check the limits of the tool you choose against your largest files before the full copy. A single oversized file can stall a batch, so split archives or move exceptional files by a separate method rather than letting them block everything else.
How long does a business team migration take?
A small team with a tidy folder tree can finish in a week or two, including audit and verification. Larger teams with years of accumulated sharing should plan three to four weeks, with the audit taking as long as the copy itself. The copy speed matters less than the audit quality. A fast copy of a messy permission tree just delivers the mess sooner.
Should we use a migration tool or copy files manually?
For more than a few users, use a migration tool. Tools handle large inventories, preserve timestamps and versions where supported, log failures per file, and run delta copies for changes made during the move. Manual drag-and-drop works for a single folder but loses metadata, breaks permission tracking, and gives no error log when something is skipped. The tool’s report becomes your verification evidence.
When is it safe to cancel Dropbox?
Only after the permission audit passes, external collaborators confirm access, shared links are replaced, and the team has worked a full week from Box alone. Keep Dropbox read-only during that week so nothing new lands in the old system. Cancelling early saves one month of fees and risks a week of confusion, which is a poor trade for any team that shares files with clients.
How do we handle files owned by people who left the company?
Transfer ownership before the copy, not during it. Ask an admin to reassign orphaned files and folders to a current team member or to a team-owned archive folder, and record the reassignment in the mapping sheet. Files owned by departed staff are the ones most likely to fail in a migration tool, because the tool cannot act on behalf of an account that no longer exists. Sorting ownership first prevents silent gaps in the new Box folders.
A cleaner Box, not just a copied Dropbox
The temptation in every file migration is to measure success by gigabytes moved. Resist it. Measure this move by the permission audit, by the external collaborators who confirmed access, and by the folders that finally have owners again. Box rewards teams that arrive with a tidy map, because its admin controls and governance features only help when someone has decided who should see what. Arrive with a copied mess and Box will faithfully govern that mess. Arrive with an audited, mapped, redesigned tree and the team gets something Dropbox never quite gave them. A file system they can explain to a new hire, a client, or an auditor without apologising for it.
That is how you switch Dropbox to Box business team with confidence, in waves, and with the old platform still warm.