Data Migration Lead

Data Migration Lead – S/4HANA Program (BTL on RISE)

Role overview

The Data Migration Lead is accountable for the end‑to‑end governance and execution oversight of all data migration activities required to move BTL from ECC to S/4HANA on RISE. While the System Integrator (SI) will execute most of the technical migration mechanics, this role ensures there is robust governance, controls, business ownership and data quality across all migration cycles.

They are responsible for making sure that all agreed data in scope is migrated, including master data and transactional data (e.g. open items, balances, in‑flight transactions), and that data is properly cleansed, mapped, validated and signed off by the relevant business owners.

Key responsibilities

1. Data migration strategy, scope & governance

• Own and maintain the overall data migration strategy and approach for the BTL on RISE programme, aligned with target architecture, MDG strategy and deployment plan.

  
  

• Define and manage data migration scope across master and transactional data (e.g. business partners, GL/CO, tax, assets, contracts, open AP/AR items, FI‑CA items, balances, historical data where agreed).

  
  

• Establish and run data migration governance: forums, roles and responsibilities, decision rights, sign‑off points and escalation paths.

2. Planning & coordination with SI and internal teams

• Build and maintain the data migration plan and calendar across all phases (mock loads, trial runs, cutover loads, post‑go‑live corrections) in close collaboration with the SI and Deployment Services Lead.

  
  

• Coordinate with SI data migration team on design, build and execution of migration objects and tools (e.g. SAP Migration Cockpit, BODS, custom loaders).

  
  

• Ensure alignment with Data Governance / MDG, Functional Workstreams, Integration, Test Management and Satellite Systems leads.

3. Business engagement, cleansing, mapping & ownership

• Define and drive a data ownership model: identify data owners and stewards for each domain (e.g. Finance, Tax, Treasury, O2C, P2P, Payments).

  
  

• Orchestrate business‑led cleansing and enrichment activities for ECC and upstream data, ensuring timelines and quality expectations are clear.

  
  

• Oversee mapping design and sign‑off from source to S/4HANA target (including MDG models), ensuring mappings are documented, reviewed and approved by process and data owners.

4. Build, mock cycles & quality controls

• Define data quality and reconciliation controls for each object and cycle (e.g. record counts, control totals, sample checks, exception handling).

  
  

• Plan and oversee mock migration cycles (e.g. Mock 0 / 1 / 2 / Dress Rehearsal), including scope, success criteria, execution, issue tracking and remediation.

  
  

• Ensure that defects and issues from mock runs are analysed, prioritised and resolved in time for next cycles and cutover.

5. Cutover & go‑live data migration

• Own the data migration workstream within the cutover plan: sequence of loads, freeze periods, dependencies (interfaces, jobs, manual steps), rollback options.

  
  

• Ensure all data loads executed during cutover are tracked and reconciled (e.g. open items, balances, master data, configuration‑dependent reference data).

  
  

• Provide a data‑migration‑focused readiness view into go/no‑go decisions (completeness, quality, residual issues, workarounds).

6. Post‑go‑live support & Hypercare

… lees de volledige omschrijving bij Booking.com.