Forum Discussion
Convert Classic root site to Communication site
In our recent intranet projects, we recommend users to go with main Intranet site using communication site template and we expect that to be the root site collection of the tenant. The issue is every tenant root site collection is a based on classic team site template and we will never be able to convert it to a communication site template. Apart from this big limitation, it gives other design challenges like missing global navigation, left nav etc.
One of the blog says about create a communication site, save the template as wsp. Delete the root site collection and recreate the site using the communication template that we saved earlier. Is this method is approved by Microsoft?
Ravi
- As Juan said not supported. In the near future they are adding the ability to change the navigation to either left, top or none. This will let normal left nav looking modern sites look like comm sites. Just have to wait for that feature.
What I’ve done is just created a comm site as our landing page and pointed everyone to it. And on the toot collection made a classic page he home page and put a redirect on it to redirect to the comm site. Been working fine.Thank you Juan and Chris,
As of now, I will take the redirect option, so users land on the Comm site from root site collection.
Thanks!
Ravi
How do you make this redirect work. Can you provide a step-by-step approach?
- Yeah. Tomorrow when I get in. But it’s just a response redirect script web part on the homepage. Just make a 2nd blank page and put the redirect script on it. Then set it as homepage. That way you can always get back to your default.aspx if you have too. Anyway if you need more instruction let me know and I’ll do some screens and the script.
- No, this method is not supported by Microsoft....might I ask why you don't simply use modern features in the root site collection in SPO
Can we create Communication site with modern Ui, inside classic root site in SharePoint online?
There is a new method to achieve this supported by Microsoft, I've wrote a blog post explaining how to do it.
All you have to do is to execute the site swap comandlet available on the latest version of the SharePoint Online Management Shell.
