Migration Methods

Whenever a PACS is replaced by a successor system, plans must be made for access to historical data in the existing legacy system. The choices are to either keep the legacy archive running including an interface to new system, or migrate the data to the new system. The size and complexity of the data transfer task is such that data migration is a project element that must be explicitly planned and budgeted for.


The figure below compares Rapid Migration methodologies to conventional migration methods. Conventional methods request the legacy PACS server software to retrieve image data from internal Image Storage and send it out using DICOM STORE operations. In Third-Party migration, the retrieved data is sent directly to the new PACS; in Store-and-Forward migration the data is sent to the migration appliance, which forwards it to the new PACS. In contrast, Rapid migration reads image storage directly, bypassing the legacy PACS server software altogether and using independent Migration Server hardware to transform legacy image data into DICOM output streams. Rapid Migration thus offers greater speed and lower load on aging legacy systems still serving clinical operations. Rapid Data Migration Methods

(Click photo to enlarge for detail.)


Nonetheless, conventional migration is still appropriate in a number of situations. For do-it-yourselfers, Laitek offers MigrateNOW!™, a free tool for 3rd Party Conventional Migration.


And no matter which migration method you ultimately select, it’s an unsurpassed opportunity for Data Cleansing.