Forum Discussion
Removing the empty classic team root site and create a new modern communication root site
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 ?
John Wynne wrote:
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.ok i agree with you and thanks for the great replies. so what i am planning to do is as follow:-
1. create all the lists and libraries inside the current classic team site.
2. where i will be using the modern UI.
3. later in the future if Microsoft provide a CMD or a feature to enable on the classic root team site, then we can enable it, which will/should convert the classic root team site to a modern communication root site, and without having to migrate any thing or losing any of the data we already have? so we even do not have to delay our project
what do you think about my above 3 points?
- That is a good solution and supported. Then switch over when the shell commands are released in Q2.
To note the other ways are supported too - a redirect to a communication site is in a standard web part and the shell commands to convert will be released fully supported.
Glad we helped get you to a solution!
Best, ChrisChrisHoardMVPthanks for the great replies.
ChrisHoardMVP wrote:
To note the other ways are supported too - a redirect to a communication site is in a standard web partnow adding a redirect is not an appraoch we want to follow, as our customer want the intranet to be on the root (which is understood). it tooks us decade till we convince them that the url for the root should have sharepoint.com inside it :)
ChrisHoardMVP wrote:
and the shell commands to convert will be released fully supported.i am not sure if the shell command will be supported on classic team sites which contain lists and libraries and data? or Microsoft will assume that the script will/should be run on empty root site?. for example i have this scenaro in my mind which is capable to break the shell commands, now if you create a new modern communication site, you can not enable the publishing features. so let say inside our current root classic team site we have enabled the publishing features on the site collection and site levels,, so what will happen when we run the shell command to convert the classic root to modern communication site? For me i usually on any classic team site (online, root or even on-premises) first thing i do is that i enable the publishing features, but for our new project i will not enable those publishing features,, as i do not want to complicate or break the proposing shell commands.. any advice or opinion on this will be highly appreciated ?
Thanks
- It’s a sensible approach and remember you will have Microsoft support. There is plenty of official Microsoft expertise here (not me!) and via your official help on your tenant. Microsoft Docs is an excellent resource.
