S/4HANA is Not One Size Fits All: A Practical Guide to Every Deployment Flavour
A breakdown of every S/4HANA deployment path, greenfield, brownfield, bluefield, RISE, and SaaS, with guidance on when to use each and how AWS services map to each approach.
Introduction
One of the most common questions I hear from customers planning their SAP S/4HANA journey is: "Which deployment path is right for us?"
The answer is never simple because S/4HANA isn't a single product with a single deployment model. It's an ecosystem with multiple flavours, each designed for different business contexts, timelines, and risk appetites. Choosing the wrong path can mean months of rework, blown budgets, or a stalled transformation entirely.
This guide breaks down every major S/4HANA deployment flavour, when to use each one, and how AWS services map to each approach.
The Deployment Spectrum
| Approach | What It Means | Best For | Timeline |
|---|---|---|---|
| Greenfield | Fresh install, clean slate, no legacy data | New subsidiaries, M&A carve-outs | 12 to 18 months |
| Brownfield | In-place upgrade from ECC to S/4HANA | Preserve customizations and historical data | 9 to 15 months |
| Bluefield | Hybrid: new system shell, selective data migration | Clean system but keep some history | 12 to 24 months |
| Landscape Transformation | Consolidate multiple ECC systems into one | Post-M&A consolidation | 18 to 30 months |
| RISE with SAP | SAP-managed infrastructure | Offload infra management to SAP | 6 to 12 months |
| S/4HANA Cloud Public | Full SaaS, multi-tenant | Mid-market, standard processes | 3 to 6 months |
1. Greenfield (New Implementation)
A completely fresh S/4HANA installation with no data migration from legacy systems. You start from SAP Best Practices and configure forward.
When to Choose This
Pick greenfield when you're spinning up a new business unit, when an acquired company needs its own standalone ERP, when your current ECC is so heavily customized that conversion would cost more than starting fresh, or when you genuinely want to adopt SAP Best Practices and re-engineer your business processes.
AWS Architecture Considerations
Use Amazon EC2 with x2idn or u-series instances for HANA, sized for your target state rather than legacy. AWS Launch Wizard for SAP automates the HA deployment with pre-validated architectures. Set up AWS Backup from Day 1 without worrying about legacy data dependencies.
Risks to Watch
Business users lose historical reporting. Mitigate this by keeping legacy in read-only mode or archiving to Amazon S3 with Amazon Athena for queries. Expect a longer user adoption curve since the UI and processes are new.
2. Brownfield (System Conversion)
An in-place technical upgrade where your existing ECC system gets converted to S/4HANA. Data, customizations, and configurations carry forward.
When to Choose This
Go brownfield when you have heavy investment in custom ABAP code you want to preserve, when regulations require data continuity for audit trails and financial history, when you have a tight timeline with no appetite for process re-engineering, or when you're running fewer than 3 production ECC instances.
AWS Architecture Considerations
Right-size your Amazon EC2 instances for HANA memory requirements using the SAP HANA sizing report. Use Amazon EBS io2 Block Express for consistent IOPS on HANA persistence. AWS Application Migration Service handles the lift-and-shift of your ECC system first, then you convert in the cloud. Plan for a temporary compute burst during conversion since those runs can be CPU and memory intensive.
Risks to Watch
Custom code remediation takes time. Use SAP Readiness Check and Custom Code Analyzer early. Your HANA database footprint will be larger because historical data carries over. Plan for downtime during cutover.
3. Selective Data Transition (Bluefield)
A hybrid approach using tools like SAP S/4HANA Migration Cockpit or third-party options (SNP CrystalBridge, Syniti) to selectively move data objects into a fresh S/4HANA shell.
When to Choose This
Bluefield works when you want a clean S/4HANA system but must retain select master data, open items, or historical transactions. It's also the right fit when regulatory requirements mandate certain data retention but you don't want the full legacy baggage, or when you're consolidating multiple ERPs into one instance.
AWS Architecture Considerations
You'll run parallel landscapes: source (ECC) and target (S/4HANA) simultaneously during transition. Use Amazon S3 as a staging area for extracted data objects. AWS Glue and AWS DMS handle ETL for non-SAP data sources. Amazon Redshift serves as the historical data warehouse for legacy data that doesn't move to S/4HANA.
4. Landscape Transformation (Consolidation)
Using SAP Landscape Transformation (SLT) or similar tools to merge multiple ECC or S/4HANA systems into a single target instance.
When to Choose This
This fits post-M&A situations where you've inherited multiple SAP instances, when you're running 5 or more ECC systems across regions, or when you have a standardization mandate from leadership.
AWS Architecture Considerations
Your target system must handle the combined workload across Multi-AZ or Multi-Region. Amazon EC2 High Memory instances (u-24tb1) support very large consolidated HANA databases. AWS Direct Connect provides dedicated connectivity for bulk data replication. AWS Transit Gateway handles network connectivity between multiple VPCs.
5. RISE with SAP (Private Cloud Edition)
SAP manages the infrastructure and base platform while you retain control over the application layer. It runs on AWS but SAP handles the operations.
When to Choose This
Go with RISE when you want to reduce infrastructure management overhead, when you don't have the internal team to manage HANA operations, or when you're comfortable with SAP managing patching, upgrades, and HA.
AWS Architecture Considerations
Infrastructure is managed by SAP (running on AWS behind the scenes). Your customer-managed extensions still run on your own AWS account through BTP and side-car apps. AWS PrivateLink provides secure connectivity between your VPC and the SAP-managed environment.
6. S/4HANA Cloud, Public Edition (SaaS)
Full multi-tenant SaaS where SAP manages everything: infrastructure, application, and upgrades. Customization is limited to clean core and key user extensibility only.
When to Choose This
This works for mid-market companies with standard processes, organizations with minimal custom development, teams that prioritize fast time-to-value, and businesses comfortable with quarterly mandatory upgrades.
AWS Architecture Considerations
Your AWS footprint is minimal since SAP manages the runtime. Focus on integration: connecting S/4HANA Public Cloud to your other AWS workloads. Amazon EventBridge handles event-driven integration. Amazon API Gateway plus Lambda serves as middleware for real-time integrations.
Decision Framework
Ask yourself these questions in order:
Do you have existing ECC? If no, go Greenfield or Public Cloud.
Must you preserve ALL historical data? If yes, go Brownfield.
Multiple ECC systems to consolidate? If yes, go Landscape Transformation.
Want SAP to manage infra? If yes, go RISE with SAP.
Otherwise, Selective Data Transition (Bluefield) is likely your best fit.
Key Takeaways
- There is no "default" path. Each deployment flavour solves a different business problem.
- Start with the business question, not the technical one.
- AWS provides infrastructure flexibility for every flavour.
- Don't underestimate the functional workload. Process alignment is where projects stall.
- Plan for coexistence. Most real-world migrations involve multiple flavours across different business units.
Further Reading
- SAP S/4HANA on AWS: https://docs.aws.amazon.com/sap/latest/general/s4hana.html
- AWS Launch Wizard for SAP: https://docs.aws.amazon.com/launchwizard/latest/userguide/what-is-launch-wizard-sap.html
- SAP on AWS Architecture Best Practices: https://docs.aws.amazon.com/sap/latest/general/arch-guide-architecture-guidelines-and-decisions.html
- AWS Well-Architected SAP Lens: https://docs.aws.amazon.com/wellarchitected/latest/sap-lens/sap-lens.html
- Certified Instance Types: https://docs.aws.amazon.com/sap/latest/general/sap-planning-certified-instances.html
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article