Monitoring points for Box

If you haven’t yet, review the Google Workspace Migrate best practices first.

Before you migrate content from Box, review the following points.

Google Workspace Migrate version
If you're running a version of Google Workspace Migrate earlier than 2.1.8.1, you need to update the platform and nodes before you migrate data from Box. Updating to a newer version of Google Workspace Migrate won't wipe any existing settings. For details, see Upgrade the software.
File versions
The default settings template for Box includes migrating 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.  To disable version migration, uncheck the Migrate versions box in the settings template. For details, go to Migrate Box content.
Large user accounts
Due to Box API limits, Google Workspace Migrate can process approximately 250,000 objects per user per day. If a single user owns more than 250,000 files or file versions, you could have delays. If so, consider splitting ownership of the files with other users before you migrate data.
Large single-user migrations
A migration of 400,000 files or more to one user's Google Drive account requires extra 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 400,000 files that are being migrated to Drive 10 accounts per node We recommend you set up temporary Google Workspace 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
Google Workspace Migrate does not support migrations from a single managed user account. Plan to migrate all accounts through a single enterprise administrator migration.
Migrating to shared drives
You can't migrate content to a user's My Drive and any shared drives in one migration. You must run the migrations separately. If you're migrating to shared drives, you must use a shared drives settings template. Learn more about settings templates.
Restricted permissions
Restricted permissions (where a child file or folder has fewer permissions than its parent) are not supported by shared drives. If the file or folder has restricted permissions on the source account, the restricted permissions are not migrated.
Migrating shared folders & files
Shared folders and files are only migrated to Google Workspace under the owner. For example, if user1 creates and shares a Box folder with user2, the folder appears under All Files in Box for both users. However, the folder is migrated to Drive only for user1. User2 can access the file on the target account by clicking Shared with me in Drive. For details, go to Find files shared with you in Drive.
Access level in Drive
If you're migrating content to Drive, the target user must have the correct access level before you start the migration: If you're migrating data to a shared drive, the user needs to be a Content manager or Manager of the shared drive. For details, go to Shared drives access levels. If you're migrating data to a folder in a user’s My Drive, the user must be an owner of the folder.
Running test migrations to Drive
If you delete items in the target Drive account following a test migration, make sure to empty the trash before rerunning the migration. Google Workspace Migrate tracks items by ID and will restore items from the target account's trash if you run the migration again. Emptying the trash avoids this issue and allows you to run a fresh migration.
Groups
For Google Groups, you must create groups in the target account first. Groups aren't automatically created by the migration process. When migrating groups: Use an identity mapping to map a group on the source account to an existing group on the target account. For details on what to specify in the mapping, go to Create & manage an identity mapping. It might take up to 24 hours to see new groups on the target account. Until then, you won't see them in the tree-view for a scoped view or mapping. Additionally, a mapping for a group could display as invalid.
Migrating files & folders to multiple locations in Drive
Google Workspace Migrate attempts to remigrate a file or folder to a new location in Drive if: You're migrating from Drive and the source item has more than one parent. The item is moved on the source or target account and then remigrated. The item's target location is changed in a mapping, and the item is remigrated. The outcome of the remigration depends on the item’s existing and new locations. If both locations are in My Drive or in the same shared drive, the item is moved to the new location. Otherwise, the item is not moved and the transaction fails with error code 1081344.
Access to shared drives on target account
If the original content authors don’t have access to the shared drives on the target account, files are transferred using the target GUser account specified in the mapping. This type of transfer can create bottlenecks and slow a migration. We recommend that you: Make sure that the Migrate folder permissions setting is turned on in the settings template. Go to Migrate Box to shared drives. Add additional target GUser accounts to help distribute load. Use at least one target GUser account for each active node server.

Next step

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

_{Google, Google Workspace, 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.}