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, open a different tab, visit the Box site and log out of Box. After logging out, go back to your Mover site and try connecting your Box Connection.

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 that the permissions of the Box user account are correct. Mover will only be able to perform actions that are allowed for the Box user. The Box user account being used should have "Editor" permissions, or higher.

There are some actions that are not allowed for Box "Viewer" permissions unless the user performs those actions on the Box platform itself. This means that some "Viewer" actions that succeed on the Box platform will not succeed for the same user when they access Box from another platform, such as Mover.

Disabled Connection

Because Box uses the oAuth authorization protocol, there may be future errors with the authentication even after your Connection and Migration have run smoothly for some time.

When you've resolved the problem that caused the authentication error, you can re-enable your Connection by saving its configuration. Even if you don't make any changes to the configuration, saving the record will cause Mover to re-enable the connection so that any associated Migrations will begin working again.