There’s no secret method to implementing an ERP. There is, though, an order that works and a few shortcuts that almost always backfire. This is the sequence we follow with clients in the UAE, the GCC and India.
Step 1: Agree what success looks like
Before any software is touched, write down what should be different in six months. “Close the month in five days.” “Payroll in one afternoon.” “Stock count matches the system.” Those become the test at the end.
Step 2: Study how work happens today
Sit with the people who do the work, not just their managers. The real process is often different from the one on paper, and that’s where surprises come from.
Step 3: Fix the scope and the price
Agree which modules, companies and branches go live first. Anything else goes in a later phase. Scope creep is the most common reason projects run over.
Step 4: Set up the system
Companies, branches, chart of accounts, taxes, approval chains, document layouts. Configure first and customise only what’s left.
Step 5: Clean and load the data
Customers, suppliers, items, opening balances and employees. Clean it before loading, then check the totals against your old system and your auditor’s figures.
Step 6: Add the local checks
- UAE: test VAT settings, bilingual invoices and the WPS file with your bank.
- Saudi Arabia: register for ZATCA e-invoicing early and test GOSI and Mudad with real data.
- Qatar: load QID and permit dates and test the WPS transfer.
- Oman: agree end-of-service rules under the 2023 law before loading employees.
- Kuwait: check PIFSS and indemnity balances for every employee.
- Bahrain: test VAT returns and SIO deductions on a full month.
- India: map Tally ledgers, test GST returns and run a parallel payroll with PF and ESI.
Step 7: Train each team on its own screens
Short sessions per department beat one long session for everyone. Give people a practice database so they can make mistakes safely.
Step 8: Go live at a sensible time
The start of a month or quarter, away from year-end and audits. Run payroll in parallel for one month if you can.
Step 9: Stay close for the first month-end
Most questions come in the first four weeks. Having the consultant who set up the system available then makes the difference between a team that trusts the new system and one that drifts back to Excel.
Questions we’re often asked
How long should ERP training take?
Short sessions per department over a few weeks work better than one long session. Plan support for the first month-end.
Should we run payroll in parallel?
Yes, for at least one month if you can. It catches differences before employees notice them.
What is the best time to go live?
The start of a month or quarter, away from year-end, audits and busy seasons.
This is how we run Odoo, Zoho, Business Central and ZEO Cloud HR & Payroll projects. If you’re planning one, get in touch.