Final Migration to-do list

As each campus explores the data in their test Alma instance, staff will likely identify a range of different types of problems with the migrated data.  These problems may stem from a variety of different causes.  Perhaps staff forgot to export a field from their current ILS, and this field didn't migrate to Alma.  Maybe a location was misidentified on your Migration Form as a physical location.  

Many of the problems that you identify during the test phase can be resolved by making adjustments to your Field Mapping Form, Migration Form, the data in your current system, or to your data exports.  You may not know what caused a particular problem, and further identification of these types problems might require opening a ticket with Ex Libris.  Other problems might require post-migration cleanup.  

In order to ensure that your data migrates in the best possible state, it's important to record the problems that you see in your test load, and identify a path forward for each issue.  You can prevent many of the problems you encounter in the test load by tracking these issues along with the steps necessary to resolve these issues.  Making sure that all steps are completed before the final load will secure an improved final data migration.  

One method for tracking these issues is shown in the table below.  A tab labelled "Final Migration to-do List" is now included in your testing google doc spreadsheets.  You can also copy a version of this to-do list from here: https://docs.google.com/spreadsheets/d/1BdIFGuNEMNQyK6mbdq2K9jP3h78VWa0yZT1Zb_Uz7FY/edit?usp=sharing.