Home

Classic vs Modern

%3CLINGO-SUB%20id%3D%22lingo-sub-283464%22%20slang%3D%22en-US%22%3EClassic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283464%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20still%20on%20classic%20UI%20and%20we%20were%20recently%20asked%20by%20our%20TAM%20what%26nbsp%3Bis%20preventing%20us%20from%20moving%20to%20the%20Modern%20experience.%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20are%20the%20reasons%20we%20had%3A%3C%2FP%3E%3COL%3E%3CLI%3ENo%20way%20to%20direct%20user%20to%20our%20classic%20search%20by%20default%20on%20a%20modern%20site%20search%20box.%20Modern%20search%20does%20not%20have%20support%20for%20refiners.%20Also%20doesn%E2%80%99t%20support%20display%20templates%20that%20we%20can%20use%20to%20customize%20the%20experience.%3C%2FLI%3E%3CLI%3ERequired%20fields%20are%20no%20longer%20mandatory.%26nbsp%3BModern%20is%20fine%20if%20you%20are%20not%20concerned%20about%20strict%20metadata%20requirements.%20We%20are%2C%20so%20it%E2%80%99s%20not%20usable%20for%20us%20currently.%3C%2FLI%3E%3CLI%3EDocument%20sets%20not%20supported%20yet.%3C%2FLI%3E%3CLI%3EOn%20lists%2Flibraries%20the%20Title%2FName%20field%20is%20truncated.%20Without%20customization%2C%20long%20titles%2Fnames%20will%20not%20be%20viewable.%3C%2FLI%3E%3CLI%3EIssue%2FTask%20lists%20are%20not%20supported%2Ffully%20implemented%20and%20alternate%20between%20modern%20and%20classic%20UI%20depending%20on%20what%20you%20are%20doing.%20Also%20the%20Gantt%2Ftask%20bar%20views%20are%20missing.%3C%2FLI%3E%3CLI%3EDisconnect%20between%20the%20modern%20UI%2F%20classic%20experience.%20Can%20be%20a%20disjointed%20experience%20for%20users.%3C%2FLI%3E%3CLI%3EBuggy.%20It%20appears%20that%20Modern%20is%20in%20a%20permanent%20beta%20and%20bugs%20appear%20regularly.%20Classic%20is%20stable.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20curious%26nbsp%3Bto%20hear%20pros%2Fcons%26nbsp%3Bfor%20Classic%2FModern%20from%20others%20working%20with%20large%20enterprise.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-283464%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285360%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285360%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20think%20of%20only%20the%20negatives%2C%20you'd%20most%20likely%20still%20have%20SP2007.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20biggest%20reason%20why%20we%20upgraded%20was%20mobile%20access%20and%20alignment%20with%20O365%20products%20and%20features.%20We%20had%20a%20customized%20SP2010%20that%20fit%20our%20needs%20really%20well%2C%20it%20came%20down%20to%20the%20value%20that%20SP%20Online%20was%20creating%20through%20ability%20to%20access%20from%20anywhere%20easily%20in%20addition%20to%20new%20features%20and%20ease%20of%20collaboration.%20As%20others%20have%20mentioned%2C%20this%20is%20not%20to%20be%20taken%20lightly%20as%20it%20is%20significant%20work%20for%20both%20you%20and%20your%20users%20when%20it%20comes%20down%20to%20change%20management.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284951%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284951%22%20slang%3D%22en-US%22%3EYeah%20that%20takes%20some%20work%20with%20adoption.%20But%20I%20never%20hear%20my%20users%20say%20they%20hate%20sharepoint%20anymore%20after%20moving%20to%20modern.%20Just%20sayin.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284946%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284946%22%20slang%3D%22en-US%22%3EWe%20have%20to%20acknowledge%20that%20this%20is%20a%20hard%20choice.%20It%20is%20hard%20because%20of%20the%20differences%20in%20the%20user%20experience%20as%20well%20as%20the%20features.%20On%20top%20of%20all%20this%20Try%20to%20explain%20Microsoft%20Teams%20and%20SharePoint%20dynamic%20and%20inexistence%20of%20classic%2C%20it%20gets%20worse.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284906%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284906%22%20slang%3D%22en-US%22%3ENot%20out%20of%20the%20box%2C%20but%20at%20least%20I%20have%20seen%20one%20in%20the%20SPFx%20repository%20kept%20by%20the%20SharePoint%20Team%20that%20could%20be%20fien%20for%20you%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284899%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284899%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20to%20mention%20the%20Calendar%20is%20not%20working%20in%20Modern%20UI%20(Currently%20Modern%20UI%20don't%20have%20any%20Calendar%20webpart).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283634%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283634%22%20slang%3D%22en-US%22%3EI%20would%20go%20definitively%20for%20modern%20because%20while%20your%20points%20are%20really%20valid%2C%20there%20are%20some%20features%20in%20the%20modern%20UI%20that%20are%20awesome%3A%3CBR%20%2F%3E1.%20Filters%20Panel%3CBR%20%2F%3E2.%20Upload%20directly%20document%20templates%20in%20the%20modern%20UI%3CBR%20%2F%3E3.%20Flow%20integration%3CBR%20%2F%3E4.%20Modern%20Pages%2C%20Modern%20WebParts%3CBR%20%2F%3EIn%20regards%20of%20some%20of%20your%20pain%20points%2C%20there%20are%20some%20that%20are%20already%20addressed%20%2F%20to%20be%20addressed%3CBR%20%2F%3E1.%20Modern%20document%20sets%3A%20They%20are%20working%20on%20it.%3CBR%20%2F%3E2.%20Title%2FName%20field%20is%20truncated%3A%20You%20can%20change%20columnd%20width%20and%20save%20the%20view.%3CBR%20%2F%3E3.%20Search%20customization%3A%20It's%20coming%20next%20year%20and%20also%20take%20a%20look%20to%20what's%20caming%20with%20Microsoft%20Search%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283589%22%20slang%3D%22en-US%22%3ERe%3A%20Classic%20vs%20Modern%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283589%22%20slang%3D%22en-US%22%3EValid%20points.%20Bugs%20aren't%20as%20bad%20thou.%20Specially%20if%20you%20stay%20in%20normal%20release.%20I%20find%20there%20are%20many%20pages%20and%20workloads%20that%20Modern%20makes%20sense%20for%20and%20works%20well.%20But%20in%20others%20not%20so%20much.%20Running%20a%20Hybrid%20setup%20should%20be%20a%20good%20path%20to%20look%20down.%3C%2FLINGO-BODY%3E
Frequent Contributor

