PLATFORM
Box Migration Tool
Leaving Box usually means moving everyone at once: hundreds of people, each with their own folders, plus folders shared between teams, Box Notes, older versions and sharing settings that people rely on. Doing that by hand, one account at a time, is where most Box moves stall.
MigrationFox lets a Box admin pick the people to move right in the source picker, sends each person to their own OneDrive or into a shared SharePoint library, and handles the Box-specific details (shared folders, Box Notes, versions, dates and sharing) along the way.
Moving Box to Microsoft 365? Read the step-by-step guide: Migrate Box to SharePoint and OneDrive.
Connect Box
Connect Box by signing in with your Box account (OAuth). A Box developer token also works.
Move a whole Box enterprise, not one account at a time
When the account you connect is a Box admin (or a co-admin with the “Manage users” permission), the source picker offers Browse other users’ Box in this enterprise. It lists everyone active in your enterprise along with the storage each person uses. Open a person to browse their folders as them.
This uses Box’s “as-user” access, and Box logs those actions as the admin acting for that user. If the connected account isn’t an admin, you see a clear message explaining why the option isn’t available.
Many people in one go
Tick the people you want (or Select all) in the source picker, and MigrationFox creates one migration per person. Then choose where they land:
- Each person to their own OneDrive: matched automatically by exact email, then by the same username before the @ (useful when your email domain is changing), then by the same display name. Only unique matches are used. You can change or skip any match, or import a CSV of
sourceEmail,destEmail. - Everyone into one shared SharePoint library: with a folder per person.
- Optional extra subfolder for everyone, such as “From Box”, so migrated content is easy to find.
Shared folders are copied once
In Box, the same folder can appear in many people’s accounts. Copying it from every one of them would create duplicates. MigrationFox copies a shared folder once, from its owner: in each person’s migration, folders that someone else shared with them are skipped, because the owner’s migration copies them. The picker labels these folders “shared by <name>” so you can see what will happen.
Sharing settings
Turn on Migrate permissions and Box folder collaborations are recreated on the destination folder, translated through your user mapping:
- Viewer / Previewer → read
- Editor, Uploader variants, Co-owner → edit
- Owner → edit (sharing can’t grant ownership in SharePoint or OneDrive)
Not yet supported: Box group collaborations (these are skipped and named in the job log so you can recreate them) and sharing set on individual files. Sharing is copied for folders only.
Box Notes become Word documents
Box Notes only open inside Box. When moving out of Box, MigrationFox converts each note to a Word document (.docx), keeping headings, bold, italic, underline and strikethrough, bulleted and numbered lists, checklists (☐ / ☑), tables, links, quotes and code blocks. Images in a note become a placeholder line such as “[Image: name]”, because the note file itself doesn’t contain the image.
Conversion is on by default; turn it off to keep the original .boxnote file. If a note can’t be read, you still get a Word file with its text.
Version history
Box keeps earlier versions of files on Business plans and above. With Copy version history turned on, earlier versions are uploaded oldest first, then the current file, so the version history in SharePoint or OneDrive contains each version’s content. You can set a per-file cap on the number of versions.
One limit: each earlier version’s date and “Modified by” show the time of the migration and the migration account. The current file keeps its original dates.
Dates and time zones
Files keep their Box Created and Modified dates (the file’s content dates). Folder dates are set again after all files have landed, because SharePoint resets a folder’s Modified date whenever a file is added to it.
Tip: SharePoint shows times in the site’s time zone (Site settings → Regional settings). A new site may default to Pacific time, so times can look hours off until you set the right zone.
Large files, long paths and filters
- Large files: uploads to Box over 20 MB use Box’s chunked upload. Downloads from Box stream through without being stored on disk.
- Long paths: file and folder names are cleaned up for SharePoint’s limits: illegal characters are replaced, and paths are fitted to SharePoint’s 400-character limit.
- Filters: developer folders (
node_modules,.git,.venvand similar) and OS junk files (Thumbs.db,.DS_Store) are skipped by default. You can also exclude file types and set a maximum file size.
Re-runs and cutover
People keep working in Box until cutover day. Re-run a migration with Incremental to replace only files that are newer in Box than at the destination. For files that already exist at the destination you can also choose Skip, Replace or Keep both.
Where Box content can go
Box to SharePoint and OneDrive
Send each person to their own OneDrive, or put everyone into a shared SharePoint library with a folder per person. See the Box to SharePoint and OneDrive guide.
Other destinations
Box content can also go to Google Drive, Dropbox, Amazon S3, Azure Blob, SFTP, or another Box enterprise.
Where it runs
On MigrationFox web, migrations run in our cloud and use credit. In MigrationFox for Windows, they run on your own PC with MigrationFox Pro.