Introduction
Reasons for migrating to the SharePoint Server Subscription Edition
- End of life of the previous version (IT life cycle / supportability / compliance)
- New functionalities and the "Modern UI"
Why a "simple upgrade" is not easily possible with SharePoint - complexity of a migration
Presentation of the typical phases of a migration to the SharePoint Server Subscription Edition
Analysis
- Recording the current status of the old SharePoint farm
- What needs to be considered? (data / solutions / forms and workflows)
- Support of the inventory with tools or PowerShell scripts
- Determination of quantity structure and identification of special requirements (use cases)
- How can a migration succeed?
- Stumbling blocks
- K.-o. criteria
- Determining the scope of the migration
- Deciding which type of migration should be carried out
- Tool-based (pure content migration)
- By attaching and upgrading the databases (content and service databases)
- Mixed scenario (tool + database attachment)
- Third-party tools
- Is the solution also available for SPSE? What to do if not?
Infrastructure implementation
- Scaling and setting up the target platform (SharePoint, SQL, Office Online Server, workflow manager if necessary)
- Set up an adequate migration infrastructure
- Test farm
- Test clients
- Migration client (for tool-based migration)
- Mail system
- SharePoint 2016 farm (if the migration is based on SharePoint 2013)
An initial test migration (with evaluation)
- Carrying out an initial migration for evaluation
- Identification of potential problems
- Testing use cases (and solutions)
- Determine telemetry for planning
- Developing procedures and checklists for the migration (rework)
The migration concept and the cut-over plan
- Description of the migration processes and a roadmap
- Definition of the time schedule
- Documentation of the practical implementation
The productive migration
- Necessary preparations (clean-up)
- Freezing all development and configuration activities
- Carrying out the migration
- Carrying out rework
Go-live or rollback?
- Release of the system
- User support after the migration
Communication
- Involving users in the migration process
- (Partial) automation of communication processes
Practical tasks (hands-on labs)
- Planning and scaling target environment
- Provision of a migration tool (exemplary)
- Use of PowerShell for automation
- Creation of a cut-over plan
- Carrying out a migration by attaching databases
- Migration of content with a migration tool