Forum Discussion
SharePoint Site Collection in SPOnline
Hi All,
I have a query regarding best practices for moving to SP Online.
We have a site collection in SP 2013 OnPremise which has around 1500 subsites. Now we are planning to move to SPOnline.
I would like to know what is the recommended/best practices for moving this to SPOnline as per Microsoft.
Should we retain the same structure i.e one site collection and 1500 subsites or should each be migrated to individual site collection?
I am sceptical of migrating it to individual site collection as in this case we will have huge number of site collections which will be difficult to manage.
I am just worried whether there will be any performance impact if one site collection has these many subsites in SP Online. Right now we are not facing any performance issues in SP2013 OnPremise
Any inputs would be helpful.
Thanks & Regards
Nithesh ERAKKARA
- Hi Paul,
Thanks for a quick reply. Yes we will be using ShareGate for the migration.
But just wanted to know if there is any best practices or recommendation from Microsoft for site collections in SPOnline and will so many subsites in one site collection have any performance impactI think it really depends. In general, I would think the strategic direction would be not have many sub sites and to have them be Site Collections. You can then leverage Hub sites to associated common sites (the old sub sites). This will allow for a lot more flexibility as the business structure may change and re organizations happen, etc.
Do these sub sites all inherit the same permissions as the (top level Site Collection) parent?
Do you roll out content from sub sites to parent (top level Site Collection)?
What drove the decision to make them all sub sites in the beginning?
There may be a valid reason to still maintain sub sites, but I think in general MS is making the recommendation to only do sub sites as the exception and to go forward with Site Collections and hub sites.
For the record, I am old SharePoint dude, and it toke me a while to get my head around this new approach, but I am embracing it now and I am seeing the real long term benefit to there new approach.
This will allow me to spend more of time focusing on the more complex business process and solutions using SharePoint and other O365 tools, and not spending the majority of my time changing and moving content.
