The last mile of DMS migration: Closing out the non-clinical archive

In Article 1, we made the case for consolidating clinical documents into Epic Gallery. In Article 2, we examined the engineering required to move tens of millions of those documents without patients or providers noticing. This final installment covers what remains once the clinical migration is complete: the non-clinical archive and the work required to shut the legacy system down for good.

The archive was never just a chart repository

Once a DMS migration has moved millions of patient records into Epic Gallery, the clinical portion is finished. Patient charts are unified, image retrieval is efficient, and clinicians have a single login. However, the remaining business back-office documents still stand between the organization and a complete exit from the legacy DMS.

Open almost any legacy environment (e.g. OnBase, OpenText, M-Files or an aging file share nobody quite owns anymore), and the medical record is only part of what is there. Over the last 15 or 20 years, these platforms became the default storage location for whatever department needed somewhere to store documents: AP invoices, supply chain records, vendor contracts, credentialing files and decades of HR records.

Epic Gallery renders clinical documents in the patient chart; enterprise business files require a different home. Capturing the full financial return from sunsetting legacy DMS depends on establishing a clear destination for that non-clinical footprint so the legacy application can be fully retired.

Why non-clinical data cannot follow the clinical record

Clinical content moves through an architecture designed around patient care. Documents are displayed, matched to the correct patient through identifiers such as the medical record number and enterprise master patient index, and linked to an encounter or order.

Forcing administrative files into the clinical repository creates predictable problems. Vendor invoices, purchase orders, W-2s and contracts can clutter workflows, consume primary storage, and create avoidable access and compliance risks. Their metadata works differently as well: Where clinical files index against patient demographics and encounters, non-clinical records depend on vendor IDs, invoice numbers, employee IDs, contract dates, and fiscal years.

This is where pre-migration discovery audits often produce the biggest surprises: Teams find document types nobody remembered, organized under index schemas tied to departments or workflows that no longer exist. The clinical migration may be well understood, but the remaining business archive is often full of unknowns.

The “read-only” trap costs more than it saves

Faced with a stranded non-clinical archive, many health systems arrive at the same compromise: leave the legacy application running in read-only mode. Accounting can still retrieve an old invoice, HR can find a personnel file from 2008, and nobody has to solve the problem today.

That compromise is more expensive than it appears. A read-only environment still carries software maintenance and support fees. It still consumes data center capacity, cloud subscriptions or aging on-premises hardware. Operating systems and databases still require patching, backups and monitoring. The aging application also continues to create cyber risk, especially as a shrinking user base draws operational attention elsewhere.

The internal cost also matters. Read-only environments remain on internal IT’s plate after the clinical migration is complete, delaying the team’s full transition to modern systems. Finance, HR and legal teams must also maintain separate logins and move between the two systems: the modern system for current records and the legacy platform for historical ones. Routine lookup becomes a more laborious, multistep task, and switching between systems can lead to missed records, version confusion, and manual entry errors. The organization ends up with the same fragmentation the migration was intended to eliminate.

An active archive gets the job done for less

The alternative is to move the non-clinical records into a lightweight, active archive or cloud repository. Then preserve appropriate access and sunset the legacy DMS.

The remaining content typically follows two paths. Live operational records, such as active vendor contracts and current employee files, move into the ERP, HR, or other business system that should own them going forward. Historical compliance records (e.g. seven-year AP files, prior employee records and tax archives) move into a secure, searchable active archive. During extraction, proprietary formats and legacy TIFFs can be normalized into standards such as PDF/A for long-term accessibility.

This approach can reduce storage, infrastructure and licensing costs while giving finance, HR and legal teams role-based, browser-based retrieval without legacy client software.

Field experience shows that active archive user adoption often requires more attention than the technical transition. Back-office users may initially prefer the familiar legacy client, but adoption improves quickly when the new archive preserves their search fields, access rules and response times. User validation therefore belongs inside the decommissioning plan.

The final cut: A four-step decommissioning playbook

Treat the legacy DMS shutdown as a defined project milestone with clear ownership and exit criteria.

1. Complete data reconciliation – Verify and document that clinical content is rendering completely and correctly in the native EHR repository, non-clinical records are accounted for in their target systems or archive(s), and authorized business users can retrieve what they need.
2. Clear litigation, audit, and retention holds – Confirm that active legal holds and other exceptions are cataloged, preserved and protected from automated destruction.
3. Terminate the contracts – Issue formal cancellation notices to software, hosting and support vendors before their auto-renewal windows close.
4. Tear down the environment and sanitize the media – Power down the hosts or virtual machines, sanitize storage in accordance with organizational policy and applicable NIST guidance, and release the associated data center, cloud and network resources.

Skip any one of these steps and the project can remain open operationally, legally or financially long after everyone assumes it is finished.

Closing the loop: DMS migration endgame

The move out of a legacy DMS begins with a clinical rationale and depends on disciplined pipeline engineering to get patient records where they belong. But the ultimate measure of success is knowing the legacy system can be decommissioned with confidence.

Health systems that pair a clean Gallery migration with a structured plan for the non-clinical archive complete the exit: clinicians work from a unified chart, business teams retain appropriate access to historical records, IT removes technical debt, and the organization captures the financial return it set out to achieve.

About the author

Max Lyons brings 16+ years of healthcare IT experience, with deep expertise in enterprise content management, intelligent document processing, and large-scale clinical data migrations. At Quoris, he leads the data services portfolio with a consultative approach focused on helping health systems move critical content cleanly, completely, and with confidence.

About the sponsor

Quoris is a global healthcare IT firm with more than 26 years of experience helping health systems get more from their clinical and operational technology. Its FastLane program offers accelerated extraction and conversion services for data headed to Epic Gallery from any environment, hosted or on-premises. FastLane works alongside your Epic team and is led by Gallery-accredited, veteran DMS professionals who work directly inside your network, with no data leaving your environment and no third-party tools introduced.