Tips for Enterprise Production Cutover Projects
What is production cutover?
Production cutover is the transfer of the Enterprise Project solution from the project team to the business. It starts with the creation of the production instance the phase will close following the first month end transacted on your erp/crm (EBS, , Siebel,PSFT, JDE,...)
This is where you initiate your planned recipe for cutover week:
Example of statements that should be included: No Legacy systems will be available during cutover week except for the Payroll process.
You should also outline the manual transaction mechanisms that will be used to capture and maintain business operations if any systems remain operational.
The production cutover plan, outlines all the process steps and manual procedures/activities to be executed in the migration of Legacy systems to Oracle, also identifies and assigns resources and management to each control process , including sequences of all tasks using linked dependencies to set dates for deliverables, and identifies and integrates all other points of coordination.
Tips: One item that is usually overseen is task duration, we all tend to be optimistic add some slack, the point the longer you take to perform your task the more pressure is added to your colleague, and make sure you check all dates on your plan, in most cases an enterprise wide implementation takes longer than a day.
Here is a high level flow of production cutover team diagram:
Be very careful that all transactions are accounted, workflows complete (as much as possible), payments complete. Review cutover best practices for more detailed advice (ping your consultants, they’ve done this before). If you don’t do this you will hit serious problems.
Cutover is a stressful time no matter how well planned. The Project Manager should ensure everyone stays calm, ensure work is balanced and avoid burn-out for those working shifts. Organize some food during the cutover, step in to calm any friction quickly and monitor every last aspect of progress.