DICOM Data Migration Doesn’t Have to Be Painful. So Why Do Some PACS Vendors Make It That Way?.

Your images. Your patients. Your data. Why should leaving a PACS vendor become a financial and technical nightmare?

Why Does a Simple Migration Request Create So Much Resistance?

A hospital can spend years working with a PACS vendor, paying its monthly fees, maintaining its contractual obligations, and trusting that vendor with one of its most valuable clinical assets: patient imaging data.

Everything seems to work reasonably well. Until the hospital decides to change vendors.

Suddenly, a straightforward request to export its DICOM images becomes an enormous technical undertaking. The explanations begin. The limitations appear. The fees start accumulating. What should be an orderly transition turns into a frustrating, expensive, and unnecessarily complicated process.

Why does requesting your own imaging data sometimes seem to create a crisis for the very company entrusted with managing it?

The Excuses Are Becoming Familiar

At OffSite Image Management, we have encountered situations where healthcare organizations face significant obstacles when attempting to migrate imaging data from an existing PACS environment.

1. "We don’t export data. You’ll have to query and retrieve it yourself."

The vendor has stored the customer’s imaging studies for years, yet when the customer requests an export, the responsibility is transferred entirely to the receiving organization.

Query/retrieve is a legitimate DICOM capability. It can be useful for migration. But making the customer retrieve years of historical studies individually, without practical assistance or bulk-export capabilities, can turn a manageable project into a prolonged and resource-intensive process.

2. "It will cost $4,000 per terabyte to export your data."

Imagine a hospital with 16 terabytes of imaging data. At $4,000 per terabyte, the proposed migration cost becomes $64,000. For many community and rural hospitals, that represents a substantial unplanned expense.

Certainly, data migration involves real costs. Infrastructure, personnel, validation, network capacity, and project management all require resources. But customers deserve a transparent explanation of those costs.

A fee should reflect the actual work being performed, not simply the amount a vendor believes it can charge a departing customer.

3. "We can only push one study at a time, and our services cost $300 per hour."

PACS systems routinely handle thousands of imaging transactions. They receive studies, route images, transmit examinations, and exchange information with other systems.

Yet some vendors describe bulk export as though it were an extraordinary capability beyond the normal operation of their technology.

If a system can route DICOM studies during everyday operations, it is reasonable to ask why an organized bulk-migration workflow cannot be supported. There may be technical constraints, but those constraints should be explained and addressed rather than used to make migration impractical.

4. "Your data is stored in a proprietary format. Conversion will cost another $25,000."

Why should a healthcare organization bear an excessive financial burden because its vendor chose a proprietary storage architecture?

DICOM exists in part to support interoperability between medical imaging systems. Vendors may use proprietary internal storage methods, compression, indexing, or database structures. Those design decisions can be legitimate.

But they should not become an unreasonable barrier to a customer’s ability to retrieve its clinical information in a usable, standards-based format.

5. "Your data exists in multiple copies, and we don’t know which one is complete."

A customer may be told that imaging data has been copied across multiple storage locations over the years and that the vendor cannot confidently identify the complete dataset.

The proposed solution? Export everything, including duplicate copies, and charge the customer accordingly.

Redundancy and replication are important components of a reliable imaging environment. But maintaining multiple copies should not prevent a vendor from identifying the authoritative studies and constructing a validated migration dataset.

If the archive cannot reliably account for its contents, the issue is larger than migration cost. It raises questions about data governance, inventory management, and the organization’s ability to retrieve its own clinical records.

DICOM Migration Is a Technical Project, Not a Technical Mystery

Migrating years of medical imaging data is not always simple. A large archive may contain millions of images, historical patient identifiers, duplicate studies, inconsistent metadata, legacy formats, and examinations associated with multiple facilities.

Patient identity reconciliation may be necessary. Accession numbers may need to be mapped. Studies may require validation. Network bandwidth and storage performance must be considered. A well-executed migration requires planning, testing, monitoring, and verification.

None of that should be minimized. But these are known technical challenges. They are not reasons to make data migration unnecessarily difficult.

Healthcare imaging vendors work with DICOM every day. They understand C-STORE, C-FIND, C-MOVE, DICOMweb, study identifiers, transfer syntaxes, and image routing.

The same expertise used to receive and manage imaging studies should also support an orderly transfer when the customer chooses to leave.

The Customer Has Already Paid for the Service

The hospital signs a contract. The vendor provides services. The hospital pays its fees. The relationship may continue for five, seven, ten, or even twenty years.

Eventually, the organization may decide to move in another direction. Perhaps its clinical needs have changed, another platform offers better capabilities, the organization has merged with another health system, or it simply wants a different service provider.

Whatever the reason, once contractual obligations have been satisfied, the customer should be able to transition without being subjected to unreasonable obstacles.

