Complication: You’re tasked with migrating file systems to Box and your source system permissions / ACLs do not exactly fit with Box’s waterfall permission scheme. This is a challenge for a variety of source systems, such as: network file shares, Windows Servers, SharePoint, or other EFSS systems. It’s laborious and time consuming to start from scratch and manually reset all file permissions and content ownership relationships. Also, migrating nested groups is a challenge without the right migration solution and strategy. FTP and other 3rd party migration tools do NOT provide analytics and automation to efficiently and reliably complete your Box migration.
Resolution: With Cloud FastPath you can easily identify source system permissions, collaboration groups, and content owners. From there you can review, modify if warranted, and then automatically map both on-premises and cloud-based file systems into Box while preserving source system permissions and content ownership relationships.
Migrating permissions to Box with Cloud FastPath
To get started, a lightweight Cloud FastPath agent is deployed on or near the source system (nothing to install when cloud-to-cloud) – use Cloud FastPath’s central web-based control panel to search and select the content of interest – and then simply press “play” to run a dry-run analysis of the content. This produces a heuristic based Excel report showing how Cloud FastPath would automatically map user accounts, permissions, and groups into Box. This Excel based report can be shared with department heads to make sure they approve of the user and permission mapping, and if warranted, you may modify content ownership and permission mappings in this convenient Excel report.
Once the mapping is confirmed accurate you upload this file back to the Cloud FastPath app. Cloud FastPath then automatically places the content into multiple Box accounts based on the ownership of the source files/folder and translates from one ACL system to another – for example from Windows NTFS to Box. This maps on-premise users to Box users and on-premise groups to Box groups.
Nested Groups: For migrating nested groups this depends on how you want the Box system to end up. Take as an example that you have a group “Sales” that has a child group “US West Sales” with Justin as a member and a folder “Sales Templates” shared with the “Sales” group. Given that Box doesn’t support nested groups, you could either:
- Add Justin to both the “Sales” and “US West Sales” groups and then we can share the “Sales Templates” folder with just the “Sales” group. The downside to this approach is that as members are added to child groups they will have to also be added to the parent groups.
- Add Justin to just the “US West Sales” group and share the “Sales Template” folder with both the “Sales” and “US West Sales” groups. The downside to this approach is that as new folders are shared with the parent groups each child group will also have to be added as collaborators separately.
The first is the default permission mapping Cloud FastPath will generate, but you can of course override that to add the additional sharing with the “US West Sales” group with a simple find and replace in the generated “Permissions” sheet of the spreadsheet we generate.
Cloud FastPath does not create the groups in Box nor add members to it, so building that group membership directory will need to be done separately (perhaps using the Box Single Sign On Active Directory integration).
Conclusion: Cloud FastPath’s built-in analytics and automation allows you to reliably and efficiently migrate source system users and permissions into Box.