The 7 mistakes that make an ERP project fail in Morocco
According to Gartner, more than 55% of ERP projects exceed their initial budget and schedule. Among the Moroccan SMEs we have worked with, the rate of partial failures — an ERP that is installed but not used, or used at 20% of its capacity — is even higher.
These failures do not come from bad software. They come from predictable, avoidable mistakes, made before the first line is even configured. Here are the seven we see most often.
Mistake 1 — Buying an ERP before understanding your own processes
This is the most fundamental mistake, and the most common. A company decides to deploy Odoo because a competitor uses it, because a salesperson convinced them, or because management wants to "go digital". It picks the software first and thinks about its processes afterwards.
What happens: The ERP is installed with its default configuration. Teams try to use it, but the workflows do not look like what they actually do. In the end, urgent customisations are made, often badly, and the data becomes inconsistent.
The right approach: First map the processes as they really exist, not as they should exist. Who does what, in which order, with which documents, with which exceptions. It is this mapping that determines what the ERP must do — not the other way round.
At Nexa Code Agency, we spend two to three weeks with our clients' teams before touching the configuration. It is this phase that decides whether the project succeeds.
Mistake 2 — Deploying everything at once (the big bang)
An ERP like Odoo covers dozens of areas: sales, purchasing, inventory, accounting, HR, projects, marketing, e-commerce. The temptation to switch everything on from day one is strong — you might as well make the most of what you are paying for.
What happens: Teams are trained on fifteen modules at the same time. Two weeks after go-live, nobody really knows how to use any of them. The data entered is wrong. Test data gets created in production without anyone realising. Management loses confidence in the system.
The right approach: Start with the two or three modules that have the strongest immediate impact on the business. For most Moroccan SMEs, that is the sales chain: quotation → sales order → delivery note → invoice. Stabilise that block, train the teams on it, check that the data is clean. Only then extend to the following modules.
A phased deployment takes longer overall, but it produces a system that is actually used — which is worth infinitely more than a system that is complete on paper.
Mistake 3 — Neglecting the quality of the starting data
The ERP will absorb all your existing data: your customer base, your product references, your order history, your price lists. If that data is messy in Excel, it will be messy in the ERP — with the added complexity of a more sophisticated system.
What happens: Duplicates multiply in the customer base. Product references are inconsistent. Historical prices do not match reality. Teams stop trusting the data and go back to their personal Excel files. The ERP becomes a parallel system rather than a single source of truth.
The right approach: Before importing anything into the ERP, clean the data. Merge duplicates, standardise references, validate prices. Importing clean data takes twice as long to prepare, but it saves the project.
We systematically support our clients through this phase: audit of the existing data, cleaning, validation before import. It is a thankless step, but a non-negotiable one.
Mistake 4 — Choosing the integrator on the lowest price
An Odoo project is at least 80% integration and 20% software. The software is the same for everyone — it is the integrator who decides whether the deployment succeeds or fails.
What happens with a low-end integrator: Copy-paste configuration without understanding the client's processes. Modules set up with defaults and no adaptation. Poorly written custom modules that break at the first update. Rushed training. Disappearance after go-live.
What a bad integrator really costs: We regularly hear from clients who come back after a failed first deployment. The cost of the recovery almost always exceeds what a good project would have cost from the start. You pay twice: once for the mistake, once for the fix.
The right approach: Assess an integrator on verifiable references — named clients with live URLs, deployments in your sector, a team you can reach after delivery. Ask to speak to existing clients before signing.
Mistake 5 — Underestimating training
An ERP is not intuitive in the way a consumer app is. It is a professional tool with its own logic: stock movements, accounting journals, validation workflows. Your teams have to understand that logic to use the tool properly.
What happens without serious training: Data entry errors multiply. Documents are created in the wrong status. Stock becomes inconsistent because someone does not know the delivery note must be validated before the invoice is created. The manager spends their time correcting errors instead of running the business.
The right approach: Organise training sessions by role, not by module. The salesperson does not need to know how accounting works. The accountant does not need to know how to place a purchase order. Everyone must master the workflows of their own job, with exercises based on real cases from the company's activity.
We always include a post-launch support period: two to four weeks during which our team is available to answer questions and fix errors in real time.
Mistake 6 — Ignoring Moroccan regulations
Odoo is international software. It does not come with Moroccan specifics built in. A deployment carried out without Moroccan expertise will produce an ERP that works but is not compliant.
The critical points in Morocco:
- VAT: the Moroccan rates (20%, 14%, 10%, 7%) must be configured precisely. A configuration error produces incorrect VAT returns.
- Chart of accounts: the CGNC (the Moroccan General Accounting Code) has specifics that the French chart of accounts (often used by default) does not fully cover.
- Digital stamp (cachet numérique): mandatory on commercial documents in Morocco. It is absent from standard Odoo, so you need a custom module or a third-party one.
- Financial statements: the balance sheet and the CPC (profit and loss account) in the Moroccan format are not generated automatically by standard Odoo. They require configuration or a dedicated module.
An integrator who has not worked on projects in Morocco will not necessarily know these specifics. It is a real risk, especially for accounting.
Mistake 7 — Giving up at the first difficulty
The first months after an Odoo go-live are almost always hard. Teams are looking for their habits. Some workflows are not yet smooth. Minor bugs appear. The temptation to go back to Excel is strong.
What happens: Faced with resistance from the teams or with the first problems, some managers decide to "put the ERP on hold". A few weeks later, everyone has gone back to the old tools. The months of integration work are lost.
The right approach: Anticipate this phase. It is normal and predictable. The answer is not to relax the adoption rules (allowing a parallel return to Excel kills the project) but to increase support during this period. That is precisely why we plan a post-launch support phase in all our projects.
The rule of thumb: if a team genuinely uses the ERP for two full months without going back to Excel, adoption is won. That is where it holds.
How to avoid these mistakes in practice
| Mistake | Warning sign | Solution |
|---|---|---|
| Processes not mapped | You start by choosing the software | 2-3 week analysis phase before anything else |
| Big bang | Everything switched on from the start | Phased deployment, sales chain first |
| Dirty data | Immediate import without cleaning | Audit and clean the data before import |
| Wrong integrator | No verifiable references | Check named clients and speak to references |
| Training neglected | A single session for everyone | Sessions by role, post-launch support |
| Moroccan regulations ignored | Integrator with no Morocco experience | Check knowledge of the CGNC, VAT, cachet numérique |
| Giving up at the first difficulty | Return to Excel tolerated | Reinforced support during the first two months |
For the details of our deployment method, see our Odoo ERP service. For an overview of how Odoo works in an SME, read our guide Odoo for Moroccan SMEs.
Frequently asked questions
How long does it take for an ERP to be truly adopted by the teams? In our experience: two to three months for the basic workflows to feel natural, and six months for the teams to be comfortable with all the features they use. Adoption depends heavily on the quality of the initial training and on support during the first weeks.
Can an ERP project that got off to a bad start be recovered? Yes, but it is costlier and slower than a good start. The first step is an audit of the state of the system: data, configurations, workflows. Depending on what we find, we either fix things in place or start again from a clean base. We have supported restarts after poor first deployments.
Should we change our processes to fit the ERP, or the other way round? Both, in a balance to be found. Some of a company's processes are habits that can be improved — the ERP is an opportunity to rethink them. Others are non-negotiable business realities — the ERP must adapt to them, through configuration or custom modules. The dividing line is found during the analysis phase.
Is an ERP suitable for very small businesses? Odoo Community is used by very small businesses of 3 to 5 people. For them, the issue is not the size of the ERP but the relevance of the scope deployed. A minimal deployment (sales + invoicing) can bring real value without the complexity of a full deployment.
How many employees do you need for it to be worth it? There is no threshold. We have seen companies of 5 people gain as much from an Odoo deployment as a company of 50 — because their processes were very manual and their need for traceability was high. The question is not size, it is the pain the ERP solves.
We work with SMEs across Morocco, including in Mohammedia, Casablanca and Rabat.