Cutover Strategy

(with details becomes Cutover Kickoff)

SAP
https://www.linkedin.com/in/mickaelquesnot/

PUBLIC
Agenda

1. Cutover Strategy
2. Timeline
3. Go Live Acceptance Criteria
4. Cutover Organization and Responsibilities
o Legacy Team
o Migration Team
o Business Team
5. Cutover Schedule
6. Cutover Simulations
7. Cutover Communications
8. Contingency Plan
9. Implementation Support
10. Logistics

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Cutover Strategy

• Time constraints?
• Big bang or phased?
• Sequence?
• Parallel system with legacy?

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

High Level Cutover Timeline
Mo October November December January
W 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
k

1 Business
Preparation
2 Production
Environment
Cutover Simulations
Preparation
3 Project Team
Preparation
4 Master Data
Migration
5 Cutover Preparation
6 Legacy Changes and
Shutdown
7 Transaction Data
Migration
8 Key Processes
Execution
9 Legacy Shutdown
10 Security access
enabled
11 Go Live
12 Go Live Support –
Hyper Care
13 Go Live Support –
Long Term

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Go Live Acceptance Criteria

• The business identifies the acceptance criteria during Realization in order to:
• Maintain the focus on going live on time
• Focus project team efforts on criteria tasks

• Acceptance criteria needed for major milestones

• To begin Production Cutover, for example:
• Acceptable levels of passing for Integration Tests
• Acceptable levels of trained and certified users
• Acceptable levels of open issues
• Acceptable performance criteria
• To accept Master Data, for example:
• Planned accuracy percent of data load by object
• To accept Transactional Data, for example:
• Planned accuracy percent of data load by object
• Key processes that execute correctly in Production post migration
• Meeting acceptance criteria allows move to next steps

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Cutover Organization

Cutover Manager

Legacy Data Migration Functional OCM

Team Lead Team Lead Team Lead Team Lead

Legacy Data Migration Business

Team Team Team Member

Site coordinators

Key users

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Roles and Responsibility

Cutover Manager ◼ Creates and maintains master cutover schedule

◼ Defines organization and logistics for cutover
◼ Manages cutover issues and their resolution
◼ Ensures communication to all stakeholders
OCM Team Lead ◼ Provides formal communications

Team Leads ◼ Create cutover schedule for team as input to the master cutover schedule

Legacy Team ◼ Extract data

◼ Provide reports to aid in validation
Data Migration Team Lead ◼ Creates cutover schedule for data migrations as input to the master cutover schedule
◼ Manages data loads prior to cutover
◼ Documents results of each data load
Data Migration Team ◼ Execute migrations
◼ Provide aid in validation
Business Team Members ◼ Validate converted data and resolve errors
◼ Identify and execute key process tests
Project Team ◼ Hyper care period support
Site Coordinators ◼ Manages site readiness
◼ Manages site issues and their resolution
Key Users ◼ First line support

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Long Term Responsibility

• Inventory of legacy systems

• Identify systems to sunset
• Identify any modifications needed
• Inventory of batch processes to reschedule or cancel
• Identification of security access requirements
• During cutover
• Post Go Live

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Migration Team Responsibility

• Determine whether migration is:

• One time
• Multiples for a file with deltas
• Determine approach to dual maintenance, as required
• Determine sequence of migrations
• Document migration quality tracking in Migration Quality Tracking spreadsheet
• Track record counts, validation works, and time requirements
• Create an individual spreadsheet for each data load including unit test, simulation loads, training
migration, etc.
• Aid the business to cleanse and validate the data

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Migration Team Responsibility

• Purpose
• Objectives & Goal
• Migration Plan Strategy & Methods
• Planning & Accelerated SAP (SAP Activate) Phases
• Migration Planning High Level Activities
• Go-Live Scope of Activities & Migration
• Key Team Members Worksheet
• Migration/Cutover Schedules
• Top Assumptions

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Purpose

• The Migration Plan identifies the activities to be performed during the cutover process from
getting started through execution of all related tasks: Planning, Acceptance and Execution.
• The plan further defines the activities required to facilitate a smooth transition into production
for additional SAP functionality.
• The major activities of Migration are the migration of master data and getting the Production
SAP system functionally and technically ready.
• The Migration Plan template is to be re-usable for each separate Migration effort (release
schedule).

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

