Watchpoints and best practices for Box

Before you begin to migrate content from Box, make sure you review the G Suite Migrate best practices. Then, familiarize yourself with the following points. 

Watchpoint Best practices
G Suite Migrate version If you are running a version of G Suite Migrate earlier than version, you need to update the platform and nodes before you migrate data from Box. Updating to a newer version of G Suite Migrate won't wipe any existing settings. For details, see Upgrade the software
File versions—The default settings template for Box includes file versions, which can significantly increase the migration size. The standard API rate limits for Box are low, so additional load can impact migration timelines. Carefully consider the importance of migrating versions, and decide if the increased migration time is worthwhile.

You can disable version migration by unchecking the Migrate versions box in the settings template. See Understand Box settings templates.

Large user accounts—You might see migration performance delays if a single user owns a large number of files or file versions in Box. If a single user owns a large number of files or file versions in Box, you should consider splitting ownership of the files with other users before you migrate data.

Due to Box API limits, G Suite Migrate can process up to around 250,000 objects per user per day.

Large single user migrations—A migration of 50,000 files or more to a single user’s Google Drive requires additional planning. Use a sharding users list to spread the migration load among many user accounts.

To determine the number of user accounts to add to the list, use the larger value of: 

  • One account per 50,000 files that are being migrated to Drive
  • 10 accounts per node

We recommend you set up temporary G Suite users for your sharding users list. Then, delete the users after you complete the migration. For details, see Create a sharding users list

Managed user account migrations—In Box, Managed user accounts are generally how regular users within an enterprise use Box.

G Suite Migrate does not support data migrations from a single managed user account. 

Plan to migrate all accounts through a single enterprise administrator migration.

Shared drives—You can’t migrate content to a user's My Drive and a shared drive in one migration. You must run these migrations separately.

If you’re migrating to shared drives, you must use a shared drives settings template. Learn more about settings templates.
Shared folders When migrating a shared folder from Box:
  • If you specify the folder owner in the mapping, the folder's contents and permissions are migrated along with the folder. 
  • If you do not specify the owner in the mapping, an empty folder is created in the target location and permissions and content aren't migrated.
Access level in Drive—If you're migrating content to Google Drive, the target user must have the correct access level before you start the migration. Make sure that the target user specified in the mapping has the appropriate access level in Drive:
  • If you're migrating data to a shared drive, the user needs to be a Content manager or Manager of the shared drive. 
  • If you're migrating data to a folder in a user’s My Drive, the user must be an owner of the folder.
Groups—A group in Box isn't automatically created in G Suite. You can use an identity mapping to map a group in Box to an existing group in Google Groups. When you set up the identity mapping, use the group name from Box as the identity in the first column. In the second column, use the group's email address in Google Groups. Learn more about identity mappings.

Next step

Now it's time to set up a Box connection. To get started, see Add or edit a Box connection.

Google, G Suite, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.