Three applications. One migration workflow.
The Migration Suite bundles the three applications of a legacy-PACS retirement into one workflow — Migration Engine, VNA Migration, and SynthInSight. Migration Engine fronts the legacy PACS and queries each study once, VNA Migration de-duplicates, remediates, and quality-gates every study before it reaches the net-new PACS, and both engines report PHI-free counts to SynthInSight for one unified Migration Analytics view.
PHI stays on the on-prem image path — only counts reach SynthInSight. Migration Engine and VNA Migration are non-device software under FD&C Act §520(o)(1)(D); SynthInSight is general-purpose business analytics, not a medical device.
How it fits together
Legacy PACS to net-new PACS, end to end.
The suite sits between the old and new estates. Migration Engine takes the query load off the customer’s live production archive; VNA Migration is the migration server that cleans every study on the way through; SynthInSight gives the program one PHI-free view of progress.
Want the print version? The Migration Suite poster is available as an 11×17 tabloid PDF on the posters page.
Three applications
Each keeps its own product page.
The suite is a commercial bundle, not a fused binary. Every member ships and is licensed as its own product — you can deploy them independently. Each card links to its full architecture, capability matrix, and regulatory framing.
Migration Engine
Acceleration tierFronts the legacy PACS — queries each study once
The federated query/retrieve proxy in front of the legacy source(s). It queries each study once over standard DICOM (C-FIND / C-MOVE / C-GET) or DICOMweb (QIDO / WADO), buffers and conditions studies in flight, and forwards them to VNA Migration — so the customer’s live production PACS is queried once, not hammered by the migration.
VNA Migration
Migration serverDe-duplicates, remediates, quality-gates every study
The migration server. It de-duplicates studies, remediates DICOM tags, and quality-gates every study before it reaches the destination, then forwards the clean, deduplicated, remediated studies to the customer’s net-new PACS or VNA.
SynthInSight
Migration analyticsOne unified Migration Analytics view — PHI-free
Both engines report PHI-free aggregate counts (how many studies moved / failed / skipped — never which patient or study) to SynthInSight, the single cross-product home for the migration analytics. PHI stays on the on-prem image path; only counts reach SynthInSight.
Why the suite
One workflow, bought as one.
Less load on the legacy PACS
Migration Engine sits in front of the legacy source and queries each study once, buffering and conditioning in flight. VNA Migration ingests through the Engine instead of querying the customer’s live production PACS directly — so a running migration doesn’t compete with clinical read traffic.
Remediate on the way in
VNA Migration de-duplicates studies, remediates DICOM tags, and quality-gates every study before it reaches the destination. The net-new PACS receives clean, deduplicated, remediated data — not a byte-for-byte copy of the legacy archive’s accumulated inconsistencies.
See the whole migration
Both engines report PHI-free aggregate counts to SynthInSight, so the program has one unified Migration Analytics view — how many studies moved, failed, or were skipped — across both applications, without standing up separate dashboards per tool.
PHI stays on-prem
The images and their PHI never leave the on-prem image path between Migration Engine, VNA Migration, and the net-new PACS. Only PHI-free counts — never a patient, study, or accession — reach SynthInSight. Migration Engine and VNA Migration are non-device software under FD&C Act §520(o)(1)(D); SynthInSight is general-purpose analytics.
Planning a legacy-PACS retirement?
The Migration Suite is built for legacy-PACS retirement and parallel-run cutover projects. Talk to us about scoping a migration — or evaluate any of the three applications on its own.