The document provides an overview of modernizing SharePoint Online sites from the classic experience to the modern experience. It discusses the benefits of modernization, common components between classic and modern, limitations, and provides a sample implementation approach including using the SharePoint Modernization Scanner tool to assess readiness. It also includes examples of reports from the scanner and recommendations for addressing unsupported components.

1. LEVEL 200
Getting started Modernizing your
SharePoint Online sites
NOV 23
2019 SharePoint Saturday Toronto #SPSToronto
Salman Ahmad
Manager, Microsoft Services, KPMG

2. PLATINUM
Thank You Sponsors!
SILVERGOLD

3. 3
SharePint
SharePint
The Drake & Firkin
6982 Financial Dr, Mississauga, ON L5N 8J4
SharePoint Saturday
Toronto #SPSToronto

4. About Me
Salman Ahmad
Manager, Microsoft Services & Modern Workplace
KPMG Canada
@salmandotpk
• Developer, Administrator, Architect
• Working on SharePoint since 2007
• Organizer of SharePoint Saturdays in
United Arab Emirates since 2011

5. Classic Publishing Site

6. Classic Team Site

7. Modern Communication Site

8. Modern Team Site

9. Overview of Modern experience
Key improvements
to UX/UI
•Sleek design for desktop
and mobile devices
•Improved user interface
and user experience
•Enhanced performance
Classic user interface
will be deprecated at
some point and
planning a move to
modern experience
is essential
Transformation from
classic interface to
modern requires
careful planning
keeping business
users impact in mind
SharePoint
modernization
doesn’t impact on
contents and
permissions
SharePoint
modernization only
impacts user
interfaces and user
experience

10. Why is Microsoft moving from
Classic to Modern
 Microsoft is aligning all office 365 products with latest web standards and technologies
 Improved cross browser compatibility
 Microsoft decided to move to Modern to enhance the mobile
 Microsoft has changed its development methodologies to SharePoint framework (SPfx) which
is an attempt to align development effort with modern web technologies and it is not supported
in Classic SharePoint
 Modern SharePoint improves performance

11. SharePoint Sites
Search AI AutomationSecurityExtensibility
Simple  Accessible  Secure  Integrated  Intelligent  Extensible
Microsoft 365
Intelligent
Intranet

12. Benefits – Classic to Modern UI

13. Benefits – Classic to Modern UI
 Modern sites are adaptive and may require little or no customization which results in cost
savings
 Improved user experience due to intuitive navigation resulting in easier user adoption
 Allows more features for ease of access to documents - copy and paste more files, pin
documents, add files as link, download multiple documents at a time, preview files and
Drag and drop available cross browsers
 Modern sites support mobile devices natively and has a consistent look and feel across
phone, tablet or desktop
 The new list/document library is faster and displays better
 Modern search experience is improved and can see search results as you start typing
in the search box and the results update with suggestions
 Improved supports multiple browsers including IE, Edge, Chrome, Firefox etc.
 The Sync feature in OneDrive is enhanced and is more visible.
 Hub Navigation provides intuitive way to connect all associated sites in organization and a
consistent look and feel
 More user-centric features in modern UI i.e. personalization, workflow creation and
customization of forms using Power Apps

14. Limitations– Classic to Modern UI
 Classic web parts are not supported in Modern (i.e. Custom Script web part cannot be
added in modern pages)
 Tree view and search filters/refiners are not available from left navigation of document
libraries
 Ribbon toolbar is not available in Modern experience
 Publishing feature is not available in Modern experience
 Cannot revert to Classic experience once in modern
 Some existing customizations need to be redeveloped for Modern UI
 Development for Modern experience requires learning new programming
technologies i.e. ReactJS etc. for customization
 Unsupported items that will change the business process
 Classic Web parts
 Customization (page layout changes and JavaScript changes)
 Action Bar (replaced with toolbar)
 Tree view and refiners in SharePoint document libraries
 SharePoint list and libraries UI customization
 Classic Search and Search display templates
 Availability of creating workflows using SharePoint Designer. (Replaced with Power
Automate)

15. Common Components between
Classic and Modern UI
 SharePoint pages to display information and functionality
 SharePoint lists which help to store tabular contents i.e. contact list of task list
 SharePoint libraries to classify and store documents
 SharePoint process automation components and integration with Power Automate
 Functionality to classify contents in DMS based on content types
 Site columns which helps to include metadata in lists and libraries
 Functionality to set up document templates in SharePoint
 Functionality for content management i.e. permissions, classification, workflows etc.
 Collaboration features which includes co-authoring, sharing options etc.
 Permission management for sites, lists and libraries will be the same in modern
experience
 Site structure, creation and management of list and libraries is same in both experiences
 Information management and governance i.e. site management and control, records
retention etc. will remain the same
 Creating custom themes for adopting corporate colors is available in both experiences

16. Common Components between
Classic and Modern UI
 SharePoint pages to display information and functionality
 SharePoint lists which help to store tabular contents i.e. contact list of task list
 SharePoint libraries to classify and store documents
 SharePoint process automation components and integration with Power Automate
 Functionality to classify contents in DMS based on document type i.e. memos, letters,
policies etc.
 Site columns which helps to include metadata in lists and libraries i.e. Date Modified,
Author etc.
 Functionality to set up document templates in SharePoint
 Functionality for content management i.e. permissions, classification, workflows etc.
 Collaboration features which includes co-authoring, sharing options etc.
 Permission management for sites, lists and libraries will be the same in modern
experience
 Site structure, creation and management of list and libraries is same in both experiences
 Information management and governance i.e. site management and control, records
retention etc will remain the same
 Creating custom themes for adopting corporate colors is available in both experiences

17. Modernization implementation
Approach
Assessment
Planning
Migration