A customer choosing another vendor does not erase the value of the previous business relationship. Nor should it create an opportunity to impose excessive charges unrelated to the actual work required.

A completed customer relationship should end professionally, not with a financial penalty disguised as a technical requirement.

Data Ownership Should Mean Something

Healthcare organizations are responsible for the clinical records they maintain. Their PACS vendor may host the images, manage the infrastructure, provide the software, and perform the technical services necessary to make those images available.

But providing the infrastructure does not mean the vendor should exercise unlimited control over the customer’s ability to retrieve its information.

The precise rights and responsibilities depend on the parties’ contracts and applicable law. Nevertheless, data access and portability should be fundamental considerations in every imaging technology agreement.

Customers should know how their information can be exported, what formats will be provided, what assistance is included, what fees may apply, and how the completeness of the transfer will be verified.

A healthcare organization should never discover that its imaging data is effectively trapped only after it decides to change vendors.

Reasonable Migration Fees Versus Excessive Exit Charges

There is an important distinction between charging for legitimate professional services and creating financial barriers to leaving.

A vendor may reasonably charge for additional services that require dedicated personnel, custom development, physical media, specialized conversion, or substantial project coordination, when permitted by the agreement.

Those costs should be documented, predictable, and proportionate to the work. What deserves scrutiny is a pricing structure that makes it financially unreasonable for a customer to retrieve data it has entrusted to the vendor.

A hospital should be able to ask:

• What work is included in the proposed migration fee?
• Can the data be exported through standard DICOM methods?
• Is a bulk-export process available?
• Why is conversion necessary?
• How will duplicate studies be identified?
• What validation will establish that the migration is complete?
• Are these charges disclosed in the existing contract?
• What happens if the migration takes longer than expected?

Transparent answers build confidence. Vague explanations and rapidly escalating fees do the opposite.

Vendor Lock-In Is Not Customer Loyalty

Some vendors may view difficult migrations as a way to discourage customers from leaving. But preventing a customer from changing systems is not the same as earning that customer’s loyalty.

Customer loyalty comes from reliable service, responsive support, fair pricing, technological flexibility, and a relationship built on trust.

Healthcare is a connected industry. Hospital administrators speak with other administrators. Radiology directors share experiences. Technology leaders discuss vendors, contracts, and implementation challenges.

A poorly managed migration can become part of a vendor’s reputation long after the project is complete.

If customers stay because leaving is too difficult or expensive, that is dependency—not loyalty.

An Orderly Migration Should Be a Standard Expectation

A responsible PACS migration should begin with a clear understanding of the data. The organization and its vendors should establish the study inventory, determine the required historical range, identify duplicates and exceptions, and agree on a migration methodology.

The receiving environment should be tested before large-scale transfers begin. Studies should be transferred using appropriate standards-based methods whenever feasible.

Progress should be monitored. Patient and study information should be reconciled. The completeness and accessibility of the migrated data should be validated.

And the original environment should remain available as contractually and operationally appropriate until the transition is complete.

This is not an exotic concept. It is a disciplined technology project. It requires cooperation from the departing vendor, the receiving vendor, and the healthcare organization.

When everyone works toward the same objective, migration becomes manageable.

OffSite’s Philosophy: Earn the Customer’s Business

At OffSite Image Management, we believe healthcare organizations should choose their PACS provider because of the value that provider delivers—not because their data is difficult to retrieve.

Our approach emphasizes interoperability, practical data management, and long-term customer relationships. We believe DICOM data migration should be planned, transparent, and technically responsible.

We also recognize that migration requires real resources and that each environment presents different challenges. But those challenges should be addressed openly and professionally.

If a customer decides to change providers after fulfilling its contractual obligations, the appropriate response should be to help establish an orderly transition consistent with the agreement.

Not to create unnecessary barriers. Not to manufacture complexity. And not to treat departure as an opportunity to extract one final excessive payment.

The strength of a vendor relationship should be measured by the quality of its service, not the difficulty of escaping its infrastructure.

Your Data Should Never Become Your Exit Penalty

Healthcare organizations face staffing shortages, reimbursement pressures, cybersecurity threats, technology expenses, and increasing demands for clinical interoperability.

Migrating to a new PACS should not introduce an additional crisis simply because the current vendor is unwilling or unprepared to cooperate.

Customers understand contracts. They understand that professional services have costs. They understand that transferring millions of medical images requires careful planning.

What they should not have to accept are unexplained fees, unnecessary technical restrictions, or obstacles that appear only when they announce their intention to leave.

A good PACS vendor should make it easy to stay because the service is excellent—not make it difficult to leave because the data is trapped.

After years of partnership, a customer deserves a professional transition. And the vendor should have enough confidence in its service to respect that decision.

DICOM data migration does not have to be painful.

The technology already exists. What matters is the willingness to use it responsibly.