To migrate from Box to OneDrive, you move your files, folders, and shared content from Box into Microsoft OneDrive and SharePoint, ideally with permissions, versions, and metadata intact. Done right, it follows a clear sequence: assess your data, plan the mapping, remediate issues, migrate in waves, then validate and onboard users. This guide shows you exactly how to migrate from Box to OneDrive step by step, covers the challenges that trip teams up, and explains how to move without losing data or disrupting work.
Organizations move from Box to OneDrive for good reasons: to consolidate onto Microsoft 365, cut duplicate storage and licensing costs, tighten security and compliance, and get ready for AI tools like Copilot that work best when content lives in the Microsoft cloud. The migration itself is more than a file copy. Box and OneDrive model content, sharing, and permissions differently, so a careful plan is what separates a smooth cutover from weeks of cleanup. Here is how to do it properly.
Why Migrate from Box to OneDrive?
Before the how, it helps to be clear on the why, because your reasons shape the plan. The most common drivers we see are:
- Microsoft 365 consolidation. If your organization already runs Microsoft 365, keeping files in Box means paying for and managing two ecosystems. Moving to OneDrive consolidates storage where your email, Teams, and documents already live.
- Licensing and cost savings. Retiring Box removes a duplicate subscription and simplifies licensing, which is often the fastest financial win of the whole project.
- Security and compliance. OneDrive and SharePoint bring Microsoft Purview governance, sensitivity labels, and audit trails into one place, which matters most for regulated industries.
- Copilot and AI readiness. AI tools work best when content sits in the Microsoft graph. Moving off Box is often a prerequisite for getting value from Microsoft Copilot.
- Mergers and acquisitions. When companies combine, standardizing on one platform removes friction, and Microsoft 365 is frequently the chosen standard.
Whatever the driver, a Box to OneDrive migration is really the first move in a wider box to Microsoft 365 migration, so it usually sits inside a broader Microsoft 365 migration and pays to plan with the whole environment in mind.
Box vs OneDrive: A Quick Comparison
Understanding how the two platforms differ is the key to a clean migration, because the gaps between them are exactly where content and permissions can break. Here is the box vs onedrive picture at a glance.
| Factor | Box | OneDrive and SharePoint |
| Ecosystem | Standalone cloud content platform | Native part of Microsoft 365 |
| Personal vs shared storage | All content in Box | Personal files in OneDrive, shared content in SharePoint |
| Permissions model | Box roles and collaborations | Microsoft Entra identities and Microsoft 365 groups |
| Special content | Box Notes, Box-native links | Converted to Office or Loop equivalents |
| Integration with Microsoft apps | Add-on integrations | Built in across Teams, Outlook, and Office |
| AI and Copilot | Limited | Native Copilot support |
The most important takeaway is that Box keeps everything in one place, while Microsoft splits content between personal OneDrive and shared SharePoint. Deciding what goes where is a core planning step, covered below.
Box to OneDrive Migration Challenges
Most migration pain comes from a handful of predictable issues. Knowing them upfront is how you avoid them.
- Permissions and sharing. Box collaborations do not map one to one onto Microsoft permissions, and manual copying loses them entirely. Mapping roles deliberately is essential.
- Personal vs shared content. Sending shared team content into a personal OneDrive is a common mistake. Shared content usually belongs in SharePoint.
- File versions and metadata. Older versions, timestamps, and metadata are easy to lose if the migration is not configured to preserve them.
- External shares. Links shared with people outside your organization need to be identified and recreated, or access breaks on cutover.
- Box Notes and special files. Box Notes and Box-native links do not exist in Microsoft 365 and must be converted.
- Scale and API limits. Large data volumes hit throttling and API limits, so big migrations need to be planned in waves rather than run all at once.
None of these are reasons to avoid the move. They are the reasons to plan it and, for larger or regulated environments, to bring in experienced help.
Before You Migrate: Planning and Assessment
A successful Box to OneDrive migration is mostly won before a single file moves. Spend the time here.
- Run a pre-migration assessment. Inventory how much data you have, how it is structured, who owns it, how it is shared, and what is stale enough to leave behind. You cannot plan what you have not measured.
- Decide your content mapping. Determine what goes to personal OneDrive versus shared SharePoint sites or Teams, and design the destination structure before you move anything.
- Map identities and permissions. Match Box users and collaborations to Microsoft Entra identities and groups, and decide how external sharing will be handled.
- Build a communication plan. Tell users what is changing, when, and what they need to do. Adoption depends on it.
- Choose a pilot group. Start with a small, representative set of users to validate the approach before the full rollout.
How to Migrate from Box to OneDrive: Step by Step
Here are the core box to onedrive migration steps to move files from Box to OneDrive. The exact tooling varies, but the sequence is consistent.
Step 1: Assess and clean up your Box data
Review what is in Box, archive or delete what you do not need, and resolve obvious issues like unsupported characters in file names. Migrating less, cleaner data is faster and cheaper.
Step 2: Design the destination in Microsoft 365
Set up the OneDrive and SharePoint structure to receive the content, including the SharePoint sites or Teams that shared folders will map to. Provision licenses and confirm storage.
Step 3: Map users and permissions
Match every Box user and collaboration to the right Microsoft identity and permission, and document how external shares will be recreated. This mapping is the backbone of the migration.
Step 4: Choose your migration tool
Select how you will move the data. Microsoft offers Migration Manager, a native tool in the SharePoint admin center that supports Box as a source, and there are third-party platforms with additional features. The right choice depends on your scale, permission complexity, and compliance needs.
Step 5: Run a pilot migration
Migrate the pilot group, then check that files, versions, permissions, and shared links came across correctly. Fix anything the pilot surfaces before you scale.
Step 6: Migrate in waves
Move the rest of the organization in planned batches, usually by department or site, to stay within API limits and keep disruption low. Many teams run the bulk transfer over evenings or weekends.
Step 7: Validate and reconcile
Confirm that content, versions, metadata, and permissions match the source, and reconcile any gaps. Validation is what lets you decommission Box with confidence.
Step 8: Onboard users and decommission Box
Point users to their new content, provide short training, monitor for issues, then retire Box once everything is confirmed. This is where the licensing savings become real.
OneDrive vs SharePoint: Where Should Your Content Go?
This decision deserves its own step because getting it wrong creates rework. Personal, individual files belong in a user’s OneDrive. Shared team content, project folders, and departmental libraries belong in SharePoint or the SharePoint site behind a Team. Sending shared content into personal OneDrive scatters ownership and breaks collaboration, so plan a proper box to sharepoint migration for anything that multiple people use. Getting this mapping right upfront is one of the biggest differences between a clean result and a messy one.
Handling Permissions and Roles: Best Practices
Permissions are where migrations most often go wrong, so these box to onedrive migration best practices deserve real attention and should be treated as a first-class part of the plan. Map Box roles to Microsoft permissions deliberately rather than assuming they match, because the models are different. Identify every external share and decide in advance whether to recreate, restrict, or retire it. Use automation to apply permissions at scale rather than by hand, which is both faster and less error prone. And validate a sample of permissions after each wave, because a file that migrated with the wrong access is worse than one that did not migrate at all. As a starting point, here is how common Box roles typically map to Microsoft permissions. Confirm each mapping against your own environment before you migrate.
| Box role | Typical Microsoft 365 equivalent |
| Owner or Co-owner | Site owner or Full control |
| Editor | Edit or Contribute |
| Viewer or Previewer | Read |
| Uploader | Contribute with add-only rights |
| External collaborator | Guest access through Microsoft Entra B2B |
Treating the table as a draft to validate, not a rule to apply blindly, is what keeps access correct after cutover.
Box to OneDrive Migration Tools
You have three broad options for the actual move. Microsoft Migration Manager is the native, no extra cost tool built into the SharePoint admin center, and it supports Box along with other cloud sources, which makes it a strong fit for straightforward migrations. Third-party migration platforms add features like richer permission mapping, reporting, and support for complex edge cases, which can be worth it at scale. And a managed migration service handles the whole project for you, from assessment through validation, which is the right choice for large, regulated, or business-critical environments where downtime and data loss are not acceptable.
The heavier your permissions, compliance, and volume, the more a guided approach pays for itself.
How Long Does a Box to OneDrive Migration Take?
It depends on data volume, the number of users, and how complex your permissions and external shares are. A small team can move in days, while a large enterprise with terabytes of data and thousands of users runs over several weeks in planned waves. The two biggest factors are how clean your source data is and how much permission remapping is required, which is exactly why the assessment step matters so much. A realistic plan with pilots and waves is faster in practice than rushing a single big cutover that has to be redone.
Case Study: A 55 TB Box to OneDrive Migration Across 11,000 Users
A US based large data center provider needed to move 55 TB of content off Box and onto Microsoft 365 for 11,000 users, without disrupting daily work. The hard part was scale and permission complexity, with a large volume of shared folders and external collaborations that all had to land in the right OneDrive and SharePoint locations with access intact.
TrnDigital ran a full pre-migration assessment to map the data and ownership, matched every user and collaboration to the correct Microsoft identity and permission, migrated in planned waves behind a pilot, and validated content, versions, and permissions after each wave before moving on. The migration ran seamlessly and drove strong adoption, and the client noted they could not have done it themselves. It is exactly the kind of large, permission-heavy move where a managed approach pays for itself, because the cost of lost data or downtime at that scale would have dwarfed the cost of doing it right.
How TrnDigital Helps with Box to OneDrive Migration
TrnDigital is a Microsoft focused consultancy that runs Box to OneDrive migrations end to end, from assessment and content mapping through permissions, waves, validation, and user onboarding, so nothing important is lost and business keeps running. We help SMB, mid-market, and regulated organizations, including in biotech, life sciences, and healthcare, move to Microsoft 365 with governance and compliance built in.
The track record backs it up. Beyond the 55 TB migration in the case study above, a US based retail enterprise cut licensing costs by 25 percent and improved audit readiness after consolidating onto Microsoft 365 and Azure managed services, and a US based insurance enterprise cut processing time by 50 percent with a zero-downtime deployment on Microsoft 365. Different scales, the same disciplined delivery.
Planning a move off Box? Explore our Box to OneDrive migration services, or book a free consultation with our migration consulting team to assess your data and map a plan, with no obligation to proceed.
Frequently Asked Questions
1. How do I migrate from Box to OneDrive?
Assess and clean your Box data, design the destination in Microsoft 365, map users and permissions, choose a migration tool such as Microsoft Migration Manager, run a pilot, migrate in waves, validate the results, then onboard users and decommission Box. Planning the mapping and permissions before you move is the key to doing it without data loss.
2. Can I transfer files from Box to OneDrive for free?
Yes, Microsoft Migration Manager is included with Microsoft 365 and supports Box as a source, so small migrations can be done at no extra tool cost. Larger or more complex migrations often use third-party tools or a managed service to preserve permissions, versions, and external shares reliably.
3. Will my file permissions transfer from Box to OneDrive?
They can, but only if the migration is configured to map them. Box collaborations do not match Microsoft permissions one to one, and manual copying loses them entirely. Deliberate permission mapping and validation are essential, which is why permissions are the most common source of migration problems.
4. Should shared content go to OneDrive or SharePoint?
Personal files belong in a user’s OneDrive, while shared team content, project folders, and departmental libraries belong in SharePoint or the site behind a Team. Sending shared content into personal OneDrive breaks collaboration and scatters ownership, so plan that mapping before you migrate.
5. What does not transfer from Box to OneDrive?
Common gaps include older file versions, some metadata, external sharing links, and Box-native items like Box Notes, which have no direct Microsoft equivalent. A good migration plan accounts for each of these by preserving, converting, or recreating them rather than losing them.
6. How long does a Box to OneDrive migration take?
A small team can migrate in a few days, while a large enterprise with terabytes of data and thousands of users runs over several weeks in waves. Data volume, user count, and permission complexity are the main factors, and a clean assessment shortens the timeline.
7. Do I need a partner to migrate from Box to OneDrive?
Not for small, simple migrations, but most mid-market and regulated organizations benefit from one. A partner handles the assessment, permission mapping, waves, and validation, which protects against data loss and downtime and frees your team to keep working during the move.
Conclusion
Learning how to migrate from Box to OneDrive is mostly about treating it as a planned project rather than a file copy. Assess your data, decide what goes to OneDrive versus SharePoint, map permissions deliberately, migrate in waves, and validate before you decommission Box. Do that, and you consolidate onto Microsoft 365, cut duplicate costs, tighten security, and set the stage for Copilot, all without losing data or disrupting work. If you want a Microsoft focused partner to plan and run it, TrnDigital can deliver a Box to OneDrive migration that is smooth, governed, and built to last.
