General Migration procedure
In this project, the migration team split the work into technical and administrative tasks:
The technical team did the whole planning and the Sharegate based migration.
The administrative team did the whole planning for communication, scheduling, testing and quality control including handover to the business owners.
For each site, the business owner defined a responsible person who had to
- communicate when the old site would be locked for migration or if the site would be archived instead of migrated
- do the initial testing after a site migration
- configure permissions
- invite the users to the new site once a migration was done
The migration hat to be done from client side without any server side installations due to IT policies of the customer’s internal datacenter.
Sites that had been marked for archiving had been taken out of our scope of the project and has been done by another partner.
After all sites had been analyzed and classified for archive or migration, we had 74 Sites left for migration that had been categorized into 60% sites with normal complexity and 40 % of sites with a high migration complexity.