Modernising a legacy PeopleSoft HR system while payroll keeps running is one of those problems that sounds simple until you're the one signing off on the cutover plan. I went through oracle peoplesoft resellers reviews specifically looking for firms reviewers describe handling an upgrade or re-platform without a payroll or talent disruption story attached, and a few names had exactly that kind of detail.
For anyone who's moved off an old PeopleSoft version recently: how much of the transition risk came down to the reseller's process versus your own internal readiness? And did a phased Selective Adoption approach actually reduce the payroll disruption, or did the risk just move somewhere else?
##### Post Metadata - Posted at: 4 months ago - Net upvotes: 1 ## Comments ### Comment 1 Honestly, more of it came down to internal readiness than we wanted to admit at the time. Selective Adoption did reduce the payroll exposure for us, largely because it forced us to document which customisations we still genuinely needed before anything moved. That phased pattern is the same one your MIPRO reviewers describe. ##### Comment Metadata - Posted at: about 1 month ago - Author title: SEO Content Specialist ### Comment 2 A modernization path for legacy HR systems is only as good as how it handles payroll continuity during the transition, since that's the one thing that can't afford to break even for a single cycle. ##### Comment Metadata - Posted at: about 2 months ago - Author title: Marketing ### Comment 3 On where the risk actually sits: with payroll the protection is the parallel run rather than the upgrade method. Two complete cycles calculated in both systems and reconciled person by person will surface the retro-pay, garnishment and benefit-deduction edge cases no test script anticipates, and that work is mostly your own team's capacity rather than the partner's. Selective Adoption reduces the size of each change, which makes each parallel run smaller and more frequent rather than removing the need for one. Worth agreeing who signs off a variance, and what threshold is acceptable, before the first run. ##### Comment Metadata - Posted at: about 2 months ago - Author title: Tech Consultant ### Comment 4 The strongest signal in your breakdown is Selective Adoption experience. In practice, modernisation success often comes down to how well a partner sequences updates without forcing a “big bang” change across tightly coupled HR and payroll workflows. ##### Comment Metadata - Posted at: 4 months ago - Author title: Writer ## Related discussions - [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team) - Posted at: over 13 years ago - Comments: 6 - [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section) - Posted at: over 13 years ago - Comments: 0 - [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm) - Posted at: over 13 years ago - Comments: 4