Legacy PACS Support During a PACS Migration
Keep a legacy PACS stable during migration with parallel monitoring, controlled change, validated data transfer, and clear incident ownership.
By Trisha Seal — October 1, 2026. Practical guidance for hospital imaging operations.
Migration creates a dangerous assumption: because the replacement is coming, the legacy PACS needs less attention. In reality, the old system may carry normal clinical volume while teams copy years of data and validate the new environment.
Run Two Operational Plans
The project plan governs milestones. The support plan governs today's queues, interfaces, storage, backups, and incidents. Keep both visible. The old PACS remains production infrastructure until an authorized cutover says otherwise.
Control Change on the Legacy System
Freeze nonessential configuration changes and document every necessary one. An undocumented routing edit can create discrepancies between the source environment and the migration map. Follow a formal PACS migration sequence with named owners.
Validate More Than Image Counts
Compare patient and study identifiers, dates, modalities, series, reports where applicable, and retrieval behavior. DICOM defines formats and services for exchanging imaging information, but local workflows and historical exceptions still require testing.
Monitor Both Environments
Watch failed sends, duplicate objects, storage growth, latency, and reconciliation results. A severity-based PACS support model keeps project defects separate from operational incidents while ensuring neither is ignored.
Define Rollback Before Cutover
State what triggers a pause, who authorizes rollback, and how new studies will be reconciled. Keep interim operational coverage through stabilization, not just go-live day.
RAD365 supports PACS operations and migration continuity while hospital teams retain clinical responsibility. RAD365 does not read or interpret studies.
Source
DICOM Standards Committee, Current Edition
Related Reading
Frequently Asked Questions
Common Questions
When does the legacy PACS stop being production?
Only after an authorized cutover and stabilization process confirms the replacement can carry the required workload.
Why freeze changes during migration?
A controlled change window prevents undocumented configuration drift from undermining mapping, testing, and reconciliation.
Is matching image count enough?
No. Validation should also examine identifiers, dates, modalities, series, retrieval, and relevant associated information.
Who owns incidents during migration?
Name an operational incident owner separately from the project manager, with a shared escalation path for cross-environment issues.
How long should parallel support continue?
Continue through the stabilization period defined by the hospital, based on validated performance and a controlled decommission decision.
