How to manage dual licensing costs, negotiate cloud migration credits, optimise legacy licence disposition, and structure a transition that saves 20-40% compared to SAP's default commercial path.
Part of the SAP Advisory Services content series. See also: SuccessFactors Licensing Hub | SuccessFactors Modules Breakdown | SuccessFactors Licensing Guide for CIOs.
The migration from on-premise SAP HCM to SAP SuccessFactors is one of the most financially consequential technology transitions an enterprise undertakes. For a typical 15,000-employee organisation, the 5-year total cost of ownership ranges from $5 million to $15 million depending on module scope, migration approach, and how well the licensing transition is negotiated.
This migration involves a fundamental shift in licensing economics: from perpetual licences with annual maintenance to subscription-based cloud pricing. SAP's existing on-premise HCM licences do not transfer to SuccessFactors. The migration requires a new cloud contract, creating a period of dual costs where organisations pay for both the legacy system and the new platform simultaneously. Without deliberate management, this dual-running period can add 30-50% to the transition cost.
SAP's commercial teams are incentivised to maximise the SuccessFactors contract value while maintaining on-premise maintenance revenue as long as possible. Their default position rarely includes meaningful migration credits, overlap cost relief, or legacy licence disposition unless the customer negotiates for them. Organisations that approach this transition with a structured licensing strategy save 20-40% compared to those that accept SAP's initial proposal.
| Transition Element | Common Mistake | Financial Impact | Recommended Approach |
|---|---|---|---|
| Dual running costs | Paying full price for both systems 12-24 months | $500K-$2M unnecessary overlap | Negotiate overlap credits, phased SF ramp-up, maintenance reduction |
| Legacy licence disposition | Continuing maintenance after migration complete | $200K-$800K/year wasted | Plan maintenance termination dates per module; retain licences without support |
| Migration credits | Not requesting credits for existing SAP investment | Missing $300K-$1.5M in available credits | Negotiate cloud credits based on current maintenance spend |
| SuccessFactors scoping | Buying full suite when phased approach is better | 15-30% shelfware risk | Phase modules aligned with deployment readiness |
| Contract structure | Accepting SAP standard terms without negotiation | Price escalation, auto-renewal traps | Negotiate caps, flexibility, swap rights, termination options |
Before negotiating the SuccessFactors transition, you must have a complete understanding of your existing on-premise SAP HCM licensing position. This inventory forms the foundation for every negotiation tactic, cost comparison, and migration credit discussion.
On-premise SAP HCM is licensed under SAP's perpetual named-user model. You purchased user licences upfront (a capital expense) and pay annual maintenance at approximately 22% of the net licence value. Licence types relevant to HCM include SAP Professional User (full access to all SAP modules including HCM), SAP Limited Professional (restricted access, often used for HR specialists), SAP ESS/MSS (Employee Self-Service and Manager Self-Service, lower-cost user types for portal access), and SAP Developer (for ABAP developers maintaining the HCM system). Many organisations acquired SAP HCM as part of a broader ERP licence agreement, meaning HCM named-user licences may be embedded within the overall SAP user licence pool rather than separately itemised.
Certain HCM functions use engine-based licensing rather than named-user licensing. SAP Payroll is the most significant, typically licensed per employee processed (not per user accessing the payroll system). This per-employee metric means payroll costs scale with workforce size, which is particularly relevant when comparing to SuccessFactors Employee Central Payroll pricing.
For a typical 15,000-employee organisation, annual SAP HCM maintenance (including payroll) commonly ranges from $400K to $1.2M. This number is the baseline against which you compare SuccessFactors costs and the leverage you use to negotiate migration credits.
| HCM Component | Licence Model | Typical Metric | Transition Consideration |
|---|---|---|---|
| Personnel Administration | Named User (perpetual) | HR professional users | Replaced by Employee Central. Drop maintenance when EC live |
| Employee Self-Service (ESS) | Named User (low-cost tier) | All employees with portal access | Replaced by SuccessFactors ESS. Largest user count reduction opportunity |
| Manager Self-Service (MSS) | Named User (low-cost tier) | All managers with portal access | Replaced by SuccessFactors MSS. Negotiate count reduction |
| SAP Payroll | Engine (per employee paid) | Employees on payroll | If keeping on-prem, maintain. If moving to ECP, plan phase-out |
| Time Management | Engine or Named User | Employees tracked / HR users | Evaluate if SF Time Tracking replaces or if third-party used |
| Talent Management (on-prem) | Named User | HR users / managers | Directly replaced by SF talent modules. Drop at go-live |
| Organisational Management | Named User / Engine | HR administrators | Replaced by EC org structure. Drop maintenance when EC live |
Extract your SAP HCM licence schedule: work with your SAP account team or contract records to itemise every HCM-specific licence, its metric, its net licence value, and its annual maintenance cost. This is the data you will use for TCO comparison and negotiation leverage. Identify which licences are embedded in broader ERP agreements. If HCM user licences are pooled with ERP user licences, dropping HCM does not automatically reduce your overall SAP maintenance. You need to negotiate the maintenance reduction explicitly.
SuccessFactors operates on a fundamentally different commercial model from on-premise SAP HCM. It charges an annual subscription per employee per module (or module bundle). There is no upfront licence purchase. The subscription includes the software, hosting, maintenance, support, and regular updates. Pricing is typically expressed as a per-employee-per-year (PEPY) rate. Employee Central might be priced at $10-$25 PEPY, while a full HCM suite bundle might range from $50-$120 PEPY depending on modules included, employee count, and negotiated discounts.
Each SuccessFactors module has its own PEPY rate, and different modules can have different user populations. Employee Central (core HRIS) typically covers the entire workforce. Employee Central Payroll covers employees processed through SAP's cloud payroll. Performance, Compensation, Learning, and other talent modules can be scoped to subsets. Recruiting may use an enterprise rate or per-recruiter pricing. This per-module structure means total cost is highly dependent on which modules you deploy and to how many employees.
The subscription does not include implementation services (typically a separate SI engagement costing $1-$5M+ depending on scope), data migration, integration development, custom configuration, premium support tiers, or extended enterprise licensing (for non-employee users). These excluded costs can be 50-100% of the first-year subscription value, making them essential for accurate TCO comparison.
| Licensing Dimension | On-Premise SAP HCM | SAP SuccessFactors | Implication for Transition |
|---|---|---|---|
| Purchase model | Perpetual licence (one-time capital expense) | Annual subscription (recurring operating expense) | Shifts from CapEx to OpEx; budget differently |
| Ownership | You own the licence indefinitely | You rent access; stopping payments ends access | Cloud creates vendor dependency. Negotiate exit terms |
| Ongoing cost | Approximately 22% annual maintenance on net licence value | Full subscription renewed annually/multi-year | Subscription typically 2-3x annual maintenance for equivalent scope |
| Infrastructure | Customer-managed (servers, DB, storage, IT staff) | SAP-managed (included in subscription) | Eliminates infrastructure costs. Factor into TCO |
| Upgrades | Customer-managed (periodic, expensive projects) | Automatic quarterly releases (included) | Eliminates upgrade projects. Factor into TCO |
| User flexibility | Fixed licence count purchased upfront | Adjustable at renewal (with negotiation) | Cloud more flexible if contract terms allow |
| Price predictability | Maintenance rate contractually fixed | Subscription subject to annual increases (3-8%) | Negotiate price caps; model escalation in TCO |
The transition always involves a period where both systems run simultaneously. This dual-running period is unavoidable but can be managed to minimise cost impact. For most enterprises, it lasts 6-18 months depending on migration complexity.
During the overlap, you pay full annual maintenance on the on-premise SAP HCM system, full subscription for the SuccessFactors modules being deployed, infrastructure costs for the on-premise system, and SuccessFactors implementation costs. For a 15,000-employee organisation, dual-running cost can add $500K-$2M to total migration cost if not managed. This is pure transition overhead delivering no ongoing value once migration is complete.
| Dual-Running Scenario | Duration | Estimated Overlap Cost (15K employees) | Mitigation Strategy | Potential Savings |
|---|---|---|---|---|
| No negotiation: full price for both | 18 months | $1.5M-$2.5M | None | N/A |
| SF ramp-up discount (50% for 6 months) | 12 months | $1.0M-$1.8M | Reduced SF subscription during implementation | $200K-$400K saved |
| HCM maintenance reduction (50% during overlap) | 12 months | $800K-$1.5M | Reduced on-prem maintenance during transition | $200K-$500K saved |
| Combined: ramp-up + maintenance reduction + timed cutover | 9 months | $500K-$1.0M | Full mitigation strategy | $500K-$1.5M saved vs unmanaged |
Never accept full dual costs as unavoidable. SAP presents dual running as a customer problem. In reality, SAP benefits from the migration (new cloud revenue) and should share the transition burden. Push for overlap credits, ramp-up pricing, and maintenance relief as standard terms. Map every maintenance renewal date. Know exactly when each SAP HCM module's maintenance renews. Plan cutover dates to maximise the maintenance reduction window.
Once SuccessFactors is live and the on-premise HCM is decommissioned, you face a critical decision about your perpetual SAP HCM licences. Perpetual licences do not expire. Even after stopping maintenance, the licence rights remain. You can continue using the software indefinitely, just without SAP support, updates, or legal patches. This is an important asset many organisations forget they own.
The most significant financial action is terminating maintenance on HCM-specific licences once no longer needed. For a 15,000-employee organisation, dropping HCM maintenance can save $400K-$1.2M per year. However, if HCM licences are embedded in a broader SAP ERP maintenance agreement, you may need to negotiate a maintenance reduction rather than simply cancelling. SAP may resist reducing maintenance, so you need to demonstrate the specific HCM components are no longer in use.
| Disposition Strategy | When to Use | Annual Cost Impact | Risk |
|---|---|---|---|
| Terminate maintenance immediately at go-live | All HCM functions fully migrated to SF | Save $400K-$1.2M/year | No SAP support if issues arise with legacy data access |
| Reduce maintenance to minimal HCM components | Payroll or specific functions still on-prem temporarily | Save 50-70% of HCM maintenance | Must negotiate specific component reduction with SAP |
| Switch to third-party support | Need ongoing support at lower cost during phased migration | Save 50%+ vs SAP maintenance | No SAP enhancement packs; limited to break/fix and tax updates |
| Retain licences without maintenance for data access | Historical data access needed 1-3 years post-migration | Infrastructure costs only ($20K-$100K/year) | No support; system degradation over time |
| Continue full SAP maintenance post-migration | Never. This is pure waste | $400K-$1.2M/year wasted | Common mistake when migration team does not coordinate with procurement |
In some cases, SAP will offer migration credits that convert a portion of your on-premise licence maintenance investment into SuccessFactors subscription credits. These are not standard and must be negotiated. The credit value typically ranges from 20-50% of one year's HCM maintenance applied as a discount against the SuccessFactors subscription. Always request conversion credits as part of the migration negotiation. Even if SAP initially declines, this is a standard commercial lever SAP has flexibility to offer.
| Cost Category | On-Premise SAP HCM (5-Year) | SuccessFactors (5-Year) | Notes |
|---|---|---|---|
| Software licence / subscription | $0 (already purchased; amortised) | $4.0M-$8.0M (subscription at $50-$100 PEPY x 15K x 5 years) | Cloud subscription is the single largest new cost |
| Annual maintenance / support | $2.0M-$6.0M ($400K-$1.2M/year x 5) | Included in subscription | Dropping maintenance offsets part of subscription cost |
| Infrastructure (servers, DB, storage) | $500K-$2.0M ($100K-$400K/year x 5) | $0 (included in subscription) | Cloud eliminates hardware and hosting costs |
| IT support staff (HCM basis, DBA) | $750K-$2.5M (1.5-5 FTEs x 5 years) | $250K-$750K (reduced cloud admin team) | Cloud reduces but does not eliminate IT support needs |
| Upgrades / enhancement packs | $200K-$1.0M (1-2 upgrades over 5 years) | $0 (automatic quarterly updates) | Cloud eliminates upgrade projects entirely |
| Implementation / migration | $0 (already running) | $1.0M-$5.0M (SI implementation) | One-time migration cost; amortise over contract term |
| Dual-running overlap | N/A | $500K-$2.0M (6-18 month overlap) | Negotiate to minimise; one-time transition cost |
| 5-Year Total | $3.5M-$11.5M | $5.8M-$15.8M | Cloud is often more expensive in pure cost terms |
In most cases, SuccessFactors is more expensive than maintaining on-premise HCM when measured purely on licensing and infrastructure costs over 5 years. The business case rests on strategic value (modern cloud HR platform, quarterly innovation, better employee experience), risk reduction (SAP HCM support ends 2027, extended support 2030), and operational efficiency (reduced IT overhead, eliminated upgrade projects, better data accessibility). Do not approve the migration on the assumption it will be cheaper. Approve it on strategic value, risk reduction, and operational improvement but negotiate the transition to minimise the cost premium. Model the subscription escalation: SAP's default 3-8% annual price increase means a $1.5M/year subscription becomes $1.7M-$2.0M by year 5.
Many organisations do not migrate the entire HCM suite at once. Hybrid scenarios where some HR functions run on-premise and others on SuccessFactors are common and create unique licensing challenges.
The most common hybrid scenario: Employee Central replaces on-premise HR master data, and talent modules move to the cloud, but payroll remains on-premise because cloud payroll migration is complex (country-specific tax rules, union agreements, benefits integrations). In this case you need SuccessFactors subscriptions for all employees, SAP on-premise payroll engine licences for all employees processed, a reduced set of named-user licences for payroll administrators and developers, and integration between Employee Central and SAP Payroll. The key cost lever is reducing on-premise named-user licence count dramatically. If you had 15,000 ESS/MSS users on-premise, those users now access SuccessFactors instead. You can drop to perhaps 50-200 on-premise named users.
| Hybrid Scenario | On-Premise Licences Needed | SuccessFactors Licences Needed | Key Risk | Cost Optimisation Lever |
|---|---|---|---|---|
| Payroll on-prem; core HR + talent on SF | Payroll engine + 50-200 named users | EC + talent modules for all employees | Indirect access on EC-to-Payroll integration | Drop 90%+ of on-prem named users |
| Talent phased: Perf/Comp on SF; Learning on-prem | Learning engine + named users for LMS admins | Performance + Compensation for relevant employees | Duplicate reporting if data not synchronised | Scope SF talent modules to actual user populations |
| Full HCM on-prem; only recruiting on SF | Full HCM named users + engines | Recruiting module only (enterprise or per-recruiter) | Minimal: single module, low integration complexity | Use recruiter-seat model if hiring team is small |
| EC + ECP fully migrated; talent phased | Minimal: archival access only | EC + ECP for all employees; talent modules phased | Low: clean separation | Terminate most on-prem maintenance; add talent over time |
When SuccessFactors sends data to or receives data from the on-premise SAP system (e.g., Employee Central synchronising employee records to SAP Payroll), this data exchange could technically be classified as indirect access under SAP's licensing terms. Ensure your contract explicitly permits this integration without triggering additional indirect access or digital access charges. Get this confirmed in writing as part of the migration agreement.
| Negotiation Lever | What to Request | SAP's Likely Response | How to Counter | Expected Outcome |
|---|---|---|---|---|
| Migration credits | 25-50% of 1 year's HCM maintenance as SF credit | "We don't offer migration credits" | Reference SAP cloud migration programmes; cite competitor alternatives | 15-30% credit typically achievable |
| Ramp-up pricing | 50% reduced subscription for first 6-12 months | "Subscription starts at contract signing" | Point out you derive no production value during implementation | 25-50% reduction for 6 months commonly achieved |
| Maintenance reduction | 50% HCM maintenance reduction during overlap | "Maintenance is a separate contract" | Make both deals contingent on each other; negotiate as a package | Maintenance deferral or reduction achievable |
| Price cap | 0-3% annual increase cap for full term | "Standard terms allow 5% increase" | Calculate 5-year cost difference; make cap a deal condition | 3% cap is standard achievable outcome |
| User count flexibility | Bilateral true-up/true-down at renewal | "True-up only" | Cite restructuring/divestiture scenarios; make flexibility a deal condition | 15-20% reduction band at renewal typically achievable |
You have invested significantly in SAP HCM over many years. SAP should recognise this investment when pricing SuccessFactors. Frame migration credits as loyalty recognition, not as a discount request. SAP has formal and informal programmes for migration credits. They will not volunteer them, but they have authority to offer them.
SAP is strategically motivated to migrate on-premise HCM customers to SuccessFactors. It validates their cloud strategy, grows cloud revenue, and reduces their on-premise support burden. This gives you leverage. SAP needs this migration more than you do in the short term (you can stay on-premise through 2027-2030). Do not present the migration as inevitable. Present it as a decision you are still evaluating, contingent on commercial terms.
Beyond pricing, ensure the contract includes annual price increase cap of 0-3%, bilateral user count adjustment at renewal, module swap rights (exchange underused modules for alternatives), co-terming of all additions to the original contract end date, 180-day renewal notice period (not SAP's standard 30-90 days), data export and portability rights at contract end, and SLA commitments with financial penalties for non-compliance.
For organisations also migrating their core SAP ERP to RISE with SAP (S/4HANA Cloud), the HCM-to-SuccessFactors transition takes on additional dimensions. Some RISE agreements include SuccessFactors as a bundled component, particularly HR-focused RISE configurations. However, the included scope is often limited. It may cover only Employee Central or a basic module set, with additional talent modules priced separately. Always verify exactly which SuccessFactors modules and how many user licences are included in the RISE agreement versus what requires separate purchase.
If both ERP and HCM are migrating, coordinate the timelines. A common approach: migrate SuccessFactors first (typically faster to implement, 6-12 months) while S/4HANA migration continues in parallel (typically 12-24 months). This means Employee Central is live and stable before S/4HANA goes live, providing clean organisational and employee data for ERP integration. This sequencing also lets you begin reducing on-premise HCM maintenance earlier.
RISE deals are large, strategic agreements that SAP's senior leadership tracks closely. The total contract value ($10M-$50M+ over 5 years) gives you significantly more negotiation leverage than a standalone SuccessFactors purchase. Use this leverage to secure better SuccessFactors terms within the RISE umbrella: included modules, deeper discounts, migration credits, flexible terms. SAP's motivation to close the RISE deal means concessions on the SuccessFactors component are often easier to achieve.
SAP's RISE marketing often implies SuccessFactors is included. In practice, the included scope may be limited. Get a line-item breakdown of which SF modules and how many users are covered within RISE versus what is priced separately. Use the RISE deal to negotiate SF terms you could not get standalone. A $20M RISE deal gives you leverage that a $2M SF deal alone would not provide.
| # | Action | Owner | Timeline | Key Outcome |
|---|---|---|---|---|
| 1 | Complete HCM licence inventory: itemise every on-premise HCM licence, metric, net value, and annual maintenance cost | SAP Basis / Procurement | Week 1-4 | Complete baseline for TCO comparison and negotiation |
| 2 | Build 5-year TCO model: compare staying on-premise vs migrating to SuccessFactors across all cost categories | Finance / IT / Procurement | Week 2-6 | Data-driven business case with realistic cost expectations |
| 3 | Define migration scope and phasing: which SF modules, which user populations, what deployment sequence | CHRO / HR Technology | Week 4-8 | Phased roadmap aligned with organisational readiness |
| 4 | Map maintenance renewal dates: identify when each HCM component's maintenance renews to plan cutover timing | Procurement / SAP Basis | Week 4-6 | Optimised cutover timing to minimise wasted maintenance |
| 5 | Prepare negotiation strategy: migration credits, overlap relief, pricing targets, protective contract terms | Procurement / Advisory | Week 6-10 | Comprehensive negotiation plan targeting 20-40% savings |
| 6 | Negotiate with SAP: present unified position covering SF pricing, migration credits, maintenance reduction, and contract terms | Procurement / Advisory / CIO | Week 10-16 | Signed agreement with all protective terms documented |
| 7 | Execute Phase 1 migration: deploy foundation modules (EC, critical talent); begin dual-running period | HR Technology / SI Partner | Month 4-12 | Foundation live; overlap period begins |
| 8 | Reduce on-premise footprint: drop ESS/MSS named users; reduce maintenance per negotiated terms | SAP Basis / Procurement | At SF go-live | Immediate cost reduction on on-premise side |
| 9 | Complete migration phases: deploy remaining modules; terminate remaining on-premise HCM maintenance | HR Technology / Procurement | Month 12-36 | Full SF deployment; minimal or zero on-prem HCM cost |
| 10 | Plan renewal optimisation: begin pre-renewal review 6-9 months before SF contract expires; right-size, benchmark, renegotiate | Procurement / Advisory | 6-9 months before renewal | Optimised renewal with continued cost discipline |
Organisations that follow a structured licensing transition strategy consistently save 20-40% compared to those that accept SAP's default commercial path. The savings come from negotiated migration credits, managed dual-running costs, timely legacy licence disposition, right-sized SuccessFactors subscriptions, and protective contract terms that prevent cost escalation over the contract lifecycle.
No. On-premise perpetual licences and SuccessFactors cloud subscriptions are completely separate commercial agreements. Your existing HCM licences do not convert, transfer, or apply to SuccessFactors. You must purchase a new subscription. However, negotiate migration credits that recognise your existing SAP investment, typically 15-30% of one year's HCM maintenance applied as a subscription discount.
For most enterprises, 6-18 months. Duration depends on migration complexity, number of modules being migrated, and number of countries/entities being cut over. Phased migrations (module by module or region by region) extend the overlap period but reduce risk. Negotiate overlap cost relief regardless of duration.
You can terminate maintenance on HCM-specific components once no longer in production use. Your perpetual licence rights remain. You can still access the software without maintenance, just without SAP support or updates. If HCM licences are embedded in a broader ERP maintenance agreement, negotiate the specific maintenance reduction with SAP rather than simply cancelling.
In most cases, SuccessFactors is more expensive when measured purely on licensing and infrastructure costs over 5 years. The subscription typically costs 2-3x the annual HCM maintenance amount. The business case rests on strategic value (modern platform, innovation), risk reduction (end of on-premise support), and operational efficiency, not pure cost savings.
Yes. This is the most common hybrid scenario. Employee Central replaces on-premise HR master data while SAP Payroll continues running on-premise. You need SuccessFactors subscriptions for all employees plus on-premise payroll engine licences and a reduced set of named-user licences for payroll administrators. Ensure your contract explicitly permits the EC-to-Payroll integration without triggering indirect access charges.
Migration credits are not automatically offered and must be negotiated. Typical outcomes: 15-30% of one year's HCM maintenance applied as a SuccessFactors subscription credit. May be structured as lump-sum discount, annual rate reduction, or included additional modules. SAP has formal migration programmes but does not volunteer them. You must request credits explicitly.
RISE agreements may include SuccessFactors as a bundled component, but included scope is often limited to basic modules. The primary benefit is negotiation leverage: the overall deal value of a RISE agreement gives you more influence to secure better SuccessFactors terms than a standalone purchase. Verify exactly which SF modules and user counts are included versus separately priced.
SAP's standard terms allow 3-8% annual increases. On a $1.5M annual subscription, 7% increases add $600K+ in cumulative cost over a 5-year term compared to flat pricing. Negotiate a cap of 0-3% or, ideally, fixed pricing for the initial contract term. Price caps are one of the most impactful contract terms to secure.
Third-party support (Rimini Street, Spinnaker, etc.) can provide HCM support at 50% or less of SAP's maintenance cost. Particularly effective if you need payroll tax updates or break/fix support during a phased migration. Savings can partially offset SuccessFactors subscription costs. However, third-party support does not include SAP enhancement packs or new functionality.
Begin 9-12 months before your target SuccessFactors contract signing date. You need 4-6 weeks for licence inventory and TCO modelling, 4-6 weeks for negotiation strategy development, and 6-8 weeks for active negotiation with SAP. Starting early also allows you to align cutover timing with SAP maintenance renewal dates, maximising the maintenance cost reduction window.
Redress Compliance provides independent advisory with deep expertise in SAP's commercial models for both on-premise and cloud HR, migration negotiation strategy, and contract structuring that protects the customer's financial interests throughout the transition and beyond. 100% vendor-independent. Fixed-fee engagement.
SAP Licence Optimisation ServicesIndependent SAP advisory. Licence optimisation. Migration negotiation. Contract structuring. 100% vendor-independent, fixed-fee engagement.