Forum Discussion
Way to convert existing site to modern team site UI?
Found mine have automatically switched. If I click on the cog in top right then hit "Add a Page" new UI one is automatically brought up.
Have done that for the time being on some newer team sites, along with switching the experience for doccument libraries and lists.
Still would love the other bits and pieces that come with modern UI, I remember seeing a powershell script for it a while back that can change it at the site collection level but can't find it anywhere. If anyone has it please do post, would be much appreciated!
And how about the other way around? The 'new' Team sites get automatically created when you create a 'team' group in MS Teams (as ...sharepoint.com/sites/... ) - these already have document library, calendar, etc. Can I simply convert these into a "classic" SharePoint site (as ...sharepoint.com/SitePages/... )??
I belive if you set a classic page (in the SitePages library, create a new Classic Page if necessary) as the homepage in a Group site it will get you essentially that. You'll still get the modern view by default when browsing site contents or an app view but you can also toggle that with the Switch to Classic button.
I'm really sorry - I meant a SharePoint site as in ...sharepoint.com/[site].
Maybe this will explain it better: When you simply go to the URL https://[tenant].sharepoint.com, it directs to https://[tenant].sharepoint.com/SitePages/Home.aspx, which looks like this:
I added a new Subsite named "IT", which I linked across the top when I set it up, as you can see in that screen shot. So when you click on "IT", it goes to https://[tenant].sharepoint.com/IT/SitePages/Home.aspx, which looks very much like the screen shot above.
Now....say I created a Teams group called "ITProjects", which when you click on that from the Teams landing page, it goes to https://[tentant].sharepoint.com/sites/ITProjects, which looks like this:
Can I simply convert that teams site at ...sharepoint.com/sites/ITProjects to a subsite like IT at ...sharepoint.com/ITProjects that I can link across the top just like "IT"??
Or is there no way and I have to just create it from scratch like I did with "IT" and move content over as needed? Which is not a big deal if that is the case...I just figured being able to convert will make things a little easier.
Thanks!
Just to get this right, do you want to unmodernize your "IT Projects" site, or do you simply wish to create a shared top level navigation?
If it Is the latter, then you should understand the concept of the SiteCollection first.
tenant.sharepoint.com is the top level site collection of any SharePoint deployment. Therefore when you create a subsite like "IT" you'll have the option to create a shared top level navigation for this SiteCollection only, as this was the default setting for classic SharePoint sites.
everything after /sites is what is onPrem called a "managed path". Every new SharePoint site that is connected to an Office 365 Group, creates its own SiteCollection under this managed path.Currently there is no easy way to create a so called Global Navigation that works across SiteCollections. It's not impossible, just not of the box.
The real answer lies behind the question what you really want to accomplish. Do simply want to modernize your current TeamSites for tenant.sharepoint.com, then you simply could, by creating modern pages and making them the default homepage. Only annoyance is that new subsite don't inherit from the modern template
If you want to use profit from all the other Office 365 Groups features than you'd have to migrate content from the old SiteCollection to the new one. The only unknown variable for this is the use use for your current tenant.sharepoint.com SiteCollection, the site the is currently labeled "Home" in your screenshot.
To simulate your current deployment you'd have to create a new Office 365 Group and give it a proper name (e.g. IT Department) and then create subsite for "IT Projects", though I would say you could probably leverage the existing site.
Groups just work on a flatter topology than previous SharePoint deployments that leveraged a lot of subsites.
