Choosing an ERP is the easy part. Whether it succeeds depends on how it is implemented: how well your processes are understood, how cleanly your data comes across and how confident your team feels on day one. This is the six-step plan we follow, with realistic timelines and the mistakes we see most often.
Before you begin: one owner, one goal
Name one person inside the business who owns the project and can make decisions. Agree what success looks like in plain words, for example “invoices, stock and GST from one system by 1 April”, and pick a go-live date that avoids your busiest season and the last days of a financial year.
Step 1: Discover
Map how work actually flows today: how an enquiry becomes an order, how goods arrive and leave, how money is collected, who approves what. Collect the documents you print (invoices, delivery notes, purchase orders) and the reports you rely on. The output is a requirement list everyone agrees on. Skipping this step is the most expensive mistake in ERP projects.
Step 2: Install
For a self-hosted ERP this means setting up the server, HTTPS, the database, scheduled background jobs and backups. For a cloud ERP it means creating the account and company. Either way, set up two-factor sign-in for administrators from the start, and test a backup and restore before any real data goes in.
Step 3: Configure
Start from an industry template if your ERP has one, then shape it to the requirement list: chart of accounts, tax settings, numbering series, roles and permissions, approval workflows, print formats with your logo and terms, and the reports your managers asked for. Resist the urge to configure every idea at once; get the core flow right first.
Step 4: Migrate your data
Move masters and opening balances, not years of history. A practical checklist:
- Clean customer and supplier lists first: remove duplicates, add GSTINs and correct addresses.
- Agree item codes, units, HSN codes and tax rates before importing items.
- Choose a cut-off date, ideally the start of a month or quarter.
- Import opening balances for ledgers, receivables, payables and stock as on that date.
- Reconcile: the trial balance, debtors, creditors and stock value in the ERP must match your old books on the cut-off date.
Step 5: Train every role
Train people on the tasks they will actually do, using your own data: the counter clerk on billing, the storekeeper on receipts and transfers, the accountant on payments and returns, managers on approvals and reports. Short, hands-on sessions work far better than one long demonstration. Give everyone a simple written guide.
Step 6: Go live and support
Go live on the cut-off date and plan for a few weeks of extra support (often called hypercare) while questions come in. For high-risk areas, run the old method alongside for a short period to compare results. After the first month-end close, review what is working and schedule the next round of improvements.
How long does an ERP implementation take?
It depends on the number of companies, users and processes, the state of your data and how quickly decisions are made. As a guide, our own Qila ERP implementations typically take 3–5 days for a starter set-up (one company, up to 10 users), 2–4 weeks for up to 50 users, and 4–8 weeks for several companies and up to 100 users.
Mistakes to avoid
- Copying a messy process into new software. Fix the process on paper first.
- Importing dirty data. Duplicates and wrong tax codes multiply in an ERP.
- Customising too much, too early. Live with the standard flow for a month, then change what really hurts.
- Training only one person. Every role needs its own session.
- No backup plan. Test restores before go-live, and keep copies off the server.
- Going live at the busiest time. Pick a quiet week and the start of a period.
Next steps
Still choosing a system? Read 12 questions to ask before you buy an ERP and the benefits of ERP software. Ready to plan yours? Book a Qila ERP demo and we will sketch an implementation plan for your business.
1 comment