PeopleSoft to Workday. The migration and the wind down.

Many PeopleSoft customers are evaluating a move to Workday, and the migration decision is only half the picture. The other half is how you wind down the Oracle relationship without overpaying for support during the transition or being locked into terms that outlast your use.

The migration from Oracle PeopleSoft to Workday is one of the most common platform transitions among large PeopleSoft customers, particularly for the human capital management and financials functions where Workday has established a strong position. The migration is a substantial programme in its own right, but from the Oracle negotiation perspective the critical question is the wind down, how the organisation manages the Oracle PeopleSoft support cost, the contract terms, and the compliance position during and after the transition. The buyer that manages the wind down captures the savings. The buyer that focuses only on the Workday migration frequently overpays Oracle during the transition.

This article walks through the PeopleSoft to Workday migration strategy from the Oracle negotiation perspective. The transition timeline and the dual running cost. The Oracle support during the transition. The contract terms and the exit. The compliance position during the wind down. The negotiation strategy. The framework helps an organisation manage the Oracle relationship through the migration.

The transition timeline and the dual running cost.

The migration from PeopleSoft to Workday is not instantaneous, and the transition period during which both systems run in parallel is a significant cost consideration. The organisation continues to pay the Oracle PeopleSoft support fee while it stands up, configures, and migrates to Workday, and the dual running period can extend across multiple years for a large, complex estate. The dual running cost, the Oracle support fee plus the Workday subscription during the transition, is a material element of the migration business case that is frequently underestimated.

The transition timeline also determines the duration of the Oracle support commitment, and the organisation that signs a multi year Oracle support renewal at the start of a migration may be committing to support payments that outlast its PeopleSoft use. The alignment of the Oracle support commitment with the transition timeline is therefore critical, and the organisation should avoid committing to Oracle support beyond the point at which it will retire PeopleSoft.

The structural response is to plan the transition timeline realistically, to quantify the dual running cost, and to align the Oracle support commitment with the actual PeopleSoft retirement timeline. The buyer that aligns the commitment with the timeline avoids paying for support beyond its use. See the PeopleSoft JDE pillar and the Oracle PeopleSoft product page.

The Oracle support during the transition.

The Oracle PeopleSoft support cost during the transition is a key area for optimisation, because the organisation is paying the support fee for a platform it is actively retiring. The support fee during the transition can frequently be reduced through the third party support alternative, which delivers the necessary support for the retiring platform at a fraction of the Oracle support fee. For the organisation in a multi year transition, the third party support can deliver substantial savings during the wind down.

The third party support decision during the transition is frequently more straightforward than for the long term estate, because the organisation is retiring the platform and has no need for the Oracle updates, the new releases, or the long term roadmap. The retiring PeopleSoft platform requires only the support necessary to keep it operational through the transition, and the third party support is well suited to this requirement. The transition is therefore one of the strongest cases for the third party support alternative.

The structural response is to evaluate the third party support alternative for the PeopleSoft platform during the transition, where the retiring platform requires only operational support, and to capture the savings during the wind down. The buyer that optimises the support during the transition reduces the dual running cost. See the PeopleSoft support cost optimisation article.

The contract terms and the exit.

The contract terms governing the PeopleSoft licence and support determine the flexibility of the exit, and the terms should be reviewed carefully before the migration. The support renewal terms, the termination provisions, and any minimum commitment provisions affect the organisation's ability to wind down the Oracle relationship on its own timeline. The organisation that reviews the contract terms before the migration understands its exit options. The organisation that discovers the terms during the wind down may find its flexibility constrained.

The exit from the Oracle relationship also involves the perpetual licence, which the organisation retains even after it stops paying support. The retained perpetual licence has implications for the compliance position and for any future use, and the organisation should understand its rights and obligations under the retained licence. The exit is not simply the cessation of payments but the transition to a new relationship with the retained entitlement.

The structural response is to review the contract terms before the migration, to understand the exit options and the termination provisions, and to plan the exit around the actual contractual position. The buyer that understands the contract terms exits on its own terms. See our contract review service and the audit clause negotiation article.

The compliance position during the wind down.

The compliance position during the PeopleSoft wind down requires careful management, because the transition is a period of change in which the deployment, the user counts, and the configuration are in flux, and Oracle's audit interest in a customer that is migrating away is frequently heightened. The organisation that allows its compliance position to deteriorate during the transition, through the over provisioning, the configuration changes, or the documentation gaps, creates an exposure that Oracle can pursue even as the organisation exits.

The compliance management during the wind down should maintain the accurate documentation of the deployment, the user counts, and the entitlement, and should ensure that the transition activities do not create a compliance exposure. The organisation migrating away from PeopleSoft should be particularly attentive to the audit risk, because the migrating customer is a natural target for the audit that seeks to extract a final settlement before the relationship ends.

The structural response is to manage the compliance position carefully during the wind down, to maintain the accurate documentation, and to be attentive to the heightened audit risk during the transition. The buyer that manages the compliance position protects against the exit audit. See the audit letter response article and our audit defense service.

The negotiation strategy.

The PeopleSoft to Workday migration negotiation strategy brings together the timeline alignment, the support optimisation, the contract review, and the compliance management into a coherent approach to the Oracle wind down. The strategy aligns the Oracle support commitment with the transition timeline, optimises the support cost during the transition through the third party alternative, reviews the contract terms for the exit, and manages the compliance position against the heightened audit risk. The complete strategy minimises the Oracle cost during the wind down.

The negotiation strategy also addresses the broader Oracle relationship, because the organisation migrating away from PeopleSoft may retain other Oracle products, and the wind down of PeopleSoft should be managed in the context of the wider relationship. The organisation that manages the PeopleSoft wind down as part of its overall Oracle strategy captures the full value and avoids the pitfalls of the uncoordinated exit.

The structural response is to build the complete wind down strategy, to align it with the migration timeline, and to manage it in the context of the broader Oracle relationship. The buyer that builds the strategy manages the wind down and captures the savings. See the Oracle Negotiation Playbook white paper and the Apps Unlimited deal type page.

Managing the wind down.

The PeopleSoft to Workday migration is as much an Oracle wind down as a Workday implementation, and the buyer side value lies in managing the wind down deliberately. The transition timeline and the dual running cost, the support optimisation during the transition, the contract terms and the exit, and the compliance position during the wind down each affect the Oracle cost during the migration. The buyer that manages the wind down, that aligns the support commitment with the timeline, that optimises the transition support, and that protects the compliance position, captures the savings that the uncoordinated exit forfeits.

For the broader framework see the PeopleSoft JDE pillar and the PeopleSoft Financials pricing article.