Stage 9: Go-Live
Execute the beginning-balance plan chosen in Beginning Balance Decisions. The same balance items and options carry forward onto the execution board. As each load finishes, the team marks items completed. The board list mirrors Beginning Balance Decisions (scope and depth already decided in Stage 7; item-level labels and estimates live in the options reference).
Stage 7 decided what to load and at what depth. Stage 9 is where the team runs those selections and tracks completion through go-live.
phase_key: beginning_balance_load_go_live
What this stage accomplishes
- Stage 7 selections appear on the Go-Live execution board; the team works that list and marks each balance item complete as the load finishes.
- For each in-scope balance, Balance Guidance covers interface settings, report validation, and a sample file layout for TAD loading.
- Overall completed vs remaining balances are visible in the stage summary for cutover status.
- Leadership confirms readiness for Stabilization handoff.
Typical work / artifacts
- Execution board driven by Stage 7 beginning-balance selections (empty until Stage 7 is finalized)
- Per-balance Balance Guidance (interface settings, named Vista report checks, sample Excel layout)
- Linked Tracker actions for remaining go-live work items
- Stage summary of balances completed vs remaining
- Executive readiness summary for Stabilization handoff
Execution board (mirrors Beginning Balance Decisions)
The board is populated from Stage 7. Same core objects and load-depth choices; here they become a working checklist. Mark an item complete when that balance load is actually done in Vista.
Do not re-decide scope or depth in this stage. If a selection must change, update Beginning Balance Decisions (and the options reference as needed), then refresh the board.
Balance Guidance
Balance Guidance is the unique depth for this stage: per balance item, three guidance areas that are not spelled out at this level elsewhere in the Playbook. Prefer the product UI for the circled form images and report screenshots; this page describes what to look for and why.
Interface settings
Most Vista modules that post transactions have a company parameters form that controls whether postings hit GL, Job Cost, Equipment, and related sub-ledgers.
For beginning-balance loads, those settings usually must be a specific value. In most cases they are turned off while balances are loading so the load does not create unwanted side postings.
Critical exception - Accounts Receivable: AR invoices should post to Job Cost so billed-to-date populates. Treat this as the primary (likely only) exception when most other interface switches are off for BB loads.
In the product, Interface settings shows the company parameter form with the required option circled, plus short text for where to go and what to select (target circled on the form image, not a before/after pair).
Report validation
After posting (for example job costs), run the named Vista report called out in Balance Guidance to validate the balance.
Guidance shows what to check. Example: Job Cost → Contract Cash Flow, with the cost to date total circled. That total must tie to what the client expects and to the prior ERP.
Sample file
Balance Guidance includes an Excel sample with the exact layout needed for that balance. Job Cost example columns: job, phase, cost type, amount, date, description, hours, units.
If the client can gather data in that layout, they can load via TAD: copy/paste and click through. Framing: interface settings → load → validate with the named report → use the sample layout when gathering data for TAD.
Keep this stage on execution and guidance. Deep Vista procedures and every product screenshot belong in the Balance Guidance UI and related Tracker / Implementation Balance articles, not as an exhaustive dump here.
Stage summary
End of stage shows overall balances: how many completed vs remaining. Use it as a cutover-status reference before Stabilization handoff.
Connection to Company Tracker / Vista
Linked actions on the execution board refresh against Company Tracker. Tracker rows depend on prior Stage 7 visibility sync and company-specific data. Balance loads and posting happen in Vista according to the Stage 7 plan and the interface settings / validation steps above.
Exit / moves to next stage
Go-Live is complete when in-scope balance loads are done (or remaining work is explicit), Balance Guidance checks have been applied where needed, and the team confirms readiness for post-go-live support. The implementation then moves to Stabilization.
In the product
In Mission Control, complete the Go-Live workspace (brief, execution board with Balance Guidance, stage summary, and executive readiness). For step-by-step UI, see Complete the Go-Live Stage. For shell navigation and exports, see Run the Implementation Playbook.