PeopleSoft Campus Solutions → Workday Student

Campus Solutions and Workday Student model the academic world differently — terms, programs, plans, and student groups don't map one-to-one. The migration has to carry academic structure and effective-dated student history across intact, or advising, financial aid, and reporting land broken. This transfer sequences the conversion so history is preserved and reconcilable.

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: Student Academic Record Payload
// POST to Workday Student Integration API /ccx/api/v1/students

{
  "studentId": "1000000123",          // PS_PERSON.EMPLID
  "externalStudentId": "PS_" + EMPLID, // Preserve PeopleSoft ID
  "legalName": {
    "firstName": "JAIME",            // PS_PERSONAL_DATA.FIRST_NAME
    "lastName": "RIVERA-MENDEZ",    // PS_PERSONAL_DATA.LAST_NAME
    "preferredName": "JAIME"
  },
  "academicRecords": [
    {
      "academicCareer": "UGRD",         // PS_STDNT_CAR_TERM.STDNT_CARRIER
      "program": {
        "programCode": "BS-CS-2024",   // PS_ACAD_PROG.PROGRAM
        "catalogYear": "2024",
        "admitTerm": "2024 Fall",    // PS_ACAD_PROG.ADMIT_TERM
        "status": "Active"
      },
      "enrollmentTerms": [
        {
          "term": "2024 Fall",             // PS_STDNT_CAR_TERM.STRM
          "enrollmentStatus": "F",   // PS_STDNT_ENRL.ENRL_STATUS = 'E'
          "enrolledCredits": 15.0,  // Sum(PS_STDNT_ENRL.UNITS)
          "courses": [
            { "courseCode": "CS101-01", "grade": "A" } // PS_CLASS_TBL + PS_STDNT_ENRL
          ]
        }
      ],
      "financialInfo": {
        "financialAid": true,
        "totalAwarded": 12500.00,   // PS_STDNT_AWRD.AMOUNT
        "giftAid": 8500.00,
        "loans": 4000.00
      }
    }
  ]
}

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 implementation pathway governs the migration of student records, academic history, and related data from PeopleSoft Campus Solutions into Workday Student, preserving term-by-term enrollment, program progression, and financial obligations in a structure Workday's academic model expects.

Phases

Discovery and Source Audit. Extract PeopleSoft metadata from PS_INSTALLATION, PS_ACAD_ORG_TBL, and PS_TERM_TBL to enumerate institutions, academic careers, and active terms. Profile record counts in PS_STDNT_CARTR, PS_ACAD_PROG, and PS_ENROLLMENT. Document any custom fields added via PS_CUSTOM_FIELD_DEF or extended-row inserts.
Workday Tenant Configuration. Within the target Workday tenant, configure Academic Institutions, Academic Levels (Undergraduate, Graduate, etc.), Academic Periods (mapped from PeopleSoft STRM), and Academic Programs using the Student Mgmt → Academic Structures workspace. Load Workday-supplied integration system user credentials and confirm API/auth scope.
Field Mapping and Canonical Model. Build the canonical Student Record object: map EMPLID → Workday Student ID; ACAD_CAREER → Academic Career Reference; PROG_STATUS → Academic Program Status; and financial charges from PS_ITEM → Workday Student Financial Obligation. Use EIB (Enterprise Interface Builder) or Workday Studio for the integration flow.
ETL Development and Staging Validation. Build extract scripts (SQL or PeopleSoft Integration Broker) to pull PS_PERSONAL_DATA, PS_NAMES, PS_ADDRESSES, and academic history. Transform via middle-tier service; load into a Workday staging tenant. Run row-count reconciliation and sample record review against source totals.
Data Quality Remediation. Identify and correct: duplicate EMPLID entries, missing required Workday fields (e.g., Date of Birth, Gender), inactive program records where EFF_STATUS = 'I', and orphaned enrollment rows where ENRL_STATUS does not match STDNT_CARTR. Load remediation batches back through the ETL.
Parallel Run and UAT. Execute the full migration in the production-sandbox tenant. Involve registrars, financial services, and financial aid teams to validate program history, enrollment dates, grade rosters from PS_CLASS_MNGMT, and account balances. Use Workday报告 to compare against PeopleSoft SSRs.
Reversibility Check and Audit Trail. Freeze PeopleSoft read access for migrated populations but retain a frozen clone (exported to S3 or on-prem DB) for 90 days post-go-live. Confirm audit logs in Workday capture the migration batch ID for every record inserted.
Cutover Weekend. On go-live day: re-run incremental delta (last 24–48 hours of enrollment activity), load into Workday, run the Academic Record Publish batch, and validate enrollment counts match PeopleSoft's final snapshot. Set PeopleSoft to read-only at T-0.
Post-Go-Live Stabilization. Monitor Workday's student data load jobs for 14 days. Run daily reconciliation queries comparing Workday StudentAcademicProgram and StudentEnrollment objects against the frozen PeopleSoft clone. Address any mis-mapped program actions (ADVISOR, MATR, WITHDRAW).

