Before you replace your core system: ERP or better connections?
Distinguish a platform limitation from a reporting or handover problem before committing to an ERP or core-system replacement.
A slow month-end or a growing collection of spreadsheets can make a new ERP feel inevitable. First establish whether the systems cannot run the operation, or whether useful systems are poorly connected and described differently across the business.
Those problems can look alike in a management meeting. They require different investments. A replacement should address a demonstrated limitation, with the data, workflow and ownership decisions made explicit.
Trace the problem back to the work
Follow an order, service request or new customer through the operation. Record where information is entered again, checked against another source or held while someone responds. Include cancellations, corrections and other exceptions.
For a group reporting problem, walk through the last close. List every ledger, account mapping, intercompany adjustment and manual step between the source transactions and the management report. Find the rules that exist only in a workbook or one person's knowledge.
Different charts of accounts or definitions may explain a reporting disagreement even when every ledger is internally consistent. A new platform still needs those differences resolved.
Compare improvements before choosing replacement
| Direction | Strong reason to consider it | Work that remains |
|---|---|---|
| Configure the current system | The required capability exists but is poorly set up or used | Process ownership, training and controlled configuration |
| Connect specialist systems | Each platform performs a useful role but handovers are manual | Field ownership, matching, monitoring and recovery |
| Add a governed reporting layer | Group reporting is repeatedly rebuilt from sound sources | Shared definitions, mappings, access and data quality |
| Replace a component or core platform | Support, controls or the operating model no longer meet requirements | Migration, integrations, acceptance and staff readiness |
The answer may combine several approaches. Improving connections and definitions now can also make a later replacement better informed.
Check what would actually justify an ERP
An ERP deserves serious consideration when core operational processes have outgrown the current applications. Examples could include purchasing controls, manufacturing, multi-location inventory or project management that cannot be represented adequately in the existing environment.
Unsupported software, inadequate access controls and a data model that cannot express required relationships are also material limitations. Document the evidence rather than relying on the system's age or a generic list of missing features.
Ask finance and operations to review these questions separately, then compare their answers:
- Can the current systems run the required work without uncontrolled workarounds?
- Are the main delays inside one application or at handovers between applications?
- Would agreed definitions and account mappings resolve the reporting disagreement?
- Which controls or capabilities must be demonstrated by any replacement?
- Who can own design decisions, testing and rollout alongside ordinary work?
These questions are a discussion aid. A total score cannot determine whether an ERP is the right investment for a particular business.
Build a case around a complete workflow
Test shortlisted approaches with the same representative transactions and exceptions. Compare the effort of implementation and operation, including migration, support, interfaces and future change. Give the comparison a consistent scope.
If a staged replacement is possible, identify boundaries where functions or sites can move safely. Microsoft's Strangler Fig pattern describes one technical approach to incremental replacement, but it depends on the ability to separate and route the relevant work.
Define how the business will judge improvement
Establish a baseline for a few useful measures: manual handovers, unexplained reporting differences, time spent preparing management information and the time needed to complete the affected process. Check quality alongside speed.
Twin's Suntory PepsiCo data hub work demonstrates the value of bringing sources and governance together for cross-functional reporting. It does not establish that a data hub can replace operational capabilities a business lacks.
The decision should explain which limitation matters, how the preferred approach addresses it and what remains outside the new platform. For implementation details, continue with systems integration or staged legacy replacement.