• Migration Tool path on MFT server
• Credentials for file download
• Links to the following documents:
  • Voyager Migration Guide
  • Getting Ready for Alma and Discovery Implementation
  • This document

• APAC customers: migration-dc05.hosted.exlibrisgroup.com (APAC-DC05) or migration-dc07.hosted.exlibrisgroup.com (APAC-DC07). The relevant username should be supplied by your Professional Services.
• EU customers: migration-dc03.hosted.exlibrisgroup.com (EU-DC03) or migration-dc06.hosted.exlibrisgroup.com (EU-DC03) . The relevant username should be supplied by Professional Services.
• NA customers: migration-dc01.hosted.exlibrisgroup.com (NA-DC01) or migration-dc04.hosted.exlibrisgroup.com (NA-DC04) . The relevant username should be supplied by Professional Services.
• CANADA customers: migration-dc82.hosted.exlibrisgroup.com
• CHINA customers: migration-dc81.hosted.exlibrisgroup.com.cn

1. Download the tool from MFT, as described in the email sent from Ex Libris and move it under the desired Voyager database under the following path: /m1/voyager/xxxdb, where xxxdb is name of the Voyager database, for example: voyagerdb.
2. Unzip the general package:
   >> unzip Voyager2Alma.zip
   If it is not the first time you are downloading and installing the AutoExtract kit, the following message is displayed:
   replace unzip_package.sh? [y]es, [n]o, [A]ll, [N]one, [r]ename:
3. Enter A to replace all relevant migration programs with the new programs.
4. Unzip the package:
   >> ./unzip_package.sh
5. Confirm your Voyager database:
   You are connected to the xxxdb.
   Is this the correct db (Y/N)?
   If this is not the Voyager database that you want to extract, enter No, exit the menu, and move to the Voyager database that you want to extract.
   After confirming the Voyager database, the installation continues until the prompt is displayed.
   During the installation, two new directories are created under the following path /m1/voyager/xxxdb:
   • migration_conf
   • migration_scripts

 1. Extract all areas
 2. Extract with no Acquisition
 3. Extract with partial Acquisition (without Invoice)
 4. Extract Fulfillment only (Patron/Request/Loan)
 5. Extract invoice only
 

Select one of the extraction options for your test extract.

1. Go to the migration_scripts directory of the Voyager database where the kit is installed.
2. Run the following script:
   >> ./check_database_connection.sh
   In case the connection cannot be determined, the following message is displayed, see the following example:
   The connection test to your database server failed. Enter your database server name :
   il-voy2urm02
   Enter you database port number:
   1521
   If the connection test is successful, the following message is displayed:
   Connection test success – working against the database {host}:{port}. Proceed to the menu.
3. Run the kit:
   >>./Pextract_menu
4. The Voyager-Alma Extract menu is displayed:
   The db name is: voyagerdb
   *************************************************************
   Voyager-Alma Extract Menu
   *************************************************************
   
    1. Create "dummy" Migration Form
    2. Define extract areas
    3. UB Databases option
    4. Create and validate the Voyager Migration Form
    5. Validate the P2E file
    6. Extract the Data for defined areas
    7. Check the extract progress
    8. Package the data
    9. Transfer the packaged data
    10. Check the transfer progress
    11. Extract the historical loans
   
   -------------------------------
   b. Back
   e. Exit
   
   > Please enter your selection:
5. Select  2. Define extract areas. This does not extract the data, it only defines the areas to extract so that the migration form can be created appropriately. The following menu is displayed:
    1. Extract all areas
    2. Extract with no Acquisition
    3. Extract with partial Acquisition (without Invoice)
    4. Extract Fulfillment only (Patron/Request/Loan)
    5. Extract invoice only
   Select which type of extract you are performing, according to your contractual agreement with Ex Libris regarding Acquisitions. Extract Fulfillment only is typically for cutover extracts.
6. If you are a Univeral Borrowing (UB) customer, select 3. UB Databases option

   Use this option if you will select one of the following on the migration form for UB_CUSTOMER question
