In the review phase of a G Suite (formerly Google Apps) migration using Transformer, you will:
|Feature||Target Object||Supported||Watch Points|
|Folder Metadata||Folder Metadata||Yes||Modified date and modified user metadata is preserved.|
|Folder Hierarchy||Folder Hierarchy||Yes|
|File Metadata||File Metadata||Yes||Modified date and modified user metadata is preserved.|
|Folder ACLs||Google Sharing||Yes|
|File ACLs||Google Sharing||Yes|
|SID ACLs||Google Sharing||Yes||SID ACLs correspond to identities that can only be resolved by their SID. To properly migrate, the SID for each user must be mapped using a User Map.|
|External ACLs||Google Sharing||Yes||External ACLs|
|File Versions||Google Versions||Yes||File Versions|
|Watch point||Description||Best Practice|
|External ACLs||External users or groups with a Google account can be resolved and added during migration. External users or groups without a Google Account require an email to be sent with a custom access link at migration time.||Turning on external ACL migration during the final incremental migration decreases the amount of time external users have access to migrated files before go-live.|
|File shares do not have versioning capabilities, but files are often stored sibling to each other with naming conventions used to differentiate versions.||The Transformation Suite supports regular expressions to analyze file names, and automatically collapse files that match the pattern into a version history in Google Drive.|
|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 firstname.lastname@example.org if you have any questions about this feature.