In the review phase of a Box.com migration using Transformer, you will:
|Files||Files||Yes||Link correction - non Google-native files|
|Revisions||Revisions||Yes||Revisions can be hard on the source API|
|Watch point||Description||Best Practice|
|Revisions are part of the default configuration but can be very hard on the source API. Due to limited standard quotas when accessing Box, this can impact timelines more significantly than most connectors. Users should carefully consider how important revisions are to maintain, as they will impact timelines more significantly than most connectors.||Carefully consider the importance of versions in the migrated result to decide if the increased migration time is worthwhile.|
|Box API Quotas||The default quotas available to Box API users can be too restrictive for migrating large accounts, especially with revisions.||Additional quota can be requested from Box Support. If revisions must be migrated, or if Large User Accounts are in use, making a request for additional quota is strongly encouraged.|
|Large User Accounts||In Box, single user accounts often contain a significant portion of the overall content for an organization. These large single users may require some additional configuration and planning.||The use of Shard sets is strongly encouraged.|
|Link correction - non Google-native files||Link correction within non Google-native files is not supported.|
Transformer maintains a link correction dictionary for all objects migrated, which can be exported from the software. This dictionary can be used post-migration to identify and repair broken links.
AppBridge will be releasing a limited non Google-native file link correction feature in an upcoming build. Please contact email@example.com if you have any questions about this feature.