SAP S/4HANA Migration Services

Section 01

The December 31, 2027 Cliff: Why Nearly Half of Enterprises Will Miss the Deadline

SAP ECC mainstream maintenance ends on December 31, 2027. After this date:

• ❌ No security patches (PCI-DSS and SOX audit failures)
• ❌ No functional enhancements (no new functionality while competitors innovate)
• ❌ Shrinking talent pool (SAP ECC developers retiring, S/4HANA skills shortage)

Important distinction by version: ECC 6.0 EHP 6–8 users have until December 31, 2027, with optional extended support to 2030. ECC 6.0 EHP 0–5 users already lost mainstream support at end of 2025, with no extended maintenance option.

The Math: SAP ECC 6.0 mainstream maintenance ends on 31 December 2027, with optional extended maintenance to the end of 2030 at extra cost. Plan the migration window backwards from those dates.

• Brownfield (System Conversion): 12-18 months — borderline achievable for a Dec 2027 go-live if you start now
• Bluefield (Hybrid): 18-24 months — realistically targets 2028
• Greenfield (Clean Slate): 24-36 months — plan for 2029+ or accept extended support costs

Current Status: Many ECC customers had not yet migrated or licensed S/4HANA as of Q4 2024, so a large number of organizations will still be running legacy ERP when mainstream support ends. Gartner expects 40–45% of ECC users to remain on ECC through 2027.

---

How to Choose an SAP S/4HANA Migration Partner

If you have massive custom code (20K+ lines): Infosys. Their code remediation tooling, including Panaya, targets automated refactoring at scale.

If you are in a regulated industry (Pharma/Finance): Deloitte. They prioritize governance and risk management, to avoid compliance breaches during migration.

If you want "SAP as a Service" (RISE): IBM Consulting. They are a top partner for RISE with SAP deployments and hybrid cloud architectures.

If you have complex data consolidation needs: Capgemini. They excel at Master Data Governance (MDG) and consolidating multiple ERP instances.

If you need a single partner for end-to-end transformation: Accenture. They handle everything from strategy to hypercare for global rollouts.

Red flags:

• Vendors who don't insist on a "Code Scan" before quoting a price
• No clear strategy for "Brownfield" vs "Greenfield" (trying to sell one size fits all)
• Lack of specific experience with your industry vertical (e.g., Oil & Gas vs Retail)
• Ignoring the "Data Quality" workstream in the timeline

The Partner Capacity Crunch

Migration urgency is driving demand for SAP consulting services. With many organizations still needing to migrate, finding experienced implementation partners is itself a bottleneck:

• Many organizations attempting S/4HANA migrations have little or no in-house staff who have worked on S/4HANA; ask each partner which named people will staff your program
• Project manager selection and availability often receive too little attention in planning
• A 2027 go-live is now realistic only for small brownfield programs with limited custom code and a partner already secured

If you're starting migration planning in mid-2026 or later, set realistic expectations: 2028–2029 go-live is the most achievable target for mid-size and enterprise organizations, with extended support costs in the interim. The 2033 RISE-tied option exists for the most complex global organizations.

---

Section 02

Why S/4HANA Projects Fail: What the Data Shows

Independent studies from 2025–2026 paint a consistent picture:

• ~60% of SAP migration projects are delayed and over budget (ISG survey of 200 senior decision-makers, February 2026)
• More than 60% report deviations in budget, schedule, and result quality — with 25% "heavily" and 40% "strongly" exceeding budget (Horváth study, 2025)
• Transformations take on average 30% longer than planned (Horváth)
• 65% report strong to very strong quality deficits post-migration despite overruns (Horváth)

1. The Custom Code Trap

SAP has deprecated 19,000+ function modules in S/4HANA. If you have 50K+ lines of custom ABAP (Z* programs), you carry a large remediation risk. A material share of custom ABAP in many ECC systems is unused or non-compliant with S/4HANA standards; a scan quantifies it for your estate.

