Migrate from Oracle PeopleSoft to Infor CloudSuite Corporate

PeopleSoft stores the complete COA in ACCOUNT_TBL and related tables with effective dates (DT_EFFECTIVE, DT_TERMINATION) and SetIDs governing access across business units. We extract all active and historical rows, preserving the effective-date range. Infor CloudSuite uses a company-level account structure where each company has its own chart of accounts definition. We map PeopleSoft's SetID-based COA to Infor's company accounts by resolving the SetID-to-company relationship during extraction, and handle any inactive accounts by setting an appropriate Infor status flag. Account codes and descriptions transfer directly; extended attributes map to Infor account extension fields.

GL_JRNL_HEADER and GL_JRNL_LINE store journal entries with ledger, fiscal year, accounting date, and source system fields. We preserve the original journal ID and line number, but PeopleSoft's fiscal period calendar structure may differ from Infor's fiscal calendar configuration. We flag any journals whose accounting date falls in a period that is closed or does not exist in Infor, and escalate to the customer for period calendar alignment before loading. Historical GL data volume can be large; we filter to open and recent closed periods by default unless the customer specifies a deeper history scope.

PeopleSoft uses a voucher schema for AP where voucher records represent the financial obligation before or after payment. We extract AP_INVOICE_HEADER and AP_INVOICE_LINE for open and recent historical invoices, preserving payment status, vendor ID references, GL distribution lines, and invoice number. PeopleSoft's voucher-to-invoice distinction requires a mapping decision during scoping: if the destination Infor AP module expects invoices only, we filter vouchers that are pre-invoice drafts. We map vendor IDs from PeopleSoft's VENDOR_TABLE to Infor's supplier records using a vendor ID mapping table built during master data load.

AR_BILL_LINE and associated records store receivables with billing cycle, customer ID, amount, and payment terms. We extract open AR items and recent history, preserving the customer relationship and amount fields. PeopleSoft's billing cycle configuration maps to Infor's invoice cycle settings. Note that payment terms and credit limit data transfer from PeopleSoft's CUST_TABLE to Infor's customer master to maintain payment behavior continuity.

PeopleSoft maintains customer records across FSCM and CRM modules in CUST_TABLE and related tables. We de-duplicate across modules, preserving Sold-To and Ship-To addresses, credit limits, customer profile, and W-9 or tax registration data. The customer number (CUST_ID) maps to Infor's customer ID, and address structure maps from PeopleSoft's multi-address format to Infor's address book entries with the address type preserved.

Vendor records in VENDOR_TABLE include addresses, payment terms, W-9 status, tax IDs, and routing rules tied to PeopleSoft's purchasing business unit. We extract the full vendor hierarchy and preserve any routing rules by mapping the purchasing BU to Infor's company or plant entity. Tax ID (TAX_ID) transfers to Infor's tax registration field; 1099 status maps to the Infor vendor tax configuration.

PO_HDR and PO_LINE store purchase order headers and lines with approval status, buyer ID, and schedule dates. We extract open and recently closed PO rows, preserving PO ID and line numbers for destination ordering continuity. Infor's PO structure uses order types and line statuses that we map from PeopleSoft's PO status codes. Any PO that is approved in PeopleSoft but has not yet received goods may need to be re-approved in Infor depending on the customer's cutover policy; we document this as a post-load admin action.

INV_ITEM_MASTER and INV_ITEMS_CF store item definitions with unit of measure, cost, category codes, and business-unit-specific inventory flags. We map PeopleSoft's business-unit inventory flags to Infor's warehouse or plant entity. Unit of measure conversions are extracted from a separate UOM table and loaded into Infor's UOM conversion table. Item categories map by code; if the category code set differs between systems, we build a category mapping table during the master data phase.

EMPLOYEES and PERSONAL_DATA hold the core employee record with hire date, termination date, HR status, and manager hierarchy. PeopleSoft assigns sequential numeric EMPLID values that may need remapping if Infor assigns its own employee identifiers. We preserve the original EMPLID in a custom field (e.g., legacy_employee_id__c) and work with the customer to decide on ID coexistence strategy during the scoping phase. Manager hierarchy is extracted from the supervisor relationship stored in JOB records and loaded as a reporting structure in Infor HCM.

JOB and JOBCODE_TBL store position-based and job-based HR data with effective-date sequences that are critical for compliance audits. We extract the full JOB record sequence for each employee, preserving job code, grade, salary grade, FLSA status, full-time/part-time designation, and the effective date of each job row. The effective-date sequencing means we must load records in chronological order; we build a SQL-ordered extraction by EMPLID and EFFDT to ensure the history reconstructs correctly in Infor. We also enumerate any custom fields added to the JOB record that require field-level mapping.

POSITION_DATA stores position details with incumbent assignment, budgeted headcount, and department. Where organizations run mixed position-based and job-based structures, we separate them and carry both into Infor's position management module. The incumbent-to-position linkage, stored across JOB and POSITION_DATA with EFFSEQ sequencing, is reconstructed from the ordered row extraction. Infor's position setup uses position IDs and business titles that map from PeopleSoft's position number and job title respectively.

DEPT_TBL contains the organizational hierarchy with effective-date rows and SetIDs governing security access. We extract the full department tree, preserving the SetID relationship to the Chart of Accounts. Infor's department or cost center structure uses a company-based hierarchy that we map from PeopleSoft's SetID-scoped hierarchy. Effective dates on DEPT_TBL rows are preserved by loading in sequence and mapping to Infor's effective-date field if supported, or by using Infor's as-of-date reporting for historical reconstruction.

BENEFIT_PARTICIPATION and related records store enrollment, plan assignments, and coverage dates. We extract current benefit elections and carry forward plan names mapped to Infor HCM's benefit plan structure. Note that Infor CloudSuite HCM is less feature-rich than PeopleSoft Benefits Administration; organizations with complex multi-plan benefit structures should validate that Infor's benefit module covers their plan types during the scoping phase. We flag any benefit plan types that do not have a direct Infor equivalent and document them for the customer to configure post-migration.

PeopleSoft Payroll stores pay calculations in PAY_EARNINGS and DEDUCTION_RESULT with pay group, FLSA status, and year-to-date amounts. We extract last pay date and YTD balances mapped to Infor CloudSuite HCM payroll or to a customer-maintained payroll system if the organization decides to keep payroll in PeopleSoft. Many organizations running this migration choose to separate payroll from the initial migration scope because PeopleSoft Payroll is deeply integrated with the HR data model and any disruption to payroll processing carries immediate employee impact. We document the YTD carry-forward amounts for the customer's payroll administrator to set up in the destination system.