Orchestrated epic systems migration cutover strategy switching downstream finance, HCM and SCM from legacy ERPs to Oracle Fusion in a 48–72 hour planned weekend blackout. Resolute downstream feed redirected, Willow/OpTime/Beaker OIC activated. Epic clinical operations continue untouched.
Epic clinical operations cannot pause for any cutover blackout. The cutover strategy has to switch the finance/HCM/SCM back-office while Epic continues unaffected — that's an orchestration problem not a software problem.
A non-healthcare ERP cutover can typically schedule a Friday-evening to Monday-morning blackout during which the entire enterprise stops transacting — payments paused, orders held, payroll-runs deferred. Healthcare cannot. EpicCare keeps documenting patient encounters minute by minute. Resolute keeps generating charges and downstream posting journals every few minutes. Willow keeps dispensing drugs at the bedside. OpTime keeps logging surgical case-cart materials. ASAP keeps tracking emergency arrivals. The clinical and revenue-cycle reality is 24/7/365 — cutover has to work around that.
The epic systems migration cutover strategy is engineered around this constraint. The blackout window applies to the back-office Fusion side only — Resolute's downstream feed endpoint, legacy ERP read/write, OIC integrations. Epic itself continues running. The cutover plan sequences these changes precisely: Friday 6pm legacy ERP cuts to read-only, Friday 8pm Resolute downstream feed endpoint reconfigured to Fusion GL endpoint (with Epic-side endpoint change taking 30–60 minutes), Saturday Fusion opens for back-office testing, Sunday delta capture and replay drills, Monday 6am production cut.
Throughout the blackout, delta capture stages every Resolute journal, every Willow dispense, every OpTime material consumption, every Beaker reagent consumption. At Monday open, the deltas replay in chronological order into Fusion through the new feeds. Within 4–6 hours of open, the backlog is cleared and Fusion is fully current. Reconciliation runs concurrently and confirms zero gap, zero double-post. The CFO sees an unchanged Resolute AR aging and a clean Fusion GL. Clinicians and billing staff don't notice the cutover happened.
Each decision frozen at the go/no-go gate. Two prior clean reconciliation evidence packs are the precondition.
Cutover scheduled outside 60 days of CMS cost-report due date, 30 days of 990 filing, 14 days of state regulatory filings. Year-end blocks the entire quarter.
Resolute downstream feed endpoint reconfiguration window scheduled with Epic technical team. 30–60 minutes during blackout. Pre-tested in non-prod twice.
Steady-state OIC integrations for pharmacy, surgical, lab activate during blackout. HL7 v2 / FHIR R4 / Interconnect endpoint updates pre-staged.
Cutover scheduled between payroll cycles to avoid payroll-run-during-cutover risk. Typical: cutover within 2 days post-payroll, no payroll for 4–6 days post-cutover.
Inventory cycle count programmes paused for 7 days pre-cutover and 7 days post-cutover. Avoids count discrepancies confused for migration variance.
Cutover decision predicated on two consecutive clean monthly reconciliation evidence packs. Single-period clean is not enough — variance can be coincidence.
From go/no-go gate through Monday open. Each phase has explicit owner and explicit decision criteria.
Five sign-offs at the go/no-go meeting: CFO (financial readiness), CIO (technical), Epic technical director (Epic-side endpoints), internal audit (controls), CMIO (clinical-stays-untouched). Any single no-go postpones.
6pm: legacy ERP cuts to read-only. 7pm: final Resolute downstream journal posted to legacy ledger. 8pm: Resolute downstream feed endpoint reconfigured to Fusion GL (Epic-side change). 11pm: Fusion opens for back-office testing.
Migration ops team runs Fusion-side validation: AR opening balance reconciliation against Friday Resolute snapshot, Worker count, Inventory on-hand. Any blocking variance triggers rollback decision at 24-hour mark.
Delta capture pipeline running for blackout-window transactions. Replay drills run against staging. Reconciliation runs catch any error in the replay logic before Monday open.
6am: Fusion opens for production. Resolute downstream feed posts first journals to Fusion GL. Willow/OpTime/Beaker OIC integrations activate. Delta replay starts and completes within 4–6 hours.
First-day stabilisation: reconciliation confirms zero gap and zero double-post. Open issues triaged by the migration ops team. CFO and internal audit walk the Monday end-of-day evidence pack.
Six engineered differences that minimise blackout window, prevent rollback, and keep Epic clinical operations untouched.
48–72 hours not 5–7 days. Delta capture means transactions don't accumulate in a frozen state — the system keeps capturing through blackout.
Cutover pre-rehearsed twice in non-prod with full delta capture and replay drills. Production cutover is the third execution, not the first.
Cutover decision predicated on demonstrated two-month clean reconciliation — not a single-period optimistic snapshot.
Rollback decision points at 24-hour intervals. Past 48 hours rollback requires separate weekend — but two prior clean months means it almost never reaches 48 hours.
Chronicles, EpicCare, Hyperspace, Resolute clinical/revenue-cycle, Willow/OpTime/Beaker all continue running. Cutover is back-office only.
Epic-side endpoint changes (Resolute downstream feed, Interconnect for Willow/OpTime/Beaker) pre-staged and pre-tested. 30–60 minutes execution during blackout.
An epic systems migration cutover strategy is the orchestrated plan that switches your downstream finance, HCM and SCM stack from legacy ERPs (Lawson, PeopleSoft, McKesson, on-prem EBS) to Oracle Fusion — without interrupting Epic clinical operations or the Resolute HB/PB revenue cycle. It covers go-live timing relative to month-end close, year-end and CMS cost-report deadlines; sequencing of legacy ERP read-only cut; Resolute downstream feed cutover from legacy ledger to Fusion GL; Willow/OpTime/Beaker steady-state OIC integration activation; delta capture and replay during the cutover blackout; CFO and clinical informatics sign-off; rollback contingency. The cutover happens on a planned weekend with Epic operations continuing untouched throughout.
For a regional health system the cutover blackout is typically 48–72 hours over a weekend (Friday 6pm to Monday 6am). During the blackout: final delta capture from legacy ERP runs, Resolute downstream feed switches from legacy ledger to Fusion GL, legacy ERP cuts to read-only, Fusion is opened for production transactions, OIC integrations for Willow/OpTime/Beaker activate. Epic clinical and Resolute revenue-cycle operations continue unaffected throughout — clinicians and billing staff don't notice the blackout. AP cheque runs, payroll runs and inventory replenishment cycles are scheduled outside the blackout. Academic medical centres with larger transaction volume sometimes need a 96-hour blackout — still over a planned weekend.
Resolute HB and PB continue to generate downstream AR posting journals throughout — that's the steady state both before and after cutover. What changes at cutover is the destination. Before cutover, Resolute posts to the legacy ledger (Lawson/PeopleSoft/McKesson). At the cutover blackout window, Resolute's downstream posting endpoint is reconfigured to post to Fusion GL via OIC + FBDI. The last legacy-ledger posting at Friday close-of-business; the first Fusion GL posting at Monday open. Reconciliation confirms zero gap, zero double-post. The Epic side of this change is minimal — your Epic technical team updates the Resolute downstream feed endpoint configuration. Epic operations continue.
Steady-state integration with Fusion Inventory + Cost Accounting + Procurement activates at cutover. Pre-cutover the bulk migration loads historical Willow/OpTime/Beaker inventory and transaction history; at cutover the steady-state OIC + HL7 v2 / FHIR R4 / Interconnect integrations activate. Willow pharmacy dispenses → Fusion Inventory consumption. OpTime case-cart materials → Fusion Materials Management. Beaker reagent consumption → Fusion Inventory. Each integration runs through OIC with retry, dead-letter and reconciliation built in. Epic-side configuration is the Interconnect endpoint update — usually a 30-minute Epic technical change. Pharmacy/perioperative/lab operations continue unaffected.
Resolute AR aging stays in Resolute — that's the system of record for patient and payer billing. What changes at cutover is how the consolidated AR balance appears in the GL. Pre-cutover the AR balance posts to the legacy ledger. At cutover Friday close, a final AR snapshot is taken and posted to the legacy ledger one last time; then the AR closing balance is migrated to Fusion GL as an opening journal entry. Monday open, Resolute posts its first new AR journal to Fusion GL via the new downstream feed. The CFO sees an unchanged Resolute AR aging report and an opening Fusion GL AR balance that reconciles to the cent against the Friday Resolute snapshot. No AR data is lost, no AR is double-counted.
Even with a planned blackout, some transactions occur — Resolute keeps generating downstream journals, Willow keeps dispensing drugs, OpTime keeps logging cases (the clinical side cannot stop). Delta capture catches all of these into a staging area during the blackout window. At Monday open, the deltas are replayed in chronological order into Fusion: Resolute journals post to Fusion GL via the new feed, Willow dispenses post to Fusion Inventory, OpTime materials post to Fusion Materials. Each replayed transaction goes through the same three-tier reconciliation as bulk loads. Within 4–6 hours of Monday open, the delta backlog is cleared and Fusion is fully caught up. Reconciliation confirms zero gap.
Five sign-offs at the go/no-go meeting, typically Wednesday before the planned weekend cutover. CFO signs financial readiness based on the two prior clean monthly reconciliation evidence packs. CIO signs technical readiness. Epic technical director signs Epic-side configuration readiness (Resolute downstream feed endpoint, Willow/OpTime/Beaker Interconnect endpoints, no Chronicles risk). Internal audit signs control readiness. Chief medical informatics officer (CMIO) signs the "clinical stays untouched" guarantee — this is the critical one for healthcare. Any single no-go from these five postpones the cutover to the next scheduled window (typically 2–4 weeks later).
Rollback is hour-by-hour. Hours 0–24 of blackout: if any blocking issue surfaces, decision to rollback at 24-hour mark. Rollback re-points Resolute's downstream feed to the legacy ledger, replays the blackout-window deltas into the legacy ledger, reactivates legacy ERP from read-only. Total rollback time: 4–8 hours, completed within the planned blackout window — operations resume Monday open as if no cutover attempted. Hours 24–48: rollback gets harder but still possible — additional 12–16 hours work, replay deltas, reactivate legacy. Past hour 48: rollback would require a separate planned weekend. The reconciliation framework's two-clean-month gate is designed precisely to ensure the cutover doesn't reach the rollback decision point.
Book a 30-minute cutover strategy workshop. We'll walk through your year-end timing, payroll alignment, Resolute endpoint redirect plan, Willow/OpTime/Beaker OIC activation and rollback design. Concrete cutover plan before the call ends.