SuccessFactors vs On-Premise SAP HCM: Navigating the Licensing Transition

Two Fundamentally Different Licensing Models

SAP HCM on-premise and SAP SuccessFactors operate on fundamentally different commercial principles, and understanding both is essential before evaluating the transition economics.

On-Premise SAP HCM: Perpetual Named User Licences

On-premise SAP HCM is licensed using perpetual named user licences — the organisation pays once for the licence and then pays annual support fees of approximately 22% of net licence value to maintain access to patches, legal and regulatory updates, and new releases. The licence is owned in perpetuity; support payments are ongoing but optional (with third-party support as an alternative).

SAP HCM uses the same named user licence types as core SAP ECC — Professional, Limited Professional, Employee Self-Service, and so on — with HR-specific roles and access patterns. Payroll is typically licensed as an engine metric based on the number of employees paid per period. The perpetual licence model means that the capital cost of SAP HCM depreciates over time; a fully depreciated SAP HCM installation has a very low annual total cost of ownership if support costs can be managed.

SuccessFactors: Per Employee Per Month Subscription

SuccessFactors operates on a PEPM (Per Employee Per Month) subscription model. Rather than purchasing a licence, organisations subscribe to access the software for a defined period — typically a three-year initial term — and pay based on the number of employees covered by each module.

SuccessFactors pricing is modular. Different modules carry different PEPM rates, and the total PEPM cost depends on which modules are subscribed to. Core HR and Employee Central — the foundation of the SuccessFactors suite — typically cost in the range of $8 to $21 PEPM per employee per month. Talent management modules (Recruiting, Performance and Goals, Learning Management, Succession and Development) range from $3 to $15 PEPM each. For organisations deploying multiple SuccessFactors modules, the total suite PEPM commonly reaches $25 to $40 PEPM, and in some configurations higher.

SuccessFactors subscriptions typically include annual PEPM increases of 3 to 5% as a contractual right. Over a five-year period, a $30 PEPM subscription at 4% annual uplift reaches approximately $36.50 PEPM — a 22% cost increase from the original subscription price. This compounding dynamic is rarely highlighted during the initial sales engagement but has significant long-term budget implications.

The Double-Running Cost Problem

The most significant hidden cost in the HCM-to-SuccessFactors transition is the double-running period — the interval during which the organisation is paying both SAP HCM support fees and SuccessFactors subscription fees while running both systems in parallel.

Most enterprise SuccessFactors implementations require 12 to 24 months of parallel running. During this period, the organisation pays approximately 22% of SAP HCM net licence value for on-premise support, plus the full SuccessFactors subscription for all covered employees, plus the professional services cost of the implementation project. For a large enterprise, the annual double-running cost can easily reach £2 to £5 million beyond what the steady-state SuccessFactors cost will be.

SAP offers incentives to offset some of this cost — typically in the form of credits against the SuccessFactors subscription, SAP HCM licence value credits applicable to S/4HANA or SuccessFactors purchases, or reduced implementation fees through SAP partners. These incentives are not automatic; they must be negotiated explicitly as part of the transition commercial package. Enterprises that accept standard SuccessFactors contracts without negotiating transition credits are funding a transition period entirely at their own cost.

Structuring the Transition to Minimise Double-Running

The most effective approach to minimising double-running costs is to align the SuccessFactors subscription start date with the decommissioning plan for SAP HCM, rather than beginning the subscription before the organisation is ready to migrate. This requires a realistic implementation timeline assessment — one that accounts for data migration complexity, integration requirements, and change management capacity — rather than SAP's optimistic deployment estimates.

Where possible, negotiate a phased subscription commencement — beginning the SuccessFactors subscription for the first employee population that migrates, rather than the full headcount, and adding populations as each phase completes. SAP's standard approach is to licence SuccessFactors for the full headcount from the subscription start date; a phased approach can meaningfully reduce the double-running cost during the transition period.

The Complete SuccessFactors TCO Model

Many SuccessFactors business cases presented to boards and investment committees understate the total cost of ownership because they capture only the subscription line item and the initial implementation cost. A complete TCO model for the SAP HCM to SuccessFactors transition must include the following components:

Subscription Costs

Model the PEPM subscription cost for all required modules across the full contract term, including annual escalation at the contracted uplift rate. Apply the escalation compound over the full contract period — typically five to seven years for a long-term business case — rather than using Year 1 pricing for the entire period. The cumulative difference between Year 1 pricing and end-of-term pricing at 4% annual uplift over seven years represents a 32% cost increase from the initial rate.

Integration and Middleware Costs

SuccessFactors requires integration with the core SAP ERP (S/4HANA or ECC) for data synchronisation, payroll processing (if payroll remains on-premise or moves to SAP Payroll), and financial accounting. SAP's standard integration solution is SAP Integration Suite on BTP. The BTP credits required for SuccessFactors integration may not be covered by the BTP credits bundled in RISE with SAP or standalone BTP subscriptions and may require separate negotiation.

Implementation and Customisation

SuccessFactors implementation costs vary widely by scope, modules deployed, and level of customisation. SAP's public cloud model requires organisations to work within the standard product functionality — the "clean core" principle — with extensions developed on BTP rather than in the core application. This represents a significant change from the SAP HCM model, where organisations could customise extensively within the application. The move to clean core often requires process standardisation effort and change management investment that is not captured in the software licence cost.

Ongoing Administration and Support

SuccessFactors requires a different operational model from on-premise SAP HCM. Cloud updates are released bi-annually by SAP (typically in the first half and second half of each calendar year), and organisations must test and adapt to these updates as part of their regular support cycle. The resourcing model for managing SuccessFactors — a mix of in-house system administrators and third-party support partners — has a different cost profile from the on-premise SAP Basis and ABAP developer resource model.

Negotiating the SAP HCM to SuccessFactors Commercial Package

The transition from on-premise SAP HCM to SuccessFactors is a commercial event that SAP values highly — it converts perpetual licence revenue to recurring subscription revenue. This gives SAP's sales organisation strong incentive to close the deal, which in turn gives well-prepared buyers genuine negotiating leverage.

Licence Credits for On-Premise HCM

Negotiate for SAP to provide credit for the residual value of existing on-premise SAP HCM licences against the SuccessFactors subscription. SAP offers these credits as a commercial incentive in some cases — they are not automatic and must be explicitly requested and quantified. The credit value is negotiable and depends on the original licence investment, the age of the licences, and the size of the SuccessFactors deal. Establishing the book value of existing HCM licences before the negotiation provides the quantitative basis for this discussion.

SAP Support Fee Bridge

Negotiate a reduction or credit on SAP HCM support fees for the parallel running period. SAP may agree to reduce the support rate from 22% to a lower "extended support" or "run-down" rate during the transition period while the organisation is actively migrating to SuccessFactors. This is a legitimate negotiating position that SAP has accepted in enterprise deals; it requires explicit discussion rather than assumption.

PEPM Rate Lock and Uplift Cap

Negotiate to lock the initial PEPM rate for as long as possible — ideally the full initial term — and cap any annual uplift. A PEPM rate locked at Year 1 pricing for the initial three-year term, with a capped escalation of 2% for subsequent years, significantly reduces the long-term subscription cost compared to standard 3 to 5% annual increases.

Phased Implementation Pricing

Structure the SuccessFactors commercial package with phased implementation milestones tied to subscription commencement. Begin the subscription for the initial employee population at go-live for Phase 1, with subsequent employee populations added as each implementation phase completes. This is a commercially straightforward request that aligns subscription cost with actual system usage.

SuccessFactors vs Alternatives

Not every organisation with on-premise SAP HCM should move to SuccessFactors. The decision must consider alternative HR technology options that are commercially and functionally viable:

Workday HCM: Workday is the primary competitive alternative to SuccessFactors for large enterprise HR. Workday pricing is also PEPM-based and comparable in range, but Workday's product depth in talent management and workforce analytics is generally rated higher in analyst assessments. Running a genuine competitive evaluation with Workday creates commercial leverage in the SuccessFactors negotiation and may produce a meaningfully better outcome than accepting SAP's initial proposal.

Continuing on SAP HCM with Third-Party Support: For organisations with stable, well-governed SAP HCM environments and no compelling business case for talent management transformation, continuing on on-premise HCM with third-party maintenance support is a viable medium-term option. At approximately 50% of SAP's support rate, third-party maintenance significantly reduces the annual cost of maintaining the on-premise system while the organisation evaluates its longer-term HR technology strategy.

Extending SAP HCM Within an S/4HANA Migration: For organisations planning an S/4HANA migration, the SAP HCM to SuccessFactors transition can be sequenced within the broader ERP transformation rather than as a separate initiative. Combining the two commercial discussions — S/4HANA adoption and SuccessFactors subscription — creates a larger commercial package with more negotiating leverage and the potential for bundled pricing that reduces both costs.