The complete peoplesoft hcm and finance migration playbook. Two-pillar coherent migration: PeopleSoft HCM 9.2 + FSCM 9.2 → Fusion HCM + Fusion ERP. Cross-pillar mapping, sequenced load order, FBDI + HDL, reconciliation evidence per pillar. 20–28 weeks typical.
Single-pillar migration sounds simpler but creates persistent cross-pillar integration overhead. Most mid-size PeopleSoft customers migrate both pillars together to land in a coherent Fusion state without the operational drag of permanent hybrid.
PeopleSoft HCM and FSCM share more than a database. They share ChartField design (payroll cost-allocations post to FSCM GL via department + project + class ChartFields). They share workflow infrastructure (PSAEWORKLISTHIST drives both HCM transfer approvals and FSCM voucher approvals). They share master data (PS_DEPT_TBL is referenced by both PS_JOB cost-center allocation and PS_VOUCHER distribution). Splitting the migration means establishing persistent integration to keep both pillars consistent — workable, but adds 0.5–1.0 FTE of permanent operational overhead per integration flow.
Syntra ETL's peoplesoft hcm and finance migration playbook handles both pillars in a single coherent project with shared crosswalk store (so the ChartField mapping for Finance also serves HCM cost-allocations), shared workflow design (so Fusion AMX flows cover both HCM and FSCM approvals), and shared reconciliation framework (so the audit pack covers cross-pillar compensation expense from HR worker through GL journal). The result is a clean Fusion landing where both pillars work together as they did in PeopleSoft — without the persistent integration overhead of single-pillar migration.
Customers who choose two-pillar migration typically complete in 20–28 weeks (mid-size) or 28–40 weeks (enterprise). Customers who chose single-pillar migration typically end up doing the second pillar 12–18 months later anyway and incur 12–18 months of hybrid integration cost in between. Single-pillar makes sense for strategic-hybrid intent (keep Campus Solutions on PeopleSoft permanently while modernizing FSCM on Fusion) or for very-large enterprises where two-pillar coordination is operationally infeasible.
What Syntra ETL ships pre-built across both HCM and FSCM pillars. Customer-specific overrides applied per crosswalk sign-off.
PS_LEDGER, PS_JRNL_HEADER/LN, PS_VOUCHER, PS_AR_ITEM all mapped to Fusion GL + Payables + Receivables with shared ChartField crosswalk. Period-end TB parity per ledger per period.
PS_EMPLOYEES + PS_PERSON + PS_NAMES + PS_ADDRESSES → HDL Worker. PS_JOB effective-dated history → HDL Assignment HISTORY_DATA. PS_POSITION_DATA → HDL Position. Manager hierarchy preserved for AMX approval routing across both pillars.
PS_PAY_CHECK + PS_PAY_EARNINGS cost-allocations align to FSCM GL via shared ChartField/department/project mapping. Fusion Payroll cost-allocation journal entries post to Fusion GL with cross-pillar audit trail.
PS_TL_RPTD_TIME → Fusion Time and Labor. PS_ABSENCE_HIST → Fusion Absence Management. Cost-allocation to Fusion GL through same ChartField crosswalk that drives FSCM.
PS_ASSET + PS_BOOK + PS_DEPR → Fusion Asset Mass Additions with full depreciation history. PS_PO_HDR + PS_PO_LINE → Fusion Procurement Open PO. Three-way match preserved cross-pillar.
Compensation expense audit chain from Fusion GL line back through Payroll Element Entry back to Worker back to original PS_PAY_CHECK + PS_EMPLOYEES. SOX-relevant. Signed evidence pack covers both pillars.
Two-pillar coherent migration sequenced for Fusion data dependencies. Both pillars complete in a single coherent project.
PSDBFIELD/PSRECDEFN catalog walked across HCM + FSCM. PSPCMPROG PeopleCode inventory. nVision/SQR report catalog. PSTREEDEFN ChartField tree analysis. Customization classification. Sized assessment with module-by-module risk register.
Shared ChartField → COA crosswalk designed (serves both HCM cost-allocation and FSCM GL). SetID re-modeling. PeopleCode replacement plan (Application Composer + AMX + OIC + FBDI defaults). Signed by Controller, HR Director, IT Audit Lead.
PS_VENDOR → Supplier. PS_CUSTOMER → Customer. PS_ASSET → Asset master. Open PS_VOUCHER → Fusion AP. Open PS_AR_ITEM → Fusion AR. Open PS_PO_HDR → Fusion Procurement. Reconciliation per master entity per BU.
PS_PERSON + PS_NAMES + PS_ADDRESSES → HDL Worker. PS_JOB → HDL Assignment with effective-dated history. PS_POSITION_DATA → HDL Position. PS_TL_RPTD_TIME open entries → Fusion Time. Headcount parity per legal employer per effective date.
PS_LEDGER per BU per Ledger per Year per Period → FBDI GL Balance. PS_JRNL current + prior FY → FBDI Journal Import. PS_PAY_CHECK current FY → HDL Element Entry. Older history routes to long-term archive per retention schedule. TB parity per ledger per period.
1–2 month-end parallel-run cycles. Delta-replay through Integration Broker REST. Final pre-cutover reconciliation. Cutover weekend (36–60 hours). Go-live both pillars together. PeopleSoft to read-only archive.
What separates a clean peoplesoft hcm and finance migration from a successful single-pillar migration plus 12 months of integration patches.
Fusion GL compensation expense line → Fusion Payroll Element Entry → Fusion Worker → original PS_PAY_CHECK + PS_EMPLOYEES. Cross-pillar audit chain preserved. SOX-relevant. Signed evidence per period.
Fusion AP voucher distribution → Fusion Cost Center → Fusion Position → original PS_VOUCHER + PS_POSITION_DATA. Cross-pillar attribution. Department + project + class ChartFields aligned.
Manager hierarchy from PS_EMPLOYEES drives Fusion AMX for both HCM transfer approval and FSCM voucher approval. Single source of truth. Approval audit trail consistent across pillars.
PS_JOB EFFDT history aligns to PS_PAY_CHECK pay-period boundaries. Fusion Assignment HISTORY_DATA segments align to Fusion Payroll cycle. Cost-allocation per pay period reconciles to GL per accounting period.
PS Business Units per country map to Fusion BUs per country. HCM Legal Employer per country aligns to FSCM BU per country. Localizations (1099, VAT, MwSt, country-specific Payroll elements) preserved.
First post-cutover period-end close: HCM Payroll posts to Fusion GL → Fusion GL Trial Balance reconciles to migrated PS_LEDGER. Cross-pillar close passes on first attempt. War-room support active.
PeopleSoft hcm and finance migration covers the full two-pillar migration: PeopleSoft HCM 9.2 (Core HR, Position Management, Payroll, Time and Labor, Absence Management, Benefits Administration) and PeopleSoft FSCM 9.2 (General Ledger, Accounts Payable, Accounts Receivable, Cash Management, Asset Management, Procurement, Order Management) moving together to Oracle Fusion Cloud (Fusion HCM + Fusion ERP). The two-pillar migration is the standard scenario for mid-size and enterprise PeopleSoft customers — single-pillar migration (Finance-only or HCM-only) is more common at large enterprises with strategic-hybrid intent. Syntra ETL ships pre-built peoplesoft hcm and finance migration playbook with module-by-module load sequencing, ChartField/SetID/PeopleCode mapping, FBDI/HDL emission and the reconciliation evidence pack to satisfy SOX, IRS, FERPA and state public-records auditors.
Three reasons. (1) Data dependency: payroll cost-allocation journals from HCM post to GL on Finance — if HCM goes to Fusion and Finance stays on PeopleSoft, you need a persistent integration to push Fusion Payroll journals back to PS_JRNL. That works (Syntra ships the pattern) but adds operational complexity. (2) Compliance traceability: SOX-relevant compensation expense ties HR worker data to GL journal entries. Easier to audit when both pillars live on the same platform. (3) ChartField/SetID coherence: HCM cost allocations and FSCM ChartFields share design dependencies — migrating both at once lets the target Fusion COA design serve both pillars without compromise. Customers who migrate one pillar then the other typically take 9–14 months total versus 16–28 weeks for two-pillar migration.
The load sequence respects Fusion's data dependencies: enterprise setup → master data → open transactional → balance/history → cutover. (1) Enterprise structures: ledgers, BUs, COA segments, calendars, legal employers, position structures (FSM). (2) Master data: PS_VENDOR → Supplier, PS_CUSTOMER → Customer, PS_PERSON + PS_NAMES + PS_ADDRESSES → Worker, PS_POSITION_DATA → Position, PS_DEPT_TBL → Department, PS_JOBCODE_TBL → Job. (3) Open transactional: PS_VOUCHER → Open AP, PS_AR_ITEM → Open AR, PS_PO_HDR → Open PO. (4) Balance + history: PS_LEDGER → GL Balance, PS_JRNL → Journal History, PS_JOB effective-dated history → Assignment HISTORY_DATA, PS_PAY_CHECK current FY → Element Entry. (5) Cutover: final delta replay, reconciliation, go-live.
The cross-pillar coherence that has to be preserved through the migration. PS_PAY_CHECK rows (HCM domain) cost-allocate to PS_JRNL rows (FSCM domain) via department + project + class ChartFields. PS_POSITION_DATA (HCM) drives cost center assignments that show up in PS_VOUCHER distributions (FSCM). PS_EMPLOYEES has manager hierarchy that drives AMX approval routing for both HCM workflow (timecard approval) and FSCM workflow (voucher approval). Every peoplesoft hcm and finance migration has to land both pillars in Fusion with the cross-pillar relationships intact: same Worker that owns the Fusion Time Card also drives the Fusion AP Voucher cost-allocation, same Manager that approves Fusion HCM transfers also approves Fusion AP payments. The cross-pillar mapping store maintains the bidirectional consistency.
A typical mid-size peoplesoft hcm and finance migration covering full HCM (Core HR + Payroll + Time + Absence) and full FSCM (GL + AP + AR + Assets + Procurement) with 7–10 years history runs 20–28 weeks on Syntra ETL versus 16–24 months on consultant-led programmes. Enterprise scale (50K+ workers, 50+ Business Units, multi-currency, multi-country) runs 28–40 weeks. Add Campus Solutions for higher-ed (PS_STDNT_*, PS_ITEM_SF, PS_ACAD_PROG) and add 6–10 weeks. Add Order Management (PS_OE_OPN_ORDR, PS_PRODUCT) and add 4–6 weeks. The acceleration vs consultant-led comes from pre-built PS_ table extractors, governed crosswalk store, FBDI/HDL emitters validated against current Fusion 26x release, and the peoplesoft migration reconciliation framework that catches drift before it becomes material.
Yes — Payroll history retention is one of the most regulated parts of any peoplesoft hcm and finance migration. IRS requires 4 years for federal payroll tax records (Form 941, W-2, W-3), 7 years for some state filings; ERISA requires 6 years for benefit plan records; state wage-hour laws run 3–7 years depending on jurisdiction. Syntra ETL's approach: current fiscal year + 1 prior FY PS_PAY_CHECK and PS_PAY_EARNINGS load to Fusion HCM as Element Entries (queryable from Fusion). Older payroll history routes to a long-term PeopleSoft archive (Parquet on object storage, queryable via Athena/BigQuery, retained per retention schedule). Drill-through from Fusion GL compensation expense back through PS_PAY_CHECK back to PS_EMPLOYEES — works whether the underlying data lives in Fusion or in the archive.
Yes — multi-currency and multi-country are standard scenarios in any enterprise peoplesoft hcm and finance migration. Multi-currency: PS_LEDGER per ledger per currency_cd reconciles to Fusion Ledger per ledger currency. PS_JRNL_LN monetary_amount per currency_cd vs Fusion Journal Line Entered Currency, AND PS_JRNL_LN base_amount vs Fusion Ledger Currency. Conversion rates RATE_MULT/RATE_DIV preserved. Multi-country: PeopleSoft Business Units per country mapped to Fusion Business Units per country with country-specific tax setup (US 1099, UK VAT, German MwSt, etc.). HCM multi-country: PS_JOB rows per country mapped to Fusion Assignments per legal employer per country with country-specific payroll element entries. Localizations preserved per country.
Customizations are inventoried at discovery and classified by replacement strategy. (1) Database customizations (custom PS_ table extensions, custom views, custom indexes) — extracted alongside standard tables; values route to Fusion DFFs or to long-term archive per business value. (2) PeopleCode customizations — inventoried via PSPCMPROG catalog, classified by business purpose (validation, derivation, integration, workflow), replaced with Fusion-native equivalents (Application Composer, AMX, OIC, FBDI defaults). (3) App Engine custom jobs — inventoried, classified, replaced with Fusion ESS scheduled jobs or OIC orchestrations. (4) SQR/nVision reports — catalogued, materiality-rated, rebuilt in OTBI/BI Publisher per value. Customers commonly find 30–50% of PeopleSoft customizations are dead code or redundant under Fusion's native rules engine.
30-minute call. We'll walk through your PeopleSoft HCM + FSCM footprint, modules in scope, ChartField design, customization profile and retention requirements — and produce a peoplesoft hcm and finance migration plan with timeline, scope and budget.