EHR cutover planning is the disciplined translation of a go-live date into a sequenced set of technical, operational, and workflow steps that move an organization from legacy systems to a live production environment. The Washington HCMACS Enterprise EHR Roadmap defines cutover planning as finalizing and validating detailed plans outlining all technical, operational, and workflow steps required to transition to the live system, with two full dry runs conducted before the March 2028 go-live [1]. A cutover plan is not a single-day checklist. It spans pre-cutover preparation, the activation window itself, and post-cutover stabilization, with explicit contingency procedures for a no-go decision [7]. The practical value lies in making dependencies visible before activation: interface validation, data reconciliation, user readiness, and support escalation all converge on the same date. Organizations that treat cutover as a rehearsal-driven process rather than a calendar event can identify sequencing failures while there is still time to correct them.

What a Cutover Plan Actually Contains

The General Services Administration's M3 Playbook separates cutover into pre-cutover, cutover, and post-cutover steps, with the plan integrated into the communication and program go-live schedule [7]. Pre-cutover tasks include executing preparatory activities and scheduling checkpoints to monitor progress. The cutover itself involves deploying code, activating system components, and transitioning or retiring legacy IT. Post-cutover work initiates warranty period support and updates the decommission plan for legacy systems [7]. This three-part structure matters because failures in any segment cascade into the others. A cutover plan that omits legacy decommissioning leaves duplicate systems running, while one that skips post-cutover support planning strands users during the highest-volume help desk period.

Washington's HCMACS program illustrates how these components are sequenced against a fixed date. The roadmap specifies that third-party systems must be validated for production in January 2028, with all interfaces tested and confirmed stable and all dependencies operational [1]. Cutover plan validation through two full dry runs is also scheduled for January 2028, followed by go-live readiness approval and end-user training completion in February 2028 [1]. The ordering is deliberate: interface stability and rehearsal completion precede the final readiness decision. A cutover plan therefore functions as a dependency map, not merely a task list. Each step carries a definition of done that must be satisfied before the next phase can proceed.

Dry Runs as Sequencing Validation

Dry runs are the primary mechanism for testing whether a cutover plan's sequencing will hold under operational pressure. The HCMACS program conducts two full cutover dry runs in December 2027 and January 2028 to simulate go-live activities, validate sequencing, test contingency plans, and ensure staff readiness to execute cutover procedures [1]. The milestone definition specifies that two full cutover rehearsals are completed, with sequencing, roles, and contingency plans validated [1]. This is distinct from functional testing. Dry runs test the transition process itself: whether the order of system activations, data migrations, and interface cutovers can be executed by the assigned people within the available window.

The National Learning Consortium's go-live planning checklist extends this rehearsal concept to the clinical workflow level. It recommends accompanying the go-live checklist with a rehearsal of the go-live day, using a test environment to perform each application function, including staff role-playing activities to practice patient communication and help desk contact procedures [8]. This dual rehearsal approach addresses two different failure modes. Technical dry runs expose integration and sequencing defects, while workflow rehearsals expose usability and communication gaps. A cutover plan that validates only one dimension can pass technical review while failing on the first day of real patient encounters.

A Suggested Cutover Dry Run Sequence for a Mid-Sized Clinic

As a planning exercise, a mid-sized clinic could structure its first dry run around the three-part GSA framework. Pre-cutover: confirm that lab and billing interfaces have passed production validation, reconcile medication and allergy data in the legacy system, and verify that all users have completed role-based training with competency thresholds met [1][4]. Cutover: execute the activation sequence in a test environment, including legacy system read-only conversion, interface cutover, and initial data verification, with assigned roles for each step [7]. Post-cutover: simulate the first patient encounter, test help desk escalation procedures, and run a command center checkpoint meeting to review issues [7][8]. The second dry run would then repeat this sequence with corrected defects and a compressed timeline to test contingency triggers. This is a suggested structure, not a tested protocol, and each organization's interface inventory and staffing constraints would require adjustment.

Data Reconciliation and Legacy System Transition

Data readiness is a cutover dependency that must be resolved before activation, not discovered afterward. The HCMACS roadmap lists data reconciliation as a milestone, with data reconciled and ready for use at go-live [1]. The Indian Health Service Readiness Guide for PATH EHR identifies a specific risk in this area: hybrid operation of legacy and new systems for an extended period increases billing backlogs in two systems, compromises billing staff proficiency in the new patient accounting system, increases error risk, and may materially impact cash flow and patient satisfaction [4]. The guide recommends proactive revenue cycle stabilization prior to cutover to protect mutual integrity during transition [4].

Clinical data cleanup follows a parallel path. The IHS guide directs organizations to conduct a comprehensive review and update of existing medication, allergy, and problem list data within the current system to ensure accuracy, completeness, and clinical reliability [4]. Specific actions include reconciling medications during patient interactions, verifying allergy details, confirming active problem lists, and engaging clinical staff to validate entries and remove outdated or duplicated information [4]. This work is time-consuming and cannot be compressed into the final week before go-live. Cutover planning must therefore schedule data cleanup as a distinct workstream with its own completion criteria, separate from technical interface testing.

Go/No-Go Criteria and Contingency Triggers

A cutover plan is incomplete without explicit decision points that authorize or halt activation. The GSA playbook states that if a go decision is made, the cutover plan is executed and activities are monitored toward deployment; if a no-go decision is made, contingency plan procedures are executed [7]. The playbook lists go/no-go readiness criteria and a go/no-go assessment report as inputs to the cutover planning process [7]. This means the contingency plan is not an afterthought. It is a defined procedure with its own triggers, resources, and communication steps, ready to activate if readiness thresholds are not met.

The HCMACS program operationalizes this through staged readiness assessments. Go-live readiness assessments at 120, 90, 60, and 30 days are completed, with risks mitigated and governance approval obtained to proceed [1]. The roadmap also identifies a specific risk: users not adequately trained or prepared to operate in the system at go-live [2]. This risk is addressed through training completion tracking and Day-in-the-Life activities, where users participate in scenario-based simulations and validate workflows across roles, with gaps identified and addressed prior to go-live [1]. The staged assessment cadence creates multiple opportunities to invoke contingency procedures before the activation window, rather than discovering a fatal gap on cutover day.

Post-Cutover Stabilization and Support Handoff

Cutover planning extends beyond the activation moment into the stabilization period. The HCMACS roadmap defines Phase 3 as go-live and stabilization from March to June 2028, during which the program executes go-live, stabilizes system operations, and transitions users and support teams into steady-state workflows [1]. Structured support models including Command Center operations, What to Do sessions, and Thrive training are used to reinforce user adoption, resolve workflow gaps, and improve efficiency [1]. The phase is complete when system performance is stable, high-priority issues are resolved, support volumes have normalized, users are operating effectively, and a Final Acceptance Review confirms readiness to transition to steady-state operations [2].

The GSA playbook's lessons learned reinforce the importance of planning for this period before cutover occurs. It recommends establishing an ongoing and committed contact center support at each organization to support the go-live transition, having all key subject matter experts available onsite during final pilot trial and actual deployment, and conducting daily meetings to monitor progress and issues for timely resolution [7]. These recommendations imply that post-cutover support is a staffing and communication commitment, not a technical configuration task. A cutover plan should name the support escalation path, the daily checkpoint cadence, and the criteria for transitioning from command center operations to routine help desk support.