Skip to main content

How to Migrate from Box to SharePoint or OneDrive — Enterprise Cloud Migration with RcloneView

· 4 min read
Tayson
Senior Engineer

Your company has decided to consolidate on Microsoft 365. Step one: migrate all those files from Box to SharePoint and OneDrive. Step two: don't lose anything in the process.

Box has been a staple for enterprise file sharing, but many organizations are consolidating their cloud ecosystems around Microsoft 365. Migrating from Box to SharePoint Online or OneDrive for Business is a significant project — especially when you're dealing with years of accumulated data, complex folder structures, and shared workspaces. RcloneView makes this manageable.

RcloneView app preview

Manage & Sync All Clouds in One Place

RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.

  • One-click jobs: Copy · Sync · Compare
  • Schedulers & history for reliable automation
  • Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
WindowsmacOSLinux
Get Started Free →

Free core features. Plus automations available.

Migration Planning

Assess your Box environment

Before migrating, inventory what you have:

  • Personal folders → Migrate to individual OneDrive accounts.
  • Shared folders/workspaces → Migrate to SharePoint document libraries.
  • Archived data → Consider moving to cheaper storage (S3, B2) instead of SharePoint.
  • Total data volume — Determines timeline and approach.

Destination mapping

Box SourceMicrosoft 365 Destination
My FilesOneDrive for Business
Shared FoldersSharePoint Team Sites
Department FoldersSharePoint Document Libraries
Archive/Cold DataOneDrive or Azure Blob Storage

Step-by-Step Migration

1) Add Box and Microsoft remotes

Connect both services in RcloneView:

Add Box and SharePoint remotes

For SharePoint, add it as a OneDrive Business remote and specify the SharePoint site URL.

2) Browse and compare

Open Box on the left and SharePoint/OneDrive on the right:

Browse Box and SharePoint side by side

3) Transfer in phases

Don't try to migrate everything at once. Prioritize:

Phase 1: Active projects — Files people need daily. Phase 2: Shared workspaces — Team folders and collaboration spaces. Phase 3: Archive — Old projects and historical data.

4) Run Copy jobs

Create Copy jobs for each phase:

Run Box to SharePoint migration job

5) Verify each phase

After each phase, compare source and destination:

Verify Box to SharePoint migration

Handling Limitations

File name restrictions

SharePoint/OneDrive has stricter naming rules than Box:

  • Characters not allowed: " * : < > ? / \ |
  • File names can't start or end with spaces.
  • Maximum path length: 400 characters.

Rclone automatically handles many of these conversions during transfer.

Box Notes

Box Notes are proprietary and don't have a direct equivalent in Microsoft 365. They'll need to be exported as PDFs or copied manually into OneNote/Word.

Permissions and sharing

RcloneView transfers files but not sharing permissions. After migration, you'll need to set up sharing on SharePoint/OneDrive. Plan this as a separate step.

Rate limits

Both Box and SharePoint have API rate limits:

  • Box: Varies by plan (typically 10–20 requests/second).
  • SharePoint: Microsoft throttles based on usage patterns.

RcloneView respects these limits. For large migrations, schedule transfers during off-hours and use retry (v1.3).

Keep Box and SharePoint in Sync During Transition

Not everyone will switch on the same day. Schedule syncs to keep both platforms current:

Schedule sync during Box to SharePoint transition

This gives your team time to transition gradually without data gaps.

Monitor Large Transfers

Enterprise migrations involve terabytes. Monitor progress:

Monitor Box to SharePoint migration

Batch Jobs for Migration Workflow

Use v1.3 Batch Jobs to automate the entire migration sequence:

  1. Copy Box → SharePoint (active projects).
  2. Copy Box → OneDrive (personal files).
  3. Compare Box vs SharePoint to verify.
  4. Send Slack notification when complete.

Post-Migration

  1. Verify all files — Run a final Folder Comparison.
  2. Set up SharePoint permissions — Recreate sharing structures.
  3. Train your team — Help users find their files in the new location.
  4. Monitor for 30 days — Keep Box active as a fallback.
  5. Decommission Box — Cancel after confirming everything is stable.

Getting Started

  1. Download RcloneView from rcloneview.com.
  2. Add Box and SharePoint/OneDrive as remotes.
  3. Plan your migration phases.
  4. Run Copy jobs for each phase.
  5. Verify with Folder Comparison after each phase.
  6. Schedule syncs during the transition period.

Enterprise migration doesn't have to mean enterprise complexity.


Related Guides:

Supported Cloud Providers

Local Files
WebDAV
FTP
SFTP
HTTP
SMB / CIFS
Google Drive
Google Photos
Google Cloud Storage
OneDrive
Dropbox
Box
MS Azure Blob
MS File Storage
S3 Compatible
Amazon S3
pCloud
Wasabi
Mega
Backblaze B2
Cloudflare R2
Alibaba OSS
Ceph
Swift (OpenStack)
IBM Cloud Object Storage
Oracle Cloud Object Storage
IDrive e2
MinIO
Storj
DigitalOcean Spaces