Scribd
Upload
57 views9 pages

7.2-Cut Over and Golive V1.0

The document discusses cutover and go-live activities for an ERP implementation project. It explains that cutover is the transition from the old to new system, which requires planning transaction cutover dates. The criticality of transactions must be understood to minimize business disruption during cutover. Go-live is when the company begins fully using the new ERP system. Thorough preparation is needed before go-live, including completing all configurations, testing, training, and ensuring prerequisites like data migration are finished.

Uploaded by

jon bern
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
57 views9 pages

7.2-Cut Over and Golive V1.0

The document discusses cutover and go-live activities for an ERP implementation project. It explains that cutover is the transition from the old to new system, which requires planning transaction cutover dates. The criticality of transactions must be understood to minimize business disruption during cutover. Go-live is when the company begins fully using the new ERP system. Thorough preparation is needed before go-live, including completing all configurations, testing, training, and ensuring prerequisites like data migration are finished.

Uploaded by

jon bern
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

1

IEI-4B2 – Enterprise Resource Planning

CUT OVER AND GO LIVE

Ari Yanuar Ridwan

S1 Teknik Industri – Fakultas Rekayasa Industri


2

CUT OVER

• Cutover is the final stage of ERP realization before the


company moves on to the new system. Based on
• the implementation approach, a company may take up few
modules for cutover (phased implementation
• approach) or complete cutover (for all the modules).

2
3

Cutover Planning

• For moving from old system to new ERP application, activities need
to be planned in minute details and transactions need to be stopped
in the old application for a brief period and moved to the new ERP.
• In the example, transactions in the old system is completed on 28th
and three days are planned to move the open items to the new
system before the changeover happens in the new system on 1st.
• A real-life cutover plan for a company having multiple factories and
distribution centers can be really complex.

3
4

Understanding Criticality of Transaction for Cutover Planning

• Cutover need to be planned in a way that there is minimum business disruption. It is


important to understand the criticality of the transaction before planning the cutover.
• There are some critical business transactions like customer ordering, invoicing, etc. which a
business would never like to stop as there may be chances of revenue loss, whereas
something like creating a maintenance order or creating new purchase contracts for vendors
can be differed by a week.
• Typically minimum downtime is taken for most critical transactions, i.e. last sales order and
invoice can be entered in old system up to Friday night and from Monday morning, these
will be done in the new system, whereas for not so critical transactions, a little more
downtime can be considered.
• Understanding this criticality is important and this need to be a senior management
decision for the company going for ERP as typically every department in the company
believe their transactions are most critical.

4
5

GO LIVE

• The day a company moves from the old legacy system to the
new ERP application is called “Go Live” date.
• Ideally, a company should complete all its ERP project related
activities before going live, though in reality it is far from
truth and in most cases, projects go live with several open
issues.
• However, it is important that before “Go Live”, all critical
project activities are completed.

5
6

GO LIVE PREPARATION

• All configurations
• All developments
• All testing (Unit testing, integration testing, user acceptance testing)
• Trainings of core ream, power users and end users
• Data migration completed
• All authorizations are created and authorization testing completed
• In most ERP implementations, before going live, there will be a list of

6
7

Go Live Checklist

• External Certifications • Cutover Plan


• Infrastructure • Quality Assurance
• User Workstations • End User Training
• Printers • Support
• Security • Communication/Change
• Management

7
8

Summary
• Cutover and go live is the final stage of ERP project realization before the company moves to
the new system. These activities need lots of planning for smooth transition to the new
application.
• Cutover planning details on which date the transactions from the legacy application will
stop. Post this date, the selected transactions will happen in the new system. This activity
needs to be planned looking at criticality of transactions, i.e. ensuring as less downtime as
possible for critical transactions.
• Go live checklist is a ready reference document for all the points that need to be considered
before going live. Go live decision needs to be taken only when all these critical check points
show a green status. There
• can be few not so critical open points while going live that need to be closed within an
agreed time-frame.
• It is always recommended to have a third-party audit before going live.

8
9

THANK YOU

You might also like