ERP Implementation Checklist: Why Projects Fail and How to Avoid It

An ERP can be technically fine and still fail in the company. Staff go back to Excel, the owner stops trusting the reports, and the system becomes an expensive data entry chore. Almost all of these failures come from the implementation, not the software. Here is a checklist you can follow, in the order projects actually run, with the mistakes that cause the most damage.

Phase 1: planning

• Name an owner. One person inside the company who can make decisions and chase colleagues. If nobody has time, the project will slide.
• Limit phase one. Choose the smallest set of modules that solves your biggest reconciliation problem. A tight phase one finishes; a sprawling one drags.
• Write the success measures. For example: stock difference at physical count under an agreed limit, month-end closing within a set number of days, ageing report available on demand.
• Agree decisions early. Chart of accounts, item codes, units of measure and approval limits. Delay here costs weeks later.

Phase 2: data

Dirty data is the number one hidden problem. Before migration, spend time on:

1. Item master: remove duplicates, fix units, agree one code per item.
2. Customers and suppliers: one record each, with correct PAN or VAT number, address and credit terms.
3. Opening balances: reconcile ledgers, receivables, payables and stock to a clear cut-off date, ideally the start of the Nepali fiscal year or a month end.
4. Decide how much history to carry. Many companies bring opening balances only and keep old software or files read-only.

Garbage imported on day one will be blamed on the ERP for years.

Phase 3: configuration and testing

Insist on testing with real scenarios, not just the vendor's sample data. A reasonable test list: a full purchase cycle with partial receipt, a credit sale with 13% VAT and return, a stock transfer between two warehouses, a payroll run, a cheque received and later banked, and a month-end closing. Staff who will use the system daily should do the tests, and each failure should be written down and re-tested.

Test the user permissions too. Log in as the store keeper and confirm that salary data is not visible; log in as a salesperson and confirm that purchase rates are hidden if they should be.

Phase 4: training and parallel run

Step	Purpose
Role-based training	Store, accounts, sales and management learn only their tasks
Cheat sheets	One page per task, in simple language, near the workstation
Parallel run for a short period	Enter in both old and new systems to catch gaps before cut-over
Cut-over date	A fixed date after which only the new system counts
Daily check in week one	Quick call to fix stuck users

Parallel running is tiring, so keep it short and focused on the processes with the highest risk. It is better than a hard cut-over that nobody dares reverse.

Phase 5: the first month-end

The first closing is the true test. Sit with the accountant, produce the trial balance, VAT summary, receivable and payable ageing and stock valuation, and compare them with what you would have produced before. Differences are either bugs, setup errors or old mistakes now visible. Fix them calmly and note the lessons.

Mistakes that sink projects

• Scope creep. Every department adds wishes. Collect them in a phase-two list.
• Over-customising. Changing the system to mirror every old habit creates cost and upgrade pain. Adjust the habit when it is harmless.
• Skipping training for management. If the owner does not use the dashboards, staff conclude the data does not matter.
• Entering data late. Batch entry at week end defeats real-time stock. Set a rule that transactions are entered the same day.
• Ignoring resistance. A store keeper who feels watched may sabotage quietly. Explain what the system does for them, such as fewer disputes.
• No support plan. Know who to contact, how, and what is covered.

After go-live

Review after sixty to ninety days. Which reports does the owner really use? Which fields are empty? Which approvals slow things down? Tune the system, then plan phase two, whether that is payroll, production or branch rollout. If you are still weighing the first step, read our overview of ERP software and consider whether a lighter HR management or inventory tool should come first.

A realistic expectation of effort

Owners often expect the vendor to do everything. In practice, the vendor configures and trains, but only your staff can decide the item codes, clean the party list, confirm opening balances and approve the approval limits. Plan a few hours each week from the project owner and from the accountant during setup. When that time is not protected, the project stretches and morale drops. A realistic plan is more honest than a short promise that slips.

Festival and fiscal timing

Pick the go-live date carefully. Avoid the weeks around Dashain and Tihar, when staff are away, and avoid the middle of the Ashadh year-end closing. A common choice is to start at the beginning of a Nepali month, or at the start of Shrawan with fresh opening balances, so that records do not straddle two systems.

Keep a simple issue log

From the first training day, keep a shared sheet of every problem, who reported it, who is fixing it and when it was closed. It stops complaints being forgotten, shows the vendor and the company where the real weaknesses are, and gives the owner a clear picture of progress on days when the project feels slow.

Your next step

Use the checklist above to assess your readiness: owner named, phase one scoped, data cleaning started. If you want a second opinion or a phased plan and quotation, message WebsNP on WhatsApp at +977 9846280400 with your company size and main pain points.

Get a demo and quote for ERP Software

Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.

Chat on WhatsApp

Or call / WhatsApp +977 9846280400

Your name Phone / WhatsApp Email (optional) Business / organisation What do you need?

Request demo

More guides on ERP Software