Skip to main content
This article is about Box Shuttle in the Admin Console. If you’re using legacy Box Shuttle, a standalone tool, see legacy migration guides.

Overview

Use a spreadsheet to map your source data to target data, or source collaborators to target collaborators. Download a template, fill in one row for each item, then upload the file. Use it when a job covers hundreds or thousands of items. After you select a source system, choose how to map on Map Data Settings:
  • Upload .XLSX file: Map directories in a spreadsheet
  • Map Data manually: Map each item in Box Shuttle
On Migration Settings, choose Migrate Data Only or Migrate Data and Permissions. If you choose Migrate Data and Permissions, you also choose how to map users and groups. That choice is separate from Map Data Settings. You can use a spreadsheet for data and map users and groups by hand, or the reverse.

Before you begin

Confirm the following before you start:
  • Your source system is set up in Box Shuttle. See Source system configuration.
  • The Box users you plan to migrate content into have accepted their invitations. You cannot transfer data to a Box account of a user who did not accept the invitation.

Download the template

Each source system needs different information to identify a location, so each has its own template. Always start from the template, so your columns match what Box Shuttle expects. On the Map Data Settings page, select Download formatted template. An XLSX file downloads to your machine.
Templates contain one or both of these sheets:
  • Locations, for content in an individual source account, such as a Dropbox or OneDrive user
  • Shared Locations, for content in a shared space, such as a Dropbox team folder, a SharePoint site, or a Windows drive
Your source system determines which sheets you get. A Dropbox template has both, because Dropbox has user accounts and team folders. A Windows template has only Shared Locations.

Fill out the spreadsheet

Each row maps one source location to one Box destination. Column names vary by source system, so check the header row of your template, but the pattern is always the same: identify the source location, then identify the Box target. Complete each sheet your template contains.

Locations

Enter the source account and the path you want to migrate, then the Box account and the path where that content lands. A Dropbox template uses Source Account Email, Source Path, Target Account Email, and Target Path.

Shared Locations

Identify the shared space instead of a source account, then enter the Box account and path as you would on Locations. For Dropbox, use the team folder and a path within it as the source.

Skipping a path

To leave a path out of the migration, identify it as you would in any other row, then enter y in the Skip Path column. Box Shuttle skips that path even when it migrates the parent folder.

Upload the spreadsheet

On the Map Data Settings page, select Upload .XLSX file, then select Upload and choose your completed file. Box Shuttle checks the file and reports the result next to the file name. When every row is valid, Box Shuttle marks the file Scanned successfully and makes Next available. Select Next to continue. Because your spreadsheet supplies the mappings, Box Shuttle skips the Map Data page.

Correct upload errors

The check fails in one of two ways. If Box Shuttle cannot read the file, it reports that the uploaded file is not a spreadsheet. Save your work in XLSX format, then upload it again. If Box Shuttle reads the file but finds rows it cannot use, such as a row with a required column left empty, it asks you to download the file and address the discrepancies. That download is a copy of your spreadsheet with error messages added, showing which rows need attention and why. To correct the errors:
  1. Select Download, then review each row Box Shuttle marked.
  2. Fix those rows in either the downloaded copy or your original spreadsheet.
  3. Upload the corrected file.
Box Shuttle checks the file again. Repeat until it reports that the file scanned successfully.

Map users and groups

When you migrate data with permissions, the settings page before Map Users and Groups offers the same choice, this time for collaborators. Select Download formatted template to get a spreadsheet with two sheets, one for users and one for groups. Box Shuttle prefills the source column on each sheet with the users and groups it found when it scanned your source system. Every row needs one of the following, or Box Shuttle treats it as invalid:
  • A target: the matching Box user name on the users sheet, or the matching Box group name on the groups sheet
  • A y in the skip column, for a source user or group with no Box counterpart
Upload the completed file on the same page. The check and error correction work exactly as they do for the data template.

Finish the job setup

The remaining steps are unchanged. Resolve permission conflicts, define filters and run settings, then continue to Pre-Run Validation, which lists the spreadsheets you uploaded alongside your job settings. Validate the job to confirm that your mappings point where you intended, then run a simulation before you run the transfer.

Best practices

Break a large migration into several smaller jobs rather than running it all at once.
A spreadsheet makes it as easy to misdirect a thousand directories as one. If an error goes unnoticed, you can move a large amount of content somewhere you did not intend, and unwinding that takes far longer than running several smaller jobs.
The first time you use bulk mapping, start with a job small enough to verify by hand. Confirm that the content landed where you expected, then scale up as you get comfortable with the format. Box always recommends running a simulation before you run the transfer.
Last modified on September 1, 2026