Forum Discussion
Removing the empty classic team root site and create a new modern communication root site
I want to start a new Office 365 project. and i am facing with the same old/new issue, is that there root site collection is actually a classic team site collection. but i want to have it as modern communication site. now i found some links which provide a long appraoch of converting classic team site into modern communication sites and some people mentioned that this appraoch is not supported. so i am not sure if i can simply remove the root site collection and create a new communication site inside the root. i do know that removing the root site will make all the site collections un-accessible till we create a new root site collection. so i can arrange this with our customer and do the deletion and re-creation over the week end.
but i am not sure if deleting the emty classic team root site and create a new communication site is considered a valid and supported appraoch ? as i am not seeking to convert anything, since the current classic root team site is empty...
Thanks
17 Replies
john john take a look at the announcements that were made this week at the SharePoint conference, there are lots of changes coming soon for what you can do with the root site. If your schedule allows, it will be easier.
Dean_Gross wrote:john john take a look at the announcements that were made this week at the SharePoint conference, there are lots of changes coming soon for what you can do with the root site. If your schedule allows, it will be easier.
can you let me know where i can read more about the announcement? and what will be the features for the root? second point, will there be any harm if i add some lists and libraries to the current root site, and then convert it to a communication site? as we are planning to submit 2 site collections (the classic root team site + another communication site under /sites/), so i will not be able to delay this anymore..
- see https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Updates-to-SharePoint-security-administration-and-migration/ba-p/549585, the Invoke-SPOSiteSwap cmd is coming
- Wait for official support or attempt anything else on a developer site. Don’t use your customer’s production platform.
John Wynne wrote:
Wait for official support or attempt anything else on a developer site. Don’t use your customer’s production platform.so you are saying that deleting the classic team site collection and re-creating a new modern communication site is not supported? i can not imagine why this is the case.. also i can not wait to get official announcement, as we need to start with the project. and if we apply a redirect then we will have to migrate all the content to the root site in the future..
now if deleting the classic root team site and create a modern root site is not supported, then i will work on the current classic team site, and will use the modern UI in this case... what do you think ?
- No, it is not supported yet. Stay classic until it is. This will be supported in the future and bear in mind you are in the same position as everyone else who remains within a supported SPO environment. You may experience all kinds of unpredictable issues by changing fundamental sites. Remember you will be able to ‘upgrade’ in a supported way in the future. If you have access to a Microsoft support team discuss with them but the advice remains your root site is essential for smooth operations only perform supported actions.
- I would recommend either redirect to the communications site
https://techcommunity.microsoft.com/t5/SharePoint-Developer/Convert-Classic-root-site-to-Communication-site/td-p/213004
Or waiting for the supported cmdlets on the M365 roadmap scheduled for Q2
https://techcommunity.microsoft.com/t5/Communications-Sites-AMA/Change-Tenant-Root-into-a-Communication-Site/m-p/263650#M645%C2%A0
AFAIK, a remove and add would not be a supported scenario.
Best, Chris
ChrisHoardMVP wrote:
AFAIK, a remove and add would not be a supported scenario.
Best, Chrisis there any official documentation about this ? that it is not supported? and why this will not be supported if new tenants will have their root site collection as a communication site collection..
- No official documentation that I can find that it is either supported or not supported. As this uservoice is currently open for it
https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/20308864-set-communication-site-as-root-site-collection
And the fact that they are bringing out shell commands to convert suggest it is unsupported.
Of course, nothing says it 100% isn’t. I am also going on the fact of doing things, they not work and contacting MS support only for them to say it is not officially supported after. I guess my point is there is nothing official to say this supported
Best, Chris