Core Field Mapping

PeopleSoft Entity / Field	Workday Object / Attribute	Notes
`PS_PERSONAL_DATA.EMPLID`	`Student.Student_ID`	Primary key; preserve leading zeros.
`PS_STDNT_CARTR.STM`	`AcademicPeriodReference`	Map PeopleSoft term codes (e.g., 2281) to Workday Academic Period IDs.
`PS_ACAD_PROG.ACAD_CAREER`	`AcademicCareerReference`	UGRD, GRAD, NSTD, RSPN.
`PS_ENROLLMENT.ENRL_STATUS_CODE`	`StudentEnrollment.Status`	E=Enrolled, D=Dropped, W=Withdrawn; verify status-date alignment.
`PS_STDNT_CARTR.UNT_TAKEN`	`AcademicRecord.Total_Units_Attempted`	Cumulative; recalculate from `PS_CLASS_MNGMT` if historical rounding exists.
`PS_ITEM.ITEM_AMT`	`StudentFinancialObligation.BalanceAmount`	Migrate open items only; cleared items to `PaymentHistory`.
`PS_DEGREES.DEGREE`	`DegreeConferredReference`	Conferred degrees only; in-progress plans stay in `AcademicProgram`.
`PS_ADVISOR.ADVISOR_ID`	`AcademicAdvisorWorkerReference`	Link to Workday worker; skip if advisor is not yet provisioned in tenant.

Edge Cases

Active Registrations at Cutover. Students enrolled in the current term with class assignments in PS_STDNT_CARTR but without a finalized grade must be loaded with status Active and a placeholder of Grade_Entry_Pending to avoid enrollment-verification failures downstream.
Zero-Unit Program Enrollments. Students with only co-requisite labs or zero-credit courses may produce no rows in PS_ENROLLMENT; map them explicitly from PS_CLASS_MNGMT where UNT_CRED = 0.
Program Changes Mid-Term. When EFFDT on PS_ACAD_PROG falls within the current term, create a Workday ProgramChangeEvent rather than two separate enrollment records.
International Students with SEVIS Data. PS_SEVIS_DATA fields (I-20, visa type) have no direct Workday analog; map to Custom_International_Student_Data extended attribute or omit if compliance team will re-enter manually.
Financial Holds Blocking Enrollment. Records with HOLD_ID in PS_HOLD爬 must load into Workday before enrollment records; otherwise enrollment publishes and then immediately triggers a hold violation.
Duplicate Person Records. PeopleSoft sometimes creates a second EMPLID for the same individual (e.g., re-admit). Merge into a single Workday Student with multiple AcademicProgram entries; suppress the duplicate StudentID.

Cutover

Make the cutover reversible by retaining a point-in-time PeopleSoft snapshot as read-only extracts in compressed CSV/gzip under versioned object paths (e.g., /archive/ps_cs/{snapshot_date}/). Before switching, run a hash-diff comparing record counts and a 1% sample of field-level checksums between the final Workday load and the clone. Set a rollback trigger: if Workday enrollment totals deviate more than 0.5% from the PeopleSoft snapshot, pause the domain cutover, investigate the delta batch, and re-load before declaring go-live complete. Confirm all downstream systems (financial aid, bursar, transcript) have validated their Workday data reads before closing the PeopleSoft read-access window.

What a full implementation includes

Canonical mapping between 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.