Why do imaging migrations take so long?
- Volume and file count. Archives hold years of studies — hundreds of terabytes to petabytes — spread across very large numbers of individual image files. Tools that move one file or one stream at a time crawl through them.
- Export through the old system. Many migrations pull every study back out through the legacy archive’s DICOM interface, which was built to serve reading workstations, not to empty itself in bulk.
- Data reconciliation. Patient identifiers, accession numbers, and DICOM tags must be matched, corrected, and validated against the new system — work that runs study by study.
- Clinical uptime. Radiology cannot stop reading, so migration traffic has to coexist with production — often only in off-hours windows.
- Security and integrity. Protected health information has to stay encrypted and provably intact the whole way.
Separate moving the bytes from reconciling the data
The two jobs have different bottlenecks, so give each the right tool:
| Layer | What it does | What sets its speed |
|---|---|---|
| DICOM-aware migration | Reconciles patient and study records, corrects tags, indexes studies into the new PACS or VNA | Data quality and the rules your team applies |
| High-speed data movement | Copies the underlying image files or objects between storage systems, sites, or the cloud, with integrity checks | Throughput of the whole path — storage, hosts, software, network |
Where the source archive’s storage can be read directly as files or objects, the bulk copy can run at line rate while reconciliation proceeds alongside it. Where a legacy archive only exposes its data through DICOM export, the copy speed is bounded by that interface — worth knowing before you set a cutover date.
How long does the bulk copy take?
| Archive size | 10 Gbps | 25 Gbps | 100 Gbps |
|---|---|---|---|
| 250 TB | 2.6 days | 25 h | 6.2 h |
| 1 PB | 10 days | 4.1 days | 25 h |
| 3 PB | 31 days | 12 days | 3.1 days |
At line rate — about 90% of the link. Formula: hours = data (TB) ÷ (link Gbps × 0.9 × 0.45 TB per hour per Gbps). Tools that realize a fraction of the link take proportionally longer — at 20% utilization, a petabyte on 100 Gbps takes about 4.6 days instead of one.
What does a long cutover cost?
Until the last study lands and you cut over, you run both archives: storage, licenses, support, and staff on two systems at once. Every week the migration window stretches is another week of that overlap. Put a number on it with the migration-window calculator.
A checklist for a faster, verifiable migration
- Inventory first. Size the archive, count the files, and confirm whether the source storage can be read directly or only through DICOM export.
- Split the work. Run reconciliation and the bulk copy as parallel tracks, not one serial pipeline.
- Move in parallel, at line rate. Keep many files in flight across many streams and nodes, so file count does not cap throughput.
- Verify every file. End-to-end checksums on every file or object, so “we think it copied” becomes “we can prove it did.”
- Encrypt in transit and stay in control. Keep data on your own infrastructure, encrypted, inside the controls your security team already enforces.
- Keep native formats. Land studies exactly as they were, with no proprietary wrapper to unwind later.
- Protect clinical traffic. Cap migration bandwidth during reading hours and open it up off-hours.
- Sync to cutover. Keep copying new and changed studies until the switch, so nothing is left behind.
Security and compliance
Zettar does not retain your data — it stages it only briefly in the appliance’s NVMe burst buffer and moves it, encrypted with TLS and verified with unconditional end-to-end checksums, on your own infrastructure. It works through your identity provider and supports per-transfer bandwidth caps, so migration traffic stays within the policies you set. It fits within the HIPAA and security controls your organization already enforces; it is not itself a compliance certification. See security & trust.
Proof
In one large-scale file migration, a customer cut migration time by 80% with hands-off automation (case study). And with SLAC National Accelerator Laboratory and ESnet (U.S. DOE), Zettar moved 1 PB in 29 hours at 96% link utilization, encrypted and checksummed. The Zettar zx Appliance brings that bulk-copy layer turnkey — including a compact Mini for smaller sites.
