Frequently Asked Questions
Get answers to the most common questions about SAP ECC, S/4HANA migration, RISE with SAP, costs, and timelines.
Timeline & Deadlines
When does SAP ECC support end?
SAP ECC mainstream maintenance ends December 31, 2027. Extended maintenance is available until December 31, 2030 for an additional fee (approximately 2% on top of existing support costs). Third-party support providers offer options beyond 2030.
How long does S/4HANA migration take?
Brownfield conversions typically take 12-24 months. Greenfield implementations take 18-36 months. Complex global deployments can extend to 3-5 years. Add 3-6 months for planning and vendor selection before project start.
When should I start planning my S/4HANA migration?
If you want to complete migration before the 2027 deadline, planning should start no later than 2024-2025. For complex environments, earlier is better. Projects starting in 2026 face resource constraints and rushed timelines.
S/4HANA Migration
What is the difference between S/4HANA greenfield and brownfield?
Greenfield is a new implementation from scratch, allowing complete process redesign but taking longer (18-36 months). Brownfield (system conversion) converts your existing ECC system to S/4HANA, preserving customizations and data with a shorter timeline (12-24 months) but requiring custom code remediation.
What is selective data transition?
Selective data transition (shell conversion) is a hybrid approach where you start with a new S/4HANA system but migrate selected data and configurations from ECC. It offers flexibility between greenfield and brownfield approaches.
What happens to my custom code during S/4HANA migration?
Custom code must be analyzed and remediated. SAP provides the Custom Code Migration app to identify incompatible code. Typical remediation rates: 30-50% of custom objects need modification. This is often the largest effort in brownfield conversions.
Can I keep my existing reports and transactions?
Many classic transactions and reports are replaced by Fiori apps in S/4HANA. SAP provides compatibility modes and transaction equivalents, but expect changes to user workflows. Plan for change management and training.
Costs & Investment
How much does S/4HANA implementation cost?
Costs vary significantly by scope. Small/mid-market: $2-10M. Enterprise: $10-50M. Global deployments: $50-200M+. These include software licensing, implementation services, change management, testing, and internal resources.
Is RISE with SAP cheaper than on-premise S/4HANA?
RISE shifts costs from CapEx to OpEx but total cost of ownership is often similar. RISE may appear cheaper initially but 5-year TCO analysis often shows comparable costs. The value is in infrastructure management and guaranteed updates, not necessarily cost savings.
What are the ongoing costs after S/4HANA go-live?
Expect annual costs for: maintenance/support (17-22% of license), cloud hosting (if applicable), ongoing development, training, and hypercare period support. Budget 15-25% of implementation cost annually for the first 2-3 years.
RISE with SAP
What is RISE with SAP?
RISE with SAP is SAPs bundled cloud offering including S/4HANA Cloud (private or public edition), infrastructure hosting, SAP Business Technology Platform credits, and business transformation services. It shifts spending to subscription-based OpEx.
What is the difference between RISE and GROW with SAP?
RISE with SAP targets large enterprises moving from on-premise ERP to S/4HANA Cloud. GROW with SAP targets small and mid-market companies adopting S/4HANA Cloud Public Edition with pre-configured best practices and faster implementation.
Does RISE with SAP mean SAP manages everything?
No. RISE operates on a shared responsibility model. SAP manages infrastructure and technical operations, but you remain responsible for application configuration, testing, security monitoring, custom code, integrations, and business continuity.
Can I customize S/4HANA in RISE?
Yes, but with guidelines. RISE Private Edition allows custom code similar to on-premise. Public Edition restricts modifications to extensions via SAP BTP. Both require following clean core principles for future upgrade compatibility.
Staying on ECC
Can I stay on SAP ECC after 2027?
Yes. Options include: SAP extended maintenance (until 2030 with 2% premium), third-party support providers like Rimini Street or Spinnaker, or continuing without active support. Many organizations choose to stay while planning strategic transition.
What are the risks of staying on ECC?
Key risks: No security patches (without extended maintenance), limited compliance updates, declining talent pool, no new functionality, and eventual end of all support. These risks are manageable with proper planning.
What is third-party SAP support?
Third-party support providers like Rimini Street offer maintenance and support for ECC at typically 50% lower cost than SAP. They provide tax/legal updates and fixes but not SAP enhancements. Good option for extending ECC life.
Can I modernize ECC without migrating to S/4HANA?
Yes. Options include: implementing Fiori apps on ECC, deploying SAP Business Technology Platform extensions, automating manual processes, improving integrations, and enhancing reporting with analytics tools.
Still Have Questions?
Our interactive assessment can analyze your specific situation and provide personalized guidance.