Legacy PACS Migration: Moving Medical Images to a New PACS or VNA

Treat legacy PACS migration as a programme

Replacing a PACS is not simply a bulk file copy. The archive may contain years of studies, inconsistent identifiers, unsupported objects and dependencies that are poorly documented. At the same time, clinical users still need timely access to priors. A successful programme coordinates data scope, workflow transition, technical transfer, validation, exception decisions and legacy retirement.

Choose the migration and access strategy

Decide whether all historical data must move before go-live, whether recent priors will be prioritized, and whether the legacy PACS will remain available temporarily. Common patterns include full pre-migration, phased migration by date or facility, and selective on-demand retrieval with a defined backfill programme.

• Full migration before clinical cutover.
• Priority migration of recent and clinically relevant priors.
• Phased migration alongside continued legacy access.
• PACS-to-VNA consolidation with the new PACS reading from the VNA.
• Documented exclusions for data that cannot or should not move.

Profile the archive before committing the schedule

Build a source inventory and measure actual study sizes, modalities, object types and date distribution. Vendor database totals are useful but may not match what can be discovered and transferred through DICOM. Run queries and representative transfer tests early enough to challenge project assumptions.

• Patients, studies, series and instances by year and modality.
• Estimated bytes and practical transfer throughput.
• Duplicate identifiers and demographic inconsistencies.
• Compressed, non-image, presentation state and structured-report objects.
• Studies that cannot be queried, read or transferred.

Define identity and metadata rules

Agree how Patient ID, issuer, accession number, facility and other identifiers will be handled. If data correction or coercion is required, distinguish the original source values from the normalized destination values and retain a traceable mapping. Uncontrolled changes can make reconciliation and clinical matching much harder.

Pilot the end-to-end clinical outcome

The pilot should cover discovery, transfer, destination ingestion, patient matching, viewer access and reconciliation. Include cases that represent the archive’s difficult edges, not only recent CT and MR studies. Confirm that reports, links and downstream workflows behave as intended where they fall within project scope.

Run observable, recoverable batches

Use defined batches with a durable work ledger. Rate controls should protect source PACS performance, destination ingestion and network capacity. Operators need to see queued, active, completed, failed, skipped and verified work and to act on selected studies without restarting the whole programme.

• Use non-overlapping batch criteria and retain the query definition.
• Schedule work around clinical demand and infrastructure constraints.
• Stop, retry, resume or skip selected work with an audit record.
• Keep transfer success separate from destination verification.

Reconcile before retiring the legacy archive

Reconcile the destination against the approved source inventory at study level, investigate partial or unexpected outcomes and validate clinical access. Do not retire the source solely because the planned transfer period ended. The retirement decision should be supported by evidence, residual-risk acceptance and a documented fallback approach.

• Verified expected studies and approved exclusions.
• Unresolved exception register and ownership.
• Clinical sampling results across modalities and periods.
• Retention, legal hold and access requirements.
• Read-only period, backup, rollback and decommissioning approvals.

Additional considerations for multi-PACS consolidation

Consolidating multiple archives introduces overlapping Patient IDs, accession ranges, institution names and routing rules. Inventory and reconcile each source independently before producing the consolidated programme view. Preserve source provenance so future investigations can trace an object back to its origin.