Mapping Data for Conversion

When you map data, you are identifying legacy system data and redefining it in Campus Solutions record definitions. This step can be performed while setting the conversion timeline; however, your data mapping efforts will be more focused if the conversion time line has been set.

Issues to consider when mapping data include defining the amount of historical data to be converted, code validation, workflow, reporting, and other processes. The amount of historical data converted may vary across PeopleSoft applications. The complexity of how the legacy system stores history may contribute to less history mapped into the PeopleSoft system. With code validation, valid codes for the institution may have changed over time, and this too must be considered in the conversion effort.

To map data for conversion:

  1. Define each legacy data element.

  2. Determine if the legacy data element is pertinent to the implementation scope.

  3. Map the legacy data element to the Campus Solutions data element.

  4. If the legacy data element cannot be mapped directly within your Campus Solutions product line, determine if the legacy data should continue to be tracked.

  5. Reformat the legacy data to fit, for example, the Campus Solutions field size, format or data type.

    If certain legacy data cannot be reformatted, indicate those as gaps in the gap analysis.

Spreadsheets are helpful tools when mapping data. At a minimum, these spreadsheets should include the legacy system data source (if data comes from more than one source), the legacy system data element and data type, the specific Campus Solutions or Contributor Relations record, and the specific field and data type in that record. Optional description fields might include related prompt tables, conversion translation values, and legacy system data position.

Another option is to build a mini-application using PeopleTools to map data. You can build Structured Query Language (SQL) views to link various PeopleTools tables together, such as PSRECFIELD and PSRECDEFN, which creates a robust method of identifying field attributes. You can create special reports to identify key fields, required fields, or legacy system data not yet mapped.