Cloud migration · AWS
Move your imaging archive to AWS HealthImaging.
From on-premises PACS and VNA to AWS HealthImaging or an AWS-hosted PACS, at petabyte scale. Cleansed on the way in, verified study by study, and landing in your own AWS account.
What we move, and where
To AWS HealthImaging
Your archive loaded into HealthImaging, ready for cloud-native viewers and applications.
To an AWS-hosted PACS
Migration into a PACS or VNA running on AWS, including cloud PACS vendors built on it.
Copy for research or recovery
A synchronized copy of your DICOM data in AWS for research, disaster recovery or analytics, while the local PACS stays in service.
Why a cloud move needs a migration specialist
The cloud removes storage limits. It doesn't fix the data you send it.
Clean data in, not just more data
Duplicate patients, mismatched accessions and broken studies get fixed before they reach the cloud, where they are harder to find.
Scale on demand
Migration capacity added in AWS as needed, so very large archives move in parallel instead of in sequence.
Your account, your controls
Data lands in an AWS account you own, under your IAM policies. We get access only to what the migration needs.
Proof before cutover
Every study verified in the destination, with a reconciliation report before you retire anything on-premises.
Common questions
What is AWS HealthImaging?
AWS HealthImaging is an Amazon Web Services service for storing medical images in the cloud at petabyte scale. It stores DICOM data as image sets with lossless HTJ2K encoding and gives applications fast access to images through standard interfaces.
Can you migrate from any PACS to AWS?
Yes. We extract from your current PACS or VNA, whichever vendor, and load into AWS HealthImaging or an AWS-hosted PACS, reconciling patient and study data on the way.
Does our data pass through DICOMATICS servers?
No. Data moves from your source systems into your own AWS account. Migration engines run in your environment or your account, under your access controls.
How long does a migration to AWS take?
It depends mostly on how fast your source PACS can release studies. Our free data assessment measures that, and the migration calculator gives a first estimate.
Also moving to Microsoft? See PACS migration to Azure.
Planning a move to AWS?
Tell us your source system, volume and target. We'll size the migration and show you the path.