and you also want to link Master and Stub patrons together in Alma.
-Yes migrate all UB
-Yes migrate patron, loans and fines only
-Yes combine into one institution in Alma
 1. Yes, we will be answering UB_CUSTOMER with one of the above and we want to link patrons
 2. No (either we are not using one of the options, or we do not want to link patrons)
    Select either Yes or No, depending on your response to the UB_CUSTOMER question in the Migration form.

   If you are not a Universal Borrowing customer, you may ignore this question.

7. Select 4. Create and validate the Voyager Migration Form. The following menu is displayed:
   1. Create the Voyager Migration Form
   2. Validate the Voyager Migration Form
8. Select 1. Create the Voyager Migration Form. The creation of the migration form begins. The following is displayed:
   The process is now running in the background. Please wait till the process is complete.
9. After the process is complete, the following is displayed:
   The migration form is located at: /m1/voyager/xxxdb/migration_conf/ xxxdb_generated_.xlsm
   Press Enter to continue.
10. The created migration form, named xxxdbgenerated__.xlsm can be found under the migration_conf directory of the current Voyager database.
11. After the process is complete, the following is displayed:
    The log of this process is located at: /m1/voyager/xxxdb/migration_scripts/exl_logs/voyager_migration_log.
12. After creating the form, fill in the questions and map your data according to the instructions. For more information on how to fill in the migration form, see the Voyager to Alma Migration Guide.

1. Transfer the most recent version of the Voyager migration form to the Voyager server, in the directory /m1/voyager/xxxdb/migration_conf. The migration form may already be present from the testload.
2. Name the previous migration form should xxxdb.xlsm. For example, if your database is yourschooldb, then the file should be yourschooldb.xlsm.
3. Follow the steps as described in Creating a New Migration Form to create a new migration form. Since the old migration form is in the directory, the toolkit uses the existing form and adds to it.
4. After creating the new form, download the form to your PC again, answer the questions, and map your data according to the instructions. For more information on how to fill in the migration form, see the Voyager to Alma Migration Guide.
5. Pay particular attention to any newly added locations, fiscal periods, reporting codes, and possible new questions on the Questionnaire tab.

1. Place the Voyager migration form under the Voyager database/migration_conf directory and re-name it xxxdb.xlsm.
2. Go to the migration_scripts directory of the Voyager database where the kit is installed.
3. Run the kit:
   >> ./Pextract_menu
4. Select 4. Create and Validation Migration Form.
   The following menu is displayed:
   1. Create the Voyager Migration Form
   2. Validate the Voyager Migration Form
5. Select 2. Validate Migration Form. The validation of the migration form begins and the following message is displayed:
   The process is now running in the background. Please wait till the process is complete.
   After the process is complete, the following is displayed:
   The validation report of the migration form is located at: /m1/voyager/xxxdb/migration_scripts/exl_logs/mf_validation.log.
   If the form is found to be invalid, the following message is displayed:
   ~~Number of errors: 1
   ~~Number of warnings: 3
   ~~The validation report of the migration form is located at: /m1/voyager/xxxdb/migration_scripts/exl_logs/mf_validation.log
   Please correct the errors and review the warnings listed in the validation report.
6. Review the validation report of the migration form that is located under the migration_scripts directory of the current Voyager database named mf_validation.log.
7. The validation report is divided in two sections: MIGRATION FORM ERRORS and MIGRATION FORM WARNINGS. Each line in the report refers to a specific error or warning found in the migration form.
   For example:
   ERROR: 2014-04-07 12:05:44 --- MIGRATION FORM ERRORS ---
   Sheet: Questionnaire Institution Id (as determined by the Alma Migration Team) cannot be empty
   
   WARN: 2014-04-07 12:05:44 --- MIGRATION FORM WARNINGS ---
   Sheet: Reporting Codes Fund: GN is defined in database and is not defined in the spreadsheet
   Sheet: Reporting Codes Fund: LEXIS is defined in database and is not defined in the spreadsheet
   Sheet: Reporting Codes Fund: CDHist is defined in database and is not defined in the spreadsheet
   2014-04-07 12:05:44 --- Migration Form validation is finished. Status: FAILURE ---
8. Review the warnings and correct the errors listed in the validation report. It is recommended to re-validate the corrected form after your changes.
9. Send the validated form to the Alma migration team for approval two weeks before Testload and a week before Cutover before proceeding with the extract.

