Box to OneDrive migration: Step-by-step guide with ShareGate

It’s official: Your organization is moving from Box to OneDrive. Microsoft gives general guidance for this, but those who’ve seen a cross-platform data migration know it won’t be simple. Permissions don’t map cleanly, content models are different, and the native tools only get you so far.

ShareGate Migrate takes the work off your plate by handling the tricky parts of a Box to OneDrive migration. And once you’re set up, use ShareGate Protect to continuously govern your environment via visibility, cleanup, and Copilot readiness. In this guide, we’ll explain how to transfer files from Box to OneDrive, which native migration tools help, and when to let a solution manage it for you.

Common challenges in Box to OneDrive migrations

To understand the challenges of migration, we need to understand the basic differences between the platforms.

Here’s a quick breakdown:

Platform and content model differences

Box and Microsoft 365 use different collaboration models. This can make it unclear how the content should migrate and organize. 

• Ownership and collaboration models: Box uses file-based ownership while Microsoft 365 uses team-based ownership. Align these by mapping content to Teams or SharePoint sites.
• Permission model differences: Be sure to review folder-level permissions and adjust to match the workspace and group-based access.
• Tags and metadata: Use metadata to enhance organization where appropriate, alongside folder structures.
• Embedded links and internal references: Prevent any issues after migration by reviewing and updating any broken links.

Identity and account dependencies

What happens to files owned by inactive users? Identity mismatches lead to broken permissions if you don’t address them before migration.

• Inactive or deprovisioned users: Avoid any orphaned content by making sure file ownership is reassigned to active users.
• Email and domain mismatches: Validate and map user accounts to prevent any access problems.
• External collaborators: Review external sharing to make sure users only have the access they need.

Scale and API-related constraints

Platform limits can impact your migration performance and success as you scale.

• API throttling: Schedule your migration workloads in phases or batches to account for rate limits.
• Large data volumes or high-activity accounts: Prioritize based on business impact, dependencies, and data volume.
• File name, path length, and character restrictions: Research if the naming conventions and character count will meet Microsoft 365 migration requirements.

Visibility and validation challenges

You’ll need ongoing visibility to make sure the migration is complete and accurate.

• Migration completeness and item counts: Use the automated reporting to check if all content successfully migrated over.
• Permission validation at scale: Double-check all permission structures using tools rather than relying on manual review.
• Monitoring migration progress: Track progress and spot any issues early by using reporting dashboards.

Evaluating Microsoft’s native migration tooling

Microsoft uses a native Box migration tool called Migration Manager, located in the Microsoft 365 admin center. It’s a free, built-in option for handling basic migration tasks. 

But as your migration grows in complexity, you may run into a few constraints:

• Limited permission restructuring: Migration Manager uses predefined mappings, with identity mapping options to align users and permissions.
• Less control over sequencing: For large-scale migrations, it’s common to schedule the move in batches—by department, region, or content type. Migration Manager offers less detailed control over this type of bulk sequencing due to its optimization for speed and automation.
• Handling complex ownership: Box environments rely on shared, collaborative content; OneDrive focuses on personal user storage. When migrating, native tools may struggle to map exact matches from Box to OneDrive. This can lead to permission mismatches if identity mapping and access controls aren’t configured properly.
• Reporting depth: Migration Manager does offer basic scanning and performance reports, but it lacks the details most IT admins need for troubleshooting errors, like real-time performance insights.

A step-by-step guide for migrating files from Box to OneDrive using ShareGate

Using a third-party Box to OneDrive tool like ShareGate Migrate can streamline your migration process. Here’s a step-by-step guide to do a Box to OneDrive migration using ShareGate. Follow along with this YouTube video. For the detailed import workflow, use ShareGate’s Box to OneDrive PowerShell documentation.

1. Migration planning

Check your current Box environment before deciding what’s moving and where it’s heading. Look for any outdated or redundant content to leave behind during this step. Limit your migration downtime by starting early on a user communication plan that keeps your team up to date. 

2. Remediate

Clean up your source environment before you migrate. Any invalid or inactive user accounts could cause errors during the migration. It’s much easier to fix things in Box before you start the move. 

3. Decide what content goes where

Not everything in Box will have a one-to-one destination in OneDrive. Decide what content belongs in a user’s personal OneDrive library versus what belongs in a shared Team or SharePoint site.

4. Prepare your OneDrive environment

Prepare your destination by provisioning and licensing all users in Microsoft 365. Then, confirm the identity mapping between Box and Entra ID so permissions apply correctly. Stay compliant by double-checking this step to prevent any data loss before migration. 

5. Migrate

The migration itself is a multi-stage process:

• Start with a small group of test users to find any mapping issues.
• Based on this pilot, refine your settings before moving forward.
• Start the bulk migration for all users. This heavy lift should run smoothly if validated during testing, but expect edge cases.
• Make a copy to capture any new or changed content since the first migration.
• After a final delta migration, perform the cutover. This is when users officially switch to working in OneDrive.

6. User onboarding and change management

Make sure everyone is trained on how to use OneDrive. Then, prepare your help desk for common questions. 

Use ShareGate’s automated reporting features to confirm the migration went as planned. These reports give visibility into errors, user activity, and migration status—helping teams identify and fix issues easily. Reporting also helps you stay compliant by keeping track of all actions taken and requirements met.

‍

Best practices for handling roles and permissions during migration

Instead of focusing on long-term governance configuration, we’ll explain how to map and validate during migration. Here are a few best practices to keep in mind. 

Map roles deliberately, not by assumption

Don’t assume that Box roles will carry over perfectly in OneDrive. Several Box roles don’t have a direct match in Microsoft 365. Relying on these default settings can result in broken access or oversharing. By mapping out each role, users keep the exact access needed to do their jobs. A tool like ShareGate helps make that custom permission mapping possible by automatically matching groups, users, and permission levels during migration. 

Address external access in your migration plan

Native tools don’t migrate external sharing links from Box. Decide exactly how your organization will handle external collaborators going forward. Will you reinvite external collaborators as guests in your Entra ID? Will you use anonymous sharing links in OneDrive? Establish this policy early to prevent disruptions for your external partners.

Use automation to handle permissions at scale

Checking permissions by hand for thousands of files is prone to human error and time-consuming. Use a tool that can automate this, like ShareGate’s Permissions Matrix Report. To save time, you can also import from Box to OneDrive with PowerShell and manage Microsoft 365 with PowerShell. Get a complete overview of who has access to what, so you can confirm your permissions before and after the migration.

Executing a well-structured Box to OneDrive migration

A Box to OneDrive migration forces you to rethink how your organization collaborates.

If your organization needs more control over permission mapping and migration reporting, ShareGate Migrate gives you structured tools for complicated transitions. IT teams can define exact access rules, verify content, and manage user adoption all from one place.

If you’re ready to see how ShareGate Migrate can support your organization, book a demo today.

‍