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 ?
- 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.
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, Chris
- Yes, classic site with modern UI elements or one of the above!
Hope this answers your question
Best, Chris
ChrisHoardMVP wrote:
Yes, classic site with modern UI elements or one of the above!
Hope this answers your question
Best, Christhe problem with the 2 links you provided, is that they contain lot of suggestions, and many of these suggestions are been described as unsupported as mentioned on the replies... so can you link me with the supported solution? or they all fall under having modern UI inside classic team sites?
