BytePad · Source system archival

Epic legacy instance archive for consolidations and M&A

The short answer: An Epic legacy instance archive preserves history from an Epic environment that is being retired after a merger, acquisition or instance consolidation. BytePad from InterScripts, listed in Epic Connection Hub, keeps that history retrievable for chart recall, release of information and legal hold, and can surface archived records to clinicians working in the surviving Epic instance.

Legacy Epic instancesClarity reporting dataMedia and document content

Plan your Epic archive See the BytePad platform

Why do organizations archive and retire Epic?

Legacy Epic instances appear most often after mergers and acquisitions. Two health systems on separate Epic instances consolidate onto one, an acquired hospital moves from its own Epic or a Community Connect arrangement onto the acquirer's instance, or an organization retires an older Epic environment after a re-implementation.

The surviving instance usually receives a defined set of converted data for active patients. The rest of the legacy history still has to be retained and produced for release of information, audits and litigation, and keeping a second Epic environment running only for look-up carries real hosting, licensing and staffing cost.

What does a Epic archive need to preserve?

Scope the archive around the jobs it must do once Epic is gone: chart recall, release of information, audit and legal hold, receivables follow-up, and retention through disposition.

Clinical record

Encounters, notes and clinical documentation
Orders, results, medication administration and flowsheet data
Problem lists, allergies, immunizations and health maintenance history
Surgical, anesthesia and ancillary documentation from modules in use
Imaging reports and references to images held in PACS

Revenue cycle

Hospital and professional billing history
Claims, remittances, payments and adjustments
Claims and remittance history, including X12 837 and 835 where retained
Open receivables and denial history not transferred at conversion

HIM and release of information

Patient identity and merge history, including cross-instance identity
Release-of-information requests and disclosure accounting
Chart completion and coding history
Access audit history for privacy investigations

Images and documents

Scanned documents and media stored with the chart
Outside records and correspondence
Signed consents and forms
Generated letters and patient summaries

What should you plan for when extracting Epic data?

Epic's operational database runs on InterSystems technology, with Epic moving from Caché to IRIS. Clarity, Epic's relational reporting database, runs on Microsoft SQL Server or Oracle and is populated by daily extracts from the operational database. Archive extraction commonly draws on Clarity together with document and media content, and must confirm completeness against the operational record for anything Clarity does not carry.
Coordinate with Epic and your contracts team on access, support and license terms for the legacy instance through the read-only window and final retirement. Agree who owns the legacy instance during the transition, especially when it belonged to the acquired organization.
Data converted into the surviving instance and data sent to the archive should be reconciled against each other, so that every patient and encounter is accounted for in one place or the other and nothing falls between them.
Document and media content often represents a large share of the volume. Plan its extraction, indexing and validation as a separate workstream.

How long must Epic records be retained, and what about legal holds?

Hospital records from a legacy Epic instance fall under the Medicare Conditions of Participation minimum of 5 years (42 CFR 482.24) and under state rules, which can differ when the merged organizations operate in different states. Apply the retention schedule of the state where care was delivered, by record type.

Mergers often bring litigation holds and audits that predate the transaction. Carry them into the archive at the record level, keep 42 CFR Part 2 controls on any covered records, and log every disposition decision for review.

Retention periods vary by state, record type and patient age. See hospital record retention by state and defensible disposition, and confirm the schedule with your counsel and records management team.

How does BytePad archive and retire Epic?

BytePad is listed in Epic Connection Hub in the Legacy EHR Archive category. Archived records from the retired instance can be surfaced to clinicians working in the surviving Epic system through patterns such as a Chart Review link or a SMART on FHIR app, so users do not need a second login to see legacy history.

Ingestion runs through BytePad's 100+ pre-built connectors and standards-based paths for HL7, FHIR, X12 and free text, with schema validation, record-count reconciliation and chain-of-custody on every load. Dual-running keeps the legacy instance available read-only while retrieval is proven, and the ROI and disclosure and AR Workdown modules take over requests and remaining balances.

AI Global Search

Search across structured and unstructured archived records from one interface.

100+ connectors

Pre-built connectors for EMR, LIS, RIS, ERP, EDI, file shares and mainframe sources.

Standards-based ingest

HL7, FHIR, X12, DICOM and free-text sources, with BIIG supporting HL7 v2, FHIR R4, CDA, X12 and IHE XDS.

