This guide describes the suggested steps for migrating customers from Classic EIS to Inventory. The article assumes that the district instance has already been configured as described in Production Release#SettingupaDistrictInstance.
Step-by-step guide
- Review the information contained on the Pre Data Extract Procedures page.
- Export Classic data as described in the EIS Export Process.
- Ask Jason Klinger about parameters
- Import the extracted data into Inventory as described in the Inventory section of the Import Classic Data into USxS Redesign page. This page also provides examples of common import errors.
Review the resulting import.log file for errors - ask Jason Klinger for the name of the file.
This was copied from the USAS file, if it doesn't apply edit or remove it
The end of the import log will have a binary status that will indicate whether the importer ran to completion. It will appear similar to the following example.
districtname_usasimport_1 exited with code 0
A code of 0 indicates the importer ran to completion whereas a code of 1 signifies the importer terminated with an unknown exception.
Please note: A status of 0 does not mean there were no errors and the logs should still be reviewed. This status simply means the importer ran to completion. A status of 1 always indicates a failure. With a status of 1 the underlying cause will need to be determined and the import will need to be re-run after the issue is corrected.
Just above the exit status will be an Import Summary. This summary will list each import and provide the number of records loaded and the number of errors for that import. If any errors occurred they will list below the summary information.
Review the information on the Post Import Procedures page.
Once a successful import has been certified we recommend immediately creating a database backup using the /ssdt/script/backup-usps.sh script.
- verify name of script to run to create backup
Related articles