Most ERP projects that fail do not fail because of the software. They fail because of unclear scope, poor data and users who were never brought along. This checklist is the sequence we use on every ERP implementation, whether Odoo, SAP Business One, Dynamics 365, NetSuite or ERPNext, to avoid exactly those traps.
Before the project starts
1. Define the business goals, not just the features
“We need inventory” is a feature. “We need to cut stock-outs by half and know our real margin per order” is a goal. Write down three to five measurable outcomes. Every later decision, including what to customise and what to leave standard, should trace back to them.
2. Appoint an internal project owner
Someone inside your company must own the project, make decisions quickly and have authority across departments. Without this person, even the best implementation partner will stall waiting for answers.
3. Map your current processes
Document how quotes, orders, purchases, production, deliveries, invoices and payments flow today, including the workarounds. This becomes the basis of the fit-gap analysis.
Design
4. Run a fit-gap analysis
Compare every process with the standard ERP. Classify each requirement as: fits as standard, fits with configuration, needs customisation, or change the process instead. The last category is often the most valuable: adopting a standard best practice is cheaper than customising around an old habit.
5. Choose the platform, edition and hosting
| Option | Good when |
|---|---|
| Vendor SaaS cloud | Standard processes and zero infrastructure management (for example Odoo Online, NetSuite, Business Central online). |
| Managed platform | Customisations with staging environments and automated backups (for example Odoo.sh or partner-hosted SAP B1). |
| Self-hosted cloud | You need full control, specific data residency or heavy integrations. |
6. Freeze the phase-one scope
Launch with the processes that matter most, then iterate. A focused phase one that goes live on time builds momentum. A “big bang” with every wish-list item usually does not.
Build
7. Configure first, customise second
Modern ERPs are highly configurable. Exhaust configuration (workflows, routes, approval rules, automated actions) before writing custom code. Less custom code means easier upgrades later.
8. Clean your data before you migrate it
Deduplicate customers and vendors, standardise product names and units, and agree on opening balances with your accountant. Migrating dirty data simply moves your problems into a new system.
9. Build integrations early
Connections to eCommerce, payment gateways, shipping carriers or banks often carry the most technical risk. Start them in the first sprints, not the last.
Launch
10. Test with real scenarios and real users
User acceptance testing should follow complete business flows, such as quote to cash and purchase to pay, run by the people who will do the work every day.
11. Train by role
A warehouse picker and a finance manager need different training. Short, role-based sessions plus quick-reference guides beat one long generic demo.
12. Plan the cut-over and hypercare
Pick a quiet go-live date, freeze old systems, load final balances and keep your partner on standby for the first weeks. Then review against the goals you set in step one.
The best predictor of ERP success is not the size of the budget. It is clarity of goals, clean data and engaged users.
Want a partner who follows this playbook? Talk to INSABHI about your ERP project, on any platform.