An ERP fit-gap analysis identifies where a company's business processes fit the standard capabilities of an ERP system and where the gaps are. The project's scope, development budget and timeline are largely shaped by its output. A shallow fit-gap means expensive surprises later in the project.
1. Map the processes
The analysis starts with processes, not the system. Sales, purchasing, production, inventory and finance are mapped end to end: who works with which document, which approval, in what order? At this stage, write down "how we do it today" and "how we should do it" separately; otherwise old habits get recorded as requirements.
2. Write and prioritise requirements
Each requirement becomes a single, testable sentence, then gets one of three priorities:
- Mandatory: legal obligation or business-critical (for example e-invoicing, export documents)
- Important: brings clear efficiency or control gains
- Nice to have: adds comfort; judged against budget and time
3. Map to the standard system
For each requirement, show how the standard system covers it, ideally in a demo or prototype. The goal is not to say "yes, the system does that" but to answer "how, and at what cost?"
4. Classify the gaps
Each gap gets one of four solution paths:
- Process change: the company adopts the standard. Usually the cheapest and most sustainable solution.
- Configuration: solved through settings, no code.
- Development: a report, interface, form or extension is needed. For extension types see the BAdI vs user exit article.
- Outside the system: a separate application, integration or manual step.
5. Turn the output into a decision document
The output of a fit-gap is not a spreadsheet but a decision document. For each gap it records effort, risk, owner and business justification. Management approves or trims the development list from this document. The approved list becomes the scope baseline, and later requests go through change management.
Common mistakes
- Running the fit-gap with IT only, without process owners
- Solving every gap with development by default
- Leaving reporting and interface needs out of the analysis
- Postponing data migration requirements
From fit-gap to testing
Well-written requirements turn into the scenarios of user acceptance testing at the end of the project, preserving traceability between what was asked for and what was delivered. For an independent ERP consultant, the fit-gap is the most effective tool for putting a project on realistic ground.
