5. Agenda Why Should You Make the Move?
Moving to SP 2019
Moving to SPO
Picking a Target
6. Why should you move
off your legacy
SharePoint environment?
7. To change is difficult; not to change is fatal.
- William Pollard
8. The Clock is Ticking
Product Release Mainstream
Support End
Extended
Support End
SharePoint Portal Server 2003 2003 2009 2014
Microsoft Office SharePoint Server 2007 2007 2012 2017
Microsoft SharePoint Server 2010 2010 2015 Oct 13, 2020
SharePoint Server 2013 2013 2018 April 11, 2023
SharePoint Server 2016 2016 2021 2026
SharePoint Server 2019 2018 2014 2026
Search at https://support.microsoft.com/en-us/lifecycle/search
for detailed lifecycle data on each of the above products.
9. SharePoint 2019’s New Features:
Modern Team Sites
Communication Sites
SharePoint Home
New OneDrive Sync Client
Mobile
New Options for “Citizen Developers”
New Version of the SharePoint Framework
SharePoint Online’s Features
10. SharePoint Online’s Additional Features
Hub Sites
External Sharing
Teams and Groups Integration
O365 Security & Compliance
And much more…
12. Expect a Migration, Not an Upgrade
There is no “In Place Upgrade” option
Plan to migrate to a new SharePoint 2019 farm
- sites
- services
- applications
Much like the path from SP 2013 to SP 2016
No option for SP 2013 directly to SP 2019
Must first migrate to a SP 2016, then to SP 2019
More info on upgrading to SharePoint 2019: https://docs.microsoft.com/en-us/sharepoint/upgrade-
and-update/upgrade-to-sharepoint-server-2019
13. What Will You Need to Consider?
Where are you starting from?
- SharePoint 2010? 2013? 2016?
- This will drive your approach: DB migration versus tool-based migration
What hardware will you need?
- Footprint tends to roughly double from 2010 to 2013
- AND from 2013 to 2016
- BUT not from 2016 to 2019 thanks to 2016 investments
- You can scale up or out to address this
Items to remediate:
- Large lists
- Incoming email
- Portals…
- Just to name a few
14. Options for Moving (Content) to SP 2019
Database Attach “Upgrade” (Migration)
- See https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-databases-2019
for more information
- Only works for 2016 to 2019, older versions will require staged approach
- Service Applications also need to be migrated
- Existing Site Collections *must* upgrade
(cannot delay) but retain Classic
- Unique process for MySites
Tool Based Migration
- Can start with most legacy versions as source
- Features vary widely depending on the vendor
- Still requires a new farm
- No tools available from Microsoft
16. Also Requires a Migration
There is no lift and shift option:
- No database attach
- No database shipping
Plan to use a tool:
- Microsoft’s SharePoint Migration Tool
(SPMT) -> 2013 ONLY as source
- Several third-party vendor options
17. What Will You Need to Consider?
Is it a good idea to “Lift and Shift” your content “as is?”
- What about Modern vs Classic?
- What about O365 Groups?
- What about Communication Sites?
- What about Microsoft Teams?
Watch out for time constraints
- Velocity is still a challenge for migrations to SPO
- Carefully plan your migration timeline
Items to remediate:
- All the same big-ticket items as SP 2019
20. Challenges of SharePoint 2019
Built for “cloud” scale, but can you take advantage of that?
Isn’t the “latest and greatest” SharePoint
Offers many features best-suited for SharePoint Online:
- Self-service site creation
- Mobile access
- Sharing of content instead of granting permission
Missing cloud-only features can have an impact:
- No Hub sites
- No Delve
- No Graph
- No Groups
21. Challenges of SharePoint Online
Subscription-based Pricing (OpEx versus CapEx)
No more silos between workloads
O365 is an evergreen service
- High rate of change for users
- High rate of change for IT Pros
No more SharePoint upgrades! (YAY!)
Emphasizing security and compliance is essential