Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Status

Status
colour

...

Status

Green
title

...

Decided

Owner

Gautier Todeschini

Stakeholders

James Kyndt, Frank Bolata, Boris Foiselle


Info

Decision: Option 2A: Migration by waves - GBU/BSA/GBS driven

Decision made by: LEAP SteerCo #3

Date: 

Online Meeting: LEAP - LLD Convergence

Issue

There are several ways to migrate Syensqo users and data towards the Microsoft environment, all have technical complexities and user impacts.
Syensqo is too large to consider a “big bang” approach while ensuring low disruption, and a migration by wave will create a coexistence period of 3 to 5 weeks (when both Google Workspace and Microsoft 365 will be used simultaneously).
Prolonged coexistence can lead to increased complexity, higher support costs, user confusion, and potential security risks.

...


Option 1

One Shot Cut Over

Option 2A

Migration by waves - GBU/BSA/GBS driven

Option 2B
Migration by waves - regional approach driven
Technical Feasibility

(minus)16 K active users (20 K active Mailboxes ~229 TB mailbox + ~181 TB MyDrive)

(minus) 3194 active shared drives (~ 63,6 TB Shared Drives)+ 2116 AODocs Lib. (13,7 TB)

(plus) More controlled and iterative approach, in line with the migration's partner strong recommendation.

(plus)  More controlled and iterative approach, in line with the migration's partner strong recommendation.

(plus) Simpler meeting room hardware switch (all meeting rooms in the related site will be switched)

(minus) Higher risk of miss-assignment as geographical attachment might be less precise than organizational information in the IT systems (i.e. migrating a user that is not actually located in the targeted region/site for this wave).

User Impact

(plus) All of Syensqo is impacted at the same time "band aid" approach in some cases can be seen as a better approach to change management

(minus) Show stopper: 8 days of disruption for the sync event before cutover

(plus) Smoother Intra-GBU collaboration as everyone will have Teams Chat, Outlook emails & calendar, and access to OneDrive for simple file sharing

(minus) Cross-GBU collaboration impacted during coexistence: (Calendar availability, Room Booking)

(minus) Complex Meeting rooms management for sites that have mixed GBU presence (ex: meeting rooms might have to be booked from migrated-users’ agendas only)

(plus) No coexistence issues within a single site, especially beneficial for sites with mixed GBU presence

(plus) Easier planification of meeting rooms hardware configuration and booking by users during migration

(minus) Cross-region travels during the coexistence will require more careful planification (ex: local contact for room booking)

Support Impact

(minus) Very complex to handle a company-wide, international major change, with important user impacts

(plus) Ramp up of full support through a controlled process

(minus) Worldwide population in a single wave is more challenging for of IT support and project team around cutover

(minus) Will be supporting the users in a same country on two different platforms

(plus) Ramp up of full support through a controlled process

(minus) Heavy load on a given time zone/region for each wave

Operational ComplexityN/AN/AN/A
GBU/BSA/GBS FeedbackN/A

(plus) 13/15 votes for this scenario

(minus) 2/15 votes for this scenario
CostN/A - Fast Track included in the Microsoft Contract


See also

LM01-KDD002 - Gmail Migration to Exchange Online

[WIP] LM01_KDD00x - Migration to SharePoint

The following section describes relevant documentation:

Description

Repository





Change History
limit5
[WIP] LM01_KDD00x - Personal Drives Migration to OneDrive