Objectives and Goals

Objectives Goal
• Establish the Process for the Actual Go-Live The Goal is plan to ensure a smooth transition to
Transition production
• Define the Approach and Framework for
executing the Cutover Technical IT
Infrastructure Driven
• Establish Approval Criteria for Formal Cutover Items
Acceptance Deployment
System
Design

• Define Project Team Activities, Roles, &

Responsibilities Production

• Define Organization Team Activities, Roles & Organization Security

Responsibilities
• Define Project Management Activities, Roles Business
and Responsibilities Driven Training Data

Items

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Migration Plan Strategy & Methods

• For each SAP Project Schedule, (release) there will be a separate set of Migration documents
created using the following Migration templates:
• Cutover Schedule
• Cutover Checklist
• Final Cutover Checklist
• A Cutover Schedule will be maintained for each release schedule tracking all key area
milestone dates to ensure all areas are coming together for the individual Migration effort.
• A Cutover Checklist will be created with all necessary detail and dependencies and
tested/updated via the cutover simulations and lessons learned process.
• Acceptance criteria by key area will be defined for each Migration effort using the Final
Cutover Acceptance Checklist template.
• Lessons Learned from each Migration effort are to be evaluated and included as updates to the
Migration Plan going forward.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Migration Planning & Accelerated SAP Phases

Solution Validation Phase Realization Phase Final Preparation Phase Go-Live

Create Initial
Revise & Finalize Execute Go-Live &
Migration Migration Plan
Migration Plan Support
Plan

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Migration Planning High Level (Activities)

Create & Load

Test/Re-Test Data Test/Re-Test Data Finalize Data
Data Go-Live
Migration Migration Migration
Migration
Programs & Files Files Files
Files

Develop Volume Test Cutover Activities, Execute Move Transports into Ongoing
& Stress Test Scenarios Volume & Stress Testing Production, Data migration System
Apply Latest Support (Repeat 3X min), Payroll & Validation in Production, Maintenance
Packs to DEV/QA/Prod Interface Testing w/Customer Data (Execute All Cutover Activities)

Create SAP Training Materials,

Customer Acceptance Conduct
Create End-User Production
(CAT), Regression & End-User
Training Plans Support
Security Roles & Rights Testing Training

Organization Readiness Planning

Realization Phase Final Preparation PhaseGo-Live

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Go-Live Scope of Activities
Migration
Plan Key Key Areas Acceptan Legacy Source
Components ce Criteria Data for migration

• Cutover Strategy • Technical, • Infrastructure

(Infrastructure)
• Cutover Schedule • System Design
• Functional
• Cutover Checklist (System Design) • Security
• Final Cutover • Development • Data
Acceptance (System Design)
Checklist) • Training
• Authorizations • Organizational
(Security Roles &
Rights)) • Deployment
• Data Cleansing
• Data migration Legend:
• Training
1. Items highlighted in blue are “directly” related to Migration &
• Organization are tested via the Migration process.
Change
Management
2. Items highlighted in black are “indirectly” related to Migration
• Project with the final outcome of the testing being incorporated into the
Management
Migration effort.
3. Items highlighted in grey are not part of the Migration effort and
are tracked to ensure the overall success of the
implementation.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16
Top Assumptions
• System design work (configuration and enhancements) in scope have been completed and integration tested end-
to-end.
• Interfaces from SAP to external Customer systems in scope have been completed and integration tested end-to-
end (with new data set), with receiving system resources confirming both receipt and acceptance. (Requires
downstream systems (including those connected to XI) to be locked into SAP integration testing and acceptance
schedule.)
• Additional development work (authorizations, reports, forms, migrations, etc.) in scope have been completed and
tested.
• Data to be converted into the new SAP environment has been cleansed, validated and approved for migration into
SAP.
• The cutover approval process is timely and is based on the approval criteria defined as part of the Migration plan
for both the Business owners and Information Technology areas involved.
• Pre-requisite and parallel activities are completed and approved prior to the go-live (security roles and rights
testing, customer acceptance testing, end-user training, organizational change management activities, etc.).
• Resource constraints will be managed based on priority, criticality and urgency.
• Each team involved retains the resources and skill sets required to complete the tasks related to their respective
areas in the time needed.
• No historical data is part of migration/cutover process into SAP for the go-live.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17
Business Responsibilities

• The business identifies:

• Key personnel and staffing plans
• New data requirements
• Preparation for cutover
• Business preparation activities
• Process cut off milestones
• Alternative business processes for transition periods
• Acceptable business shut-down window
• Key processes to execute in production after data migration
• End user requirements
• Training or certification requirements
• Log on distribution logistics and requirements
• Start up procedures
• Business resources for cutover:
• Key Users
• Site Coordinators
• The business is responsible for the data
• Cleansing
• Validating

• Determine dual maintenance requirements, if any

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18
Cutover Schedule

• Each functional, data, and technical team lead to maintain a list of cutover activities in Team
Cutover Schedule
• Created before migration to QA box
• Provided to Cutover Manager for use in QA build
• Once provided to Cutover Manager, the Team schedules are no longer maintained, as there is
only one Master Cutover Schedule
• Cutover Manager merges the Team Schedules into the Master Cutover Schedule
• Executes merged schedule to build QA box, Prod box, simulation cutovers, and cutover to
production
• Updates schedule as needed to provide the most error-free cutover to production
• Re-uses the schedule for each
• The Master Cutover Schedule leverages MS Project’s predecessor and successor functionality
to enable forecasting of time requirements for cutover

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

Cutover Communications

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Contingency Plan

• Risks and mitigations for cutover

• Time required to restore legacy
• Position decision points for proceeding with next steps
• Identify acceptance requirements for each decision point

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

Implementation Support

• Hyper care period

• Project team staffs cutover room for 2 weeks
• Schedule developed for 24 x 7 support
• Help Desk phone line coordination
• Long Term
• Handover to Help Desk after 2 weeks

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

Thank you.
Contact information:
F name L name
Title
Address
Phone number

Partner logo
Follow us

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose w ithout the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed w ithout prior notice. Some softw are products marketed by SAP SE and its
distributors contain proprietary softw are components of other softw are vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, w ithout representation or
w arranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions w ith respect to the materials.
The only w arranties for SAP or SAP affiliate company products and services are those that are set forth in the express w arranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
w arranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
w ithout notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, c ode, or
functionality. All forw ard-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forw ard-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as w ell as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.

See w ww.sap.com/trademark for additional trademark information and notices.

SAP folgen auf

www.sap.com/germany/contactsap

© 2021 SAP SE oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu w elchem Zw eck und in w elcher Form auch immer,
ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.
In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert w erden. Die von SAP SE oder deren
Vertriebsfirmen angebotenen Softw areprodukte können Softw arekomponenten auch anderer Softw arehersteller enthalten. Produkte
können länderspezifische Unterschiede aufw eisen.
Die vorliegenden Unterlagen w erden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich
zu Informationszw ecken. Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gew ährleistung für Fehler
oder Unvollständigkeiten in dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und
Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jew eiligen Produkte und Dienstleistungen ausdrücklich
geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.
Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer
zugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin w iedergegebene Funktionen zu entw ickeln oder zu
veröffentlichen. Diese Publikation oder eine zugehörige Präsentation, die Strategie und etw aige künftige Entw icklungen, Produkte
und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen können von der SAP SE oder ihren Konzernunternehmen jederzeit
und ohne Angabe von Gründen unangekündigt geändert w erden. Die in dieser Publikation enthaltenen Informationen stellen keine
Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche
vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von
den Erw artungen abw eichen können. Dem Leser w ird empfohlen, diesen vorausschauenden Aussagen kein übertriebenes Vertrauen
zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen.
SAP und andere in diesem Dokument erw ähnte Produkte und Dienstleistungen von SAP sow ie die dazugehörigen Logos sind Marken
oder eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen
Ländern w eltw eit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jew eiligen Firmen.
Zusätzliche Informationen zur Marke und Vermerke finden Sie auf der Seite w ww.sap.com/trademark