Migrate your Oracle PeopleSoft data

PeopleSoft FSCM stores the complete COA as records in the ACCOUNT_TBL and related tables with effective-date sequencing. We extract all active and historical rows preserving DT_EFFECTIVE and DT_TERMINATED dates and map them to the destination's account structure.

GL_JRNL_HEADER and GL_JRNL_LINE store journal entries with ledger, fiscal year, and accounting date fields. We preserve the source journal ID and line number, but fiscal period calendars often differ between systems and require explicit period mapping during load.

AP_INVOICE_HEADER and AP_INVOICE_LINE hold open and historical invoices. PeopleSoft distinguishes between voucher and invoice schemas. We extract payment status, vendor ID references, and GL distribution lines, then map to the destination's payable workflow.

AR_BILL_LINE and associated records store receivables with billing cycle, customer ID, and amount fields. We extract AR items and preserve customer and amount relationships, noting that payment terms and aging schedules vary between systems.

PeopleSoft CRM and FSCM each maintain customer records in CUST_TABLE and related tables. We de-duplicate across modules, preserving Sold-To and Ship-To addresses, credit limits, and the customer profile classification.

Vendor records live in VENDOR_TABLE with addresses, payment terms, W-9 status, and tax IDs. We extract the full vendor hierarchy and preserve any routing rules tied to purchasing BU (business unit) assignments.

PO_HDR and PO_LINE store purchase order headers and lines with approval status, buyer ID, and schedule dates. We extract open and history PO rows, preserving PO ID and line numbers for destination order matching.

INV_ITEM_MASTER and INV_ITEMS_CF store item definitions with unit of measure, cost, and category codes. We map PeopleSoft's business-unit-specific inventory flags to the destination's item master, handling unit-of-measure conversions separately.

EMPLOYEES and PERSONAL_DATA hold the core employee record with hire date, termination date, HR status, and manager hierarchy. PeopleSoft assigns sequential EMPLID values that may need remapping if the destination uses a different ID scheme. We preserve the full employment history through job data effective-dated rows.

JOB and JOBCODE_TBL store position-based and job-based HR data with effective-date sequences that are critical to preserve for compliance audits. Custom job code extensions require field-level enumeration during scoping.

POSITION_DATA stores position details with incumbent assignment, budgeted headcount, and department. Where organizations have mixed position-based and job-based structures, we separate them and carry the position incumbent mapping into the destination's org hierarchy.

DEPT_TBL contains the organizational hierarchy with effective-date rows and setIDs that govern security access. We extract the full tree, preserving the department setID relationship to the Chart of Accounts for financial reporting alignment.

BENEFIT_PARTICIPATION and related records store enrollment, plan assignments, and coverage dates. We extract current benefit elections and carry forward plan names mapped to the destination's benefit plan catalog, noting that plan IDs are not portable across vendors.

PeopleSoft Payroll stores pay calculations in PAY_EARNINGS and DEDUCTION_RESULT with pay group and FLSA status. We extract year-to-date amounts and last pay date, mapping pay components to the destination's earning and deduction codes.

PeopleSoft stores documents as Content References pointing to file systems, Content Manager, or third-party repositories outside the core database. We extract the attachment metadata and URLs but do not handle the binary file transfer in the same pass; a separate file migration step is required.