DICOM Data Migration

Move imaging data.Keep its clinical meaning.

Use Nexus to discover, validate, transform and move DICOM data between PACS, archives and cloud platforms—while keeping identity, hierarchy, provenance and availability under control.

Discuss your migration Explore the detail

Nexus migration control

A governed route from source archive to trusted destination.

Nexus provides the orchestration layer around extraction, transformation, routing, exception handling and reconciliation. The migration plan can be shaped for a one-off archive replacement, a phased consolidation or an ongoing path into cloud imaging.

Discover and profile

Build a factual picture of data volume, modalities, dates, object types, transfer syntaxes, metadata quality and source-system behaviour.

Define the migration policy

Agree inclusion rules, identity mapping, metadata treatment, de-identification, target requirements and the evidence needed for acceptance.

Extract, transform and route

Move controlled batches through Nexus, applying the required validation and transformation before delivery to the destination.

Manage exceptions

Separate duplicates, malformed objects, conflicts and unsupported content into visible queues instead of allowing silent gaps.

Reconcile and prove

Compare source and destination inventories, test retrieval, track every exception and assemble the evidence required for migration sign-off.

Cut over safely

Coordinate delta migration, coexistence, final cutover and rollback planning so clinical teams retain access to current and historical imaging.

What needs attention

The details that determine whether a migration succeeds.

Every archive has its own history. Nexus makes the technical and operational questions visible before they become cutover problems.

Source estate discovery

Inventory studies, series and instances across PACS, VNAs, media and departmental archives before designing the move.

DICOM object coverage

Identify every object type in scope—including images, structured reports, presentation states, radiotherapy objects, encapsulated documents, video and whole slide imaging.

Patient and order identity

Reconcile patient identifiers, issuers, accession numbers and organisational codes so migrated studies join the correct clinical record.

UID and hierarchy preservation

Protect Study, Series and SOP Instance UIDs, relationships and references so the receiving archive retains the original DICOM structure.

Metadata and private tags

Profile required, optional and private attributes; retain, correct, map or remove them according to an agreed migration policy.

Transfer syntax strategy

Match object encodings to the target conformance statement and control any necessary decompression, transcoding or normalisation.

De-identification by policy

Apply governed anonymisation or pseudonymisation where research, sharing or another receiving workflow requires it.

Exceptions and data quality

Detect duplicates, malformed objects, missing attributes and unsupported content early, then route exceptions for managed resolution.

Operational continuity

Keep historical priors available while bulk migration, delta loads, cutover and coexistence are coordinated around live clinical work.

Validation and reconciliation

Compare source and destination counts, verify representative retrieval and pixel data, record exceptions and produce evidence for sign-off.

Security and data residency

Plan encrypted transfer, access controls, auditability, temporary staging and regional placement around organisational requirements.

Throughput and scheduling

Model volume, bandwidth, target ingestion limits and maintenance windows so migration performance is predictable and measurable.

Controlled migration flow

Profile. Prepare. Move. Prove.

Profile

Measure the source estate and expose quality, conformance and scope before migration begins.

Prepare

Apply identity mapping, metadata policy, destination rules and controlled transformation.

Move

Route encrypted batches with visible progress, retries, throttling and exception handling.

Prove

Reconcile the destination, test clinical retrieval and document outcomes for formal acceptance.

Cloud migration targets

One Nexus migration pathway. Multiple destinations.

Nexus can coordinate migration into on-premises, hosted and cloud imaging environments, shaped around each destination’s DICOM conformance and ingestion model.

AZURE

Microsoft Azure

Prepare and route imaging data into an Azure Health Data Services DICOM service or another agreed Azure imaging architecture, using DICOMweb and Azure-based staging where appropriate.

AWS

AWS HealthImaging

Stage validated DICOM P10 objects in Amazon S3, coordinate import into AWS HealthImaging and bring import outcomes back into migration monitoring and reconciliation.

GOOGLE CLOUD

Google Cloud

Move DICOM objects through Cloud Storage into Cloud Healthcare API DICOM stores, with DICOMweb-based access and destination validation built into the migration plan.

Destination services, regions, supported objects and transfer syntaxes are confirmed during discovery against the chosen platform’s current conformance and organisational requirements.

Plan the move

Bring us the archive, destination and cutover challenge.

We can map the data estate, migration controls, cloud target and validation evidence needed for a dependable move.

Discuss DICOM migration