PeopleSoft Campus Solutions to Workday Student Data Migration

This migration extracts student data from Oracle PeopleSoft Campus Solutions—including demographics, academic programs, course history, financial aid awards, and enrollment records—and loads them into Workday Student using a phased, validated approach.

The complexity stems from fundamental differences in data models: PeopleSoft uses STU, SFA, and SHR tables with deeply embedded business rules, while Workday Student employs a worker-centric tenant model with academic-unit and credential frameworks that require re-conceptualizing program enrollment and award structures.

Free reference snippet

Yours to use

A working piece from this integration — no sign-up. The full build handles the edge cases, safeguards, and cutover.

// PeopleSoft → Workday Student Core Field Mapping

Student Demographics
┌─────────────────────────────────┬───────────────────────────────────────┐
│ PeopleSoft Field                │ Workday Student Attribute             │
├─────────────────────────────────┼───────────────────────────────────────┤
│ PERSONAL_DATA.EMPLID            │ Worker.ID (Worker_Reference_ID)       │
│ PERSONAL_DATA.NAMES.LAST_NAME   │ Student.Name.Last_Name                │
│ PERSONAL_DATA.NAMES.FIRST_NAME  │ Student.Name.First_Name               │
│ PERSONAL_DATA.BIRTHDATE         │ Student.Birth_Date                    │
│ PERSONAL_DATA.EMAIL_ADDR        │ Student.Contact_Data.Work_Email       │
│ ADDRESS.ADDRESS1                │ Student.Address_Lines[0]              │
│ ADDRESS.CITY                    │ Student.Municipality                  │
│ ADDRESS.STATE                   │ Student.State_Province_Code           │
│ ADDRESS.POSTAL                  │ Student.Postal_Code                   │

Academic Enrollment
┌─────────────────────────────────┬───────────────────────────────────────┐
│ STDNT_CAR_TERM.STDNT_CAR_NBR    │ Academic_Record_Reference.School_ID   │
│ ACAD_PROG.STDNT_CAR_NBR         │ Academic_Program_Enrollment.ID        │
│ ACAD_PROG.ACAD_PROG             │ Academic_Program_Enrollment.Program   │
│ ACAD_STATS.CUM_GPA              │ Academic_Record.Cumulative_GPA       │

Financial Aid
┌─────────────────────────────────┬───────────────────────────────────────┐
│ FA_AWARD.AWARD_ID               │ Student_Financial_Award.Award_Number │
│ FA_DISBURSEMENT.AMOUNT          │ Financial_Award_Disbursement.Amount  │
│ FA_DISBURSEMENT.DISB_DT         │ Financial_Award_Disbursement.Date    │

ETL Extraction Query
SELECT
  pd.EMPLID,
  pnk.NAMES,
  pd.BIRTHDATE,
  sct.STDNT_CAR_NBR,
  ap.ACAD_PROG,
  ap.ACAD_CAREER
FROM PS_PERSONAL_DATA pd
JOIN PS_PERS_NID pnk ON pd.EMPLID = pnk.EMPLID
JOIN PS_STDNT_CAR_TERM sct ON pd.EMPLID = sct.EMPLID
JOIN PS_ACAD_PROG ap ON sct.EMPLID = ap.EMPLID
WHERE sct.INSTITUTION = 'PSU001'
  AND sct.STDNT_STATUS = 'A'
  AND ap.EFF_STATUS = 'A'
  AND ap.PROG_STATUS IN ('AP','AC');

Implementation pathway

Step by step

How we'd take this from discovery to a production-safe cutover — the phases, the canonical mapping, and the edge cases that bite.

This integration migrates core student data from PeopleSoft Campus Solutions to Workday Student, covering demographics, academic programs, enrollment, and financial aid. The pathway assumes a full cutover migration (not delta sync) and uses batch file-based transfer via Workday Studio or EIB with intermediate staging tables for validation. Mapping is driven by Workday's academic structure model, which differs significantly from PeopleSoft's enrollment unit hierarchy.

Implementation Phases