We're still on classic UI and we were recently asked by our TAM what is preventing us from moving to the Modern experience. 

These are the reasons we had:

  1. No way to direct user to our classic search by default on a modern site search box. Modern search does not have support for refiners. Also doesn’t support display templates that we can use to customize the experience.
  2. Required fields are no longer mandatory. Modern is fine if you are not concerned about strict metadata requirements. We are, so it’s not usable for us currently.
  3. Document sets not supported yet.
  4. On lists/libraries the Title/Name field is truncated. Without customization, long titles/names will not be viewable.
  5. Issue/Task lists are not supported/fully implemented and alternate between modern and classic UI depending on what you are doing. Also the Gantt/task bar views are missing.
  6. Disconnect between the modern UI/ classic experience. Can be a disjointed experience for users.
  7. Buggy. It appears that Modern is in a permanent beta and bugs appear regularly. Classic is stable.

 

I'm curious to hear pros/cons for Classic/Modern from others working with large enterprise.

7 Replies
Valid points. Bugs aren't as bad thou. Specially if you stay in normal release. I find there are many pages and workloads that Modern makes sense for and works well. But in others not so much. Running a Hybrid setup should be a good path to look down.
I would go definitively for modern because while your points are really valid, there are some features in the modern UI that are awesome:
1. Filters Panel
2. Upload directly document templates in the modern UI
3. Flow integration
4. Modern Pages, Modern WebParts
In regards of some of your pain points, there are some that are already addressed / to be addressed
1. Modern document sets: They are working on it.
2. Title/Name field is truncated: You can change columnd width and save the view.
3. Search customization: It's coming next year and also take a look to what's caming with Microsoft Search

Not to mention the Calendar is not working in Modern UI (Currently Modern UI don't have any Calendar webpart).

Not out of the box, but at least I have seen one in the SPFx repository kept by the SharePoint Team that could be fien for you
We have to acknowledge that this is a hard choice. It is hard because of the differences in the user experience as well as the features. On top of all this Try to explain Microsoft Teams and SharePoint dynamic and inexistence of classic, it gets worse.
Yeah that takes some work with adoption. But I never hear my users say they hate sharepoint anymore after moving to modern. Just sayin.

If you think of only the negatives, you'd most likely still have SP2007.

 

The biggest reason why we upgraded was mobile access and alignment with O365 products and features. We had a customized SP2010 that fit our needs really well, it came down to the value that SP Online was creating through ability to access from anywhere easily in addition to new features and ease of collaboration. As others have mentioned, this is not to be taken lightly as it is significant work for both you and your users when it comes down to change management.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
30 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies