Short answer: A PeopleSoft to Fusion migration replaces a perpetual, customer-owned PeopleSoft license with an Oracle Fusion Cloud HCM subscription priced per employee, per month, billed indefinitely. Your existing PeopleSoft licenses carry no automatic credit toward Fusion, and there is no support deadline forcing the move before 2034 — so the migration's real cost lives in the subscription terms you negotiate, not the technology.
Key Takeaways
- Oracle Fusion Cloud HCM is licensed as a SaaS subscription priced per employee per month — unlike perpetual PeopleSoft, the subscription never ends and scales with your headcount every year (Oracle Cloud Service Descriptions, 2026).
- Your perpetual PeopleSoft licenses do not transfer to Fusion and carry no automatic credit; any migration credit or bridge concession must be negotiated before you sign the Fusion order.
- Premier Support for PeopleSoft 9.2 runs through at least 2034, so there is no contractual deadline forcing a Fusion migration — the urgency is a sales tactic, not a support fact (Oracle Lifetime Support Policy, 2026).
- For organizations on a fully depreciated PeopleSoft estate, the annual run-rate cost often rises after moving to a Fusion subscription rather than falling (Oracle Licensing Experts benchmark, 2026).
- The largest Fusion discounts and migration credits appear at Oracle's quarter-end and fiscal year-end (May 31) and only for buyers who push for them.
How does a PeopleSoft to Fusion migration change your licensing model?
Short answer: A PeopleSoft to Fusion migration converts a perpetual, owned license into a rented subscription. PeopleSoft HCM is licensed perpetually — typically per Application User or per Employee with a 22% annual support fee — while Oracle Fusion Cloud HCM is a SaaS subscription priced per employee per month and paid for as long as you use it.
This is the single most important fact in the entire migration, and Oracle's sales narrative is built to keep it in the background. PeopleSoft is Oracle's on-premise application suite, acquired in 2005, that you license once and own perpetually — the only recurring charge is the 22% support fee, which you can stop paying without losing the right to run the software. Oracle Fusion Cloud HCM is a different animal: a subscription service where you pay per employee, per month, indefinitely, and ownership never passes to you.
When the perpetual asset is fully depreciated — as most PeopleSoft estates running 9.2 are — you have effectively been running your HR system for the cost of support alone. A Fusion subscription resets that to a full recurring license fee for every employee, forever. That is not automatically a bad deal, because Fusion includes hosting, upgrades, and continuous delivery. But it is a fundamentally different cost structure, and treating it as a like-for-like swap is how organizations sign Fusion deals that quietly raise their annual Oracle spend. Start with the PeopleSoft Licensing Guide to confirm exactly what you own before you price the move.
How is Oracle Fusion Cloud HCM priced per employee?
Short answer: Oracle Fusion Cloud HCM is priced per employee per month, billed annually, with the rate varying by module bundle (Global HR, Talent, Compensation, Payroll, and so on). The employee count is your total workforce the service is provisioned for — not just active system users — which makes headcount, not usage, the cost driver.
The Fusion employee metric is where PeopleSoft veterans get caught. Under PeopleSoft, you could license a subset of users — say, 300 HR and manager self-service accounts — even with 10,000 employees in the system. Fusion Cloud HCM flips that: you subscribe per employee across the population the modules serve. A 10,000-employee organization licenses Fusion for 10,000, regardless of how many people actively log in. That shift alone can multiply the licensed quantity several times over versus a tightly scoped PeopleSoft footprint.
Fusion is also modular. Global HR is the foundation; Talent Management, Compensation, Benefits, Payroll, Workforce Management, and Recruiting are priced as additional per-employee subscriptions on top. Oracle bundles these into editions, and the per-employee rate published on Oracle's price list is a starting point that real deals discount heavily. The mechanics of this metric mirror Oracle's broader cloud pricing — the same per-employee logic that drives Java SE costs, covered in our breakdown of how the Oracle Java licensing model counts employees rather than installs.
What happens to your perpetual PeopleSoft licenses when you migrate?
Short answer: Your perpetual PeopleSoft licenses do not convert to Fusion and carry no automatic credit. Oracle treats Fusion as a separate subscription purchase. You keep the legal right to run PeopleSoft on the licenses you own, but once you migrate and drop support, those licenses become dormant assets with no trade-in value unless you negotiate one.
This is the lever Oracle hopes you never pull. Because PeopleSoft licenses are perpetual, you do not lose them by migrating — you simply stop using them, and if you cancel Oracle support, you keep the right to run the software indefinitely on the last version you were entitled to. That dormant entitlement is a negotiating asset. Oracle wants the Fusion subscription and wants you to walk away from PeopleSoft quietly. Buyers who recognize the leverage demand migration credits, support co-termination, or ramped subscription pricing in exchange for the move.
Oracle periodically runs formal programs — bridge offers, "Customer 2 Cloud" style credits, and support-conversion incentives — that apply existing support spend against Fusion subscription fees for a defined window. These are real but discretionary; they are offered to customers who ask and negotiate, not presented as a default. The forensic step is to value your PeopleSoft entitlement and unused support precisely, then put it on the table. Our Contract Negotiation service does exactly this — quantifying the dormant asset so it becomes a discount on Fusion.
PeopleSoft vs Fusion HCM: how the licensing compares
The table below isolates the licensing differences that drive total cost — not the feature set, which Oracle's sales team will happily walk you through. Read it as a checklist of what changes the day you sign the Fusion order.
| Dimension | PeopleSoft HCM | Oracle Fusion Cloud HCM |
|---|---|---|
| Ownership | Perpetual — you own the license | Subscription — you rent access |
| Primary metric | Application User / Employee | Per employee, per month |
| Recurring cost | 22% annual support only | Full subscription, billed annually, indefinitely |
| Cost driver | Licensed user count | Total employee headcount |
| Hosting & upgrades | Customer-run / self-managed | Included in subscription |
| Stop paying = | Keep running on owned licenses | Lose access entirely |
| Credit for prior spend | n/a | None automatic — must be negotiated |
| Support deadline | Premier through at least 2034 | n/a (continuous) |
The decisive rows are "Stop paying" and "Cost driver." Under PeopleSoft, walking away from support still leaves you a working system. Under Fusion, missing a subscription payment ends access. And because Fusion bills on total headcount rather than scoped users, a lean PeopleSoft footprint can balloon into a far larger licensed quantity. Both facts argue for negotiating the subscription terms — ramp, term length, price-hold caps, and headcount true-up rules — with the same rigor you would apply to a perpetual purchase.
Our Contract Negotiation service benchmarks your Fusion quote against real deal data and turns your dormant PeopleSoft entitlement into leverage. See the case studies for hard savings numbers.
How much does a PeopleSoft to Fusion migration actually cost?
Total cost splits into two streams that behave very differently. The recurring stream is the Fusion HCM subscription — per employee, per month, paid every year for as long as you run it. The one-time stream is implementation: data migration, configuration, integrations, testing, and change management, commonly running one to three times the first year's subscription depending on scope and how much PeopleSoft customization you carry forward.
The recurring stream is the one that compounds and the one buyers consistently underestimate. In our engagement data, an organization moving from a fully depreciated PeopleSoft estate frequently sees its annual Oracle run-rate rise after migration, because the per-employee subscription on full headcount exceeds the 22% support fee it replaced (Oracle Licensing Experts benchmark, 2026). That is not an argument against Fusion — the cloud model delivers value PeopleSoft cannot — but it is the reason the business case must be built on multi-year total cost, not a first-year discount Oracle dangles to close the deal.
Watch the parallel-run window most of all. During a phased migration you typically pay PeopleSoft support and a Fusion subscription simultaneously, sometimes for two to three years. Negotiate ramped subscription start dates and credits for the overlap, or that double-paying window quietly becomes the most expensive line in the project. For the cost-control playbook, pair this with our Support Reduction service.
Is there a deadline to migrate PeopleSoft to Fusion?
Short answer: No. Oracle has committed Premier Support for PeopleSoft 9.2 through at least 2034, so no contractual or compliance deadline forces a Fusion migration. Any urgency you feel comes from Oracle sales messaging, not your support entitlement — and you can use that runway to migrate on your own schedule.
This matters because manufactured urgency is the most reliable way Oracle extracts weak terms. A rushed Fusion deal — signed under the belief that PeopleSoft is "going away" — almost always carries thinner discounts, looser true-up clauses, and no migration credits, because the buyer negotiated against a clock that does not exist. There is more than eight years of committed Premier Support runway from 2026. Nothing about your support entitlement requires a 2026 or 2027 cutover.
Use the runway deliberately. Right-size your PeopleSoft licenses to strip out shelfware, consider moving PeopleSoft to third-party support to cut the maintenance fee roughly in half while you plan, and let the savings fund the Fusion migration itself. For the full picture of why the "end of life" framing is a tactic, see PeopleSoft End of Life & Support Options.
How do you negotiate a PeopleSoft to Fusion migration from strength?
Negotiate the Fusion subscription the way Oracle negotiates against you: on timing, leverage, and total cost over the full term. The buyers who win do five things consistently, and the buyers who overpay skip them under deadline pressure.
- Value the dormant asset first. Quantify your perpetual PeopleSoft entitlement and unspent support, and demand migration credits or support-conversion offsets against the Fusion fee.
- Lock the per-employee rate and a price-hold cap. Negotiate the rate, a multi-year price-protection cap on renewals, and clear rules for headcount true-up so growth does not trigger uncapped increases.
- Compress the parallel-run window. Negotiate ramped subscription start dates and overlap credits so you are not paying full PeopleSoft support and full Fusion fees at once for years.
- Time the signature to Oracle's calendar. The deepest concessions land at quarter-end and Oracle's May 31 fiscal year-end — let that work for you, not against you.
- Keep PeopleSoft as your walk-away. Because PeopleSoft runs to 2034, you can credibly stay; that optionality is your strongest lever and disappears the moment you concede the migration is urgent.
Oracle's playbook depends on the customer treating the migration as a foregone conclusion. The buyer-side counter is to keep the decision open, evidence-based, and on your timeline. Read the broader negotiation strategy in our Oracle Audit Defense Guide, since audits frequently arrive alongside cloud-migration pressure to soften your position.
PeopleSoft to Fusion Migration Licensing FAQ
How is Fusion HCM licensed compared to PeopleSoft?
PeopleSoft HCM is licensed perpetually, typically per Application User or per Employee, with a 22% annual support fee. Oracle Fusion Cloud HCM is a SaaS subscription priced per employee per month, billed annually, with no perpetual ownership. The shift matters because a Fusion subscription never ends — you pay for every employee, every year, indefinitely, whereas your PeopleSoft licenses you own outright.
What happens to my perpetual PeopleSoft licenses when I move to Fusion?
Your perpetual PeopleSoft licenses do not transfer to Fusion and carry no automatic credit. Oracle treats Fusion as a separate subscription purchase. Customers retain the right to run PeopleSoft on the licenses they own, but once you migrate and drop PeopleSoft support, those licenses become dormant assets. The negotiating lever is to demand migration credits or co-term concessions before signing the Fusion order — Oracle rarely offers them unprompted.
How much does it cost to migrate from PeopleSoft to Fusion HCM?
Total cost has two parts: the Fusion HCM subscription (priced per employee per month and paid indefinitely) plus one-time implementation, which commonly runs one to three times the first year's subscription depending on scope. The recurring subscription is the figure that compounds — a 10,000-employee organization moving from a fully depreciated PeopleSoft estate often sees annual run-rate cost rise rather than fall after migration.
Is there a deadline to migrate PeopleSoft to Fusion?
No. Oracle has committed Premier Support for PeopleSoft 9.2 through at least 2034, so there is no contractual or compliance deadline forcing a Fusion migration. Any urgency comes from Oracle sales messaging, not your support entitlement. You can migrate on your own timeline and use third-party support during the transition to fund the move.
Does Oracle give discounts or credits for migrating PeopleSoft to Fusion?
Sometimes — but only when negotiated. Oracle runs periodic migration incentives, bridge offers, and support-credit programs to accelerate cloud adoption, yet these are discretionary and rarely presented to customers who do not ask. The largest concessions come at Oracle's quarter and fiscal year-end. Without buyer-side pressure, most customers pay list-adjacent rates and forfeit credits they were eligible for.
Can I run PeopleSoft and Fusion HCM at the same time during migration?
Yes, and most organizations do during a phased migration. You keep PeopleSoft support (or move it to third-party support) while standing up Fusion in parallel, then decommission PeopleSoft module by module. The licensing trap is paying full Oracle support on PeopleSoft and a full Fusion subscription simultaneously for years — model the overlap window carefully and negotiate ramped subscription start dates to compress it.
Will moving to Fusion HCM lower my Oracle costs?
Not automatically. If your PeopleSoft estate is fully depreciated and you pay only the 22% support fee, a per-employee Fusion subscription on full headcount frequently raises annual run-rate cost. Fusion delivers value PeopleSoft cannot — hosting, continuous upgrades, modern UX — but the business case must rest on multi-year total cost, not a first-year discount used to close the deal.
Don't let Oracle frame your Fusion migration as inevitable
We model the full multi-year cost of a PeopleSoft to Fusion move, value your dormant PeopleSoft entitlement, and negotiate the subscription from strength — independent, buyer-side, built on 600+ engagements.