Reality: Code remediation is routinely under-budgeted because the custom code footprint is discovered late. Size it from a code scan rather than a generic share of program cost. Fix: Run an ABAP Test Cockpit (ATC) scan and Custom Code Migration Worklist (CCMW) via SAP Readiness Check before you sign any SI contract. Deferring remediation to the test phase doubles the cost compared to addressing it in the Explore phase.

2. Scope Creep and Decision-Making Bottlenecks

Executives love "Greenfield" because it promises transformation. But your legacy system contains 20 years of undocumented business logic. And across all project types, 78% of programs report too many equally-prioritized objectives tackled simultaneously (Horváth).

Reality: When you rebuild processes from scratch, users push back because "the new system doesn't do what the old one did." Scope creep also hits brownfield and bluefield programs mid-stream when adjacent business change requests get absorbed. Fix: Use Process Mining (Signavio/Celonis) to map actual workflows before redesigning them. Establish a strict scope freeze with executive enforcement after the Explore phase.

3. Data Migration Complexity

S/4HANA requires strict data consistency. The Business Partner model mandates migrating all customers and vendors (KNA1/LFA1) into unified BUPA records. For organizations with tens of thousands of records and poor data hygiene, this is often the single longest-running data preparation workstream. The Universal Journal (ACDOCA) and mandatory Material Ledger activation create additional pre-migration data quality requirements (see technical section below).

Reality: Cutover delays commonly trace to data migration errors and delayed business sign-off. Fix: Start data cleansing 12 months before the technical migration. Business Partner harmonization must be treated as a standalone workstream, not a cutover task.

4. People, Not Technology

Many migration teams have little or no internal S/4HANA experience, and demand for SAP consulting is high. The result can be inexperienced teams on both the client and partner side, with PM selection and availability receiving insufficient attention.

Reality: UAT cycles can run well past plan because of custom code regressions and undertrained testers. Fix: Secure your implementation partner immediately — not after scoping — and verify their S/4HANA delivery track record. Budget for change management and training separately ($20K–$100K for Fiori enablement alone).

---

Section 03

SAP S/4HANA Migration Roadmap

Phase 1: Preparation & Business Case (Months 1-3)

Activities:

• Run SAP Readiness Check and ABAP Test Cockpit (ATC)
• Define strategy (Greenfield vs Brownfield vs Bluefield)
• Build TCO model and secure board approval
• Select System Integrator (SI) partner

Deliverables:

• Readiness Assessment Report
• Approved Business Case ($8M-$50M budget)
• Signed SI Contract

---

Phase 2: Explore & Design (Months 4-8)

Activities:

• Fit-to-Standard workshops (Greenfield) or Custom Code Analysis (Brownfield)
• Design target architecture (RISE vs Native Cloud)
• Start Data Cleansing (Business Partner harmonization)
• Set up Sandbox environment

Deliverables:

• Blueprint / Design Documents
• Data Migration Strategy
• Sandbox System active

---

Phase 3: Realize & Build (Months 9-18)

Activities:

• Code Remediation (fixing Z* programs)
• Configuration of S/4HANA modules
• Data Migration cycles (Mock 1, Mock 2, Mock 3)
• Integration testing with non-SAP systems

Risks:

• Data migration load failures across mock cycles
• Custom code remediation taking longer than planned

Deliverables:

• Configured QA System
• Validated Data Migration scripts
• UAT Sign-off

---

Phase 4: Deploy & Hypercare (Months 19-24)

Activities:

• Cutover rehearsal (Dress Rehearsal)
• Production Cutover (usually a long weekend)
• Hypercare support (24/7 for 4-8 weeks)
• Decommission legacy ECC system

Deliverables:

• Go-Live
• Stable Production System
• Project Closure Report

---

Section 04

Post-Migration: Living with S/4HANA

Months 1-3: Stabilization

• Performance Tuning: HANA is an in-memory database. Poorly written SQL queries that worked on Oracle will crash HANA. Monitor expensive statements.
• User Adoption: Fiori UX is different from SAP GUI. Expect resistance. Run weekly "Lunch and Learn" sessions.

Months 4-6: Innovation

