Skip to main content
Share / Export

Stage 8: Cutover Readiness

Cutover readiness before Go-Live. Three pieces: Company Copy, Cutover Schedule (work streams with last day in legacy and first day in Vista), and Launch Confidence, ending with a stage summary of those decisions.

Prefer Cutover Schedule language for the middle piece (not “launch week”).

phase_key: cutover_readiness

What this stage accomplishes​

  • Company Copy scope is decided: which ordered / grouped setup tables move from the tested company into live (core setup only; no transactional records), including any client deselections.
  • The Cutover Schedule lists work streams with last day in legacy, first day in Vista, and an owner from the team roster (core set plus any custom streams).
  • Stakeholders record Launch Confidence (1-10), can see everyone’s vote, and edit only their own; the team records Green light, Conditional go, or Hold.
  • A stage summary captures Company Copy decisions, work streams with dates and owners, and team votes so Go-Live execution has a clear readiness picture.

Typical work / artifacts​

  • Company Copy selection (tables in product order / groups; deselect where a fresh import is preferred)
  • Cutover Schedule: work streams, last-day / first-day dates, owners
  • Launch Confidence votes and go signal (Green light / Conditional go / Hold)
  • Stage summary of those three decision areas

Company Copy​

Configuration and setup typically live in the test company. After users test and validate that setup works, Company Copy copies core setup only (no transactional records) into the live company. Live starts with tested setup and no transactions so the team can load beginning balances, then enter live transactions.

Structure​

  • Broken down by tables that can be copied
  • Specific order and grouping
  • Clients can deselect tables / setups (examples: vendors, open jobs)

Caution: fresh import vs copy​

If a list is stale (for example nine-month-old vendors), the team may prefer a fresh import instead of copying. Keep data in correct Vista format. Avoid creating a lot of new manipulation just to get records back into Vista shape. Prefer keeping Vista-ready data when you choose copy or import.

Prerequisite: HQ company setup before copy​

Whether the copy is done by the user, by consulting using TAD, or by Trimble, ensure the full HQ company setup exists before Company Copy starts. Groups associated with that HQ company record determine what values need to be remapped during the copy (test-company groups into live-company groups).

Dependencies​

The product has dependencies built in: toggling a table off inactivates tables that depend on it.

Keep this stage decision-focused. Deep Company Copy table lists and Vista procedures belong in product how-tos, not as exhaustive procedures here.

Cutover Schedule (work streams)​

A schedule / calendar of work streams so implementers and end users know last day in legacy and first day in Vista for each area.

Example: last day entering AP on a date, that work converts into Vista, then first day they can enter AP in Vista.

Features​

  • Product provides a good core set of work streams
  • Clients can add custom work streams for their situation
  • Assign an owner from the team roster (for example the AP or Payroll person responsible for that area) who is known for “last day in legacy” and “ready to start in Vista”

Treat Cutover Schedule as a general cutover concept the whole team can plan around, not only a UI checklist.

Launch Confidence​

Team / stakeholder confidence vote that they understand their area of the software and are ready.

Rules / UX​

  • Confidence scale: 1 through 10
  • Users can see everyone’s confidence
  • Users can only edit their own

Go signals​

  • Green light
  • Conditional go (for example hoping X finishes in time; if so, go)
  • Hold (not ready / want to speak up)

Hold does not mechanically block the product. It is a final participatory vote so buy-in and readiness are visible.

Ideal outcome​

If the client did setup, training, and integrations correctly, this vote should be smooth and efficient.

Stage summary​

Stage 8 ends with a summary of:

  • Company Copy decisions
  • Work streams with dates (and owners as set)
  • Team member Launch Confidence votes

Connection to Company Tracker / Vista​

Company Copy, Cutover Schedule, and Launch Confidence are Playbook process controls for cutover readiness. This stage does not use a Company Tracker sync panel the way Core Configuration, Integrations, Testing & Training, or Beginning Balance Decisions do. Vista company copy and cutover execution follow the plan agreed here.

Exit / moves to next stage​

Cutover Readiness is complete when Company Copy scope, the Cutover Schedule (work streams, dates, owners), and Launch Confidence (votes and go signal) are recorded, and the stage summary reflects those decisions. The implementation then moves to Go-Live.

In the product​

In Mission Control, complete the Cutover Readiness workspace (Company Copy, Cutover Schedule, Launch Confidence, and stage summary). For step-by-step UI, see Complete the Cutover Readiness stage. For shell navigation and exports, see Run the Implementation Playbook.