Implementation
ERP implementation checklist for Sri Lankan businesses
Prepare an ERP rollout with clear process ownership, clean master data, opening balances, device tests, staff training, acceptance and a controlled cutover.
Kaduwela, Sri Lanka · Local and remote delivery
The practical answer
Start with an outcome you can verify.
An ERP rollout is ready for a pilot when the team has agreed the workflow, prepared and checked its opening data, tested the important devices and exceptions, trained named users and defined how results will be reconciled. A software installation alone is not a completed business rollout.
Name an owner for each important process
Identify the people who can decide item naming, purchasing rules, stock corrections, customer credit and reports. A project contact can coordinate delivery, but business decisions still need the right owner. Record decisions so different branches do not interpret the same rule differently.
Walk through the current process with the staff who perform it. Keep useful controls and remove unnecessary duplicate entry only after understanding why it exists. Agree a small first release and the operational exception it must handle.
Prepare the opening position before importing it
Clean item, customer and supplier masters; map units and location identifiers; and identify duplicate records. Decide whether the project needs opening figures, historical transactions or both. A master-data import and a full-history migration have different reconciliation requirements.
Choose a cutover time for stock and balances. Specify who signs off the totals, what happens to transactions entered during the transition and how corrections are approved. Keep the original export available in a controlled location for investigation.
Use a representative pilot and written acceptance scenarios
A pilot should include the devices, roles and transactions that create real operating risk. Run receiving, billing, a return, a partial payment, a branch transfer and day close where they apply. Test what staff do when a request fails or a connection is interrupted.
Record the expected outcome before running each test. Compare source documents, stock, cash and account effects. Separate a configuration issue from a missing requirement and agree who decides whether the pilot is acceptable.
Train the normal task and the recovery task
Show staff how to complete their daily work and how to respond when something goes wrong. A cashier needs to know when to ask for approval; a supervisor needs to find a failed synchronization or explain a reversal. Keep the instructions close to the role.
Use named accounts and test what each role can see and change. Verify that branch restrictions match the operation. Training should include the person who covers an absence, not only the main daily user.
Agree the cutover decision and first review
Before the switch, confirm the tested release, approved opening data, device readiness, support contact and recovery plan. Decide who can call a pause and how the previous records would remain available if a blocker is discovered.
After the first shift, reconcile a manageable set of transactions and record unresolved differences. Review stock, balances, failed jobs and staff questions before expanding to more branches. A useful rollout ends with an owned operating process, not an unattended installation.
Compare the decisions and the evidence
| Stage | Required decision | Checkable output |
|---|---|---|
| Discovery | Which workflow and first release? | Process map and accepted scope |
| Data preparation | What is the agreed opening position? | Approved mapping and reconciled sample |
| Pilot | Do important tasks and exceptions work? | Recorded acceptance outcomes |
| Cutover | Who authorizes the move and recovery? | Named owner, support and restore plan |
Take it to your next discussion
Your preparation checklist
0 of 12 reviewed
Use this as a discussion checklist. Ticks are kept only while this page is open.
Download the blank checklistQuestions before the next step
Common planning questions
How long does an ERP implementation take?
The schedule depends on modules, data quality, users, devices, integrations and the decisions required from the business. Agree a staged plan after discovery rather than relying on a generic duration.
Should all branches switch on the same day?
A representative pilot can reduce uncertainty before wider rollout. A simultaneous switch may suit some operations, but it requires its own reconciliation, staffing and recovery plan.
Is importing our spreadsheet enough to finish migration?
No. Validate mappings, units, duplicates and opening totals, then compare a sample of actual workflows. A successful upload does not prove the imported business position is correct.
Who should approve the rollout?
The business should name owners who can approve workflows, opening data, acceptance results and cutover. The implementation team supplies technical evidence for those decisions.
Supporting references
NCSC recommends knowing how to restore backups and checking that they contain the important data. Include a restoration check in rollout planning. NCSC: backing up your data (opens a new tab)
Bring the operating problem
Let’s work through your actual requirements.
Tell us your business type, users, branches, current system and the task you want to improve. We’ll use that context to discuss the right next step.