Box or Dropbox to SharePoint migration: what gets left behind
Box or Dropbox to SharePoint migrations commonly drop or flatten version history, comments, shared-link settings and the folders of departed users, depending on the tool and scope. Microsoft partners can ask the owner, before the old account closes, whether that file history has been assessed for AI data licensing through SourceX.
What a file-share migration commonly leaves behind
A Box or Dropbox move to SharePoint or OneDrive usually copies the current version of each file for active users. The history around those files is where gaps appear: earlier versions, comments, task assignments, sharing records and content owned by people who have left.
Which of these survive depends on the migration tool, the plan tier on each side, and the mapping decisions made during scoping. Verify against your tool's documentation rather than assuming.
For a data-licensing conversation, the file share is often the best long-run record of how a company worked: contracts through their drafts, SOPs through their revisions, project folders through their delivery. Once the old tenant closes, that trail can be gone for good.
Where does the leftover content sit?
| Item | What often happens | Why it may matter later |
|---|---|---|
| Version history | Only the latest version moves, or a capped number of versions | Drafts show how documents and decisions evolved |
| Comments and review threads | Left in the source or flattened into the file | Reviewer feedback is a record of judgment and approvals |
| Departed users' folders | Owner account deprovisioned before migration | Years of a former employee's work product |
| Trash and deleted-items areas | Excluded from scope | Sometimes the only copy of removed material |
| Shared links and permission history | Rebuilt or dropped | Shows who handled which client work |
| Long path names and unsupported file types | Skipped with an error log | Silent gaps in the folder tree |
| Archived or cold folders | Left out to shorten the cutover | Often the oldest and deepest history |
When to raise it with the owner
The window is narrow because source subscriptions end soon after cutover.
| Moment | Question for the owner or IT lead | Evidence to ask for |
|---|---|---|
| Statement of work | What is in and out of scope: versions, trash, departed users? | The scope list |
| Pilot migration | Did the error report show skipped files or truncated history? | The pilot error log |
| Pre-cutover | When does the Box or Dropbox contract end, and is a full archive planned? | The renewal or end date |
| Account cleanup | Are departed users' accounts still intact? | A list of inactive accounts with departure years |
| Close-out | Who decides what happens to the leftover archive? | A named decision-maker |
How to tell a file share is worth a conversation
- The company has 50+ full-time employees at peak (contractors excluded).
- It has used the platform for several years, with archived folders still present.
- Folders cover client work, operations, finance and engineering, not just a single department.
- Someone can still run an admin-level export before the contract ends.
- The files are the company's own work, not mainly its clients' property.
The who qualifies page holds the complete baseline. If the same client is also leaving other platforms, the notes on Google Workspace mail history and Jira and Confluence cloud migrations cover the neighboring systems.
Common mistakes in scoping the move
| Mistake | Why it hurts | Fix |
|---|---|---|
| Migrating only active users | Former employees' folders vanish when their accounts close | List inactive accounts and decide each one in writing |
| Assuming "all files" means all versions | Only the latest version may arrive | Test one folder with heavy revision history in the pilot |
| Ignoring the pilot error log | Skipped files stay invisible until the source is gone | Review skipped items with the owner before cutover |
| Cancelling the source on cutover day | No fallback if gaps appear | Agree a short overlap period with the client |
| Treating archives as clutter | Oldest folders carry the deepest history | Ask who owns each archive and whether it is the only copy |
Illustrative: a fictional 120-person engineering firm moves from Box to SharePoint over a weekend. The pilot log shows several thousand skipped items under departed project managers. Because the MSP flagged it at the pilot stage, the owner keeps the Box account one more quarter and runs an admin export first.
What to say
The introduction email builder helps you prepare an owner-approved message.
What the partner does and does not do
- You raise the question at scoping and, only with the owner's approval, introduce the company by referral link or referral form.
- SourceX checks fit: headcount at peak, years of history, which systems exist and who owns the files.
- The company builds its own inventory of folders, archives and export options.
- The company and SourceX agree price and terms; buyers see the opportunity after that.
- Delivery happens only after signature and the company's authorization, with redaction rules agreed first.
- Your reward follows once SourceX has received payment.
You never open, copy or describe client files. Note that file shares often contain material owned by the company's customers, which needs consent before licensing.
Rewards for Microsoft partners
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from the company's proceeds. Read the program terms and check any Microsoft partner-program or client-contract rules before accepting fees. This is general information, not legal, tax or financial advice.
When to leave it alone
- The Box or Dropbox account is already closed and nothing was archived.
- The share holds mainly an agency customer's files and no consent exists.
- The folders are mostly personal or health information without a clear licensing basis.
- The migration is for a team that has only a few years of light usage.
For the broader pattern, see the managed service provider referral guide and the CRM cleanup note.
Next step
Add "version history, trash and departed users: in or out of scope?" to your SOW template. When a client looks like a fit, register as a partner and introduce them, or point the owner to sourcex.si/apply.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Does Box version history always transfer to SharePoint?
Not always. Some tools move only the latest version, others move a limited number, and results depend on plan tiers and settings. Run a pilot, read the error report and write down what the final scope includes, so the owner knows what will not exist after cutover.
What happens to a departed employee's Dropbox folder?
It depends on how the account was handled. If the account was deleted without transferring ownership, its content may be gone or sitting in a recoverable state for a limited time. Ask IT which inactive accounts still exist before decommissioning anything.
Can I tell a client to keep Box open just for a licensing review?
Keeping a source account alive costs money, so frame it as a decision for the owner. A short extension or a full archive export may be reasonable if the history looks substantial. The owner weighs the cost against the value of the records.
Is a file server of contracts and SOPs useful to AI buyers?
It can be. Buyers value connected operational records with outcomes, and document trails showing drafts, approvals and revisions are part of that. Value depends on breadth, history and rights, and SourceX assesses it after the company completes an inventory.
Do I need access to the files to make an introduction?
No. Partners give basic fit information only, such as company size, years of operation and the systems in use. You never export, upload or describe confidential files; the company works directly with SourceX.
How long does the process take after the introduction?
There is no fixed timeline. Once a company is deal-ready, buyers typically respond within about two weeks. A company that signs is typically paid within about 60 days of invoicing once the buyer selects the data.
Related pages
- Which US businesses are a fit for a SourceX data licensing introduction
- Google Workspace to Microsoft 365 migration: what old mail gets left behind
- Jira and Confluence cloud migration: what happens to old projects and spaces
- Prepare an owner-approved company introduction email
- Referral opportunities for managed service providers
- CRM data cleanup before migration: what to fix, what to keep, and what to assess first
Free resources
- Cash flow calculator — A 12-month cash forecast with shortfalls highlighted.
- Referral earnings calculator — Hypothetical partner earnings with the per-company cap.
- Cash conversion cycle calculator — DIO, DSO, DPO and the cash conversion cycle.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment