Cutover Planning (Templates)

Note: Most major software vendors and system integrators include similar concepts and tools in their methodologies.
If that's the case for your program, use these spreadsheets (created from a combination of software vendor methodologies) as a checklist or guide to ensure your
transition process is complete.

Use this task list to validate that your transition plan is complete. Your systems integrator should play a key role in creating a work plan.

Cutover Plan
owner:
start date:
End date:

duration planned planned

task owner dependence in hours start date end date
Star io
t
1) Pre Cutover stop
Finalize transition plan and checklists
Communicate the cutover plan to the project team
Communicate the cutover plan to the entire organization

Communicate go-live timeline to customers and suppliers as appropriate

Plan and perform physical inventory
Implement configuration management plan
2) Pre stop production environment
Install production servers
Install the operating system and network software
Connect servers to the network
Create user accounts on servers
Configure file system on servers
Configure printer drivers
Install user machines and connect them to the network
Install the database on the database servers
Install application servers
Configure Standard Application Database Objects
Create the custom database objects
Install system administration tools
Install printers and other peripheral devices
Secure access to the production environment
3) Pre stopping the learning environment user training
Depends on the training plan defined in the general project plan
4) Wit figure applications
h

EI Toolkit
Document version 1.0, June 1 of
2002 21
Last validated: June 2004
 duration planned planned
task owner dependence in hours start date end date
Set up the app users on the new system.
Configure and compile key flexfields
Enter application settings
Load initial configuration data
Deploy security settings
Register application objects.
Configure and compile descriptive flexfields
Enter or upload custom seed data
Verify the online operation of the applications.
Verify the operation of the operations jobs.
Production system backup.
5) Inst alar conversion programs

Install conversion programs and automated conversion tool software (if used)
List the location of each conversion program in the production environment.
List the location of the conversion tools in the production environment.
6) Fin perform system administration
e Make sure backups run correctly
Ensure daily procedures in place
Ensure that sufficient Database space has been allocated
7) Defi nir contingency plan for the PCO
Define contingency strategy
Determine contingency support staff
Determine the contingency project team.
Define users/management procedures
8) Imp enhance production support infrastructure
See the help desk plan for more details
9) Rhe conduct user training activities
a View the user training plan
10) Rhe perform acceptance test
a Review acceptance testing responsibilities with the team.
Backup production environment for later availability
Validate the acceptance test environment
Run the acceptance test script
Document the results.
Determine the actions required to resolve the problem.

Make recommendations for application changes or fixes based on acceptance testing

Safe acceptance of acceptance test results.
Cut ove final
r

EI Toolkit
Document version 1.0, June 2 of
2002 21
Last validated: June 2004
 duration planned planned
task owner dependence in hours start date end date
1) Ad system and network inistration
m Shut down legacy systems at the appropriate time
Check that printing/faxing is working

Verify that the user's Print/Fax defaults are set

Make sure all network communications are in place
Ensure external access to the system available
Make sure remote printers/services are available

2) Wit pour and verify data

h Verify that pre-conversion data cleanup is complete.
Describe the data conversion sequence.
Stream Downloaders
Sequence of interface table creation programs
Sequence loading programs
Sequence translation programs
Sequence interface/validation programs
Run the conversions (see Cutover Conversion Plan)
Enter manual conversions (see Cutover Conversion Plan)
Verify the converted data (see Cutover Conversion Plan

Secure acceptance that converted and verified data meets defined compliance standards
3) Veri determine production availability
Review the Production Availability Verification Checklist
Perform production readiness check
Confirm the production cut.
Prepare the support team
Obtain agreement for initial production schedule
Verify that users are trained
Verify the commitment (formally assigned dedication time) and preparation of internal and external
support staff.
Verify completion of the production environment.
Confirm the commitment of senior management through the steering committee
Distribute the initial production schedule
Obtain approval to begin production.
4) Sta io in production environment
rt Start using the production system.
Initiate incident/technical problem management procedures

EI Toolkit
Document version 1.0, June 3 of
2002 21
Last validated: June 2004
 duration planned planned
task owner dependence in hours start date end date
Launch open issues and create a resolution list
Start support
Confirm that all components of the production system are operational.
Confirm the new system live (go live and acceptance)

EI Toolkit
Document version 1.0, June 4 of
2002 21
Last validated: June 2004
nsition for your specific project.

Close
status activity Others involved

EI Toolkit
Document version 1.0, June 5 of
2002 21
Last validated: June 2004
 Close
status activity Others involved

EI Toolkit
Document version 1.0, June 6 of
2002 21
Last validated: June 2004
 Close
status activity Others involved

EI Toolkit
Document version 1.0, June 7 of
2002 21
Last validated: June 2004
 Close
status activity Others involved

EI Toolkit
Document version 1.0, June 8 of
2002 21
Last validated: June 2004
Cutover plan for conversions

The Cutover conversion plan must be created in detail by technical leaders. This plan will include owners and firms responsible for conversions and
verification. as well as what conversions are required, their type, during and sequence.

Use this to-do list to move the conversation process forward. Third-party consultants should help you refine it for your specific project.
Conversions technical owner Process owner Duration Start date End date Tester Close activity

