Forum Discussion
Consolidating into one site collection
I realized I should give just a few more details about our system, since that could make a big difference in this as well.
Like I said we have around 20 site collections in our current SP2013 farm. We also have around another dozen or so in a SP2010 farm that will be moving over someday as well. All told it's about 1tb of info. We also have another 10-12tb of data in our file shares that we have been debating moving into SP for years but never got around to it. Now with the cloud there is some push for that to happen.
We are a global company with a offices/manufacturing plants all over the world. We have several subsidiary companies, each with their own site collections as well.
One important aspect of this is that for every product our company makes, (or even thinks about making), there is a SP site for it. All data regarding that product lives in that SP site forever. Everything for that product, from it's initial concept through the end of life shut down, get's saved in SP.
We've been looking at Teams, and I would assume each product would get created as a Teams site. That way all the engineers, sales people, legal types, etc associated with that product could come together to work on it. How well does that work in Teams if you have an engineer who's a member of 30 different projects, all on Teams? Or a lawyer who has to chime in on every product, plus every other thing the lawyers have to be involved in?
I'm a little hesitant about doing all of this in Teams sites because it just doesn't feel like MS has fully developed this idea yet, and I'm nervous about committing fully to it only to find out that it doesn't scale well in a large manufacturing company. I use Teams for just my small workgroup and there are some days I SERIOUSLY want to just delete the app completely.
We also looked at Hub sites, but according to MS you can only have 50 of them per tenant. Even though we only have around 30 site collections now, planning for future growth means we'd run out of those eventually. I can't see the benefit to the hub sites that doesn't already exist with our current top level site collection home pages. or master pages.
I think Hub sites could have been cool if they could have been nested, and had way more than 50.
Ted
Don't assume that each product will get its own Team. Teams provides some new ways to create cross-functional groups of people that don't reflect your org/sales hierarchy. I belong to many project teams, i just make the active projects favorites so that they show up in UI, and when I'm not working on it I remove the Favorite. It can get tricky remembering where a Chat took place.
When you create a new Team, you can connect it to an existing Office Group, or create a new Group. You will also get a SPO Site with a document library and each channel in the Team will get a folder in that doc library. You can easily add links to other existing SP Sites/doc libraries so that the Team can easily access other products/reference material etc.
Hub sites are intended to tie together a flat site scenario, which you don't have, they won't provide much benefit for your legacy collections, but will for new stuff.
Keep in mind that you will soon be able to assign site collections to different data centers around the world.
HTH
Dean