SAP’s July 2026 maintenance and support commitments have given organisations greater freedom to divide their on-premise landscapes into separate Commercial Installations, each with its own support arrangements. For businesses considering how to manage established systems alongside modernisation programmes, this creates another option worth examining.
The principle is relatively simple. Systems that have different operational requirements may benefit from different support models. Yet an SAP landscape is rarely organised around such neat boundaries. Years of integration, shared infrastructure and evolving business processes can make apparently separate systems difficult to disentangle.
A landscape split is therefore a genuine option, but its value depends on what can be separated in practice, the work required to achieve it and the consequences for the business once the split is complete.
What does an SAP landscape split involve?
Under SAP’s Landscape Split Program, an organisation can divide an existing on-premise installation into separate Commercial Installations. Each can then follow a different maintenance and support arrangement, including SAP support, an alternative provider or no maintenance and support.
The important distinction is that this flexibility applies to Commercial Installations, rather than individual modules or licence items. Each resulting installation must have its own installation number, at least one production system and a corresponding non-production system, together with the technical components and licences needed to operate independently.
Licences must be allocated in accordance with actual usage and remain auditable. Where SAP support is selected, the relevant SAP support model must apply consistently within that Commercial Installation.
These conditions matter because a business may regard two applications as separate while their technical foundations remain closely connected. Establishing a commercial boundary requires evidence that the resulting installations satisfy SAP’s requirements, not simply a decision to allocate different support contracts to different systems.
What can realistically be separated?
SAP’s guidance distinguishes between systems with relatively limited technical dependencies and those that are highly integrated. Separate regional ERP installations, for example, may be candidates for a split where they can operate independently and meet the programme’s conditions. Similarly, a specialist application with its own technical environment may warrant investigation.
However, a product name or business function is not enough to establish eligibility. An application that appears self-contained may still depend on shared components, common development environments or tightly coupled processes elsewhere in the landscape.
SAP generally advises against splitting highly integrated systems. Customers may propose such arrangements, but the technical consequences and associated risks remain their responsibility. SAP Note 3776551 provides further guidance, including a non-exhaustive discussion of systems considered less tightly integrated.
This distinction is particularly important for the central ERP environment. Separating individual functions from a heavily integrated core can be substantially more difficult than dividing genuinely independent installations. The question is whether the proposed boundary reflects how the systems actually operate, including their dependencies, rather than how the organisation would prefer to purchase support.
The six practical workstreams
A credible landscape split assessment needs to bring commercial, technical and operational analysis together. Six areas are particularly important:
|
Workstream
|
The question to answer
|
Where complications arise
|
|---|---|---|
|
Licence allocation |
Which entitlements and users belong to each installation? |
Shared usage, incomplete records and audit exposure |
|
Integration |
Which interfaces cross the proposed boundary? |
Tightly coupled processes and unclear fault ownership |
|
Shared data |
How will information remain accurate and consistent? |
Common master data, reconciliation and ownership |
|
Environments |
Can each installation meet the technical requirements? |
Shared development, test or infrastructure components |
|
Additional licensing |
Will the proposed configuration require further entitlements? |
New systems, users or usage not covered by existing rights |
|
Support accountability |
Who resolves issues spanning different installations? |
Gaps between providers, escalation and diagnostic access |
These workstreams are closely connected. A decision to create an additional non-production environment, for instance, may affect infrastructure costs, licence requirements, integration testing and support responsibilities. A technically workable design may therefore need to be reconsidered once its commercial implications become clear.
SAP’s commitments do not automatically require customers to purchase additional licences or reprice existing ones simply because they undertake a split. Additional entitlements may nevertheless be necessary for the intended configuration or usage. Accurate licence mapping is consequently essential before financial benefits can be assessed.
Technical preparation is equally important. The necessary systems, interfaces and licences must be ready before the commercial split is executed. SAP’s role in assessing the proposed separation should not be mistaken for responsibility for designing or implementing the resulting architecture; that remains with the customer.
Support arrangements must work across the boundaries
One of the less obvious consequences of a landscape split is the need to manage business processes across different support arrangements.
Consider a transaction that begins in one installation and depends on data or functionality in another. If it fails, each provider may be able to demonstrate that the system within its responsibility is functioning correctly, while the end-to-end process remains disrupted.
This is why support accountability deserves attention before a split takes effect. Organisations need clear arrangements for incident investigation, access to diagnostic information, escalation between providers and responsibility for problems involving interfaces or shared processes.
Different support models may also provide different coverage for updates, security requirements and regulatory changes. The appropriate choice depends on the role of each system, its risk profile and how long the organisation expects to retain it.
A split may offer more choice over individual installations, but the business still needs an effective operating model for the landscape as a whole.
Costs and timing: looking beyond the split itself
Potential maintenance savings are often the starting point for considering a landscape split. They should not be treated as an automatic outcome.
SAP’s programme states that dividing a Commercial Installation does not, in itself, reduce the aggregate SAP support fees associated with the original installation. Any change in expenditure depends on the support arrangements subsequently selected. The business case must also account for technical implementation, additional environments, possible licensing requirements and the ongoing cost of coordinating separate installations.
The timetable introduces another consideration. SAP provides for requests to be processed within six months, with effective dates falling on 1 January, 1 April, 1 July or 1 October, subject to the programme’s conditions.
For example, consider a request submitted on 9 November 2026. If SAP completes processing and the requirements are confirmed before the end of December, an effective date of 1 January 2027 may be possible. If processing is completed in January, the next quarterly date would be 1 April 2027. If SAP uses the full six-month processing period, the next quarterly date would be 1 July 2027.
These dates illustrate the processing rules, rather than guaranteeing when an individual split will take effect. Incomplete technical preparation can move execution to a later quarter. Contractual obligations also need to be considered: a split does not restart the existing Initial Term for maintenance and support, and that term may affect when a different SAP support model can begin.
SAP also requires customers or relevant partners to be current on payments due, while eligible customers purchasing through resellers must coordinate the process through the reseller. These conditions, together with any contractual notice requirements, need to be understood before committing to a timetable.
Is a landscape split the right option?
A landscape split can be useful where systems have sufficiently distinct technical and operational requirements to justify different support arrangements. It may allow an organisation to retain a stable application under one model while continuing to develop or modernise other parts of its estate.
For highly integrated environments, however, the cost and complexity of separation may outweigh the anticipated benefit. The same assessment may also reveal that a phased migration, architectural simplification or different approach to support would better serve the organisation’s objectives.
The decision should therefore form part of a wider ERP strategy, with the proposed support arrangements assessed against the actual landscape, its future direction and the business’s tolerance for operational risk.
At Helixr, our independent, system-agnostic approach allows us to assess these options without assuming that a landscape split is necessarily the preferred outcome. Understanding technical dependencies, licence implications and the full cost of each route is essential to making a sound decision.
SAP’s revised commitments have created greater choice for organisations managing on-premise systems. The practical value of that choice depends on whether the proposed separation is technically achievable, commercially worthwhile and sustainable in operation.
This article provides general commentary on SAP’s published maintenance and support commitments. Organisations should review the applicable programme requirements and their individual contracts, and obtain appropriate legal and licensing advice before making contractual changes.
Further information can be found by reading:
Helixr’s Insight: SAP ECC Support Beyond 2027: Your Options | Helixr
SAP’s: landscape-split-program.pdf
Neil has an astute eye for detail and excels at bringing teams together to deliver results. Always positive in outlook, he combines over 24 years experience in delivering complex business change solutions with natural people skills.
From experience in manufacturing, warehousing and logistics to delivering global ERP solutions, his wide-ranging knowledge combined with his calm, measured approach means he is adept at delivering solutions that work.
Through planning and due diligence to execution and stabilisation
Understanding the levers for successful integration
Expertly navigate the challenges and risks
Unpick the opportunities to drive the bottom line

Disentangling a well-established site from a complex corporate infrastructure-with stringent timelines, local compliance challenges, and a rigid transitional services agreement (TSA) in place.
Expertly navigate the challenges and risks.
Combining processes, systems and people to deliver maximum results
Working with what you've got to make things even better
Making your data work for you to deliver
real insight

How we streamlined and future-proofed, a soon-to-be obsolete labelling solution and a rapid client expansion across multiple new sites.
Enhancing decision making and strategic
alignment to drive performance
Using the latest technology to drive efficiencies, innovation and operational excellence
Meeting local requirements while
delivering smooth cross-border
operations
Simplifying supply chain finance
Improving compliance accuracy and
automation using tax technology