Compare SAP S/4HANA deployment models for UK businesses, including Public Cloud, Private Cloud, On-Premise and Two-Tier ERP, and choose the right option.
Choosing the right SAP S/4HANA deployment model is one of the most important decisions UK businesses make during an ERP transformation. The choice affects implementation speed, flexibility, customisation, operating costs, upgrade management, and the way the organisation manages its SAP environment over the long term.
For organisations moving from SAP ECC or another legacy ERP platform, the decision is not simply about choosing between cloud and on-premise infrastructure. It requires an assessment of existing SAP investments, business process complexity, custom development, regulatory requirements, data governance, and the organisation's desired operating model.
UK businesses must also consider requirements such as HMRC Making Tax Digital (MTD), UK GDPR, post-Brexit customs and trade processes, and industry-specific compliance obligations.
This guide explains the main SAP S/4HANA deployment models, compares Public Cloud, Private Cloud, On-Premise, and Two-Tier ERP approaches, and provides a practical framework for selecting the right model for a UK enterprise.
Short Answer: To choose the right SAP S/4HANA deployment model, assess your existing ERP landscape, business process complexity, customisation, data and compliance requirements, and desired level of IT control. Need help selecting the right approach for your UK organisation? Talk to our SAP experts.
Executive Summary: Which SAP S/4HANA Deployment Model Is Right for Your Business?
SAP S/4HANA can be deployed through several models, each designed for different levels of standardisation, flexibility, and operational control.
- SAP S/4HANA Cloud Public Edition: A SaaS model built around standardised processes, Clean Core principles, and SAP-managed innovation. It is generally suited to organisations that can adopt SAP Best Practices and want a faster, more standardised implementation.
- SAP S/4HANA Cloud Private Edition: A dedicated cloud environment providing greater flexibility for complex business processes, existing SAP investments, and controlled transformation programmes. It is commonly considered for large enterprises and SAP ECC migrations.
- SAP S/4HANA On-Premise: A customer-controlled deployment providing the greatest degree of infrastructure and system-management control. It can suit organisations with specific security, operational, or architectural requirements.
- Two-Tier ERP: A strategy that combines SAP environments across different organisational levels, such as a Private Cloud or On-Premise corporate ERP with Public Edition deployments for subsidiaries or newly acquired businesses.
SAP S/4HANA also brings together major ERP capabilities into integrated Lines of Business (LoBs), including:
- Finance
- Sales
- Sourcing and Procurement
- Supply Chain
- Manufacturing
- Asset Management
- R&D and Engineering
The right combination depends on the organisation's existing ERP landscape, business complexity, customisation requirements, operating model, regulatory considerations, and transformation objectives.
SAP S/4HANA Deployment Models Explained
The deployment model determines how SAP S/4HANA is hosted, managed, extended, and updated. It also influences the level of control the organisation has over the ERP environment.
| Deployment Model | Environment | Customisation and Extensibility | Upgrade Approach | Typical Fit |
| Public Edition | SAP-managed SaaS environment | Clean Core and supported extensibility models, including SAP BTP | SAP-managed regular releases | Standardised processes, new implementations, fast-growing organisations |
| Private Edition | Dedicated cloud environment | Greater flexibility for complex requirements and existing SAP investments; Clean Core recommended | Customer has greater control over timing within SAP's lifecycle requirements | Large enterprises, complex SAP landscapes, ECC transformations |
| On-Premise | Customer-managed infrastructure | Broadest system and development control | Customer-managed | Organisations requiring significant infrastructure and operational control |
| Two-Tier ERP | Combination of deployment models | Depends on each tier and integration architecture | Depends on the individual environment | Global organisations, acquisitions, subsidiaries, decentralised operating models |
1. SAP S/4HANA Cloud Public Edition
SAP S/4HANA Cloud Public Edition
SAP S/4HANA Cloud Public Edition is SAP's SaaS deployment model. SAP manages the underlying cloud infrastructure and software environment, while customers adopt a standardised ERP architecture designed around SAP's best-practice processes and Clean Core principles.
The model is particularly attractive to organisations that want to reduce infrastructure management and avoid carrying large amounts of legacy customisation into the new ERP environment.
Key Characteristics
Standardised business processes
Public Edition is designed around SAP Best Practices and a Fit-to-Standard implementation approach. Organisations are generally expected to adapt their processes to the capabilities of the standard solution rather than heavily modify the ERP core.
SAP-managed operations
SAP manages the underlying technical environment and delivers regular software updates and innovations as part of the cloud service.
Clean Core architecture
Direct modifications to the ERP core are not the preferred extension model. Where additional functionality is required, organisations can use supported extensibility approaches, including side-by-side extensions through SAP Business Technology Platform (SAP BTP).
Faster implementation potential
Because the platform provides preconfigured processes and a highly standardised operating model, Public Edition can support faster implementations than heavily customised ERP environments, although actual timelines depend on scope and organisational complexity.
Best Fit for UK Organisations
Public Edition can be a strong option for:
- new SAP implementations;
- mid-market organisations with relatively standard processes;
- fast-growing businesses;
- subsidiaries and newly acquired companies;
- organisations willing to adopt SAP Best Practices;
- businesses looking to reduce legacy technical debt.
Main Constraint
The principal trade-off is flexibility. Organisations with highly specialised processes or significant legacy customisation may find the standardised Public Edition model more restrictive than Private Edition or On-Premise.
SAP S/4HANA Cloud Private Edition
2. SAP S/4HANA Cloud Private Edition
SAP S/4HANA Cloud Private Edition provides a dedicated cloud environment with greater flexibility than Public Edition. It is particularly relevant to enterprises with complex processes, existing SAP landscapes, significant custom developments, or requirements for a more controlled transition from SAP ECC.
Private Edition is commonly associated with RISE with SAP, SAP's transformation offering that combines SAP software with cloud infrastructure and services.
Key Characteristics
Greater functional and technical flexibility
Private Edition is designed to support more complex enterprise scenarios and provides a broader transition path for organisations with existing SAP investments.
Support for complex SAP landscapes
Enterprises can assess existing custom developments, integrations, industry-specific processes, and historical ERP configurations and determine which elements should be retained, redesigned, or retired.
Controlled transformation
Private Edition can support different transformation approaches, including system conversion, new implementation, and selective data transition, depending on the target architecture and project strategy.
Clean Core remains important
The additional flexibility of Private Edition should not be interpreted as a reason to carry all legacy customisation forward. Organisations should still reduce unnecessary modifications and move suitable extensions outside the core wherever possible.
Best Fit for UK Organisations
Private Edition is often considered by:
- large enterprises;
- organisations migrating from complex SAP ECC environments;
- multinational groups;
- businesses with industry-specific processes;
- organisations with significant existing SAP customisation;
- companies requiring a phased ERP transformation.
Main Constraint
Private Edition generally involves greater implementation and operating complexity than a highly standardised Public Edition deployment. Organisations must also actively manage their customisation and technical debt rather than simply transferring it into the new environment.
3. SAP S/4HANA On-Premise
SAP S/4HANA On-Premise
SAP S/4HANA On-Premise allows an organisation to operate SAP S/4HANA within infrastructure that it controls directly or through a hosting arrangement.
This model provides the highest degree of control over infrastructure, system architecture, integrations, and operational policies, but it also places more responsibility on the organisation.
Key Characteristics
Infrastructure control
The organisation is responsible for decisions around infrastructure, operating environments, system architecture, security controls, and maintenance.
Greater technical flexibility
On-Premise provides broad options for system-level configuration and development, subject to SAP's product and support framework.
Customer-controlled operations
The organisation has greater responsibility for upgrades, maintenance, monitoring, security, backup, disaster recovery, and technical operations.
Best Fit for UK Organisations
On-Premise may be appropriate where organisations have:
- specific infrastructure or security requirements;
- significant existing SAP investments;
- highly controlled operating environments;
- specialised integration requirements;
- internal capabilities for managing SAP infrastructure;
- regulatory or operational constraints affecting cloud adoption.
Main Constraint
The additional control comes with additional responsibility. Infrastructure costs, specialist SAP skills, maintenance, security, upgrades, and lifecycle management can create a significant long-term operating burden.
For this reason, On-Premise should generally be selected because there is a clear business, regulatory, or architectural reason for retaining infrastructure control rather than simply because it is the traditional ERP model.
4. SAP S/4HANA Two-Tier ERP
SAP S/4HANA Two-Tier ERP
Two-Tier ERP is not simply another hosting option. It is an architectural strategy for organisations that operate different SAP environments at different levels of the enterprise.
For example, a multinational organisation could maintain S/4HANA Private Edition as its corporate ERP while deploying S/4HANA Cloud Public Edition for smaller subsidiaries, newly acquired companies, or less complex business units.
Example Two-Tier Architecture
| Organisational Tier | Possible Deployment | Primary Role |
| Tier 1: Corporate ERP | S/4HANA Private Edition or On-Premise | Group finance, core operations, governance, consolidation |
| Tier 2: Subsidiaries | S/4HANA Cloud Public Edition | Local operations, standardised processes, rapid deployment |
Why Use Two-Tier ERP?
A single global ERP template may be unnecessarily expensive or slow to deploy across every entity.
Two-Tier ERP can help organisations:
- onboard acquisitions faster;
- standardise core processes without forcing one architecture everywhere;
- reduce deployment complexity for smaller entities;
- maintain corporate financial visibility;
- support different levels of business complexity;
- create a scalable architecture for international growth.
The success of this approach depends heavily on integration, master data governance, security, and clearly defined responsibilities between the two tiers.
SAP S/4HANA Public Cloud vs Private Cloud
SAP S/4HANA Public Cloud vs Private Cloud
For many organisations, the most important decision is whether to adopt Public Edition or Private Edition.
Both provide a cloud-based SAP S/4HANA environment, but they are designed around different operating models.
| Decision Factor | Public Edition | Private Edition |
| Primary Model | Standardised SaaS ERP | Dedicated cloud ERP |
| Process Strategy | Fit-to-Standard | Greater flexibility for complex processes |
| Customisation | Strong focus on Clean Core and supported extensibility | Greater flexibility, with Clean Core still recommended |
| Existing ECC Complexity | Better suited to organisations willing to redesign processes | Better suited to complex SAP transformation scenarios |
| Implementation Approach | Primarily new implementation / standardised deployment | New implementation, system conversion, or selective transition depending on scenario |
| IT Operations | SAP-managed | Managed cloud model with greater customer control |
| Innovation Model | Regular SAP-managed updates | More controlled lifecycle and upgrade planning |
| Typical Strength | Standardisation and speed | Flexibility and transition from complex landscapes |
| Typical Trade-Off | Less flexibility for specialised requirements | More complexity and governance |
The Key Decision
The question should not simply be:
"Which cloud model is better?"
Instead, organisations should ask:
"How much standardisation can our business realistically adopt, and how much legacy complexity do we need to transform?"
If the organisation is prepared to standardise processes and minimise customisation, Public Edition can provide a highly streamlined operating model.
If the organisation has substantial SAP investments, complex business processes, or a large transformation backlog, Private Edition may provide a more practical transition path.
SAP S/4HANA Migration Approaches: Greenfield vs Brownfield vs Selective Data Transition
Choosing a deployment model is only one part of an SAP S/4HANA transformation. Organisations also need to determine how they will move from their existing ERP environment to the target S/4HANA architecture.
The main SAP S/4HANA transformation approaches are Greenfield, Brownfield (System Conversion), and Selective Data Transition. Each approach offers a different balance between process transformation, continuity, data retention, implementation complexity, and technical risk.
The right choice depends on the quality of the existing ERP environment, the amount of customisation, the importance of existing business processes, data migration requirements, and the organisation's willingness to redesign its operating model.
| Migration Approach | What It Means | Best Suited For | Primary Advantage | Main Trade-Off |
| Greenfield | New S/4HANA implementation based largely on SAP standard processes | Organisations seeking significant business transformation or moving from non-SAP ERP | Clean starting point and strong process standardisation | Requires greater process change and data migration planning |
| Brownfield / System Conversion | Existing SAP ERP system is converted to S/4HANA | Organisations with valuable existing SAP processes, configuration, and investments | Preserves more of the existing SAP environment | Can carry legacy complexity and technical debt forward |
| Selective Data Transition | Selected data, processes, and configuration are moved into a new S/4HANA environment | Complex enterprises seeking a balance between continuity and transformation | Greater control over what is retained and redesigned | More complex transformation and data planning |
Greenfield: New SAP S/4HANA Implementation
A Greenfield implementation creates a new S/4HANA environment rather than directly converting the existing ERP system.
The organisation can redesign business processes around SAP standard functionality, adopt SAP Best Practices, rationalise customisations, and establish a Clean Core from the beginning.
Greenfield can be particularly appropriate for:
- organisations implementing SAP for the first time;
- businesses replacing a non-SAP legacy ERP;
- companies with heavily fragmented or outdated processes;
- organisations willing to standardise their operating model;
- enterprises using the transformation to achieve significant process redesign.
The main benefit is the opportunity to avoid reproducing unnecessary legacy complexity. However, Greenfield requires more extensive business process design, data migration, testing, change management, and user adoption.
Brownfield: SAP S/4HANA System Conversion
A Brownfield approach, commonly referred to as System Conversion, transforms an existing SAP ERP environment into SAP S/4HANA while retaining a significant portion of the existing configuration, processes, and business investment.
This approach can be attractive to organisations that have a mature SAP ECC environment and want to modernise the technical platform without completely redesigning their business processes.
Brownfield can be appropriate where:
- existing SAP processes remain strategically important;
- the organisation has significant investment in SAP configuration and data;
- business disruption needs to be minimised;
- the organisation wants a more controlled transition to S/4HANA;
- there is a clear business case for retaining selected existing capabilities.
However, System Conversion should not simply become a technical exercise of moving legacy ERP into a new platform. Existing custom code, integrations, and processes should be assessed before conversion to determine what should be retained, redesigned, replaced, or retired.
Selective Data Transition
Selective Data Transition sits between a full Greenfield implementation and a traditional Brownfield conversion.
Instead of either rebuilding everything from scratch or converting the existing ERP system largely as-is, the organisation selectively moves relevant data, processes, configuration, or organisational structures into the target S/4HANA environment.
This approach can be valuable for large enterprises with complex ERP landscapes, multiple business units, acquisitions, or historical data requirements.
For example, an organisation may decide to:
- redesign selected business processes using SAP standard functionality;
- retain specific business capabilities that continue to provide value;
- migrate only relevant historical data;
- consolidate multiple ERP environments;
- establish a new organisational structure while preserving required operational information.
The main advantage is flexibility. The organisation can determine what should be retained and what should be transformed rather than applying the same approach to the entire ERP landscape.
The trade-off is increased planning and execution complexity. Data selection, transformation, reconciliation, testing, and integration require careful governance.
How Migration Approach and Deployment Model Relate
The migration approach should be considered together with the target deployment model.
For example:
- Greenfield + Public Edition can suit organisations prioritising standardisation, rapid adoption, and a Clean Core.
- Brownfield + Private Edition can provide a practical path for complex SAP ECC transformations where existing investments remain important.
- Selective Data Transition + Private Edition can suit large enterprises that need to combine process transformation with continuity.
- Two-Tier ERP + Greenfield Public Edition can support rapid deployment of standardised S/4HANA environments for subsidiaries or newly acquired businesses.
There is no universally correct combination. The decision should be based on the target operating model, existing ERP landscape, business transformation objectives, data requirements, and acceptable level of change.
How to Choose the Right Migration Approach
A practical assessment should consider five questions:
- How valuable is the existing ERP configuration?
If existing processes provide genuine business value, a conversion or selective transition may be preferable to rebuilding everything. - How much technical debt exists?
Extensive custom code, outdated processes, and complex integrations may make a Greenfield transformation more attractive. - How much process change is the business prepared to accept?
Greenfield requires greater willingness to adopt new processes, while Brownfield generally preserves more of the existing operating model. - What historical data must be retained?
Data retention and migration requirements can materially influence the transformation approach and target architecture. - What is the desired future operating model?
The organisation should define its target business and IT model first rather than allowing the limitations of the legacy ERP system to dictate the S/4HANA architecture.
The objective is not simply to move the existing ERP to S/4HANA. A successful transformation should determine which existing capabilities are worth preserving, which should be redesigned, and which can be retired — while creating a target architecture that remains scalable and maintainable over the long term.
SAP S/4HANA Modules and Lines of Business
Once the deployment model is defined, organisations also need to determine which SAP S/4HANA capabilities should be included in the target ERP landscape.
SAP S/4HANA organises these capabilities into integrated Lines of Business (LoBs) rather than treating ERP functions as completely separate modules.
| SAP S/4HANA Line of Business | Key Capabilities | Traditional SAP Modules |
| Finance | General Ledger, Accounts Payable, Accounts Receivable, Asset Accounting, Controlling, Treasury, Group Reporting | FI, CO, FI-AA, Treasury |
| Sales | Sales orders, pricing, delivery, billing, availability checks, order-to-cash | SD |
| Sourcing and Procurement | Purchasing, supplier management, contracts, requisitions, purchase orders, invoice matching | MM-PUR, MM-IV |
| Supply Chain | Inventory management, warehousing, transportation, logistics, trade processes | MM-IM, LE-WM, EWM, TM |
| Manufacturing | MRP, production planning, production execution, quality management | PP, QM |
| Asset Management | Maintenance planning, work orders, equipment management, asset performance | PM / EAM |
| R&D and Engineering | Project management, product lifecycle management, engineering changes, BOM management | PS, PLM |
These capabilities share the SAP S/4HANA digital core and can connect operational processes with their financial and analytical impact.
For example, a sales process can connect order management, availability, delivery, billing, and financial accounting within an integrated architecture rather than relying on disconnected systems and extensive batch-based reconciliation.
The exact functional scope should depend on the organisation's industry, operating model, existing applications, and transformation priorities.
How to Define the Right Functional Scope
The goal should not be to implement every available SAP S/4HANA capability. Functional scope should be determined by the organisation's business model, industry requirements, existing systems, and transformation priorities.
A practical approach is to:
- identify the core processes that must move to S/4HANA;
- assess which legacy capabilities can be replaced by SAP standard functionality;
- determine which specialised requirements need additional SAP solutions or extensions;
- define which processes should remain outside the S/4HANA core;
- align functional scope with the selected deployment model.
For example, a manufacturing organisation may prioritise Finance, Manufacturing, Supply Chain, Procurement, Sales, and Asset Management, while a professional services business may place greater emphasis on Finance, Sales, Project Management, and Procurement.
The selected deployment model and functional scope should therefore be considered together.
UK Regulatory Considerations for SAP S/4HANA
UK Regulatory Considerations for SAP S/4HANA
Deployment decisions for UK organisations should account for regulatory and compliance requirements from the beginning of the architecture process.
HMRC Making Tax Digital
SAP S/4HANA can support digital tax reporting processes and integration with HMRC services. The exact configuration and integration requirements depend on the organisation's tax processes, SAP architecture, and applicable HMRC requirements.
UK GDPR
UK GDPR requirements should be addressed through appropriate data governance, access controls, security architecture, retention policies, and processing controls.
Cloud deployment does not automatically determine GDPR compliance. Organisations must assess the complete data-processing and security architecture, including where data is stored, how it is accessed, and which providers process it.
Post-Brexit Trade and Customs
Organisations involved in UK-EU trade may require processes supporting customs declarations, commodity classification, duties, import/export controls, and related documentation.
SAP solutions such as SAP Global Trade Services can support relevant trade and customs scenarios where required.
Industry-Specific Requirements
Financial services, healthcare, defence, public sector, and other regulated industries may have additional requirements affecting infrastructure, security, auditability, data management, and operational resilience.
These requirements should be assessed before selecting a deployment model rather than treated as an implementation-stage issue.
How to Choose the Right SAP S/4HANA Deployment Model
How to Choose the Right SAP S/4HANA Deployment Model
There is no universal deployment model that is best for every organisation. The right decision depends on several dimensions.
1. Assess the Existing ERP Landscape
Start by understanding the current environment.
Consider:
- Is the organisation already running SAP ECC?
- How heavily customised is the existing system?
- How many integrations exist?
- How complex are the current business processes?
- Is the business consolidating multiple ERP systems?
- Is historical data required in the new environment?
A highly customised SAP ECC landscape typically requires more detailed transformation planning than a new implementation from a non-SAP ERP.
2. Define the Target Process Model
Determine how willing the business is to change its existing processes.
If the organisation is prepared to adopt SAP Best Practices and standard workflows, Public Edition may be attractive.
If business-critical processes require substantial redesign, complex functionality, or controlled transition from an existing SAP environment, Private Edition may provide greater flexibility.
3. Establish the Customisation Strategy
Inventory existing custom developments and classify them according to business value.
For each custom solution, ask:
- Is it still required?
- Does SAP standard functionality now cover the requirement?
- Can the process be redesigned?
- Can the functionality be implemented through supported extensibility?
- Does it provide genuine competitive differentiation?
This assessment helps prevent historical technical debt from dictating the future architecture.
4. Evaluate IT Operating Capabilities
The organisation should also consider how it wants to operate SAP after implementation.
A SaaS-oriented model can reduce infrastructure management and allow internal IT teams to focus more on business applications and transformation.
An On-Premise model provides greater control but requires stronger internal capabilities across infrastructure, security, SAP Basis, database management, monitoring, and lifecycle management.
5. Assess Regulatory and Security Requirements
Identify requirements affecting:
- data residency;
- data protection;
- cybersecurity;
- auditability;
- business continuity;
- operational resilience;
- industry-specific controls.
Do not assume that a particular deployment model is automatically compliant. Compliance depends on the complete architecture and operating controls.
SAP S/4HANA Deployment Decision Matrix
SAP S/4HANA Deployment Decision Matrix
The following framework can help executive teams structure the initial assessment.
| Business Requirement | Public Edition | Private Edition | On-Premise |
| Rapid standardised implementation | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
| Maximum process standardisation | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
| Complex existing SAP landscape | ⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Existing ECC transformation | ⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ |
| Extensive legacy customisation | ⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Infrastructure control | ⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Reduced infrastructure management | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐ |
| Clean Core adoption | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ |
| Subsidiary / acquisition deployment | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐ |
These ratings are directional rather than universal. The appropriate deployment model should be validated against the organisation's actual SAP landscape, requirements, and target operating model.
SAP S/4HANA Deployment Models: Real-World Scenarios
Public Edition: Fast-Growing Consumer Goods Company
A UK consumer goods company is expanding across Europe and wants to replace a fragmented legacy ERP environment.
The business has relatively limited customisation and is willing to standardise finance, procurement, sales, and reporting processes.
Why Public Edition Fits
The organisation can adopt SAP Best Practices rather than reproduce legacy processes. SAP-managed infrastructure and regular updates also reduce the need for the internal IT team to manage complex ERP infrastructure.
Potential Outcomes
- Standardised processes across entities
- More consistent reporting
- Reduced reliance on spreadsheets
- Lower infrastructure management requirements
- Faster onboarding of new business units
The critical success factor is the company's willingness to standardise rather than customise.
Private Edition: International Manufacturing Group
A UK-headquartered manufacturing group operates across multiple countries and has a combination of SAP ECC, local ERP platforms, and custom applications.
Several manufacturing and finance processes depend on existing custom developments, while the group also needs a phased migration strategy.
Why Private Edition Fits
Private Edition can provide a more flexible transition path for a complex SAP landscape. The organisation can assess existing developments, redesign unnecessary customisation, and retain critical capabilities where there is a clear business case.
Potential Outcomes
- Controlled migration from SAP ECC
- Greater process harmonisation
- Phased transformation across entities
- Reduced infrastructure management
- Support for complex manufacturing and finance processes
The key requirement is flexibility combined with cloud transformation.
On-Premise: Organisation Requiring Maximum Infrastructure Control
An organisation has strict internal security and operational policies and requires direct control over its SAP infrastructure, integrations, and system lifecycle.
It has the internal technical capability to operate SAP and a clear business reason for retaining infrastructure control.
Why On-Premise Fits
On-Premise allows the organisation to retain control over infrastructure architecture, technical operations, security configuration, integrations, and upgrade planning.
Potential Outcomes
- Maximum infrastructure control
- Alignment with internal security policies
- Greater control over system operations
- Preservation of specialised enterprise architecture
The trade-off is a higher operational responsibility compared with managed cloud models.
Two-Tier ERP: Global Enterprise with Multiple Acquisitions
A global group operates a central S/4HANA environment but continues to acquire smaller companies that use different ERP platforms.
Deploying the corporate ERP template to every acquisition would be expensive and slow.
Why Two-Tier ERP Fits
The group can maintain its central SAP environment while deploying a more standardised S/4HANA Cloud environment for selected subsidiaries.
Potential Outcomes
- Faster acquisition integration
- Consistent group reporting
- Standardised master data and integration
- Greater local agility
- Scalable ERP architecture
The key requirement is balancing central governance with local deployment speed.
RISE with SAP vs GROW with SAP
RISE with SAP vs GROW with SAP
RISE with SAP and GROW with SAP are commercial and transformation offerings associated with different SAP cloud adoption scenarios. They should not be treated simply as alternative technical deployment models.
RISE with SAP
RISE with SAP is primarily associated with enterprise transformation and is commonly used with SAP S/4HANA Cloud Private Edition. It can provide a managed framework for organisations transitioning complex SAP environments to the cloud.
It is particularly relevant for organisations that need to modernise existing SAP landscapes while retaining greater flexibility.
GROW with SAP
GROW with SAP is designed to help organisations adopt SAP S/4HANA Cloud Public Edition using a more standardised implementation approach.
It is particularly relevant for businesses starting a new SAP implementation and willing to adopt SAP standard processes.
The Practical Difference
The decision should therefore begin with the desired S/4HANA deployment model and business operating model, rather than choosing RISE or GROW as an isolated product decision.
Clean Core and SAP S/4HANA Deployment
Clean Core and SAP S/4HANA Deployment
A Clean Core strategy should be considered regardless of whether the organisation chooses Public Cloud, Private Cloud, or On-Premise.
The principle is straightforward:
Keep the ERP core as standard as practical and implement differentiated functionality through supported extension and integration patterns.
This approach helps organisations:
- reduce technical debt;
- simplify future upgrades;
- adopt SAP innovations more easily;
- reduce the cost of maintaining custom code;
- separate business differentiation from core ERP operations.
SAP BTP can support side-by-side extensions, integrations, data services, and custom applications where appropriate.
The objective is not to eliminate all customisation. It is to ensure that every extension has a clear business justification and is implemented in an architecture that remains maintainable over time.
SAP S/4HANA Cost Considerations
The cost of an SAP S/4HANA transformation depends on much more than the selected deployment model. Organisations should evaluate the total cost of ownership (TCO) across implementation, licensing or subscriptions, migration, integrations, customisation, infrastructure, and ongoing support. For a more detailed breakdown of implementation costs and the factors that influence SAP S/4HANA investment in the UK, see our SAP S/4HANA implementation cost guide for UK businesses.
The main cost factors include:
- SAP licensing or subscription costs: The commercial model and required SAP capabilities influence the recurring cost of the solution.
- Implementation scope: The number of business processes, legal entities, countries, users, and Lines of Business affects the size and complexity of the implementation.
- Migration complexity: Moving from a heavily customised SAP ECC environment can require significantly more analysis, remediation, testing, and data migration than a new implementation.
- Customisation and extensions: Existing custom code may need to be redesigned, replaced by standard SAP functionality, or rebuilt using supported extension approaches such as SAP BTP.
- Data migration: The volume, quality, history, and transformation requirements of legacy data can materially affect project effort.
- Integration: Connections to CRM, HR, banking, tax, e-commerce, warehouse, manufacturing, and other third-party systems can add significant implementation and ongoing support requirements.
- Infrastructure and operations: Public Edition can reduce the organisation's responsibility for infrastructure management, while Private Edition and On-Premise may involve different levels of technical and operational responsibility.
- Testing, training, and change management: Business adoption, user training, process redesign, testing, and organisational change are important parts of the overall transformation cost.
- Ongoing support and optimisation: The business case should also account for application support, monitoring, security, upgrades, extensions, and continuous improvement after go-live.
Public Cloud vs Private Cloud vs On-Premise: Cost Profile
The deployment model affects where costs and responsibilities sit, rather than simply determining whether an implementation is expensive or inexpensive.
| Cost Area | Public Edition | Private Edition | On-Premise |
| Infrastructure management | Lower customer responsibility | Managed cloud model with greater flexibility | Highest customer responsibility |
| Implementation complexity | Generally lower for standardised processes | Generally higher for complex environments | Depends heavily on existing landscape |
| Customisation | Lower | Higher flexibility | Broadest flexibility |
| Migration from complex ECC | May require significant process redesign | Often more suitable for complex transitions | Can support complex transitions |
| Upgrade management | SAP-managed | More controlled lifecycle | Customer-managed |
| Internal IT requirements | Generally lower | Moderate to high | Highest |
| Long-term TCO drivers | Subscription, implementation, extensions, integrations | Subscription, implementation, customisation, operations | Infrastructure, licences, implementation, support, upgrades |
The most appropriate model should therefore be evaluated against the organisation's business requirements and long-term operating model, rather than selected solely on the basis of initial implementation cost.
For example, a Public Edition deployment may reduce infrastructure and technical management requirements but require greater process standardisation. Private Edition may involve a more complex transformation but provide a more practical path for enterprises with significant SAP investments. On-Premise can provide maximum control, but the organisation assumes greater responsibility for infrastructure, security, maintenance, and lifecycle management.
Building an SAP S/4HANA Business Case
Before selecting a deployment model, organisations should model both initial transformation costs and ongoing TCO. A realistic business case should compare the expected investment against potential benefits such as reduced legacy-system costs, process automation, faster financial reporting, improved operational visibility, and lower technical debt.
For complex SAP transformations, a detailed assessment of the existing ERP landscape can help identify migration complexity, integration requirements, customisation risks, and the most appropriate target architecture before implementation begins.
SAP S/4HANA Deployment Checklist
SAP S/4HANA Deployment Checklist
Before selecting a deployment model, UK organisations should be able to answer the following questions:
Existing Landscape
- Are we migrating from SAP ECC or another ERP?
- How much custom code do we have?
- How many third-party integrations are business-critical?
- Do we need to consolidate multiple ERP systems?
Business Processes
- Which processes can move to SAP standard functionality?
- Which processes genuinely require differentiation?
- How willing are business teams to change existing workflows?
Data and Compliance
- What data needs to be migrated?
- What are the retention requirements?
- What data protection and residency requirements apply?
- Which UK tax, customs, or industry regulations affect the solution?
IT Operating Model
- How much infrastructure do we want to manage ourselves?
- What SAP technical skills do we have internally?
- How much control do we need over upgrades?
- What are our security and business continuity requirements?
Future Strategy
- Do we want a standardised cloud ERP?
- Are we planning acquisitions or international expansion?
- Will subsidiaries require different ERP deployment models?
- How will we maintain a Clean Core?
Conclusion
Conclusion
Selecting an SAP S/4HANA deployment model is a strategic ERP decision rather than simply a technology or hosting choice.
-
SAP S/4HANA Cloud Public Edition is generally strongest when an organisation can standardise processes, minimise customisation, and adopt a SaaS operating model.
-
SAP S/4HANA Cloud Private Edition provides greater flexibility for complex enterprises, existing SAP investments, and organisations transitioning from highly customised ECC environments.
-
SAP S/4HANA On-Premise remains relevant where an organisation has specific requirements for infrastructure control, technical independence, or specialised operational policies.
-
Two-Tier ERP can provide a scalable strategy for organisations that need to combine a central SAP environment with faster, more standardised deployments for subsidiaries and acquisitions.
The decision should ultimately be based on the organisation's existing ERP landscape, process complexity, customisation strategy, regulatory requirements, IT operating model, and long-term transformation objectives.
Once the deployment model is established, the next step is to define the appropriate S/4HANA functional scope and determine which business capabilities should form part of the target digital core.
With the right SAP S/4HANA Consulting approach, organisations can align deployment architecture, business processes, integrations, and extensibility strategy before implementation begins.
With multiple SAP S/4HANA options available, our consultants can help you choose the right path
Frequently Asked Questions
What are the main SAP S/4HANA deployment models?
The main deployment options are SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, and SAP S/4HANA On-Premise. Organisations can also use a Two-Tier ERP strategy that combines different deployment models across corporate and subsidiary environments.
What is the difference between SAP S/4HANA Public Cloud and Private Cloud?
Public Edition is a SaaS model focused on standardised processes, Clean Core, and SAP-managed innovation. Private Edition provides a dedicated cloud environment with greater flexibility for complex processes, existing SAP investments, and enterprise transformation scenarios.
What is the best SAP S/4HANA deployment model for SAP ECC migration?
The appropriate model depends on the complexity of the existing ECC environment. Organisations with significant customisation, complex integrations, and specialised processes often consider Private Edition, while organisations willing to redesign processes around SAP standard functionality may consider Public Edition.
What is the difference between RISE with SAP and GROW with SAP?
RISE with SAP is primarily associated with enterprise transformation and is commonly used with SAP S/4HANA Cloud Private Edition. GROW with SAP is designed around adoption of SAP S/4HANA Cloud Public Edition and standardised implementation approaches.
Which SAP S/4HANA deployment model is best for a UK enterprise?
There is no universal answer. Public Edition can suit organisations prioritising standardisation and faster SaaS adoption, while Private Edition or On-Premise may be more appropriate where complex processes, existing SAP investments, or specific control requirements are important.
What are the main SAP S/4HANA Lines of Business?
The main functional areas include Finance, Sales, Sourcing & Procurement, Supply Chain, Manufacturing, Asset Management, and R&D and Engineering. The exact scope depends on the organisation's industry and business processes.
Does SAP S/4HANA Public Cloud support custom ABAP?
SAP S/4HANA Cloud Public Edition does not support direct modification of the ERP core. Organisations should use supported extensibility mechanisms, including SAP BTP and other SAP extension frameworks, to implement additional functionality while maintaining a Clean Core.
What is a Clean Core strategy in SAP S/4HANA?
Clean Core is an approach to keeping the S/4HANA core as standard and maintainable as practical. Custom functionality is implemented through supported extension and integration mechanisms where appropriate, reducing technical debt and simplifying future innovation and upgrades.
How does SAP S/4HANA support UK regulatory requirements?
SAP S/4HANA can support UK tax, financial, data governance, and trade processes through standard functionality, localisation, configuration, and integrations. Requirements such as Making Tax Digital, UK GDPR, and post-Brexit customs processes should be assessed as part of the overall solution architecture rather than treated as deployment-model decisions alone.
Is SAP S/4HANA On-Premise still relevant?
Yes. On-Premise remains an option for organisations with specific infrastructure, security, operational, or architectural requirements and sufficient internal capabilities to manage the environment. However, the additional control also brings greater responsibility for infrastructure, maintenance, security, and lifecycle management.
What is Two-Tier ERP?
Two-Tier ERP is a strategy in which an organisation operates different ERP environments at different organisational levels. For example, a corporate headquarters may use S/4HANA Private Edition while subsidiaries use S/4HANA Cloud Public Edition. This can support faster subsidiary deployments while maintaining central governance and financial visibility.
How should a company choose an SAP S/4HANA deployment model?
Start by assessing the existing ERP landscape, business process complexity, customisation, integration requirements, regulatory obligations, IT operating model, and future growth plans. The organisation should then compare these requirements against the standardisation and flexibility offered by each deployment model.
Disclaimer: The information in this article is provided for general informational purposes only. SAP S/4HANA deployment options, commercial programmes, product capabilities, support policies, regulatory requirements, and implementation approaches may change over time. The appropriate deployment model depends on each organisation's ERP landscape, business processes, data, customisations, integrations, security requirements, and project objectives. Examples are illustrative and should not be interpreted as guarantees of specific results. A detailed assessment of the existing SAP environment and business requirements is recommended before making deployment, technology, or investment decisions.
.webp)
