You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Status

WORK IN PROGRESS

Owner

Gautier Todeschini

Stakeholders

James Kyndt, John Donovan, Frank Bolata, Boris Foiselle

Issue

Google Sites are not migrated by Fast Track, so another migration scneario has to be determined to transfer them to the M365 environment.

Recommendation

Option 3: Rebuild of most used & critical Sites by Center of Excellence, and rebuild of other Sites by their Syensqo owners.

Background & Context

Google sites have a direct alternative in the office 365 ecosystem: SharePoint Communication sites
Since there is a direct migration path, 3rd party tools are available on the market to faciliate the migration of Google Sites towards Sharepoint Sites.

There are around 1800 Google Sites existing at Syensqo today, many of them duplicated at the separation as they were "shared resources" between Solvay and Syensqo.

Assumptions

  • Google sites have a 90 % compatibility with the components in SharePoint sites.
  • 350 to 400 Google Sites are estimated to be used and important for business operations 

Constraints

Impacts


Options considered

Option 1: Manual Rebuild by Center of Excellence

Option 2: Manual rebuild by Site Owners, with guidelines and support from the Center of Excellence

Option 3: Hybrid 1 + 2: Rebuild of most used & critical Sites by CoE, and rebuild of other Sites by their owners

Option 4A: Migrate with 3rd party tooling - Bit Titan
Option 4B: Migrate with 3rd party tooling - Cloudiway

Evaluation

Options

Option 1: Manual Rebuild by Center of Excellence

Option 2: Manual rebuild by Site Owners, with guidelines and support from the Center of Excellence

Option 3: Hybrid 1 + 2: Rebuild of most used & critical Sites by CoE, and rebuild of other Sites by their owners

Option 4A: Migrate with 3rd party tooling - Bit Titan

Option 4B: Migrate with 3rd party tooling - Cloudiway

Technical Feasibility

(Easy) 

(plus) Rebuild by a team of skilled technical expers who master the M365 solutions

(Easy) 

(plus) Sites visuals and interfaces can be recreated by end users / editors after training or knowledge materials

(minus) Application-enabled files surfaced on the site might be complex to rebuild and require assistance of the COE (underlying Apps Script, Appsheet ...)

(Easy) 

(plus) Rebuild by a team of skilled technical expers who master the M365 solutions

(plus) Simple Sites visuals and interfaces can be recreated by end users / editors after training or knowledge materials

(plus) 


User Impact

(Medium)
(minus) Freeze period to switch platforms

(minus) Coexistence situations along sites rebuild

(Medium)
(minus) High rebuild workload for Site owners / editors and their users

(minus) Coexistence situations along sites rebuild


(minus) Coexistence situations along sites rebuild



Support Impact

(Small)

(plus) Manual recreation has the best end result

(plus) Less questions to the support team, as rebuilt sites are tested and demoed to their owners

(plus) 


(plus) 
Time to Implement

(High)

(warning) Sites must be assessed, rebuilt, tested and demoed

(High)

(warning) Risk of delay if some site owners do not rebuild their site on time, especially for sites with customized artifacts in their ecosystem.




Security & Compliance

(Very Good)

(plus) Security & Compliance guidelines can be checked as part of the Sites rebuild (on functionalities and usage)





Operational Efficiency

(Very Good)

(plus) Assessment and rebuild will bring rationalization opportunities and standardization of some customized components.

(minus) High change management and awareness efforts to engage site owners in the rebuild of their sitesyellow circle Moderate change management and awareness efforts to engage site owners in the rebuild of their sites(plus)  
Cost

(High)

CoE resource costs (roughly 12 FTEs over 4 months)

(plus) 
white circle  


Supporting documents:


Version Published Changed By Comment
CURRENT (v. 9) Feb 19, 2026 11:48 CHUDZIAK-ext, Aleksander
v. 15 Feb 19, 2026 11:09 CHUDZIAK-ext, Aleksander
v. 14 Feb 13, 2026 15:05 CHUDZIAK-ext, Aleksander
v. 13 Nov 27, 2025 16:54 TODESCHINI-ext, Gautier
v. 12 Nov 27, 2025 16:37 TODESCHINI-ext, Gautier

Go to Page History

See also

LM01_KDD001 - Migration Strategy

  • No labels