An ERP core strategy is one of the most useful steps in an ERP programme, and it is often left until too late. Many programmes begin with which platform to move to, when to upgrade and how to migrate. Those questions matter, but they can commit a business to a technology decision before it has agreed what the ERP needs to do.
A better starting point is the core itself. Which capabilities genuinely belong inside the ERP, and which could be delivered more effectively elsewhere? Settling that first makes decisions about modernisation, investment and new capabilities clearer. It also helps avoid carrying unnecessary complexity into a new system.
This is a business question before it is a technology one. Finance, operations, supply chain and IT leaders need to agree which processes must run the same way across the organisation, which need room to change quickly, and who is accountable for the data and decisions that go with them.
As specialist applications have matured and integration has become easier, there is more scope than there used to be to decide what stays in the core. There is also more scope to get that decision wrong.
Why the ERP core grows
ERP environments rarely become complex through deliberate design. More often, complexity builds up as organisations respond to departmental requirements, acquisitions, regulatory changes and local needs. Each change is usually reasonable at the time.
The difficulty is that nobody assesses the cumulative effect. Functionality can stay in place after the requirement behind it has changed. Customisations and interfaces become part of everyday processes, and duplicated capabilities and complex dependencies build up without a clear view of the value they still provide.
That has a cost. A heavily customised core is generally more expensive to maintain, harder to upgrade and less straightforward to connect to new applications. A change to one process can affect others, which adds testing effort and slows the response to new requirements.
It matters most when an upgrade or migration is on the table. Treating every existing customisation and interface as a requirement for the future state is a common way to carry complexity into a new platform, and it limits the benefit modernisation was meant to deliver.
ERP core strategy: a practical way to decide
A well-defined core is a stable foundation for the processes and data that need to work consistently across the organisation. That typically means essential financial and operational transactions, core master data and the controls that protect the integrity of business records.
The simplest test is how standard, stable and closely connected to other transactions a process is.
The points below shows the principle:
This is a principle, not a rule. Some specialised processes are so closely tied to core transactions that separating them would add disproportionate integration or control risk. A standard process can sit outside the core if there is a compelling operational or commercial reason.
Each decision also needs to weigh the availability of standard functionality, the cost of customising, and what it would mean to run the process outside the core. The aim is a deliberate boundary between the stable transactional foundation and the capabilities that can evolve more independently.
These are questions for the business as much as for IT. The people who run the processes are best placed to say how standard they are and how often their requirements change.
Where specialist applications add value
Specialist applications are most valuable where requirements go beyond what a broad ERP platform typically offers. Areas where a specialist approach is often worth evaluating include:
These are examples of where a specialist approach is worth evaluating. They are not a case for moving those functions out of the core automatically. The answer depends on the organisation’s requirements, its existing systems and the benefits an alternative could realistically deliver.
There is a commercial side too. A specialist application can avoid extensive ERP customisation or a larger transformation programme, but it adds licensing, integration and support responsibilities. The comparison that matters is the total cost of the resulting architecture, not the functionality of one product in isolation.
We have seen this in practice. In one engagement, a global organisation’s existing provider proposed a solution for a core business function. Helixr recommended a vendor assessment before any commitment was made. The organisation went on to select a specialist platform that cost less than the proposed solution and offered more functionality, and Helixr supported the implementation.
Our Perspective on independent ERP advice, “Independent ERP Advice: Choosing the Right Solution”, looks at how to weigh these options.
Why integration quality decides the outcome
Once capabilities sit around the core, integration decides how well the architecture works. A specialist application can offer excellent functionality, but the benefit is lost if data moves inconsistently, processes need manual intervention or nobody is clear who is responsible when something fails.
Good integration is more than the technical ability to exchange data. The architecture needs to be clear about which system is the master for each data object, and how that data will flow between systems. Without that, it is easy to lose control of both data and processes. It also means deciding how transactions move between applications and how exceptions are found and resolved. Security, access control, monitoring and accountability need to be considered across the whole process, not system by system.
That includes data ownership. Defining the core is not only a question of process ownership. It also needs clarity over where key business data is mastered and governed. Functionality can be spread across several platforms successfully, provided accountability for critical data is clear and each data object has a single master system.
The risk is greatest when a process spans several platforms. Unless the end-to-end workflow is designed and governed, the consistency and visibility the ERP was meant to provide can be lost. Investment in integration therefore needs to go alongside decisions about the scope of the core.
What a defined core means for upgrade, migration and AI decisions
A clear boundary around the core improves the decisions that follow. When it is clear what must stay in, modernisation requirements can be assessed more accurately. Functionality built up through years of customisation may no longer need to be reproduced, and capabilities better suited to specialist applications can be handled in a separate, coordinated programme.
That can reduce the scope and complexity of a migration, although the benefit depends on the existing architecture and the integration work needed. It also supports a phased approach, modernising the core while other capabilities develop at a pace set by business priorities.
It changes the question about an existing platform too. Some organisations will find that their transactional systems remain effective while particular functions need improvement, which points to targeted investment rather than wholesale replacement. Where the core itself has become the constraint, knowing exactly what it is responsible for strengthens the case for transformation.
For SAP ECC customers approaching the end of mainstream maintenance, the same review is a useful first step before choosing between a move to S/4HANA, a phased approach or a period of optimisation. Our Insight, “SAP ECC Support Beyond 2027: What the EU decision means for your options”, covers those choices.
AI adds another reason to make these distinctions. AI capabilities may increasingly work across applications, supporting analysis, automation and coordination without every function sitting on one platform. How well they do so will depend on reliable transactions, accessible data and clearly defined interfaces.
As we explore in our Perspective on ERP and AI strategy, nobody can yet say which version of the future will dominate. A stable, well-governed core with good integration does not decide which technologies to adopt. It gives an organisation more freedom to choose as solutions mature.
Getting the boundary right
There is no universally correct ERP core. The right scope depends on the operating model, industry requirements, existing technology and priorities for future development. A relatively standardised business will draw the line differently from one with highly specialised processes or complex regulatory obligations.
Helixr is independent and system-agnostic. We are an SAP partner and work with other platform providers too, so we can assess these requirements without assuming that any one platform or architecture is the answer. We help organisations understand their existing environment, separate essential core capabilities from functions that could be delivered elsewhere, and weigh the technical and commercial implications of the options.
Our work starts with the business: how processes run, where requirements differ between functions and regions, and who is accountable for decisions and data. We bring that business knowledge alongside technology expertise, which is why we work with finance, operations and supply chain leaders as well as IT.
We also help deliver the result, from simplifying the landscape to implementing the chosen architecture.
Technology choices tend to be easier to make once the boundaries are clear: what the ERP core is expected to do, what it is not expected to do, and how the wider architecture will support both. An ERP core strategy gives an organisation that starting point.
If you are weighing an upgrade, a migration or a major investment, we would be happy to talk through what belongs in your core.
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