Mighty QuinnConsultingMighty Quinn Consulting — home
Workplace

Construction · IT

SharePoint Migration

Moving 20 TB of active sites and 80 TB of archive out of SharePoint 2016 and into SharePoint Online, then isolating what was left behind.

Duration
~12 months
Budget
~240.000 €
Project team
MQC 7 · Client 5 + 5

End-of-project survey

Overall satisfaction8/10
Budget9/10
Time7/10
Quality9/10
Collaboration9/10

Every project ends with the same questionnaire: five answers from 0 to 10, in the spirit of a Net Promoter Score. We publish what comes back, including when nothing does.

The project was completed on time, with high quality, and effectively managed within the allocated budget. Handling of the migration process was impressive, and the transition was smooth. There was clear communication and efficient coordination throughout, ensuring that all objectives were met, and the attention to detail in the decommissioning phase was much appreciated.

Construction

The brief

  • Migrate all project sites from the existing SP2016 environment to SharePoint Online (20 TB active sites, 80 TB archived sites, more than 2,500 site collections)
  • Re-implement business critical custom solutions (custom code, Nintex)
  • Isolate the existing SP2016 environment

The build

  • Definition of the overall migration concept including key stakeholder communication
  • Setup and automation of the migration environment based on ShareGate
  • Establishment of a minimal Power Platform governance concept
  • Creation of a central migration site with a migration backlog for communication and documentation
  • Definition of an isolation concept based on dedicated user accounts and jump hosts
Tech stack
  • Microsoft SharePoint 2016
  • Microsoft SharePoint Online
  • Microsoft Power Platform
  • ShareGate
Our part
  • Project Management
  • Conception
  • Development
  • Migration

The good

  • Migration approach for external users and guest user introduction enabled seamless collaboration with customers and contractors
  • High acceptance from site responsibles, based on a central information site

The bad

  • Integrating externals during the project required more concise documentation and guidelines
  • Significant fluctuations in data throughput
  • Some confusion with the guest user concept, on both the business and the external company side