Over the last year I worked on nine ERPNext implementations: a pharmaceutical manufacturer, a Saudi contractor, an insurance claims administrator, an HR rollout for a maintenance company, distribution, textiles, beauty retail, a self-storage business and a general trading company. Different industries, very different people. The same lessons kept coming back.
1. Start with the paperwork, not the modules
Every business already has a system. It lives in Excel sheets, printed forms, WhatsApp groups and one person who remembers everything. Before I open ERPNext, I ask for the real documents: the invoice they print, the approval form they sign, the report the manager reads on Sunday. Those papers tell you the workflow far better than a requirements meeting.
2. Model the business, then bend the software
ERPNext is flexible, which is its strength and its trap. A contractor does not think in "sales orders"; they think in contracts, interim payment certificates and retention. An insurance administrator thinks in claims, schemes and turnaround time. When the system speaks the business's own words, through custom DocTypes, fields and print formats, people actually use it.
3. Approvals are where projects succeed or fail
Most of the real customization lives in approvals: who signs off a purchase above a budget, who can close a claim, which manager approves leave. I build these as clear workflows with server-side validation, so the rule is enforced by the system, not by memory.
4. Bilingual print formats matter more than dashboards
In Egypt and the Gulf, the document that leaves the building is often the most important feature. Arabic and English print formats for invoices, contracts and certificates earn trust faster than any chart.
5. Plan the go-live like a launch
Data migration, user testing, training and a quiet first week do not happen by accident. I treat go-live as its own phase: migrate in rehearsals, train each department on its own documents, and stay close for the first days.
The short version
ERP projects are not software projects with some business attached. They are business projects that happen to need software. The closer the system mirrors how people already work, the faster it becomes the place where the work actually happens.
