Understanding the Conversion Process

Here is a review of the scope of the conversion process, so that you can gain an understanding of the phases involved:

• Decide how much data to convert.

  You may choose to convert a different amount of data for each application. For example, you may want to convert 10 years' worth of student records data, two years of admissions data or two years of financial aid data.

• Map data to PeopleSoft data fields.

  To effectively plan a conversion, dig into the old system and identify that one obscure field on that one obscure table and figure out how it maps into the new PeopleSoft system. In some cases, it is difficult, and at times impossible, to map all the codes and tables from the legacy system directly to PeopleSoft tables. In addition, think about the impact that these legacy fields or codes have on reports generated by the PeopleSoft system.

• Export the data, using a Structured Query Report (SQR) or another method to interim tables.

  Use the interim tables to review and clean up the data before moving it to the PeopleSoft system. Corruption of data often is the result of data entry errors. You do not want to move corrupt data from the old system to the new PeopleSoft system.

• Import the data using an SQR.