In the review phase of a Dropbox migration using Transformer, you will:
|Feature||Target Object||Supported||Watch Points|
|Yes||Google Drive performance optimization|
|Paper||None||No||Migration of Dropbox Paper is not currently supported|
|Revisions||Revisions||Yes||Revisions can be hard on the source API|
|Comments||None||No||Dropbox comments cannot be read from the source API in a form that can be converted to Google Doc comments|
|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 Dropbox, this can 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.|
|Google Drive Performance Optimization for Large Accounts||A large number of files written to a single Google Drive account can cause significant performance degradation. Dropbox for Business accounts often have a large number of files concentrated into a single account, causing Google Drive performance to degrade both during and after migration.||Transformer provides the ability to migrate unlimited numbers of files to a single Google Drive account without performance degradation. The use of Shard sets is strongly encouraged. Please review the Shard Sets documentation for configuration details.|
Shared Folder Names
When a folder is shared, each user with access is able to give the folder a different name. As this is not available in Google, we use the Dropbox shared folder name, which is locked as the name of the folder at the time it was shared.
|Named Groups||Dropbox can assign permissions to groups such as "Everyone at <Organization>."||To migrate these permissions, your user mapping should include an entry indicating that "Everyone at <Organization>" maps to target domain.|
|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.