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

Compare with Current View Page History

« Previous Version 5 Next »

Status

  Pending Stakeholder Review

Owner
Stakeholders

Purpose

This document outlines the Syensqo-wide approach to data migration and readiness to move to SAP S/4HANA. It establishes a strategic and operational framework to ensure data is clean, reliable, structured and available at go-live.

The objectives are:

  • To plan, govern and control data migration activities from legacy systems to the SAP S/4HANA platform.

  • To define scope, dependencies, roles, risks and timelines aligned with cutover planning.

  • To ensure business engagement and ownership in all data quality and validation activities.

  • To meet global regulatory, operational and integration requirements with third-party systems.

  • To institutionalize data quality and governance practices that extend beyond go-live.


Background

The migration to SAP S/4HANA is a core enabler of business transformation and digital integration across Syensqo operations. Accurate and high-quality data is critical for the success of this initiative as it directly impacts core business processes, user adoption, reporting accuracy and legal compliance.

This data approach takes into consideration the need to:

  • Harmonize disparate legacy system data models into a unified global standard.

  • Ensure operational continuity during cutover by preloading critical data and validating business readiness.

  • Enable phased go-lives while managing cross-system data dependencies.

  • Use repeatable and scalable tools and methods that support global harmonization efforts.

Key steps include:

  1. Inventory and classification of all data objects

  2. Definition of transformation rules and mappings

  3. Execution of data profiling, cleansing and enrichment

  4. Mock load cycles for reconciliation and process testing

  5. Final cutover execution with validation and audit trails


Data Migration Scope

The scope of data migration for this global ERP transformation encompasses all essential master data, open transactional data and selected historical records required to ensure business continuity, legal compliance and readiness at the point of cutover. Data will be migrated from multiple SAP ECC source systems, legacy third-party applications and local tools into a harmonized SAP S/4HANA environment.

Data Sources

Data Targets

Data Dependencies

The data dependencies diagram will be used to ensure Syensqo's data migration timeline remains achievable, dependent object loads may begin once the corresponding predecessor objects have been technically loaded with 100% success and have passed initial data verification. This approach supports timely execution across all load waves and has been designed to balance efficiency with data integrity.

Link - Data Dependencies Diagram 

Data Migration Process

Data Extraction

Data extraction from Syensqo legacy systems is performed using Syniti Migrate, a tool designed specifically to streamline and automate the end-to-end data extraction process. This tool has been selected to align with Syensqo’s objective of reducing manual effort, increasing traceability, and accelerating migration readiness.

The adoption of Syniti Migrate offers the following advantages:

  • Minimizes dependency on legacy system owners by automating data pulls, reducing manual handovers and time-intensive coordination.

  • Enables both full and delta extractions, supporting iterative load cycles and ensuring data accuracy across multiple mock migrations.

  • Supports scheduled or on-demand extraction, allowing flexibility to align with validation cycles, mock cutovers and business availability.

  • Requires minimal to no custom development within the legacy systems, preserving system stability and reducing the risk of disruptions during the extraction phase.

This tool-driven approach has been integral in maintaining data integrity, auditability and repeatability across Syensqo’s global migration waves.

Data Transformation

Data Load

Special Requirements


Team and Deliverables

Functional Team

Deliverables

Roles

Data Team

Deliverables

Roles

Business Team

Deliverables

Roles

Third Party Vendor

Deliverables

Roles


Assumptions


Data Migration Risks & Issues

Risk/IssueMitigation Action








 

Data Validation Process


Pre-Load Validation




Post-Load Validation




Data Privacy


Change log

Version Published Changed By Comment
CURRENT (v. 5) Mar 24, 2026 17:02 WENNINGER-ext, Sascha clarified that export-controlled data will not be handled in Syniti and require manual load, and that this is not in scope for Mock 1
v. 160 Mar 12, 2026 15:41 DE MEERLEER-ext, Charles Small adjustments after alignment with R3 Migration Lead
v. 159 Mar 12, 2026 15:20 DE MEERLEER-ext, Charles Addition of R3 specific approach and nuances, in accordance with Dean Leighton.
v. 158 Feb 04, 2026 17:28 DUNNE-ext, Al Removed CUI Instance references - CR0279
v. 157 Jul 24, 2025 19:06 WENNINGER-ext, Sascha updated in line with RACI from signed Syniti contract
v. 156 Apr 23, 2025 09:54 LEIGHTON-ext, Dean
v. 155 Apr 23, 2025 08:59 LEIGHTON-ext, Dean
v. 154 Apr 23, 2025 08:48 LEIGHTON-ext, Dean
v. 153 Apr 23, 2025 08:41 LEIGHTON-ext, Dean
v. 152 Apr 23, 2025 08:33 LEIGHTON-ext, Dean

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels