The document discusses planning for a SharePoint migration. It covers establishing a migration team, communicating the plan to stakeholders, surveying the current farm for customizations, and testing the migration process including customizations. The testing phase is emphasized to find issues early when migrating to the new SharePoint version using real customer data and fully evaluating the upgrade process.
3. Who am I?
• Brian Caauwe
• Manager, Consultant, Speaker and new dad
• Email: bcaauwe@avtex.com
• Twitter: @bcaauwe
• Technical Editor
• Professional SharePoint 2013 Administration
• Certifications
• MCM: SharePoint Server 2010
• MCSM: SharePoint
8. SharePoint History
Release History and Roadmap
2001 2003 2006 2009 2012 201620112010
Core Collaboration
Content
Management
Cloud and
Enterprise
Social
Cloud
Connected
9. Poll
What are your “largest”, “time consuming”, “hardest to
overcome” issues with SharePoint Migrations?
10. Migration Overview
Typical Issues
Resources
Customizations
Available Disk Space
Customizations
I’m looking at you Branding
Testing
Or lack thereof
Knowledge
Customizations
That configuration from 3 years ago
Customizations
Workflow manager, SharePoint Apps
Customizations
That guy who wrote that code
11. Migration Overview
Scenarios – On Premise [Out of the Box]
• 2010 – Need to go through 2007
• 2013 – Need to go through 2010
• 2016 – Need to go through 2013
18. Migration Patterns
On Premise
• Site Collection Upgrades
• No more “preview” sites
• No more compatibility view
• Methods
• Upon database attach (DEFAULT)
• Upon first browse
• Admin upgraded with Upgrade-SPSite
Traditional “Forklift”
19. Migration Patterns
Online
• Same “structure” moved online
• No native tools from MSFT like database attach
Traditional “Forklift”
22. Migration Patterns
Re-architect
• BEST time to tackle during migration
• Realign with the business
• Put EVERYTHING on the table
• On Premise, Online, Hybrid
• Web Applications
• Service Applications
• Customizations
• Managed Paths
• Site Collections
• Sites
• Lists / Libraries
• Permissions
• Metadata
23. Migration Patterns
Moving content comes with some pain
• Workflows
• Running
• Embedded Urls
• Alerts
• Favorites
• Old Users
Moving Content
24. Migration Patterns
Moving Content
Native Methods (On Premise)
• Move-SPSite (Moves site between content databases)
• Set-SPSite (change URL for host based site collections)
• Backup-SPSite / Restore-SPSite
• Export-SPWeb / Import-SPWeb
• Get granular to lists and libraries with -Path
28. Migration Cycle
Managing a complex process
• Communication
• Farm Customization Surveys
• Migration Customization Testing
• Environment Cleanup
• Environment Build Out
• Customizations Deployment
• Operations Scheduling
• Rollback Plan
• Post-Migration Activities
• Ongoing Support Calls
Before you get your servers… or licensing
29. Migration Cycle
Learn
•Migration methods
•New capabilities
•Downtime mitigation
Prepare
•Document
environment
•Manage
customizations
•Plan upgrade strategy
•Make items
upgradable
Test
•Build test farms
•Use real data
•Evaluate techniques
•Find issues early
Implement
•Build production farms
•Deploy customizations
•Minimize downtime
•Monitor progress
Validate
•Troubleshooting
•Upgrade event failures
•UI/UX issues
•Data issues
30. Migration Cycle
Learn
About YOUR environment
• Customizations (Solutions / Features / Cowboy)
• Your code
• Branding
• 3rd party
• Authentication Provider
• Classic vs. Claims
• FBA
• Custom STS
• Hardware Requirements (YOU NEED MORE)
• Disk Requirements (include backup and restore sizing)
• Resource Requirements
• TechNet Reference: http://technet.microsoft.com/en-
us/library/cc262485.aspx
31. Migration Cycle
Learn
Upgrade Methods
• Services Application (FIRST)
• Hybrid
• Point in time migration
• Swing migration
• Content Database
• Read-only outage acceptable to reduce
“downtime”
32. Migration Cycle
Learn
Web Browser Requirements
• IE 10+ / Edge
• Google Chrome (latest version)
• Mozilla Firefox (latest version)
• Apple Safari (latest version)
• What about mobile?
Office Requirements
• 2016, 2013, 2010?
• SharePoint Designer / InfoPath
33. Migration Cycle
Learn
“Deprecated” Features
• Sandbox Solutions
• code == bad
• XML == OK
• SharePoint Online Solution Inspector:
https://www.spcaf.com/blog/introducing-sharepoint-sandboxed-
solutions-inspector/
• SharePoint Foundation
• Forefront Identity Manager (FIM)
• Excel Services
• Tags & Notes
• What’s deprecated or removed from SharePoint 2016:
https://technet.microsoft.com/EN-
US/library/mt346112(v=office.16).aspx
34. Migration Cycle
Prepare
Reconnect with users
• Ask your users how they are using your
solutions
• Determine dead sites
• Remove data clutter
• Prioritize items that are fixed in 2016
• Re-visit information architecture
• Build internal buzz
• Start communication early!!
35. Migration Cycle
Prepare
Upgrade Strategy
• Different Roles, Different Upgrade Schedules
• SQL
• Office Web Applications
• Workflow Manager
• SharePoint
Upgrade Operations
• Roles on call, required, optional
• Downtime / Disruption limits
• URL adjustments (AVOID IF POSSIBLE)
36. Migration Cycle
Prepare
SharePoint 2013 Environment
• Validate / Complete Visual Upgrade
• Cleanup sites, webs, versions
• Isolate customized site collections into separate
databases
• Isolate ROOT (/) site collections into separate
databases
• Prepare site and list “templates” for migration
• Service Applications
• Swing Upgrade: Prepare Farm for Service Application
consumption
39. Migration Cycle
Prepare
Moving Content
• PowerShell
• Move-SPSite
• Backup-SPSite / Restore-SPSite
• Export-SPWeb / Import-SPWeb
• 3rd Party Tools
• MANY out there
Customization Gathering
• PowerShell
• Get-SPSolution
• Export-SPInfoPathAdministrationFiles
40. Migration Cycle
Test
SharePoint 2016 Environment
• Build / Prepare SQL environment
• Ensure Max Degree of Parallelism
• Migrate Associated Services
• Office Online Server
• Workflow Manager
• Microsoft Identity Manager
41. Migration Cycle
Test
SharePoint 2016 Environment
• Build SharePoint environment
• Use YOUR real data
• Use similar hardware as production
• Farm Configurations
• Web Applications
• Create Managed Paths
• Manual web.config changes
• Service Applications
• Build out new service applications NOT being
migrated
• Swing Upgrade: Prepare Farm for Service
Application publishing (2016) / consumption (2013)
• Apps configuration
• Get/Set-SPAuthenticationRealm
42. Migration Cycle
Test
Service Applications
• Test service applications to upgrade
• User Profile: Create Import Connections
• Search: Perform crawl to populate index
• Swing Upgrade: Publish service applications and
consume for validation
Content
• Run Test-SPContentDatabase prior to Mount-
SPContentDatabase
• Test Site upgrades outside of database attach
• Browse
• Scripted
43. Migration Cycle
Test
Perform MULTIPLE test upgrades
• Create a checklist
• Document your process AND procedures
• Create scripts for repeatable process
• Take user error out of the equation as much as possible
• Identifies YOUR time requirements
End user Testing
• Real accounts
• Customization Testing
• They know their sites better than you
• Performance / Load Testing
44. Migration Cycle
Implement
Service Application Upgrade Order
• Secure Store
• Business Connectivity Services (might require SSS)
• Managed Metadata
• User Profile (requires BCS and MMS)
• Search (crawl account needs to have access to UPA)
• PerformancePoint
• App Management
• Project
• Make sure associated services are also running
45. Migration Cycle
Implement
Content Database Upgrade Order
• Root level site collections
• Easy (less customization)
• Hard (most customization)
• ALWAYS Test-SPContentDatabase before Mount-
SPContentDatabase
Upgrade Order for Social Experience
• Upgrade MySite Host Site Collection
• Upgrade Personal
• PowerShell initiated
• User Initiated (First Accessed)
46. Migration Cycle
Validate
Logs
• Server logs
• Event Logs
• ULS Logs
• Upgrade Logs
• Site Collection Maintenance Logs
• Do NOT ignore “warnings”
Issue Resolution Order
• Authentication
• Customizations
• Content
47. Migration Cycle
Validate
Data Integrity
• Orphans / DB issues
• Missing Data
Site Sampling
• Choose all high impact / visibility sites
• Choose some simple sites
• Get at least one of each site definition
• Choose most high customized sites
• Ensure what you are validating WORKED before
upgrade
48. Migration Cycle
Validate
Verify Services
• New Service Application functionality
• Upgraded Service Application functionality
Customizations
• Might need to deploy to -CompatibilityLevel All
User Experience
• Master Pages, Page Layouts
• CSS and Themes
50. Aftermath
Fixing Issues
• You WILL miss something
• Solutions / Features
• Templates / Definitions
• Fab 40 … don’t go there
• Large Lists / Wide Lists
• User Experience
• Use Site Collection Health Checks to help
• Unghosted pages
• Non-reghostable pages
• Incompatible HTML
51. Aftermath
New Features
Plan for new feature rollouts
• Data Loss Prevention
• eDiscovery
• Retention Policies
• Hybrid
• Search
• User Profiles
• App Launcher
Plan for what’s next
• Take a hint from what’s coming in Office 365
52. Aftermath
Support
• Support calls WILL happen
• “something changed”
• “what is this new button”
• Who will receive support calls?
• Can they solve the problems
• Do they have permissions to do so
• What is the escalation process
• Proactive vs. Reactive Support
53. Aftermath
Patching
• Is your architecture ready for Zero Downtime
Patching?
• Redundant Services
• Load Balancer
• Microsoft Shipping Public Updates (PU)
MONTHLY
• Features Packs
• Get new features from SPO before new major version
• Requires Software Assurance
54. Aftermath
Patching
• Turn OFF Windows Update!!!
• For Public Updates, Service Packs and Feature
Packs, same cycle applies
• Learn
• Prepare
• Test
• Implement
• Validate
• Deploy Software Updates for SharePoint Server
2016
• https://technet.microsoft.com/EN-
US/library/cc263467(v=office.16).aspx
55. Aftermath
Ongoing Training
What Method(s) work for your organization
• Classroom
• Train the Trainer
• Self Service
• User Group
• Feature Focuses
• Lunch and Learns
• General vs. Solution based
60. Resources
• Create a Communication Plan (SharePoint 2013)
• https://technet.microsoft.com/en-us/library/cc263345.aspx
• Upgrade Worksheet (SharePoint 2013)
• https://www.microsoft.com/en-us/download/details.aspx?id=30370
• Upgrade to SharePoint Server 2016
• https://technet.microsoft.com/en-us/library/cc303420(v=office.16).aspx
• Upgrade Service Applications to SharePoint 2016
• https://technet.microsoft.com/EN-US/library/jj839719(v=office.16).aspx
• Upgrade Content Databases to SharePoint 2016
• https://technet.microsoft.com/en-us/library/cc263299(v=office.16).aspx
• Upgrade to Project Server 2016
• https://technet.microsoft.com/en-us/library/gg502590(v=office.16).aspx
61. Resources
• SharePoint Online Migration API User Guide
• https://support.office.com/en-us/article/SharePoint-Online-Migration-API-
User-Guide-555049c6-15ef-45a6-9a1f-a1ef673b867c
• SharePoint Online Solution Inspector
• https://www.spcaf.com/blog/introducing-sharepoint-sandboxed-solutions-
inspector/
• New and improved features in SharePoint Server 2016
• https://technet.microsoft.com/en-us/library/mt346121(v=office.16).aspx
• What’s deprecated or removed from SharePoint Server 2016
• https://technet.microsoft.com/EN-US/library/mt346112(v=office.16).aspx
• Deploy Software Updates for SharePoint Server 2016
• https://technet.microsoft.com/EN-US/library/cc263467(v=office.16).aspx
67. Migration Planning
Migration Customization Testing
• Upgrade Issues
• Wide lists
• Authentication Mismatch
• Modified Databases
• Customizations
• Recommendations
• Complete Customer & Farm Survey’s BEFORE testing
• Set Testing Goals
• Test customizations
• Use REAL data
• Evaluate branding requirements
• TEST YOUR Upgrade Process
• http://www.microsoft.com/en-
us/download/details.aspx?id=30366
68. Migration Planning
Environment Cleanup
• Remove Stale Content / Unneeded Versions
• Review Quotas / Locks
• Cleanup Templates, Solutions, Features,
Web Parts
• User Driven, OM / PowerShell can help
• Repair Data issues
• User Driven, OM / PowerShell can help
• Verify “Healthy” Environment (e.g. Health
Analyzer, Event Logs, SP Logs)
• Balance / Organize Content Databases
• Root sites
• “Issue Sites” in their own DBs
69. Migration Planning
Environment Build Out
SharePoint 2016 Migration Requirements
• SharePoint 2013 with SP1 and March 2013
PU
• Database version 15.0.4481.1005 or higher
• SharePoint sites need to be in 2013 mode
• CompatibilityLevel 15
70. Migration Planning
Environment Build Out
Hardware
• SharePoint Version(s)
• SQL Version(s)
• Office Online Server (Business Intelligence)
• Workflow Manager
• Microsoft Identity Manager (FIM Replacement)
Application
• Service Accounts
• Service Application Requirements
72. Migration Planning
Operations Schedule
Sample Schedule
• Planned 36 hours outage (read-only)
• Up to 54 hours emergency outage if rollback is required
• Downtime mitigation process can reduce outage time
Schedule Operation
Friday
2200hrs
Start backups
Saturday
0000hrs
Start upgrade of content farm/databases
Sunday
1200hrs
Upgrade must be effectively complete, or rollback of
environment must begin
Monday
0600hrs
Environment must be completely working, either as original
version or new version
73. Migration Planning
Rollback Plan
• DNS, Load Balancer, Service Applications, SQL Locks
• Draw a line in the sand
• How long does it take to implement?
• How long does it take to rollback?
• Test, Test and Re-Test processes AND procedures
• Prepare communication
Customizations
Available Disk Space (leave room for current production, new production and GROWTH requirements)
Customizations (Integrations like Workflow manager, SharePoint Apps now need to keep the Authentication Realm if forklifting)
Testing (most migrations, include SOME testing time… but ask the WHO, WHAT, WHEN, WHY and HOW of testing)
Customizations (Branding always changes between versions… colors, master pages, page layouts)
Resources (Make sure you have enough I/O, Memory and TIME!!!!
Customizations (Configurations that you make at the farm level that you haven’t changed in years like upload size, farm features, alternate access mappings, etc)
Knowledge (Learning the changes between platforms… what’s new, what’s not there anymore… This is CONTINUAL)
Customizations (3rd party code, developers who don’t exist anymore,
2010: MOSS 2007 needed to be @ SP1 + October 09 CU
2013: SharePoint 2010 just needed to be RTM
2016: SharePoint 2013 needs to be the “Real” SP1
No need to have an intermediate server level (can jump from 07 to 16)
Other restrictions such as GUID resets (SiteId, WebID, ListId, ItemId)
Users that no longer exists cannot be resolved
Alerts and Workflows are not part of the “content”
- Workflows can be dealt with 3rd party tools
Scenarios – Online
Manual… YUCK
SharePoint Online Migration API
PowerShell 3.0 required (NOT supported in SharePoint 2010 … workaround available through cmd parameters)
Azure subscription for side loading content
3rd Party Tools… more on these later
All of these cmdlets are specific to SharePoint 2016, however much are the same process as upgrading to SharePoint 2013
All of these cmdlets are specific to SharePoint 2016, however much are the same process as upgrading to SharePoint 2013, except App Management and Project
By default, when upgrading content databases it will upgrade site collections as well unless you use the -SkipSiteUpgrade switch parameter
BitTitan – MigrationWiz: Focuses on documents, but can also pull from other sources (e.g. Google Docs)
Sharegate – Also does some site admin management
AvePoint – Migrator: Part of their suite of products
Microsoft – PowerShell and SharePoint Online Migration API
Metalogix – Content Matrix and Content Matrix Express
Dell – Migration Suite: Previously the Quest migration tools
The SPO Migration API does not create any structure, it’s primarily used for moving content
Is your current architecture ancient like the existing Greek architecture
Is it classical like the Tower of London
Is it practical like the Chicago Skyline
Is it, and does it NEED to be “modern”
Migration Team Makeup:
Stakeholders – Decision makers, budget holders and people who WANT you to succeed
Server Admins – Can also include network admins, but they hold the keys to the kingdom
Database Admins – Yes, SharePoint needs a health SQL environment and they need to support your system
SharePoint Admins – We didn’t forget about you
Site Admins – The people who know the content and usage scenarios the best
Security Admins – With great power comes great responsibility… darn firewalls, security hardening and GPO’s
Designers – Those masterpages and page layouts need to be dusted off
Developers – 01100111 01100101 01100101 01101011
Site Users – End user testing NEEDS to happen for success
Migration Team Communications
Roles: What each role is responsible for
Timelines: High level timelines and when they will be needed
Issue Tracking: How to submit issues and what is the process for remediation
Site Owner Communications
Surveys (Who, What, Where, When, Why, How)
Training
Site User Communications
Reason: Provide what will make their work easier
Plan: Timeline and how it will effect them
Status Updates: Regular scheduled updates