Abstract
Software updates often involve data migration, especially when converting legacy software implemented to interface with outdated relational database management systems or other nonrelational database electronic files. Moreover, many software applications rely on data migration to import data from a variety of platforms. Usually, database migrations are time consuming and error prone. Based on their experience designing and implementing custom utilities to convert a large number of legacy databases and files in different platforms, RTI computer scientists developed five criteria that need to be considered when evaluating a data migration tool (DMT). These criteria can help users and software development project managers make informed decisions in data conversion tasks, help software developers assess design and implementation considerations for future DMT products, and provide guidelines for database administrators to evaluate a general DMT.
