A Tale of Two Interfaces
If you've been using SharePoint for a few years, you've likely encountered both the modern and classic experiences. Understanding the difference is important — especially if you're planning a new SharePoint Online deployment or migrating an older environment to the cloud.
Microsoft has been steadily moving SharePoint toward the modern experience since 2016, and today, all new SharePoint Online sites use it by default. However, classic sites still exist in many organizations, particularly those that have been running SharePoint for years.
Classic SharePoint Sites
Classic SharePoint sites are based on the older SharePoint interface that dates back to SharePoint 2010 and 2013. Key characteristics include:
- Built on server-side rendering — pages are generated on the server and delivered as full HTML.
- Heavily reliant on SharePoint Designer for workflows and customization.
- Uses web parts that were designed for older versions of SharePoint.
- Supports InfoPath forms, which are no longer being developed by Microsoft.
- Customization often requires knowledge of SharePoint Designer or Visual Studio.
While classic sites still work in SharePoint Online, Microsoft has made clear that investment in new features is focused exclusively on the modern experience.
Modern SharePoint Sites
Modern SharePoint sites represent the current and future state of SharePoint Online. They are built on a React-based framework and designed to be fast, mobile-responsive, and easy to customize without code.
- Responsive design — works seamlessly on desktop, tablet, and mobile.
- Modern web parts — a rich library of drag-and-drop components like News, Events, Quick Links, and People.
- Integration with Microsoft 365 — deeply connected to Teams, OneDrive, Planner, and Viva Connections.
- Faster performance — uses client-side rendering for speed.
- SharePoint Framework (SPFx) — the modern way to build custom web parts and extensions.
Modern Site Types Explained
| Site Type | Best For | Navigation Style |
|---|---|---|
| Team Site | Project teams, department collaboration | Left-side navigation |
| Communication Site | Intranets, company news, broadcasting | Top navigation |
| Hub Site | Connecting related sites together | Shared hub navigation |
Should You Migrate from Classic to Modern?
For most organizations, the answer is yes — but it requires planning. Consider the following:
- Custom solutions: Classic web parts, InfoPath forms, and SharePoint Designer workflows need to be rebuilt using modern equivalents (SPFx, Power Apps, Power Automate).
- User training: The modern interface looks and behaves differently, so plan for a period of change management.
- Migration tools: Microsoft provides the SharePoint Migration Tool (SPMT) and third-party tools like Sharegate or Metalogix to assist.
Quick Comparison
| Feature | Classic | Modern |
|---|---|---|
| Mobile Responsive | ❌ No | ✅ Yes |
| Microsoft 365 Integration | Limited | ✅ Deep |
| New Feature Investment | ❌ Stopped | ✅ Active |
| No-Code Customization | Limited | ✅ Extensive |
| SharePoint Designer Support | ✅ Yes | ❌ No |
If you're starting fresh with SharePoint Online, build on the modern experience from day one. It's faster, more capable, and fully aligned with Microsoft's product roadmap.