The user experience migrating from Archivists’ Toolkit (AT) and Archon to Archivesspace is proven to be quite different. Even though Archon migration should make up a smaller percentage of users conducting migrations, the bulk of support time is now spent addressing Archon migrations. Often, the only way to troubleshoot an Archon migration, is to attempt the migration on our end. Needless to say, this is very time consuming process.
This disproportionate support cost is primarily a result of the Archon migration tool design in that it:
● Requires a greater number of pre and post migration steps to be performed than the AT
● Less robust – failure of a single record to migrate often requires complete restart of migration
● Harder to debug problems – There is no simple migration report generated, nor can a
single record be migrated to quickly test out a problem.
Moreover, it recently became apparent that the Archon migration tool also needs to 1) Migrate data into an existing Archivesspace instance to facilitate the merging of archive records from numerous repositories, 2) Migrate digital objects which are not linked to any Collection records.
Given the above, the Archon migration tool will be rewritten to match the design of the AT tool which has already proven to require much less direct support. A rewrite, rather than simply extending the current tool is needed because the current design makes it difficult to implement and test the needed functionality.