When planning a data migration between two different systems, understanding how those systems treat users and permissions differently is a key part of the planning process. It is important to understand two key factors:
- What your goals are for users and permissions
- What the source and target systems support
For example, perhaps you wish to preserve the source permissions and users as closely as possible. On the other hand, perhaps you are using this data migration as an opportunity to “clean up” permissions and sharing. Alternatively, maybe this is an archive-oriented migration and you want to deliberately change sharing, ownership and permissions.
The sections below describe some of the many use cases that Cloud FastPath supports for user and permission mapping.
Choosing a Scenario
|Scenario||Preserve Permissions||Preserve Folder Structure||Move All Files|
|Preserve File Structure, Grant Additional Permissions||No||Yes||Yes|
|Preserve Permissions, Change File Structure*||Yes||No||Yes|
|Warn User on Permission Conflicts (and skip non-conforming files/folders as default)||Yes||Yes||No|
*This option can be executed automatically for Windows to Box jobs, but you will need to add the option to your account. Contact firstname.lastname@example.org and tell them you need the “change structure preserve share” flag. Once that flag is added, you will see an option on the Mapping Strategy page of the mapping wizard to “Preserve Permissions, Change File Structure.”
Generate the map as usual, and you will see redirects in the mapping sheet whenever an item has reduced permissions. For example, if a Windows folder /folder/foldera/folderSecret has reduced permissions, it will set up a redirect in the mapping sheet to a root directory named folder>foldera>folderSecret with the correct permissions.