SharePoint is a versatile platform that has evolved significantly over the years. With the introduction of the modern experience, users benefit from a responsive design, enhanced user interface, and seamless integration with Office 365 features. However, there are times when you may need to switch between the classic and modern views due to compatibility, user preferences, or specific feature requirements. In this guide, we’ll walk you through how to switch a SharePoint site from classic to modern view and vice versa.
Understanding Classic and Modern Views
Before diving into the steps, let’s take a deeper look at the two experiences to understand when and why you might choose one over the other:
Modern Experience
- Designed with mobile responsiveness in mind, ensuring a seamless user experience across devices.
- Features a faster, more intuitive interface that promotes productivity.
- Offers enhanced web parts like the Hero Web Part, Quick Links, and modern document libraries that improve collaboration and content presentation.
- Provides better integration with Office 365 tools such as Power Automate, Power Apps, and Microsoft Teams.
- Some limitations include reduced flexibility for custom scripts and restricted support for legacy customizations like Content Editor Web Parts.
Classic Experience
- Retains support for older customizations, including InfoPath forms, custom master pages, and legacy workflows.
- Ideal for organizations that heavily rely on script-based solutions or third-party web parts that are not compatible with the modern experience.
- Includes features like datasheet views and older web parts, which may not yet have modern equivalents.
- However, the classic experience can feel outdated and lacks the performance and visual appeal of the modern interface.
By understanding these differences, you can make informed decisions about which experience is most suitable for your SharePoint site’s requirements.
How to Switch from Classic to Modern View
1. Ensure Prerequisites
- Verify Modern Compatibility: Ensure that the site’s lists and libraries are modern-ready. Avoid unsupported customizations like InfoPath forms or script-based solutions.
- Enable Modern Experience: In some cases, modern experiences may need to be explicitly enabled in your SharePoint tenant.
2. Steps to Switch
Using the User Interface:
- Navigate to the Site: Open the SharePoint site you want to update.
- Access Library Settings: For document libraries or lists:
- Click on the gear icon (Settings) in the top-right corner.
- Select Library settings or List settings.
- Update Default Experience:
- Scroll down to the Advanced settings section.
- Under List experience, select New experience (modern view).
- Save changes.
- Update Web Parts: If the site uses older web parts, replace them with modern web parts where possible.
Using PowerShell:
For administrators managing multiple sites, PowerShell can be used to enable the modern experience:
# Connect to SharePoint Online
Connect-PnPOnline -Url https://yourtenant.sharepoint.com -UseWebLogin
# Enable Modern Experience for a Library
Set-PnPList -Identity "LibraryName" -EnableContentTypes $trueHow to Revert from Modern to Classic View
1. Identify Compatibility Issues
Reverting to the classic experience might be necessary for several reasons, such as:
- The need to use custom scripts or InfoPath forms that are not supported in the modern interface.
- Relying on legacy workflows or third-party solutions that only work with classic views.
- Preference for older features like datasheet views or traditional web parts.
Before reverting, assess whether these needs can be addressed in other ways, such as modernizing the customizations or replacing unsupported features.
2. Steps to Revert
Using the User Interface:
- Navigate to the Site: Open the SharePoint site you want to modify.
- Access Library Settings: Go to the gear icon (Settings) and select Library settings.
- Update Default Experience:
- Scroll to the Advanced settings section.
- Under List experience, select Classic experience.
- Save changes.
Using PowerShell:
Reverting to classic experience for multiple sites or libraries can be automated:
# Connect to SharePoint Online
Connect-PnPOnline -Url https://yourtenant.sharepoint.com -UseWebLogin
# Disable Modern Experience for a Library
Set-PnPList -Identity "LibraryName" -EnableContentTypes $falseThis method is particularly useful for administrators handling bulk updates across multiple sites or libraries.
Limitations and Considerations
When switching between classic and modern views, it’s essential to keep the following limitations and considerations in mind:
- Feature Availability: Some features are exclusive to either modern or classic experiences. For instance, modern web parts like the Hero Web Part or Quick Links are unavailable in the classic experience, while certain legacy web parts work only in classic mode.
- Performance Differences: Modern views are optimized for better performance, offering faster load times and a more responsive design.
- Customization Compatibility: Custom scripts, master pages, and InfoPath forms may not function properly in modern views. Always test customizations before switching.
- User Experience: Switching experiences may confuse end-users if they are not familiar with the interface changes. Provide adequate training or documentation to ensure a smooth transition.
- Global Impact: Changes made to a library or list’s experience settings can affect all users accessing it. Be mindful of the broader implications before making the switch.
By carefully considering these factors, you can avoid potential disruptions and maximize the benefits of both experiences.
Switching between classic and modern views in SharePoint is straightforward and can be done using the user interface or PowerShell for bulk operations. While the modern experience is ideal for most scenarios due to its enhanced features and responsiveness, the classic experience remains relevant for legacy customizations and specific use cases. Evaluate your organization’s needs and choose the experience that best suits your requirements.
For further details, refer to
Microsoft’s official documentation.
You can also look at some support samples from the community
By following the steps in this guide, you can confidently manage your SharePoint site’s experience and ensure optimal usability for your team.
Accounting.js Branding Cascading StyleSheet Cheat Sheet Connect Content Type CSS Currency Date Formats Dates Flows Hillbilly Tabs HTML5 Intl Javascript JavsScript JSON Format View Luxon NodeJs Numeral.js O365 OneDrive Out Of The Box Overflow Permissions PnP PowerAutomate Power Automate PowerShell Pwermissions ReactJs Rest Endpoint Send an HTTP Request to SharePoint SharePoint SharePoint Modern SharePoint Online SharePoint Tabs ShellScript SPFX SPO Styling Sync Teams App Transform JS TypeScript