Box

Add a Box Connection

Create a new Connection for your site, and select Box as the remote server type.

Provide a Connection Label so you can identify the connection in a list.

Connect Your Account

Mover uses OAuth authentication to connect to your account. Once you have saved your connection in Mover, you can click the Connect your Account button to start the login process. By logging into the service with OAuth, your credentials are never saved by Mover.

Using Multiple Box Accounts

You can add multiple Box Connections, each associated with a different Box account.

Sometimes, your web browser will automatically connect to your existing Box account when you add another Box Connection. To prevent this, log out of Box in your browser before adding the new Connection in Mover.

Box is Not Case Sensitive

Be aware of case sensitivity differences when copying, moving, or syncing files and folders between connections. Copying items from a system which is not case sensitive to another that is case sensitive could result in 1 item being treated as 2 different ones, such as attempting to overwrite MyFile.txt with myfile.txt .

In the other direction, copying from a case sensitive system to another that is not case sensitive can cause files to be overwritten, and folders to have their contents merged, if their case insensitive names are a match.

Troubleshooting

Insufficient Permissions

Make sure the permissions of the Box user account are correct. Mover can only perform actions that are allowed for the Box user, so the connected account needs "Editor" permissions or higher.

Some actions are not allowed for Box "Viewer" permissions unless the user performs those actions on the Box platform itself. A "Viewer" action that succeeds on the Box platform will not succeed for the same user when they access Box through Mover.

Disabled Connection

Because Box uses the OAuth authorization protocol, authentication can fail later even after your Connection and Migration have run successfully for some time.

Once you've resolved the problem that caused the authentication error, re-enable your Connection by saving its configuration. Saving the record causes Mover to re-enable the connection so that any associated Migrations will begin working again, even when no fields have changed.