ERP projects fail for ordinary reasons: unclear scope, dirty data, untested cutover and a team that was never trained. The software is rarely the only problem. A checklist does not guarantee success, but it makes the risky assumptions visible before they become expensive.
This checklist is grouped by workstream. For each group, name an owner and keep evidence. An item is not complete because someone says it is; it is complete when the evidence exists and someone has signed off.
Use the checklist in two passes. First, mark each item red, amber or green and assign an owner. Then set a review date for every red item. A checklist with no dates is a wish list.
1. Sponsorship and scope
- Write the business case in one page: the problem, the expected change and how it will be measured.
- Define the modules and processes in scope, and list what is out of scope.
- Name the executive sponsor and the decision rights for scope, budget and go-live.
- Set the budget envelope, including licences, implementation, data, training and post-go-live support.
- Agree the success measures before the first demo.
Owner: managing director or CEO. Evidence: signed charter, scope list and budget approval.
2. Process fit
- Map the current process, including exceptions and workarounds.
- Agree the to-be process and the policies behind it.
- Run a fit-gap analysis against standard ERP functionality.
- Set a rule for customization: who approves it, and how it will be maintained at upgrade time.
- Identify reports and statutory outputs that must be produced on day one.
Owner: department heads with the project manager. Evidence: process maps, fit-gap log and signed design decisions.
3. Data readiness
- Assign owners for the chart of accounts, item master, customer and supplier master, price lists and opening balances.
- Define the data standards: codes, units of measure, tax codes, currencies and duplicate rules.
- Clean and deduplicate before migration, not during it.
- Rehearse the migration at least twice and reconcile totals to the source.
- Document retention and access rules for personal data.
Owner: finance and operations, with a named data owner per domain. Evidence: data dictionary, migration runs and reconciliation sign-off.
4. Solution and vendor
- Demo the real scenarios, not the vendor's showcase data.
- List every interface: bank, payment, ecommerce, warehouse, payroll, tax or reporting.
- Define roles, approvals, segregation of duties and audit trails.
- Agree the service level, support hours and escalation path.
- Confirm who owns the configuration, custom code and documentation.
Owner: project manager and IT lead. Evidence: signed contract, interface list, role matrix and support agreement.
5. Testing
- Write user acceptance tests from real transactions, including negative cases.
- Test month-end close, inventory valuation, tax calculation and multi-branch reporting.
- Test permissions with the actual roles, not an administrator account.
- Measure performance with realistic volume.
- Keep a defect log with severity, owner and acceptance date.
Owner: business test lead with QA. Evidence: test scripts, results, defect log and sign-off.
6. Training and change
- Train by role, using the new process and the user's own data.
- Publish short standard operating procedures and a quick-reference card.
- Name champions in each department and give them time to support others.
- Test competency before go-live, not after.
- Plan communication for customers and suppliers if invoices or portals change.
Owner: HR and operations. Evidence: training register, competency check and published SOPs.
7. Cutover
- Set a freeze window for master data and transactions.
- Rehearse the cutover end to end, including the rollback.
- Define go/no-go criteria and who can call a stop.
- Prepare the support rota for the first two weeks.
- Keep the old system readable for the agreed retention period.
Owner: project manager with the executive sponsor. Evidence: cutover runbook, rehearsal record, go/no-go minutes and rollback plan.
8. Post-go-live
- Reconcile bank, inventory, tax and receivables daily for the first month.
- Track issues by severity and close them with a named owner.
- Compare actual benefits with the business case at 30, 60 and 90 days.
- Schedule the first upgrade and review customization debt.
- Hold a lessons-learned session while the team still remembers.
Owner: finance and the project manager. Evidence: reconciliations, issue log, benefit review and upgrade plan.
In Bangladesh, add VAT and statutory reporting, multi-branch inventory, cash collection and mobile payment reconciliation to the test scope. If the team works in Bangla, test the screens and reports in Bangla as well as English, and confirm that local support is available after go-live.
Verification
Verification is not a meeting. Sample transactions from source to report, compare opening balances, attempt a period close, and ask a user who was not on the project team to complete a core task. If the evidence cannot be reproduced by someone else, it is not evidence. Keep it in one shared folder with a date and an owner, so an auditor or a new project manager can follow the trail.
Common mistakes
- Customizing the ERP to match a process that should change.
- Treating the project as an IT project with no business owner.
- Starting migration with dirty master data.
- Skipping the cutover rehearsal.
- Ending support on go-live day.
- Underestimating tax, VAT and statutory reporting.
Metrics
Track close time, order-to-invoice time, inventory accuracy, migration reconciliation variance, open defects, training completion and the cost of customization. Review them at 30, 60 and 90 days, then quarterly.
Where this fits in our work
If you need help with selection, process design or implementation oversight, start with Operations & Business Software. The pricing page explains how we scope work. For the reporting layer, read AI-ready data foundations, year by year.
Sources
- Microsoft Learn, Dynamics 365 implementation guide, accessed 17 November 2026.
- SAP, SAP Activate methodology, accessed 17 November 2026.
- ISO 21500:2021, Project, programme and portfolio management — Context and concepts, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.