• Embedded Analytics: Turn on standard Fiori analytics apps. Stop dumping data to Excel.
• Process Automation: Use SAP Build Process Automation to replace manual workflows.

---

Section 05

The 3 Migration Strategies: Decision Matrix

As of early 2026, ISG research found 34% of organizations choosing brownfield, 18% greenfield, and nearly half (48%) opting for a bluefield hybrid. ISG explicitly notes that brownfield and hybrid approaches "may limit long-term benefits and make it more difficult to adopt newer technologies such as AI" due to fragmented processes and legacy data structures.

1. Brownfield (System Conversion) ⚡ Fastest — 34% of orgs

What it is: Technical upgrade. Convert your existing SAP ECC system to S/4HANA using SAP's Software Update Manager (SUM) and Database Migration Option (DMO).

Timeline: 12-18 months Cost: $300K-$800K (mid-size, 500-2K users) | $5M-$50M (enterprise, 5K+ users) Pros:

• ✅ Fastest path (borderline viable for Dec 2027 go-live if starting now)
• ✅ Retains all historical data and customizations
• ✅ Lower risk (no business process redesign)

Cons:

• ❌ You bring forward all technical debt (custom code, workarounds)
• ❌ No business transformation (same old processes, new platform)
• ❌ Lower post-migration AI readiness — fragmented processes and legacy data structures
• ❌ Custom code remediation is still required regardless

Best For:

• Manufacturers with highly complex, industry-specific processes and decades of clean transactional data
• Tight timelines with low tolerance for business disruption
• Organizations where stability matters more than transformation

---

2. Greenfield (Clean Slate) 🌱 Highest Risk, Highest Reward — 18% of orgs

What it is: Reimplementation from scratch. Install a fresh S/4HANA instance, redesign business processes, migrate only historically relevant data.

Timeline: 24-36 months Cost: $1M-$3M (mid-size) | $50M-$300M+ (enterprise) | $400M+ (Fortune 500 / global) Pros:

• ✅ Forces best-practice process redesign
• ✅ Eliminates technical debt entirely
• ✅ Highest post-migration AI readiness — clean processes, clean data
• ✅ Unlocks full S/4HANA innovation (Fiori UX, embedded analytics, AI/ML)

Cons:

• ❌ Longest timeline — 2027 go-live is not achievable for enterprise programs
• ❌ Over 60% of SAP migration programs exceed budget and timeline (Horváth 2025) — greenfield amplifies this
• ❌ Requires Subject Matter Experts who know undocumented business rules
• ❌ Scope creep risk is highest — legacy systems contain 20+ years of undocumented logic

Best For:

• Companies entering new markets or consolidating multiple ECC systems
• Organizations willing to trade short-term disruption for a genuinely modern platform
• New SAP adopters with nothing to migrate

---

3. Bluefield (Hybrid) 🔵 Most Popular in 2026 — ~48% of orgs

What it is: Selective data transition. Redesign critical processes, migrate only the data you need, keep some historical data where it matters.

Timeline: 18-24 months Cost: $600K-$1.5M (mid-size) | $20M-$80M (enterprise) Pros:

• ✅ Balances speed and transformation
• ✅ Allows process redesign where it matters most without full reimplementation
• ✅ Avoids the "bring everything forward" trap of Brownfield

Cons:

• ❌ Adds coordination complexity — two systems during transition
• ❌ Requires mature data governance (you need to know what to keep/discard)
• ❌ Medium post-migration AI readiness — selective redesign leaves some fragmentation

Best For:

• Organizations that want some process optimization but can't justify full reimplementation
• Mid-sized enterprises (500-5,000 users) with data governance in place

---

Section 06

Engagement Models: Choose Your Path

1. DIY / Assessment (<$100K)

• Tools: SAP Readiness Check, ABAP Test Cockpit (ATC), Process Mining (Celonis)
• Goal: Understand your custom code footprint and data quality before hiring an SI.

2. Guided Strategy ($100K-$500K)

