This walkthrough guides you through configuring Box for migrations.
If you are looking to migrate multiple users, team drives, permissions, versions or if you are looking for any enterprise functionality, consider using Movebot's Project Manager
To configure Box, once you are at the source or destination configuration,
- Select Box from the dropdown
- Click Link Storage and login with your Box account
|As Team Admin||This enables you to log in with an admin account to view multiple users and additional content that your user doesn't natively have access to.|
|Exclude Shared Content (Recommended)||
If any content has been shared with you, this will be migrated by default. Should you wish to only migrate data that you have created or 'own' then tick this.
It is recommended as if you are migrating multiple users, you will migrate the same files multiple times and thus will increase the cost of your migration.
Click below to go to Movebot and Get Started
Should you have any issues or questions, please do not hesitate to email email@example.com
Movebot Box Migration FAQ
How is Box different compared to other providers?
Unlike other providers, Box does not have the concept of a shared drive or centralized location such as a site. Instead Box relies on a shared files and a "shared with me" mechanism where files are shared and accessible via shared folders. This is migrated when permissions are enabled during the migration. If migrating from Box, we recommend extracting the Box collaborators report and uploading that.
Why can I not see Box shared folders in Movebot like I can see Google Shared Drives, or SharePoint sites?
With regards to Box and not seeing the folders you would expect, this is due to ‘shared folders’ actually residing under a user’s account. Box itself does not have the concept of centralised storage like SharePoint, Google Shared Drives, etc. Instead it operates more that a user owns the data that is stored under a shared folder. Often what we find in these circumstances is that a single user holds the majority of the data. The best path forward is to run a full organisational scan and this will help identify where your data resides.
Otherwise, if you are looking into a user where folders are missing that you expect to be there, then you may need to disable "Exclude Shared Content" under the Box connector. However, disabling this should only be done if migrating strictly folders and not users (you may end up with duplicates).
Box unsupported characters and files
Movebot automatically sanitises file and folder names to ensure they comply with Box's standards. Box states what they support in their knowledge base article here. Movebot identifies these as part of its scan and on completion these can be found under the flagged issues tab. Additionally, depending on your subscription, Box may have file upload size limits.
Does Movebot sync files or support delta migrations?
Movebot offers a source-to-destination delta - when you run a transfer, we compare the destination files to the source and only transfer new or modified files. After the migration has started we strongly recommend not altering your data structure (moving folders or files) or renaming files or folders until after the migration. Doing either of these could cause duplicate files and folders depending the hierarchy and where the item was edited.
We compare the timestamps of the files in both the source and destination and transfer the newest versions only. This can be turned on under your migration's global settings.
Does Movebot delete files?
We do not delete your data from any source. Think of our operations as a "copy and paste".
What happens to external Sharing links?
Movebot does not recreate external sharing links. These will have to be set in the destination post migration. Additionally, we do not re-share links with external collaborators.
Does Movebot preserve file versions?
Yes, this is an option within Movebot to migrate all or some of the file versions related to a specific file. By default we only move the most modified file.
Does Movebot notify users?
By default this is disabled, however this is a setting within the migration global settings. We do however recommend erring on the side of caution as migrations are a behavioural change and excessive emails can cause distress with users.