3.3 Cutover Planning

Last updated
Save as PDF

Overview

Cutover planning is key to ensure that production environment is prepared and a strategy is developed to import data and connect any related systems successfully in advance of go-live. Ops Sizing allows production infrastructure to be prepared to handle required numbers of master data and expected volume of transactions. As Coupa is dependent on other source systems for master data it is important that planning includes any activities that must be done in those systems to import valid up to date information. It is recommended that any legacy transactions are finished out in old system to allow for smooth transition into Coupa where all of transaction data starts there. Customers typically will aim to close out stale open POs to reduce number of open orders. If there is still need to import legacy POs into Coupa then only those open amounts that are yet to be invoiced and received are brought in via file uploads or manually created for small volumes.

Activities

Activity	Key Inputs	Roles & Responsibilities	Deliverables	Supporting Documents
Review data volumes and finalize ops/infra sizing document	Client, Partner, Coupa PS	For partner led implementations, partner is responsible for providing the data volumes. Coupa TS technical architect is responsible for ensuring that the partner does this. Coupa TS technical architect is responsible for getting the data volumes for Coupa led implementations Coupa TS technical architect is responsible for reviewing the data volumes and then submitting the ops/infra sizing document for Ops and performance review	Sign off from Coupa Ops and performance teams on the instance sizing	Ops sizing template
Master Data loading strategy for MTP	Client, Partner, Coupa PS	Coupa TS technical architect is responsible for reviewing the master data load strategy, associated task, project plan and providing appropriate guidance to the partner and client.	Signed off (Coupa, partner and client) master data load plan
Review strategy and plan to load historical/open transactions into Coupa as part of MTP/Go-live	Client, Partner, Coupa PS	Coupa TS technical architect is responsible for reviewing the transactional load strategy, associated tasks, project plan and providing appropriate guidance to the partner and client.	Signed off (Coupa, partner and client) transactional data load plan
Schedule MTP plan review	Client, Partner, Coupa PS	Partner/Coupa PM is responsible for scheduling this call with Client and Coupa TS technical architect Coupa TS Technical architect is responsible for reviewing the technical/integrations related tasks and provide feedback to the project team.	Signed off (Coupa, partner and client) MTP plan	See "MTP Checklist" in Move to Production section