18. SharePoint Modernization
Scanner
• Microsoft has provided a tool called SharePoint Modernization Scanner which helps to
• Iterate whole site structure within a site collection
• Generate reports of readiness of a site(s) for modernization
• Find readiness of the site(s) to connect to Office 365 group(s)
• Find compatibility of the lists and libraries for modern user interface
• Find readiness of Wiki and web part pages for page modernization
• Outcome of this tool is used to drive the planning, remediation, and migration while
transforming classic sites to modern

19. Modernization Scanner Reports
• SharePoint Modernization Scanner generates number of reports for site readiness and
inventory.
• These reports are
• Office 365 Group Connection Readiness
• Office 365 List Readiness
• Office 365 Page Transformation Readiness
• Office 365 Publishing Portal Transformation Readiness
• Office 365 Classic workflow inventory
• Office 365 InfoPath inventory

20. Reports Analysis (1/8)
Overview
Total Site Collections Scanned 1
Total Websites Scanned 812
Total Lists Scanned 4809

21. Reports Analysis (2/8)
Overview of Site Collection
Site Collection URL https://newcompany.sharepoint.com/sites/adm
Web Template BLANKINTERNET#0 (Publishing Site)
Ready for Groupify No
Groupify Blocker Publishing Feature
Customization Available Yes

22. Reports Analysis (3/8)
Overview of Sub sites (1/2)
Modernization complexity Medium
Total Subsites 812 (including root site)
Subsites ready for modernization 810
Subsites not ready for modernization 2
Reason for no readiness Use of web template which modern
experience doesn’t support
(Publishing Site, Search Center)

23. Reports Analysis (4/8)
Overview of Sub sites (2/2)
Sites with modern page web feature
enabled
740
Sites with modern page web feature
disabled
72
Web Publishing feature enabled 4
Web Publishing feature disabled 808

24. Managed and structural navigation is supported in modern experience
and will be moved without any issue.
Reports Analysis (5/8)
Overview of Navigation
Websites with managed top navigation 792
Websites with structural top navigation 20
Websites with managed left navigation 704
Websites with structural left navigation 108

25. Reports Analysis (6/8)
Overview of Customization
Are Custom Actions supported in modern
experience?
No
Number of Custom Actions in use 8
Custom Action use through JSLink
Number of lists with JSLink (custom actions) 712

26. Reports Analysis (7/8)
Overview of Lists
Total number of lists 4808
Number of lists supported for modern experience 3293
Number of lists not supported for modern experience 1515
Number of lists with undefined rendering issues 12
Number of lists with JSLink (custom actions) 712
Number of lists with Auto Experience setting 4800
Number of lists with Classic Experience 8

27. Reports Analysis (8/8)
Overview of Pages
Total Pages in sites 1568
Pages with 100% mapping 1562
Pages with not 100% mapping 6
Unmapped web parts on pages Search Box web part
Script Editor web part
Content Editor web part
XSLT List View Web Part

28. Reports Analysis Overview
Components Overview
Components # of scans # of failed # of passed Reason of failure Solution
Available? Y/N
Recommended Solution
Web Sites 812 2 810
Site template is not supported for
modernization
No
Wait if Microsoft supports
modernization of publishing sites
Lists 4808 3293 1515
Use of customized JavaScript and
custom actions
Yes
Convert custom JavaScript into
SharePoint Framework extensions
(Development effort required)
Pages 1568 6 1562 Use of unmapped web parts Yes
Use of community developed web
parts
Custom Actions 8 8 0
Modern experience doesn’t support
Custom Actions
Yes
Convert Custom Actions
functionality into SharePoint
Framework extensions
(Development effort required)
Unique Web
Parts
9 4 5
Modern Experience doesn’t have
mapped web part
No
Use some other web part to fulfill
the requirement

29. Demo
SharePoint Modernization Scanner

30. Improvement Opportunities for
moving to Modern UI

31. Suggested solutions for
unsupported components
• Check Office 365 roadmap if a solution to move publishing site to modern experience
will be provided. If not, contents migration would be required
• Use similar web part available in modern experience for unsupported web part
• Convert Custom Actions into SharePoint Framework Extensions
• Create new pages to replace publishing pages and add web parts or convert
publishing pages into modern pages
• Format list and libraries using SharePoint Framework Extension Field Customizer

32. Implementation Approach
• Phased approach with one first level site at a time.
• Evaluate and map unsupported web parts with existing similar web parts
• Translate custom actions into SharePoint Framework extensions
• Use community developed script editor web part for script editor web part, content editor
web part or for JSLinks functionality
• Use PowerShell to move Sites, Pages and Lists to modern experience
• ConvertTo-PnPClientSidePage -Identity "somepage.aspx" -Overwrite

33. Timelines
POC 1 week
DEV Environment 3-4 weeks
UAT Environment 3-4 weeks
Production Environment 6-8 weeks

35. Evaluation
Session Evaluation http://bit.ly/spsto19sessioneval
Event Evaluation http://bit.ly/spsto19eventeval

36. Thank you
Toronto community!
Toronto SharePoint Business
(meetup.com/tspbug/)
Toronto SharePoint
(meetup.com/torontospug/)
Metro Toronto .NET
(meetup.com/metrotorontoug/)
North Toronto Cloud &
DevOps
(meetup.com/NorthTorontoUG/)
Toronto Nintex User Group
(meetup.com/TorontoNintexUG/)
IT Pro Toronto
(meetup.com/ITProToronto/)
Toronto Enterprise DevOps
(meetup.com/Toronto-
Enterprise-DevOps-User-
Group/)
Toronto Power Platform
(meetup.com/Toronto_Power_Pl
atform_UG/)
NOV 23
2019 SharePoint Saturday Toronto #SPSToronto