The files appear in SharePoint, but a project owner cannot open a folder and a customer’s Box link still points to the old workspace. Another team notices that an important Box Note lost part of its content. These are separate migration problems. A transfer count cannot answer whether the right people can use the right documents in the new location.
For the Microsoft Migration Manager route, plan content coverage, destination structure and access as separate workstreams. This guide covers that route rather than every third-party migration tool. Use the wider data migration checklist and engineering scope to define requirements that the native copy does not satisfy.
Define the Box content you intend to move
Microsoft’s Box FAQ describes copying accessible files and folders within a Box user account. Items the user cannot access are excluded. The overview requires source credentials with Read access to every Box user account in scope. Build an account and folder inventory before treating a connected account as complete coverage.
Separate active team documents from personal working folders, historical records and content shared by outsiders. Record an owner for each scope decision. For any deliberately excluded content, keep its location and retention owner in the migration record. An exclusion should be a decision somebody can explain, not an item that disappeared between reports.
| Area | Documented Box route behavior | Recommended decision |
|---|---|---|
| Accessible files and folders | Copied into the configured destination | Reconcile against an agreed inventory |
| File history | Only the most recent version transfers | Handle required historical versions separately |
| Box Notes | Converted to Word with omitted elements | Review important notes for usable content |
| External sharing | Links and external collaborator sharing are not recreated | Approve destination access separately |
| Source content | Copied rather than deleted | Assign a later source-retirement decision |
Connect with the right administrative scope
Create the Box migration project from the Microsoft 365 admin center’s migration tools. The documented destination roles include Microsoft 365 Migration Administrator, SharePoint Administrator and Global Administrator. Microsoft recommends using the least privileged role suitable for the work. Confirm destination access and source coverage before authorizing the connection.
The Box overview describes signing in and adding the Microsoft 365 migration app to Box custom apps. Treat the connection as an administrative integration with an owner. Record which project uses it and who will remove unneeded access after acceptance. Do not confuse successful authorization with proof that every folder or account is accessible.
Assess the content before the first transfer
Scanning Box users is optional in Migration Manager. If a team skips the scan, it should not claim to have completed a preflight assessment. For a controlled rollout, scan representative and high-risk content, review the available reports and keep unresolved items visible before moving tasks into the migration list.
Microsoft’s unsupported-content documentation identifies restricted files, files beyond the supported size limit and excessive destination path lengths as general problems. Shortcut files are skipped in Box migrations. Box getting-started instruction files are also ignored. Do not replace these specific boundaries with a claim that every file format will migrate.
Box Notes convert to .docx documents. The conversion omits elements including File Preview, Table of Contents and Annotations. Select notes with those features for manual review. Opening a converted document is only the first check. Its owner should confirm that the remaining content still supports the original work.
Approve destination paths before tasks start
On User migrations, review the destination for each Box user task. A task needs a valid destination. Once the task starts, its destination cannot be changed for later delta syncs. For SharePoint, the documented destination selection includes the site URL, document library and optional folder. Make that mapping an approved input to the run.
Bulk destination uploads need their own coverage check. Microsoft notes that rows with blank destination paths are skipped during validation. A successful validation is therefore not proof that every planned task has a populated path. Compare the upload against the full account inventory and explicitly list any tasks still waiting for a destination.
Map identities and inspect permission changes
Complete identity mapping before migration. Map source users and groups to the intended Microsoft 365 identities. The permission settings documentation says folder permissions migrate by default. File permissions do not migrate by default, so destination files inherit the parent folder’s permissions unless file-level permission migration is enabled in project settings.
The role conversion also needs review. Microsoft maps Box Co-owner, Viewer Uploader, Previewer Uploader, Uploader and Editor to Can edit. Previewer and Viewer map to Can view. Those destination roles are not a promise that every source capability restriction survives unchanged. Test representative users against the actual destination behavior, especially where upload and viewing rights were intentionally different.
External sharing needs a separate workstream. The Box FAQ says external sharing links are not recreated and content is not automatically shared with external collaborators. Keep a reviewed list of intended external recipients and replacement links. Do not automatically reopen access merely because an old folder had guests.
Use incremental runs without reorganizing the destination
Migration Manager’s Box incremental feature compares source and destination timestamps and transfers new or modified files, with the newest versions determining transfer behavior. Microsoft describes this feature as always on. It is a file-transfer mechanism, not evidence that the two platforms share identical collaboration state.
Avoid renaming or rearranging migrated content before the final transfer. Microsoft warns that name and directory changes can be treated as new objects and cause duplicates, including duplicated folder trees. Agree the target structure before migration and keep users from reorganizing the landing area during the transfer sequence.
Permission-only changes also need attention. The general permission documentation says delta permissions transfer when the corresponding files transfer. Do not assume an unchanged document receives every later access change. Recheck important permissions at cutover and keep a separate remediation list for discrepancies.
Accept the migration using reports and real users
A Completed task can still contain item-level failures for unsupported files. Microsoft explicitly distinguishes task status from those failures. Reconcile source inventory, copied items, approved exclusions and unresolved errors. A clean-looking project dashboard does not replace the item review.
- Match every planned Box account to a completed or explicitly deferred task.
- Review item failures and identify an owner for each exception.
- Open representative documents and converted Box Notes.
- Test internal access with ordinary users rather than only administrators.
- Approve replacement external sharing and communicate the new working location.
- Complete the final transfer and document who can authorize source retirement.
The migration copies content and does not delete it from Box. Keep the original workspace available under an agreed operating policy until owners accept the destination. That is a recommended cutover control, not a guarantee of automatic rollback. If destination editing has begun, compare changes before deciding where users should resume work.
How Remqa helps with Box migration
Remqa engineers can plan source inventories, destination mapping, access tests and exception reconciliation around a Box migration. The work includes the operating handoff, not just initiating a copy. Use the migration services overview to scope the move and bring a representative folder set to the first review. If other workspaces are involved, compare the separate Google Drive to SharePoint migration guide rather than assuming the same conversion rules apply.