Cutover Plan Template
Cutover Plan Template
Cutover Plan Template
Note: Most leading software vendors and systems integrators include similar concepts and tools in their methodologies.
If that is the case for your program, utilize this these spreadsheets (created from a combination of software vendor's methodologies)
as a checklist or guide to ensure that your cutover process is complete.
Use this list of tasks to validate that your cutover plan is complete. Your system integrator should plan a key role in creating a cutover plan for your specific project.
Cutover Plan
owner:
start date:
end date:
EI Toolkit
Document version 1.0, June 2002 1 of 12
Last validated: June 2004
Duration Planned Planned
Task Owner Dependency in hours Start Date End Date Status Signoff Others involved
Secure access to the production
environment
3) Prepare User Learning Environment
See EUT Plan for details
4) Set Up Applications
Set up the application users in the new
system
Set up and compile the key flexfields
Enter the application setups
Load the initial setup data
Implement the security configuration
Register the application objects
EI Toolkit
Document version 1.0, June 2002 2 of 12
Last validated: June 2004
Duration Planned Planned
Task Owner Dependency in hours Start Date End Date Status Signoff Others involved
Back up the production environment for later
availability
Validate the acceptance test environment
Execute the acceptance test script
Document the results
Determine required actions for problem
resolution
Make recommendations for application
changes or corrections based on
acceptance testing
Secure acceptance of acceptance test
results
Final Cutover
1) System and Network administration
Shut down legacy systems at appropriate
time
Verify Printing/Faxing is working
Verify user Printing/Faxing defaults are set
up
Ensure all network communications are in
place
EI Toolkit
Document version 1.0, June 2002 3 of 12
Last validated: June 2004
Duration Planned Planned
Task Owner Dependency in hours Start Date End Date Status Signoff Others involved
Verify the converted data (see Cutover
Conversion Plan)
Secure acceptance that the converted and
verified data meets century date compliance
standards.
3) Verify Production Readiness
Review the production readiness verification
checklist
Conduct production readiness verification
Confirm the production cutover
Prepare the support team
Obtain agreement for the initial production
schedule
Verify that users are trained
Verify commitment and readiness of internal
and external support personnel
Verify the completion of the production
environment
Confirm senior management commitment
via the steering committee
Distribute the initial production schedule
Obtain approval for beginning production
4) Begin Production
Initiate using the production system
Initiate incident/technical issue management
procedures
Initiate open issues and create a resolution
list
Initiate support
Confirm that all components of the
production system are operational
Declare the new system live
EI Toolkit
Document version 1.0, June 2002 4 of 12
Last validated: June 2004
Duration Planned Planned
Task Owner Dependency in hours Start Date End Date Status Signoff Others involved
EITK 0604
EI Toolkit
Document version 1.0, June 2002 5 of 12
Last validated: June 2004
Note: Most leading software vendors and systems integrators include similar concepts and tools in their methodologies.
If that is the case for your program, utilize this these spreadsheets (created from a combination of software vendor's methodologies)
as a checklist or guide to ensure that your cutover process is complete.
Use this checklist/signoff as a final verification that you are ready to go live. Owners should be the lead for that area.
Final signoff
Role Function
Program Manager - Provides management support - decisions, resources, direction
Project Manager - Organizes detailed transition
Cutover Owner - Leads the execution of the cutover plan
Migration Team Member - Execute the detailed tasks
Technical Team Member - Implement production environment and performs data conversions
Validation Team Member - Responsible for final validation of prod'n environment just before go live
Others:
Use this log as a sample of those components that should be tracked for issues that arise during cutover of tasks to step you through the converstion process. Many projects utilize the same
log or database used during the other phases of the project. Whether a formal database is in place or not, use this as a guide to assure your issue tracking meets the typical requirements.
Target
Date Impact/ Completion Current Completion
Issue # Initiator Opened Summary Description Importance Type Owner Date Status Date Resolution
1
2
3
4
5
….