1. Create the file according to the instructions in the Voyager to Alma Migration Guide.
2. Place the file under the Voyager xxxdb/migration_conf directory and name it xxxdb.csv
3. The form must be in all lowercase.
4. The Voyager migration form must be present and completed (all tabs mapped)
5. Change the directory to migration_scripts: ../migration_scripts and run the kit ./Pextract_menu.
6. Select option 5. Validate the P2E file from the main menu.

After the process is complete, if there are errors, the following is displayed:

3. Correct any errors regarding the format or the electronic type in the file, for example:

1. Place the approved and validated migration form under the Voyager xxxdb/migration_conf directory and name it xxxdb.xlsm.

1. Place the approved and validated e-resource P2E file under the Voyager xxxdb/migration_conf directory and name it xxxdb.csv.
2. Go to the migration_scripts directory of the Voyager database where the kit is installed.
3. Run the following script:
   >> ./check_database_connection.sh
   If the connection cannot be determined, the following message is displayed, for example:
   The connection test to your database server failed. Enter your database server name:
   il-voy2urm02
   Enter you database port number:
   1521
   If the connection test is successful, the following message is displayed:
   Connection test success. Proceed to the menu.
4. If a secondary item file is used, place it in migration_scripts/secondary_item/secondary_item.csv prior to running the extract. See the Voyager to Alma Migration Guide, Appendix C, for more information on generating this file.
5. Run the kit:
   >> ./Pextract_menu
6. Select 2. Define extract areas. This does not extract the data, it only defines the areas to extract prior to extracting. The following menu is displayed:
    1. Extract all areas
    2. Extract with no Acquisition
    3. Extract with partial Acquisition (without Invoice)
    4. Extract Fulfillment only (Patron/Request/Loan)
    5. Extract invoice only
7. Select which type of extract you are performing, according to your contractual agreement with Ex Libris regarding Acquisitions. Extract Fulfillment only is typically for cutover extracts.
8. Select option 6. Extract the Data for defined areas.
9. Define the directory (with enough prerequisite disk space) in which to place the extracted data. (A default directory is recommended.):
   The default root path for the extracted output files is: /m1/voyager/xxxdb/voyagerdb_extract. Press enter to confirm or enter a different root path:
   The Voyager migration form validation process extract starts running after you answer the questions above. The validation report is produced at the end of the process. If the form is invalid, the extract does not proceed. If the form is valid, the extract begins automatically.
10. Indicate if this is a testload or a cutover extract.
    Is this a testload or cutover extract? [T/C]:
    For testload extracts, the site may choose to allow staff to continue working during the data extract. At the end of extracting each data element, the migration program compares the number of records extracted vs the number of records in the database.  If the numbers do not match, for example if a record was added in the middle of the extract because staff are working, the extract program assumes an error.  To correct the potential error, the program will attempt to re-extract - but only for cutover loads.   The program will not attempt to re-extract for testloads.  
11. Jobs running in the background will slow the extract process and may stop it. Therefore, the extract reports if any Voyager jobs are running.
    If the extract encounters a running job or a scheduled job (within 48 hours) the list of jobs is displayed. You are asked if you want to continue or to exit the extract in order to disable the jobs.
12. After checking , the extract begins and the following message is displayed:
    Voyager extract is now running in the background. Press ENTER to go back to the main menu.
13. Press ENTER to go back to the Voyager-Alma Extract menu and select option 7. Check the extract progress to monitor the process.

1. Go to migration_scripts directory of the Voyager database where the kit is installed.
2. Run the kit:
   >> ./Pextract_menu
3. Select option 7. Check the extract progress. The following message is displayed:
   Monitoring the extracted output files located at the following root path: /m1/voyager/xxxdb/voyagerdb_extract/<date&time>
   The monitoring output is refreshed every 1 minute
   The screen refreshes every minute, so you can see the progress for each area:
   AREA EXTRACTED PROGRESS
   ==== ========= ========
   
   PATRONS 206 100.0%
   LOANS 347 100.0%
   REQUESTS 21 100.0%