Source Extract & Staging Build — Extract source data from PeopleSoft using PSQuery or CI to flat files (CSV/JSON). Load into Workday staging tables via Workday Enterprise Interface Builder (EIB) or Workday Studio batch inbound. Validate row counts against PeopleSoft query results before moving to transform.
Student Identity Resolution — Map PeopleSoft EMPLID to Workday StudentID using the enterprise ID map or create new Workday student records. Handle duplicate detection (same person in multiple careers). Set SourceSystemId on Workday records for traceability.
Academic Structure Mapping — Map PeopleSoft ACAD_CAREER + INSTITUTION combinations to Workday AcademicUnit and AcademicCareer. Translate PeopleSoft program codes (PROG, PLAN, SUBPLAN) to Workday ProgramOfStudy, AcademicPlan, and AcademicSubPlan via a lookup table maintained in Workday.
Enrollment & Term Alignment — Map PeopleSoft term codes (STRM) to Workday AcademicPeriod using a term calendar crosswalk. Translate enrollment status codes: E (enrolled), D (dropped), W (withdrawn) to Workday EnrollmentStatus values. Handle waitlisted and pending enrollment states.
Financial Aid Transformation — Map PeopleSoft aid year (AID_YEAR) and award item types to Workday FinancialAidYear and AwardType. Convert disbursement schedules. Include FAFSA and expected family contribution data where applicable.
Data Validation & Reconciliation — Run Workday inbound validation reports. Validate foreign key integrity (referenced academic units exist, programs are active). Cross-check aggregate counts: total students, active enrollments, financial aid packages. Log all rejected or transformed records with reason codes.
User Acceptance Testing — Conduct parallel run: load test data into non-production Workday environment, validate against PeopleSoft reports. Execute end-to-end scenarios: admit → enroll → award → graduate. Fix mapping gaps, repeat validation until thresholds (typically ≥99.5% match) are met.
Cutover Execution & Validation — Execute final extract from PeopleSoft at agreed freeze point. Load to Workday production. Run post-load reconciliation comparing totals and sampled record-level data. Switch business processes to Workday; retain PeopleSoft as archive for a defined period (typically 6–12 months).

Canonical Field Mapping

PeopleSoft Field	Workday Field	Transform Logic	Validation Rule
`EMPLID`	`StudentID`	Use ID map lookup; create new if unmatched	Unique, not null; length ≤ 20
`NAME`, `NAME_PI`	`LegalNameData`	Concatenate; map to `PreferredName` separately	At least one name component present
`ACAD_CAREER` + `INSTITUTION`	`AcademicCareer`	Composite lookup to Workday career reference	Career must exist in Workday tenant
`STRM`	`AcademicPeriodReference`	Term code crosswalk table (maintained in Workday)	Period is active or historical per migration scope
`ENRL_STATUS`	`EnrollmentStatus`	Code translation: E→Enrolled, D→Dropped, W→Withdrawn	Valid status enumerated value
`STDNT_CAR_ID`	`AcademicCareerProgramReference`	Link to program record created from `PROG` mapping	Foreign key to existing program
`ITEM_TYPE` + `AID_YEAR`	`FinancialAidAwardTypeReference`	Award item type mapped via configuration table	Award type active for given aid year

Edge Cases

Split identities — Students with multiple EMPLID records (e.g., re-admits, concurrent programs) must consolidate to a single Workday student with multiple academic careers; duplicate prevention logic must handle this correctly.
Program end-datedness — PeopleSoft programs with past end dates must be loaded as historical (inactive) in Workday; failing to set ProgramEndDate causes incorrect eligibility calculations post-migration.
Mid-term enrollment changes — Dropped courses with different drop dates require EnrollmentDropDate populated; omitting this causes enrollment verification reports to be incorrect.
Pending aid with rejected ISIR — Financial aid in "pending" state in PeopleSoft must not be loaded as accepted in Workday; ensure AwardStatus mapping respects the original aid packaging status.
Special character encoding — Names with diacritics or non-ASCII characters must be normalized per Workday's character handling; failures corrupt name display in student-facing tiles.
Course section cross-listings — Shared course sections in PeopleSoft (cross-listed sections) must map to a single Workday section or be handled via section association; loading both creates phantom duplicate capacity.
FERPA restricted records — Flag RESTRICT_ACCESS students; missing this flag in Workday exposes sensitive records to unauthorized advisors.

Cutover

Cutover must be reversible and reconciled: before the freeze, extract a complete snapshot of PeopleSoft data with a confirmed AS_OF timestamp. Load to Workday staging and validate aggregates (student count ±0, enrollment count ±0, award total ±$0) before committing to production. Retain the PeopleSoft database in read-only standby for a minimum of 90 days post-cutover to support record-level correction requests. For any corrected record, apply a delta transform to Workday rather than re-running the full migration bundle. Document the final reconciliation report (record counts, dollar totals, exception log) and archive it with the migration package; this becomes the audit baseline for the first Workday academic year close.

What a full implementation includes

Canonical mapping between Oracle PeopleSoft Campus Solutions and Workday Student, to the field level.
The edge cases that corrupt data at cutover — identified, handled, and tested.
Production-safe rollout: reversible, phased, with reconciliation checks.
Handover documentation your team can operate from.