AppBridge Documentation : Review features and watch points - to G Suite Migration

In the review phase of a migration using Transformer, you will:

Supported Features

FeatureTarget ObjectSupported 
FilesFilesYesLink correction - non Google-native files
RevisionsRevisionsYesRevisions can be hard on the source API
Box NotesUnsupportedNo 
PermissionsGoogle SharingYes 

Watch Points

Watch pointDescriptionBest 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 QuotasThe 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 AccountsIn 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 filesLink 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 if you have any questions about this feature.


Next: Preparation - Box to G Suite Migration