Move the archive off the old PACS without losing studies.
Multi-node routing, tag morphing, reconciliation and a transfer log that survives an audit. Built for the engineer who has to prove, six months later, that every study arrived.
One-time payment · perpetual licence · 30-day money-back guarantee
Runs inside your network. Studies move from your source node to your destination node and nowhere else.
| Slice | Studies | Sent | State |
|---|---|---|---|
| CT · 2019 Q1–Q4 | 18,442 | 18,442 | complete |
| MR · 2019 Q1–Q4 | 6,180 | 6,180 | complete |
| CR · 2020 Q1–Q2 | 31,905 | 31,905 | complete |
| US · 2020 Q3 | 4,772 | 4,769 | 3 retrying |
| NM · 2020 Q4 | 912 | 912 | complete |
| CT · 2021 Q1 | 12,006 | 7,318 | in progress |
| XA · 2021 Q1 | 1,447 | 0 | queued |
Work is queued in slices by modality and date range, so a multi-year archive moves in pieces that fit the maintenance windows you are actually given. Counts are reconciled per slice.
What it does
Everything a PACS migration needs, and a record of what it did.
Bulk study migration
Move whole DICOM archives, not files one at a time. Work is queued by modality and date range so a multi-year migration can be run in slices that fit the maintenance windows you actually get.
Multi-node DICOM routing
Route studies across multiple source and destination DICOM nodes in one job. Useful when a migration is really several archives converging on one new PACS.
Tag morphing on the wire
Transform, remap or clean DICOM tags as studies move. The destination gets the values it expects without a separate rewrite pass over the archive.
Anonymisation during transfer
Strip PHI as part of the migration when the destination is a test, research or vendor environment — no staging copy of identified data to secure and then delete.
Reconciliation you can defend
Counts are compared between source and destination per slice, so "the migration finished" is a number you can show someone rather than an impression.
Retry handling
Transfers that fail are recorded and retried rather than silently dropped. A flaky night on the network does not mean starting the slice again from zero.
A full transfer audit trail
Every run writes what moved, when, from where, to where, and what changed on the way. That log is what a compliance review asks for months after the go-live.
Transfer reporting
Per-run reports summarising studies attempted, succeeded, retried and failed — the artefact that goes into the project pack, not a screenshot of a progress bar.
Hospital-tested
Built for, and used on, real PACS migrations in production rather than assembled from a specification. The rough edges it handles are the ones that actually turn up.
How a migration runs
Six phases per slice, repeated until the archive is across.
A migration is not one long job you start and hope about. It is a series of bounded slices, each of which is scoped, transferred, reconciled and reported before the next one starts.
| Phase | What happens |
|---|---|
| Scope | Pick the source nodes, modalities and date ranges for a slice. Large archives are migrated as a series of slices rather than one unbounded job. |
| Dry run | Query the source and see what the slice contains — study counts by modality and date — before anything is transferred. |
| Transform | Apply tag morphing and, where required, anonymisation rules so studies arrive shaped the way the destination expects. |
| Transfer | Send to one or more destination nodes, with failed transfers recorded for retry rather than dropped. |
| Reconcile | Compare source and destination counts for the slice and report anything that did not arrive. |
| Report | Write the run report and audit log — attempted, succeeded, retried, failed — for the project record. |
Read this before you buy
What this software does not do.
It is a migration tool, not a migration project.
The engine moves studies between DICOM nodes you already control. It does not negotiate access to a legacy vendor’s archive for you, and it cannot extract from a system that will not serve C-FIND and C-MOVE. If your outgoing vendor has to enable something first, that conversation still has to happen.
Throughput depends on your source PACS, your network and the destination’s ingest rate — not on this software. Plan slices around the windows those systems give you rather than around a headline transfer figure.
Reconciliation compares what was sent against what arrived. It confirms the transfer, not the clinical correctness of the destination archive: validating that studies display and hang correctly in the new PACS is still a human acceptance step.
The software does not certify your migration as compliant. Responsibility for meeting HIPAA, GDPR and your institution’s own requirements stays with you.
Pricing
One licence, one machine, no subscription.
$99
per machine · one-time
- Perpetual licence for version 1.x
- Bulk study migration with multi-node DICOM routing
- Tag morphing and anonymisation during transfer
- Reconciliation and retry handling for failed transfers
- Full audit trail and transfer reporting for every run
- Free updates within version 1
- Email support
- Re-activation on a replacement workstation on request
Your licence key arrives by email after payment, together with the installer download link, and activates from inside the application.
Paddle.com Market Ltd is the merchant of record for this order and handles payment, tax and invoicing. Prices are shown in your local currency at checkout and any applicable VAT or sales tax is added there — the total is shown before you confirm. No subscription, no auto-renewal.
Requirements
Specifications
- Deployment
- Runs on a workstation or server with DICOM network access to both the source and destination nodes. No cloud component; studies never leave your network.
- Standards
- Standard DICOM networking — C-FIND, C-MOVE and C-STORE against conformant source and destination nodes. Reads and writes standard Part 10 files.
- Licensing
- One licence per machine. Internet required once, to activate; offline thereafter.
- Licence key format
- MAJW-XXXX-XXXX-XXXX-XXXX
- Delivery
- Licence key and installer download link emailed after payment.
- Support
- Email support from the engineers who built it, included with the licence.