1. Open the Voyager-Alma Extract menu and select option 8. Package the data. The following message is displayed:
   Packaging the extracted data. This may take several minutes. Please wait.
   Data packaged into /m1/voyager/xxxdb/voyagerdb_extract /migration_transfer
   After the packaging is completed, the packaged extract data is placed in the transfer directory. This directory is located under the directory in which the extracted data was placed, as entered after selecting option 6. Extract the Data. This directory is located under the default location /m1/voyager/xxxdb/voyagerdb_extract /migration_transfer
2. Open the Voyager-Alma Extract menu and select option 9. Transfer the packaged data.
3. Select the MFT server to which you want the data transferred, according to your region:
   Select the mft server by the optional regions:
   1. APAC
   2. EUR
   3. USA
   4. CANADA
   5. CHINA
   
   Please select your region:
   If your region is APAC, EU, or NA, you are asked to select one of the data centers in your region, according to Professional Services. You are asked to enter your MFT user name. Copy and paste the key from the link sent to you by Ex Libris. Below is an example of the key you are asked to insert.

   Enter your password:

   -----BEGIN RSA PRIVATE KEY-----

   MIIEoAIBAAKCAQEAz+h+RByvWo5aLNxpXS0hNh2DKlipYA81Ur+pVzoILXiA3EWW

   h6zfCOxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxbP0UPtbKojfhIgCbAJrtwa7jszxu

   XW9vn95ulDUNNuoyKGyyVeve7InsFx0NTzlLaJeJq3vfPCVXvO8InRY7giX/zCE0

   yxsOal+Wsf5vn+9L8XGEdcaG37vPWGEBfaNYywIBIwKCAQBNORj0ujKAuIfkxuVO

   fnoMySIXCv0VDPaMcxMDJC7sUVRvEoheR4YKnIVxq+edr12hLcdp7g5VjihxmxVP

   -----END RSA PRIVATE KEY-----

   The following message is displayed:
   Verifying the connection to the MFT server requested can be established. Please wait.
   If the connection cannot be established, the following message is displayed:
   Cannot establish connection to the MFT server requested. Do you want to try again resetting your password? (Y/N) [N]
   When the connection is established the data transfer begins and the following message is displayed:
   Data is being transferred.
   The data is transferred securely using MFT.
4. Open the Voyager-Alma Extract menu and select option 10. Check the transfer progress. The following message is displayed:
   NN% files of the extract was transferred
5. Check the progress again by selecting option 10. Check the transfer progress. The transfer is considered completed when the following message is displayed:
   The transfer is complete.
   The data transfer process can take up to 48 hours to complete, depending on the size of your data and your Internet connection speed. The functioning of Voyager is not affected by this process running in the background, and your normal work in Voyager can proceed in parallel. If the process does not complete within 60 hours, contact Ex Libris.
6. Inform Ex Libris when the data transfer process is completed.

1. Move to the migration_scripts directory under the desired Voyager database.
2. Run the following script:
   >> ./check_database_connection.sh
   If the connection cannot be determined, the following message is displayed, for example:
   The connection test to your database server failed. Enter your database server name:
   il-voy2urm02
   Enter you database port number:
   1521
   If the connection test is successful, the following message is displayed:
   Connection test success. Proceed to the menu.
3. Open the Voyager-Alma Extract menu by entering the following:
   >>./Pextract_menu
4. Select option 2. Define Extra areas from the Voyager-Alma Extract menu. The following is displayed:
    1. Extract all areas
    2. Extract with no Acquisition
    3. Extract with partial Acquisition (without Invoice)
    4. Extract Fulfillment only (Patron/Request/Loan)
    5. Extract invoice only
5. Select option 4. Fulfillment only (Patron/Request/Loan).
6. Define the directory (with enough prerequisite disk space) in which the extracted data will be placed. (A default directory is recommended.)
   The default root path for the extracted output files is: /m1/voyager/xxxdb/voyagerdb_extract. Press enter to confirm or enter a different root path :
7. Select option 6. Extract the data for the defined areas.
8. Monitor the process via the monitoring screen as described in the section above.
9. After the extract is completed, package the data and transfer it as described in the sections above.