Best Practices for Migrating from dcm4chee v2 to dcm4chee-arc-light (v5)

63 views
Skip to first unread message

Loki

unread,
Jun 3, 2025, 2:27:00 AMJun 3
to dcm4che

Dear dcm4che Community,

I am currently planning a migration from dcm4chee v2 to dcm4chee-arc-light (v5) in a hospital environment with a large volume of archived studies spanning multiple years.

We have both systems set up and running locally (Linux environment). My current approach is to migrate data disk-by-disk, based on the entries from the filesystem table in dcm4chee v2.

Before proceeding further, I would appreciate expert input on the following:

Questions:

  1. Is the disk-by-disk + C-MOVE hybrid approach valid and reliable for full-scale migration from v2 to v5?
    If not, what strategy do you recommend for ensuring completeness, integrity, and traceability?

  2. Are there known issues when migrating DICOM data from dcm4chee v2 to v5 over the DICOM protocol (C-MOVE) — especially regarding private tags, character sets, or structured reports?

  3. Is there any supported migration tool, script, or documented method provided by the dcm4che team for database-level migration or mapping from v2 to v5?
    (For example: mapping Patient/Study/Series metadata or preserving StudyInstanceUIDs and AccessionNumbers.)

  4. Do StudyInstanceUIDs need to be remapped or regenerated, or is it best to retain them as-is when moving to v5?

  5. How can I verify that all studies from v2 have been successfully and completely migrated into v5?
    Any recommended verification strategies?

  6. What are the recommended practices to ensure both performance and data safety while doing a full migration (thousands of studies, TBs of data)?

I’d be truly grateful for any insights, caveats, or community-shared experience around this type of migration. My goal is to ensure a safe, complete, and verifiable transition from v2 to v5 without compromising data integrity or PACS functionality.




fleetwoodfc

unread,
Jun 16, 2025, 12:52:41 PMJun 16
to dcm4che
Do you have the option of leaving the dcm4chee v2 system in place as an imaging archive i.e. is it required to transfer the existing data?  You could just leave it in place then configure the new v5 system to access it's data when needed.

AKS

unread,
Jul 6, 2025, 5:37:43 AM (11 days ago) Jul 6
to dcm4che
How do you setup that?
Reply all
Reply to author
Forward
0 new messages