11/13/2019 00:37:23 446648496.xls 9 of 21

Note: Most major software vendors and system integrators include similar concepts and tools in their methodology. If that's the case for your program, use
these spreadsheets (created from a combination of methodologies from software vendors such as a checklist or guide to ensure your transition
process is complete.

Use this checklist/logout as a final verification that you're ready to go live. Owners must

Acceptance process completed

SRM Requirements
Full integration test PR MANAGERS EYECT FOR REV ISAR AND R
Complete end user training THIS LIST OF SEE ENTON CONFIRMS
CES WILL BE D BY
RIFICATION REVIEWED
Documents of completed procedures EVERY AREA
Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature THIS SECTION A COMPLETE
SRM Tenders SIMILAR TO THE BEFORE TO TWO
Full integration test THE STEPS TO EACH ZONE IS C SIGNED PO R LOS Ger
Complete end user training
Documents of completed procedures
Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
SRM Offers
Full integration test
Complete end user training
Documents of completed procedures
Final cutover checklist Owner Closing Date

11/13/2019 00:37:23 446648496.xls 10 of 21

 Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
Contract administration
Full integration test
Complete end user training
Documents of completed procedures
Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
Inventory management
Full integration test
Complete end user training
Documents of completed procedures
Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
Budget
Full integration test
Complete end user training
Documents of completed procedures
Distributed documentation

11/13/2019 00:37:23 446648496.xls 11 of 21

 Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
MRP/MPS
Full integration test
Complete end user training
Documents of completed procedures
Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
Payment management
Full integration test
Complete end user training
Documents of completed procedures
Distributed documentation
Ready team
Verified user accounts
Verified conversions
Complete manual conversions
Established communications
Final system test accepted
Help desk established
Legacy Systems and Stopped Entry
Final signature
Complete business closure
Deliveries THIS SECTION A COMPLETE
Payments to suppliers FROM THE PROPO DETAILS RITIONED BY ADA ARE
Production/Reported Inventory ON THE SHEET PLAN LCULO RECO ICATION RTES
Other steps OF C
Data conversion

11/13/2019 00:37:23 446648496.xls 12 of 21

 Review detailed cut over plan
Equipment configuration
Installed system
System configuration
Operational printers
Communications
Team members informed of Go/No-Go decision

Team members ready to GO

Team members ready to GO
Operational Issue Tracking
Operational Issue Tracking
Technical Validations
Sufficient disk space
sufficient memory
Verified production system
Legacy or previous systems, secured and turned off
signature management
Project Managers Signature
Sign clients
Client Manager Signature
Sponsor 1 signature
Sponsor 2 signature
Sponsor signature 3
Sponsor signature 4

11/13/2019 00:37:23 446648496.xls 13 of 21

 Ias.
are)

r the leaders of that area.

Final user acceptance

Complete closure
Conversion verification
Equipment verification
Communications setup
Technical verification

Final signature of closed

cutover plan

project entities

11/13/2019 00:37:23 446648496.xls 14 of 21

Complete information for distribution and reference during transition.
Insert rows for all functional/process areas instead of the 'XX' placeholder.

Cutover team and contact information

Role Function
Project Manager Provides administrative support: decisions, resources, direction
Project Manager Organize a detailed transition.
PCO Task Owner Lead the execution of the cutover plan
Migration team member Execute detailed tasks
Technical team member Deploy the production environment and perform data conversions.
Validation team member Responsible for the final validation of the production environment just before its release.

mobile phone
Role Name Hours Landline telephone number E-mail number
Project Manager
Project Manager
Owner Cutover Plan
SRM migration team
SUS migration team
GEDIC migration team
Migration Team Reports
Internal control validation team

Risk and compliance validation team

PCO validation team
Other validation equipment
Member 1 technical team
Member 2 technical team
Others:

Mobile phone
Role Name Hours Landline telephone number E-mail number
Executive
Sponsor 1
Sponsor 2
Sponsor 3
Sponsor 4
HR Manager
Owner training plan

11/13/2019 00:37:23 446648496.xls 16 of 21

Help Desk Owner (indicate MDA
operator contacts)

11/13/2019 00:37:23 446648496.xls 17 of 21

Location

Location

11/13/2019 00:37:23 446648496.xls 18 of 21

11/13/2019 00:37:24 446648496.xls 19 of 21
Note: Most major software vendors and system integrators include similar concepts and tools in their methodology. If that's the case for your program, use
these spreadsheets (created from a combination of software vendor methodologies) as a checklist or guide to ensure your transition process is complete.

Use this log as a sample of those components that should be traced for problems that arise during task cutting to guide you through the log or database used during the
other phases of the project. Whether or not a formal database exists, use it as a guide to ensure that tracking

PCO issues registry

Issue Issue
identifier opening Impact/ Deadline for Actual Actual End
Issue # name date Issue Description Importance Issue Type Owner completion state Date
1
2
3
4
5

11/13/2019 00:37:23 446648496.xls 20 of 21

gias.

the conversation process. Many projects use the same problem to

meet typical requirements.

11/13/2019 00:37:23 446648496.xls 21 of 21