How to Scope an ERP Implementation Project

The contract gets signed. The kickoff happens. Three months in, the client is asking for things the vendor thought were excluded. The vendor is insisting they were included. Nobody has documentation clear enough to resolve it.

This is the most common and most expensive mistake in ERP implementations. It happens before the work starts.

Define the boundaries explicitly

Every ERP implementation needs a scope document that lists what is in scope, what is out of scope, and what is conditionally in scope (meaning it can be added for a defined additional cost if needed).

The out-of-scope list is as important as the in-scope list. Without it, everything that was not explicitly discussed becomes a negotiation.

Scope by business process, not by module

ERP vendors sell modules. Your business runs processes. Scope the implementation by mapping your specific business processes - how you take an order, how you manage a production run, how you close the month - and defining exactly which steps the new system will handle.

This process-level mapping reveals the edge cases that cause scope disputes: the customer with special pricing logic, the product category with different quality requirements, the business unit that runs on a different fiscal calendar.

Get the data migration in scope explicitly

Data migration is the most frequently underscoped element of an ERP implementation. Which data is moving? How far back does history go? Who cleans it? Who validates it? What happens to data that does not meet the quality threshold for migration?

These questions need answers before the contract is signed, not during the migration.

Define done

When is the project complete? Go-live is not complete - it is the beginning of a support period. Define the acceptance criteria: what does the system need to do, and at what level of accuracy, for the implementation to be considered successful?

If you are in the process of scoping an ERP implementation, we offer independent scope reviews. Catching ambiguity before the contract is signed is worth significantly more than resolving disputes after.