ERP implementation in industrial SMEs: the 7 steps

The success of an ERP implementation project in an industrial SME depends as much on change management as on the technical choice of software.
The key stages: scoping, process mapping, vendor selection, configuration and testing, data migration, pilot rollout, change management.
The most frequent pitfalls: a budget that overlooks indirect costs, an ERP too complex for the size of the company, data migrated without cleansing, a big bang rollout with no pilot phase.
This guide covers the practical course of an ERP project – not a vendor comparison, nor a theoretical definition of ERP.

An ERP project handled badly in an industrial SME is not just a piece of software that disappoints. It is often 6 to 18 months of operational disruption, an exhausted team, and a partial return to Excel in the months that follow. Here is the step-by-step course of an implementation that holds up, and the pitfalls that derail the majority of projects.

Step 1 – Project scoping

Before even looking at a single vendor, scoping lays the foundations of the project.

What must be clarified from the outset:

A steering committee with clear responsibilities: who decides, who arbitrates in the event of conflict between departments.
The measurable objectives, not vague intentions. “Reduce invoicing errors by 20 %” can be steered; “modernise our management” cannot.
A overall budget including licence, integration, training, data migration and change support – not just the price quoted by the vendor.
A realistic reverse schedule, with margins for the unexpected, particularly on the data migration phase.

Pitfall no. 1: the budget that overlooks indirect costs. The price of the licence or subscription is often only a fraction of the real cost. Training, customisation, production downtime during the switchover, internal time mobilised: these indirect costs frequently represent more than half of the total budget.

Step 2 – Map the existing processes

This is the most frequently rushed stage, and the one that costs the most to put right later.

What needs to be done:

Map the real processes – sales, procurement, production, stock, HR, finance – not the theoretical processes described in a forgotten quality manual.
Identify the current friction points : manual re-entry, parallel Excel files, tasks with no clear owner.
The requirements in every departmentmust be gathered, not only from management or the IT department.
Distinguish what must be standardised (aligned with ERP best practice) from what must be kept as a specific development (a genuine business advantage).

Pitfall no. 2: skipping this stage to move faster. A company that chooses its ERP before having mapped its real requirements runs the risk of selecting an unsuitable tool – discovered only six months later, in the middle of configuration.

Step 3 – Choose the vendor suited to the size of the SME

The choice of vendor comes after the mapping, never before.

Selection criteria that matter for an industrial SME:

A modularsolution, allowing you to start with a limited scope and then extend progressively.
A responsive support line in French, with response times compatible with a production site that cannot wait 48 hours when something is blocked.
A genuine interoperability with your existing tools (MES, specialised production planning software, customer EDI).
A total cost of ownership consistent with the size of the company – not a solution designed for multinationals, with the complexity and maintenance cost that come with it.

Pitfall no. 3: choosing an ERP that is too complex. Many industrial SMEs are seduced by the functional richness of an ERP designed for much larger groups, then in reality use only 20 % of its capabilities – for a disproportionate maintenance cost.

Step 4 – Configuration and testing

Configuration translates your validated processes into the system. It is a technical stage, but one that must remain steered by the business teams, not solely by the integrator.

Best practice:

Favour the standard configuration of the ERP as far as possible; every specific development adds complexity and future maintenance cost.
Organise acceptance tests with end users, on real cases drawn from your own activity – not only fictitious data sets supplied by the integrator.
Test the edge cases : an urgent order, a customer return, a supplier stock-out – rare scenarios are often the ones that block the most in real production.

Step 5 – Migrate the data without corrupting it

Data migration is the moment when many ERP projects quietly go off the rails.

What must be done before migrating:

Clean the existing databases: duplicate customers, obsolete suppliers, inactive product references.
Identify all the data sources to be migrated – parallel Excel files, legacy software, document management systems – often more numerous than one thinks at the outset.
Check theintegrity of the migrated data through cross-checks, not merely by counting rows.

Pitfall no. 4: migrating dirty data. An ERP fed with uncleansed data reproduces and amplifies existing errors – and, on top of that, user confidence in the new tool collapses within the first few weeks.

Step 6 – Roll out in stages, not big bang

Pitfall no. 5: the big bang rollout. Switching all departments and sites over at once multiplies the risks: if a production module has a configuration fault, it can paralyse the entire company on the same day.

Recommended approach:

Start with a limited pilot scope (one department, one site, one critical process such as invoicing or stock management).
Validate real operation before extending to the other departments.
Adjust the configuration on the basis of field feedback from the pilot, before generalisation.
Track concrete indicators from the pilot onwards: error rate, processing time, user satisfaction.

Step 7 – Change management, the real success factor

Pitfall no. 6: neglecting change management. Statistically it is the leading cause of failure in ERP projects, well ahead of technical problems.

What works:

Involve end users from the mapping stage onwards, not only at training time.
Train on real cases from their own job, not on a generic vendor demonstration.
Appoint business champions (“super-users”) in each department, able to answer day-to-day questions without systematically calling on the integrator.
Communicate the first concrete results, however modest, to build confidence in the tool as the rollout progresses.
Plan for post-rollout support lasting several months – the ERP project does not end at go-live.

Summary of the pitfalls to avoid

A budget that ignores indirect costs (training, customisation, internal time).
Process mapping rushed or skipped.
An ERP chosen for its functional richness rather than for its fit with the size of the company.
Data migrated without prior cleansing.
A big bang rollout with no pilot phase.
Change management treated as an end-of-project detail.

FAQ – ERP implementation in industrial SMEs

How long does an ERP implementation project take in an SME? Between 6 and 18 months depending on the scope, the number of sites and the complexity of the processes to be integrated.

What is the main cause of failure in an ERP project? Insufficient change management, well ahead of purely technical or functional problems.

Should all historical data be migrated into the new ERP? No. It is better to cleanse and migrate only the active and reliable data, archiving the history separately where necessary.

Does a pilot rollout delay the overall project? It adds a few weeks to the initial schedule, but sharply reduces the risk of a general blockage during the full rollout.

What budget should be planned for an ERP in an industrial SME? The cost varies considerably depending on the vendor and the scope, but 30 to 50 % should systematically be added to the licence price to cover integration, training and change support.

Sources

Explore our Digital Transformation services →

Discover our ERP/MES Integration expertise →

Author

Xavier Schuster

Consultant at SXE Consulting. Industrial consulting firm based in Luxembourg, 25 years of experience in operational excellence.

View profile →

ERP in industrial SMEs: implementation guide and pitfalls to avoid