Chain-of-custody and validation

Source-to-target migration with chain-of-custody preservation, schema validation and dual-running.

ROI and disclosure

Release-of-information request management and tracking against the archive.

AR Workdown

Cash posting, reconciliation and workflow management for legacy claims data.

Document management and OCR

Scanned, faxed and unstructured documents converted into searchable records.

Deployment and compliance

Commercial Azure and AWS, Azure Government and AWS GovCloud, under HITRUST r2, SOC 2 Type II and ISO 27001:2022 controls.

BytePad is listed in Epic Connection Hub in the Legacy EHR Archive category. BytePad was reviewed in the KLAS Emerging Company Spotlight (February 2026), where interviewed customers reported 100% Would Buy Again (emerging data per KLAS methodology) and an A+ Likely to Recommend rating (emerging data per KLAS methodology).

What does a phased Epic decommissioning look like?

InterScripts runs Epic retirements through the four phases of the 12-step legacy EHR decommissioning playbook. A single system typically takes 9 to 18 months end to end.

Phase 1 · Steps 1 to 4
Discover and plan
Inventory, dependency mapping, retention-schedule mapping and a written disposition policy.
Inventory the legacy instance's modules, Clarity coverage, media stores, interfaces and downstream consumers. Agree instance ownership, access and license terms for the transition, and assign retention by record type and state.
Phase 2 · Steps 5 to 7
Select the archive and move the data
Platform selection, full and incremental source extraction, then ingest with validation and reconciliation.
Extract from Clarity and media stores in full, then incrementally until the legacy instance goes read-only. Reconcile the archive and the converted data in the surviving instance against the legacy patient and encounter counts.
Phase 3 · Steps 8 to 10
Cut over and prove retrieval
Interface sunset, ROI and disclosure workflow validation, and a read-only sustainment window, typically 6 to 12 months.
Retire legacy interfaces after each consumer has a replacement. Connect BytePad to the surviving Epic instance and prove chart recall, release of information and audit retrieval during the read-only window.
Phase 4 · Steps 11 and 12
Sunset and hand off
License termination, infrastructure decommission under chain of custody, and operational handoff.
Retire the legacy instance under the agreed terms, sanitize retained infrastructure under a documented chain of custody, and hand the archive to business-as-usual ownership.

Where can you read more about Epic retirement?

Other source systems: MEDITECH, Oracle Health (Cerner), Allscripts / Veradigm, GE Centricity, NextGen Healthcare, eClinicalWorks, athenahealth.

What do teams ask about Epic archiving?

Can BytePad archive a legacy Epic instance after a merger?

Yes. InterScripts has archived legacy Epic instances during consolidations and mergers. Clarity and media content are extracted, validated with schema validation and record-count reconciliation, and loaded into BytePad with chain-of-custody preserved so the legacy instance can be retired.

Can clinicians see the archived records from the surviving Epic instance?

Yes. BytePad is listed in Epic Connection Hub, and archived records can be surfaced in the surviving Epic instance through patterns such as a Chart Review link or a SMART on FHIR app, so clinicians stay in their normal workflow.

Is Clarity enough to archive an Epic instance?

Clarity is the usual starting point because it is a relational copy of operational data, but it is populated by daily extracts and may not carry every element or document. Confirm completeness against the operational record and plan document and media content as a separate workstream.

Why archive instead of converting everything into the surviving Epic instance?

Converting full history adds cost and clutters the chart with data clinicians rarely use. A common pattern is to convert active-patient data into the surviving instance and archive the rest, where it remains searchable and available for release of information and legal hold.

How long does retiring a legacy Epic instance take?

A single legacy system typically takes 9 to 18 months from inventory to final sunset, including a 6 to 12 month read-only sustainment window. Merger timelines, contract terms and media volume drive where a program falls in that range.

Ready to retire Epic?

Bring your Epic inventory, retention questions and contract dates. We will walk through a BytePad archive and a phased decommissioning plan with your team.

Request a BytePad demo

Sources & references

Epic is a registered trademark of Epic Systems Corporation. All other product and company names are trademarks of their respective owners and are used for identification only. KLAS is a registered trademark of KLAS Enterprises, LLC. InterScripts is not affiliated with, sponsored by or endorsed by the vendors named on this page.