• Deliverables: Business Case, Roadmap, Vendor Selection (RFP management)
• Goal: Select the right strategy (Greenfield vs Brownfield) and partner.

3. Full Migration ($2.5M+)

• Deliverables: Technical migration, code remediation, testing, hypercare
• Goal: Execute the migration on time and on budget.

---

Section 07

Custom Code: The Silent Budget Killer

SAP has deprecated 19,000+ function modules and database tables in the move to S/4HANA. If your organization has custom ABAP code (Z* and Y* programs), you must:

1. Scan your code using SAP Readiness Check or ABAP Test Cockpit (ATC)

2. Classify findings:

   • Red (Blocker): Deprecated function modules (must rewrite)
   • Yellow (Warning): Performance issues (should optimize)
   • Green (OK): Compatible with S/4HANA

3. Remediate:

   • Low (<5K lines): $500K-$2M (editorial scoping ranges)
   • Medium (5K-20K): $2M-$10M
   • High (20K-50K): $10M-$50M
   • Extreme (50K+): $50M-$150M

The Hidden Trap: Most organizations discover their true custom code footprint 12 months into the project. By then, it's too late to change strategy.

Action: Run a Custom Code Assessment in your Planning phase (cost: $50K-$150K). This will save you $10M+ in scope creep.

---

Section 08

The Data Migration Technical Challenges No One Warns You About

These are the issues that consistently cause go-live delays and post-migration firefighting:

1. Universal Journal (ACDOCA) and the End of Reconciliation

S/4HANA replaces separate FI and CO tables with a single Universal Journal (ACDOCA). During brownfield conversion, all historical FI/CO documents must be migrated and balanced. Any data quality issues in ECC — inconsistent profit center assignments, incorrect cost element classifications — surface here as hard blockers that halt the conversion.

2. FI Document Splitting

Document splitting enables real-time financial statements by segment or profit center at the line-item level. It is not retroactively applied to historical documents during a brownfield conversion. Organizations that want segment reporting must either activate splitting on go-live date (accepting limited historical drill-down), or run a parallel pre-conversion GL migration. SAP recommends activating document splitting from the first day of the new fiscal year and running a single project per company code group if fiscal years differ. This decision must be made during the Explore phase — changing it post-go-live is extremely expensive.

3. Material Ledger: Mandatory for Everyone

In S/4HANA, Material Ledger (ML) is mandatory and activated for all materials — even for organizations that never used actual costing. This forces a data migration of ML opening balances and requires currency type configuration decisions before cutover. For companies with large international inventories and multiple currencies, this is a substantial data preparation workload that surprises teams who assumed only actual costing clients would be affected.

4. Business Partner (BUPA) Mandatory Migration

ECC stores customers and vendors in separate master data tables (KNA1 and LFA1). S/4HANA mandates the Business Partner (BUPA) model, requiring all customers and vendors to be migrated and de-duplicated into Business Partner records before go-live. For organizations with tens of thousands of customer/vendor masters — particularly those with poor data hygiene — BUPA harmonization is frequently the single longest-running data preparation workstream. Start this 12+ months before cutover.

5. Data Volume and HANA Licensing Implications

S/4HANA on HANA in-memory pricing is partly license-influenced by data volume. Large organizations often discover they are carrying 20+ years of transactional data that must be archived or selectively migrated, creating unexpected cost and timeline pressure. Build a data archiving strategy into Phase 1, not Phase 3.

---

Section 09

RISE with SAP vs Native Cloud (AWS/Azure): The Great Debate

RISE with SAP (SAP-Managed Private Cloud)

What it is: SAP hosts your S/4HANA instance, manages infrastructure, and bundles licensing into a single subscription.

Pros:

• ✅ Simplified procurement (single contract vs negotiating with SAP + AWS)
• ✅ Managed services (SAP handles patching, upgrades, backups)
• ✅ Faster deployment (SAP pre-configures infrastructure)
• ✅ OpEx model (no upfront infrastructure CapEx)

Cons:

