We are currently in the discovery phase of our planned 2016 Sharepoint Online move. We are currently using DFs. Below are some stats behind our company:
- Roughly 250 internal users
- Potential for many external users (individual files only)
- 175 subsites or site collections that are basically clients
- Permissions are mostly based on defined Active Directory groups, but with the possibility for specific site / library / file access for those outside using SP Permissions
- Roughly 2 TB of data with the need for that to double in the next 5 years
Initially, I was planning on doing individual site collections for each "client" as I was worried about the 2000 subsite limit. Since then, the scope of what might possibly be under each client has dropped and we're looking at more metadata filtering and less subsites. I also have gathered information that Site Collections might be the way to go because of permissions.
The final reason why I was leaning in that direction was some of the things I am reading about Team Sites and Sharepoint Online, like below:
- 1TB limit for data in a single site collection
- 300 User Limit for a single site collection
- 5000 item limit for a list or library
Are these still actual numbers? If I need to migrate 1.5TB of data, is a single site collection impossible? Does the 300 user limit include external users?
The final piece to this puzzle is why I am currently leaning back to subsites or at the very least open to that design. We have a billing team that needs to process and store invoices in a single repository. I would like to display these (possibly in a metadata based list-view) on each individual client site. I can do this within a single site collection (at least do it more easily), but haven't been able to do list views across site collections.