Download PicBackMan and start free, then upgrade to annual or lifetime plan as per your needs. Join 100,000+ users who trust PicBackMan for keeping their precious memories safe in multiple online accounts.
“Your pictures are scattered. PicBackMan helps you bring order to your digital memories.”
Need to move your files from Box to SharePoint? You're not alone. Many organizations are making this transition to take advantage of SharePoint's robust features and integration with Microsoft 365. Whether you're handling a small project or a company-wide migration, I'll walk you through four straightforward methods to transfer your content efficiently.
In this guide, I'll cover manual downloads and uploads, using the Microsoft Migration Tool, third-party migration services, and sync tools that can help you move your files with minimal hassle. Let's get started with these practical solutions!
The most direct approach to moving files from Box to SharePoint is the manual download and upload method. This works best for smaller file collections or when you need to be selective about what you transfer.
For larger files, you might notice the upload takes longer. SharePoint shows a progress indicator, so you can track the status of your uploads.
When downloading multiple files from Box, use the "Download as ZIP" option to keep folders intact. This helps maintain your organization structure when uploading to SharePoint.
For SharePoint uploads, you can drag and drop files directly into the browser window instead of using the upload button. This works well for multiple files and can save you time.
Microsoft offers a free migration tool specifically designed to help transfer content to SharePoint Online. While it doesn't have direct Box integration, you can use it after downloading your Box content to your computer.
The tool will analyze your content, migrate the files, and provide a summary report when finished. You can track the progress in real-time through the tool's interface.
The SharePoint Migration Tool works best with a stable internet connection. For large migrations, consider running the tool during off-hours when network traffic is lower. You can also adjust the number of simultaneous uploads in the tool's settings to match your network capabilities.
For larger organizations or complex migrations, third-party tools offer direct Box to SharePoint migration capabilities. These services can save time and preserve more metadata during the transfer process.
While each service has its own specific workflow, the general process follows these steps:
Third-party tools typically come with licensing costs, so you'll need to evaluate whether the benefits justify the expense for your situation. Many providers offer free trials or demo migrations, which can help you assess their effectiveness before committing.
| Feature | AvePoint | ShareGate | CloudFastPath |
|---|---|---|---|
| Direct Box to SharePoint migration | Yes | Yes | Yes |
| Preserves version history | Yes | Yes | Yes |
| Permission mapping | Advanced | Basic | Advanced |
| Incremental migration | Yes | Yes | Yes |
| Reporting capabilities | Comprehensive | Detailed | Advanced analytics |
| Pricing model | Quote-based | Per user/month | Project-based |
If you're looking for a middle-ground solution that's more efficient than manual transfers but doesn't require specialized migration services, sync tools can be a practical option.
Sync tools create a connection between your Box and SharePoint accounts, allowing files to be copied from one platform to the other. They typically work by:
While not a direct Box-to-SharePoint solution, you can use the OneDrive sync client in combination with the Box sync client to create a bridge between the two services:
For users comfortable with command-line tools, Rclone offers a powerful way to sync between cloud services:
When using sync tools, start with smaller folders to test the process before attempting to sync your entire Box account. This helps identify any potential issues on a smaller scale.
Also, be mindful of file path length limitations in Windows if you're using sync clients. SharePoint has a maximum URL length of 400 characters, so deeply nested folder structures might cause problems during syncing.
To help you decide which method is best for your specific situation, here's a comparison of all four approaches:
| Factor | Manual Transfer | Migration Tool | Third-Party Services | Sync Tools |
|---|---|---|---|---|
| Cost | Free | Free | $$$ (Subscription/License) | $ (Some free options) |
| Technical expertise needed | Low | Medium | Medium | Medium-High |
| Best for file volume | Small (GB) | Medium (100s GB) | Large (TB+) | Medium (100s GB) |
| Preserves metadata | No | Partial | Yes | Minimal |
| Preserves permissions | No | No | Yes | No |
| Time investment | High | Medium | Low | Medium |
Regardless of which method you choose, proper preparation will make your migration smoother and more successful. Here are some essential steps to take before starting the transfer:
After completing your migration from Box to SharePoint, there are several important tasks to ensure everything is working properly:
Even with careful planning, you might encounter some obstacles during your Box to SharePoint migration. Here are some common challenges and how to address them:
Challenge: SharePoint has URL length limitations (400 characters), which can cause issues with deeply nested folders.
Solution: Flatten your folder structure where possible, or break up deeply nested content into separate document libraries.
Challenge: Box and SharePoint have different permission models, making direct mapping difficult.
Solution: Document your Box permission structure before migration, then recreate a similar structure in SharePoint using its permission levels and groups.
Challenge: SharePoint doesn't allow certain characters in filenames that Box permits.
Solution: Scan for problematic filenames before migration and rename files to remove characters like # % & * : ? / { | } ~
Challenge: Large files may timeout during upload or download.
Solution: Use methods that support chunked uploads, like third-party tools or the SharePoint Migration Tool, which can resume interrupted transfers.
Challenge: Internal links to Box content will break after migration.
Solution: Use SharePoint's link tracking features to create new shareable links, and consider using a redirect solution for frequently accessed Box links.
Videos are precious memories and all of us never want to lose them to hard disk crashes or missing drives. PicBackMan is the easiest and simplest way to keep your videos safely backed up in one or more online accounts.
Simply download PicBackMan (it's free!), register your account, connect to your online store and tell PicBackMan where your videos are - PicBackMan does the rest, automatically. It bulk uploads all videos and keeps looking for new ones and uploads those too. You don't have to ever touch it.
Transferring files from Box to SharePoint doesn't have to be complicated. The four methods we've covered—manual transfer, using Microsoft's Migration Tool, third-party services, and sync tools—offer options for every situation, from small personal migrations to enterprise-level transfers.
For small amounts of data, manual transfers or sync tools may be sufficient. For medium-sized migrations, Microsoft's SharePoint Migration Tool provides a free and effective solution. And for large, complex migrations with specific requirements for preserving metadata and permissions, third-party migration services offer the most comprehensive approach.
Whichever method you choose, proper planning and testing are essential for success. Take time to audit your content, design your SharePoint structure, and verify your migration results. With the right approach, you can enjoy a smooth transition to SharePoint and take full advantage of its collaboration features and integration with Microsoft 365.
Most migration methods don't preserve Box comments or annotations. Third-party migration services offer the best chance of preserving this metadata, but even they have limitations. Consider extracting important comments as separate documents if they contain critical information.
Migration time varies greatly depending on the volume of data, method used, and network conditions. Small migrations (under 10GB) might take hours, while enterprise migrations with terabytes of data could take weeks. Plan for approximately 2-4GB per hour for manual methods, and 5-10GB per hour for specialized tools under optimal conditions.
No, Box shared links will not work after migration to SharePoint. You'll need to create new SharePoint sharing links and distribute them to replace the Box links. Some third-party tools can generate reports of existing Box shared links to help you identify what needs to be recreated.
Yes, users can continue working in Box during migration planning and execution. However, consider implementing a "freeze period" just before final migration to prevent changes to files that might not get captured. Alternatively, use incremental migration features in third-party tools to capture ongoing changes.
Yes, you'll need administrative access to both platforms. For Box, you need admin privileges to access all content. For SharePoint, you need site collection admin rights to the destination sites. For third-party tools, you may need to create service accounts with appropriate permissions in both systems.