• ❌ Vendor lock-in (tied to SAP's cloud strategy)
• ❌ Less control (you can't customize infrastructure)
• ❌ Potentially higher long-term costs (2-5 year contract lock-in)

Best For:

• Organizations with low cloud maturity (no AWS/Azure expertise)
• Finance/HR teams who want "SAP as a Service"
• Companies wanting to shift from CapEx to OpEx

---

Native Cloud (AWS/Azure/GCP)

What it is: You deploy S/4HANA on AWS EC2, Azure VMs, or Google Compute Engine. You manage infrastructure.

Pros:

• ✅ Full control (customize infrastructure, networking, security)
• ✅ Integration with cloud-native services (Lambda, S3, Databricks, Power BI)
• ✅ Cost optimization (Reserved Instances, Spot Instances, auto-scaling)
• ✅ Multi-cloud strategy (avoid single-vendor lock-in)

Cons:

• ❌ Requires in-house cloud expertise (DevOps, FinOps, Security teams)
• ❌ More complexity (you own the infrastructure stack)
• ❌ Higher upfront planning (network design, disaster recovery, compliance)

Best For:

• Enterprises with mature cloud platforms (already on AWS/Azure)
• Organizations with cloud-native architectures (Kubernetes, microservices)
• Companies optimizing for long-term cost (5-10 year horizon)

---

Section 10

Hidden Costs You Must Budget For

The split below is an illustrative allocation for a hypothetical $8M project, not a measured benchmark.

What's NOT Included:

• Ongoing managed services ($50K-$500K/year)
• SAP licensing (typically 20-30% annual increase)
• Extended SAP support if you delay ($2M-$10M/year for large enterprises)

---

Section 11

ROI & Business Case

Operational Savings (Post-Migration)

• Faster batch processing (real-time vs overnight jobs), to be measured in a pilot
• Lower infrastructure cost where in-memory computing eliminates data redundancy, to be validated against your hosting costs
• Faster financial close (Siemens reported 10 days → 3 days)

Break-Even Timeline

Divide one-time investment by documented annual savings (operational savings plus extended-support costs avoided, net of new run costs), and include the parallel-run period. Use your own cost baseline rather than a generic payback figure.

Only migrate if you plan to stay on S/4HANA for several years. If you're exploring non-SAP alternatives (Oracle, Microsoft), factor in switching costs ($20M-$50M).

---

Evidence note: Earlier versions of this page cited project counts, median costs and timelines, success rates and unsourced cohort statistics that could not be reproduced from available records; they have been withdrawn. Survey figures are attributed to Horváth and ISG. Cost and timeline ranges are editorial scoping ranges, not supplier quotes. See our methodology.

---

Section 12

Risk Factors

December 31, 2027 Support Deadline

SAP ECC mainstream maintenance ends December 31, 2027. Post-deadline: no security patches, no innovation, and a shrinking talent pool. Extended support available to 2030 at ~2% annual maintenance premium (EHP 6-8 only — EHP 0-5 support already ended in 2025).

Custom Code Remediation

SAP has deprecated 19,000+ function modules and database tables. Custom ABAP code must be refactored. For enterprises with 50K+ lines of custom code, this can be a very large line item; scope it from a code scan (editorial scoping range up to $150M for the most extreme estates).

Migration Overruns Are the Norm, Not the Exception

Over 60% of SAP migration programs report budget and schedule deviations (Horváth, 2025; ISG, 2026). Projects run 30% longer than planned on average. Greenfield carries the highest individual risk; brownfield programs still routinely exceed timeline and budget due to underestimated custom code and data complexity.

---

Section 13

Feasibility Analysis

Ideal candidates

• SAP ECC 6.0 with <20K lines of custom code (Brownfield conversion in 12-18 months)
• Organizations with clear process redesign mandate (Greenfield with executive buy-in)
• Finance/Manufacturing verticals with standard processes (pre-built industry solutions)

Break-even cost: Divide one-time investment by documented annual operational savings net of new run costs; include extended-support costs avoided and the parallel-run period Talent risk: HIGH - SAP ECC talent aging out, S/4HANA skills shortage