Every implementation starts with a version of the same question: how does your business actually work? Most companies answer it from memory, in a meeting — and the answer is wrong in ways nobody notices until configuration is half built.
Mapping the process first is the least glamorous phase of an ERP project. It is also the one that decides most of the outcome.
What you find is not what you were told
The documented procedure and the real one diverge quietly. There is a spreadsheet somebody built in 2021 that the whole approval chain now depends on. There is a step everyone skips because it stopped making sense two reorganisations ago. You cannot configure around what you have not seen.
It separates the process from the workaround
A large share of what a team does every day exists only because the current system cannot do something. Those steps should not be rebuilt — they should disappear. Without a map they get faithfully reproduced in the new system, and the company pays good money to preserve its own workarounds.
It turns arguments into decisions
When two departments describe the same process differently, that is not a documentation problem. It is an unresolved decision about how the business should run. Surfacing it on a diagram, before anyone has configured anything, makes it a normal management conversation instead of a change request with a price tag.
It makes scope real
Once the current state is on paper, the gap between it and the standard system becomes visible and countable. That gap is your scope. Estimating without it is guessing, and guessing is how timelines quietly double.
It gives you a baseline
If you never measured how long order-to-invoice took before, you will never be able to say what the ERP achieved. A map with a few honest numbers attached turns "the system feels faster" into something you can actually report.
None of this needs to be a six-month exercise. For most mid-sized businesses the core processes can be mapped in a matter of weeks, and the output is a handful of diagrams anyone in the business can read.
It is the phase that is easiest to cut when the timeline is tight — and the one whose absence you feel for the rest of the project.