Disciplined wind-down of the legacy ERP/HRIS stack sitting alongside Epic — Lawson, PeopleSoft, McKesson, ageing EBS. Licence termination, infra retirement, knowledge transfer. Epic Chronicles remains the active clinical system. $1–3M typical annual savings.
We are not retiring Epic. We are retiring the legacy ERP/HRIS stack that was sitting alongside Epic, once Oracle Fusion has taken over their workload and the cloud archive has taken over their retention obligation.
Healthcare organisations running Epic almost always have a constellation of legacy systems alongside it: Lawson HR and Lawson Finance for back-office (a standard pairing for 20+ years in healthcare); PeopleSoft HR/Payroll in many academic medical centres; McKesson Materials Management; regional practice management installs from pre-Epic ambulatory acquisitions; ageing on-prem Oracle EBS at some sites; legacy reporting tools like Cognos and MicroStrategy connected to all of the above. Each of these systems represents licence fees, infrastructure cost, vendor support contracts and institutional complexity.
Oracle Fusion go-live takes over the workload — finance, HCM, SCM, procurement. The Epic Systems cloud archive takes over the retention obligation — historical data lives in the queryable archive, satisfying state retention and audit requirements without keeping the legacy systems alive. Once both are in place, the legacy systems can be decommissioned. That's the epic systems decommissioning project: the disciplined sequence of licence termination, infra retirement, interface cutover and knowledge transfer that captures the multi-million-dollar annual savings.
Critically, Epic itself is unaffected. Chronicles stays as the operational EHR. EpicCare keeps running. Hyperspace stays on every clinical desktop. MyChart stays for patients. The clinical risk profile is zero. What's happening is a back-office consolidation: legacy ERP/HRIS retires, Oracle Fusion takes over, Epic stays the clinical system of record. This is the most common 2025–26 pattern in healthcare ERP modernisation.
Each one is a discipline that captures real savings — and avoids real risk.
Fusion stable for 1–2 month-ends. Archive loaded with retention-period data. Reports rebuilt. Interfaces re-pointed or retired. Knowledge transfer complete. No legacy system retires before its checklist is signed off.
Every Epic-to-legacy and legacy-to-Epic interface inventoried. Each one either retired (legacy endpoint gone) or re-pointed to Fusion via OIC. Confirmation from receiving endpoint required.
SME interviews recorded + transcribed, runbooks documented, customisations inventoried, integration map captured. Knowledge base survives the decommissioning.
Per legacy system: vendor licence agreement reviewed, termination notice timing observed, termination certificate captured. No 'oh we forgot to cancel' surprises.
Servers, databases, middleware, network equipment, integration platform — released in the right order so dependencies don't break the active environment.
Full data manifest, reconciliation pack, interface log, licence cert, infra log, knowledge artefact list — all hash-signed. CFO, CIO, internal audit sign-off before power-off.
A repeatable wind-down sequence applied per legacy system. Typical timeline per system: 3–6 months from Fusion go-live to power-off.
Fusion stable (1–2 month-ends signed off). Archive loaded with the legacy system's retention-period data. Reports rebuilt in OTBI / BIP. Confirmation from finance, HR, IT — all green-lit to proceed.
Every Epic-to-legacy and legacy-to-Epic interface inventoried. Each one re-pointed to Fusion via OIC with HL7 v2 / FHIR R4 modern patterns, OR retired (because legacy endpoint is gone). Receiving endpoints confirm cutover.
SME interviews recorded + transcribed. Runbooks for every operational process documented. Customisations inventoried + classified (replaced / obsolete / still-needed). Integration map captured.
Legacy system moved to read-only mode. Runs in that state for 60–90 days. Any access requests routed to archive. Confirms nothing critical was missed. Privacy officer + internal audit walkthroughs against read-only system.
Vendor termination notice issued per contract terms. Servers powered off, databases dropped (after archive confirms), middleware removed, network equipment released. Termination certificates captured.
Full evidence pack assembled: data manifest, reconciliation, interface log, knowledge artefacts, licence cert, infra log. CFO, CIO, internal audit sign-off. Legacy system is officially retired.
Concrete annual savings categories. Numbers are typical for a regional health system retiring Lawson + McKesson + PeopleSoft alongside Epic.
$500K–1.5M/year typical for legacy ERP/HRIS licence + vendor support fees terminated. Multi-instance academic medical centres often $1–3M/year.
Servers (often 5–15 per legacy ERP), database licensing (Oracle DB, SQL Server, DB2), middleware — typically $200K–800K/year per major system retired.
Operational support contracts with vendor for older systems often $200K–500K/year, plus internal FTEs maintaining the legacy stack who can be redeployed.
Legacy integration platforms (Mirth, Cloverleaf, older middleware) often $100–300K/year. Re-pointed to Oracle Integration Cloud which is typically part of the Fusion subscription.
Cognos / MicroStrategy / older BI tools connected to retiring systems can be terminated. Often $100–400K/year per BI tool. Reports rebuilt in OTBI / BIP.
Server racks, cooling, data centre footprint — savings increasingly material as ESG reporting matures. Often $50–200K/year per legacy ERP retired.
Important framing: we are NOT retiring Epic itself. Epic Chronicles remains the active clinical system of record. Epic Systems decommissioning in the Oracle Fusion context means retiring the legacy systems that were sitting alongside Epic — typically Lawson HR/finance, McKesson finance, PeopleSoft HR, legacy practice management, ageing on-prem EBS — once their workload has migrated to Oracle Fusion (for finance/HCM/SCM) and once their retention obligation is satisfied by the cloud archive. Epic stays. The legacy ERP and HRIS stack that was running alongside Epic gets decommissioned. That's the licence-saving, infra-saving, knowledge-transfer-completing project this page is about.
Because the legacy systems are held alive for three reasons before Fusion arrives: they're the system of record for finance/HCM/SCM workloads, they hold the retention-period historical data, and they have institutional knowledge embedded in their reports and processes. Oracle Fusion go-live solves the first reason. The Epic Systems cloud archive solves the second. Knowledge transfer + report rebuild solves the third. Once all three are addressed, the legacy ERP/HRIS that was sitting alongside Epic can be retired — typically Lawson HR, PeopleSoft, McKesson finance, ageing EBS, regional practice management installs. The Epic Systems decommissioning sequence is the disciplined wind-down that captures the savings.
Significant. Typical regional health system retiring Lawson HR + Lawson Finance + McKesson Materials + PeopleSoft Payroll alongside Epic: $500K–1.5M/year in software licence + support fees. Plus hardware (often 5–15 servers per legacy ERP), database licensing (Oracle DB, SQL Server, DB2 — often $200K–800K/year), middleware (often $100–300K/year), and integration platform fees. Plus operational support contracts with the vendor (often $200K–500K/year for the older systems). Total annual savings after full Epic Systems decommissioning typically $1–3M for a regional system, $3–8M for an academic medical centre with multiple instance consolidation. Numbers compound: every year the legacy systems stay alive is annual fees that don't come back.
Yes — and that's part of the value. Every legacy ERP sitting alongside Epic has interfaces in both directions: Epic Resolute → Lawson GL feed, Lawson HR → Epic provider master, McKesson Materials → Epic Willow inventory, etc. These interfaces are typically aging HL7 v2 messages, point-to-point flat files, or older Mirth/Cloverleaf integration engine flows. As part of Epic Systems decommissioning, each of these interfaces is either retired (because the legacy endpoint is gone) or re-pointed to Oracle Fusion via Oracle Integration Cloud (OIC) using modern HL7 v2 / FHIR R4 patterns. The result: a smaller, modern integration estate with Epic clinical + Oracle Fusion ERP/HCM + a handful of remaining clinical-only integrations.
Typically 3–9 months post-Fusion go-live, depending on the number of legacy systems and the readiness of the archive layer. The dependency chain: Fusion go-live must be stable (typically 1–2 month-ends signed off). The archive must be loaded with the legacy system's retention-period data. Reports rebuilt in OTBI / BIP. Integration interfaces re-pointed to Fusion or retired. Knowledge transfer complete (typically a knowledge capture project that produces runbooks + recorded SME sessions). Then the legacy system can move to read-only mode, run in that state for a confirmation period (typically 60–90 days), then be powered off, licences terminated, hardware released. Multi-instance academic medical centres often run a staggered Epic Systems decommissioning where one legacy system retires per quarter.
Knowledge transfer is a non-trivial part of Epic Systems decommissioning. Legacy systems have 10–20+ years of customisation: Lawson Form Files with custom logic, PeopleSoft Application Engine programs, McKesson custom reports, integration mappings nobody documented. Syntra ETL's knowledge transfer module captures all of this as part of the decommissioning project: SME interviews recorded and transcribed, runbooks for every operational process documented, customisations inventoried and classified (still-needed vs replaced-by-Fusion vs obsolete), integration interface map captured with current-state and target-state. Output is a Confluence/SharePoint knowledge base that survives the decommissioning. The legacy system can be powered off without losing institutional memory.
Yes — these are independent tracks. Epic upgrades happen on Epic's quarterly release cadence regardless of what's happening with downstream ERP. Epic Systems decommissioning of legacy ERP/HRIS systems happens on its own timeline, gated by Fusion go-live and archive completion. The two tracks coordinate around interface cutovers: when a legacy system's Epic interface is being re-pointed to Fusion, the change is coordinated through Epic's standard interface change management and any required Epic upgrade window. Otherwise the tracks run in parallel. We commonly see Epic Systems decommissioning of Lawson happening during the same fiscal year as an Epic May release upgrade, with no impact between them.
Comprehensive. Per legacy system being decommissioned: full data extraction manifest (every record extracted, hashed, archived), reconciliation pack (legacy source vs archive vs Fusion to the cent for finance, person-by-person for HCM, transaction-by-transaction for materials), interface retirement log (every interface either retired or re-pointed, with confirmation from the receiving endpoint), licence termination certificate from vendor, hardware decommissioning log, knowledge transfer artefact list. All evidence is hash-signed and retained for SOX, HIPAA, Joint Commission and any state audit purposes. CFO, CIO and internal audit each sign off on the decommissioning pack before the legacy system is powered off.
Book a 30-minute discovery call. Walk through your legacy ERP/HRIS inventory, current vendor contracts, Fusion go-live status and archive readiness. Concrete decommissioning sequence, savings projection and timeline before the call ends. Epic stays — only the legacy stack retires.