In short
This ERP implementation checklist splits the project into ten phases, each with a checklist and a clear "done when" test. The phases that decide success are the unglamorous ones: cleaning data before it moves, agreeing a cutover date, loading opening balances that tie to your old books, and testing full quote-to-cash and procure-to-pay flows with real documents. Finish with a supported first month-end, not a go-live party.
Who owns the ERP implementation checklist?
One named project owner owns the ERP implementation checklist, with authority to make process decisions. Each phase also needs the right people at the table.
| Role | Responsibility |
|---|---|
| Executive sponsor (owner or MD) | Sets priorities, breaks deadlocks, protects time for the team |
| Project owner | Runs the plan, chases decisions, signs off each phase |
| Process owners (sales, purchasing, stores, finance) | Describe today’s process, approve the new one, test it |
| Data owner | Cleans and loads data, signs off reconciliations |
| Implementation lead (vendor or partner) | Configures the system, advises on design, trains trainers |
If one person holds several roles in your business, that’s normal for an SME. Just make sure nobody is the only one who knows how a key process works.
Phase 1: Scoping
Scoping decides what goes live, for which companies and on what date. Most later problems trace back to a scope that was never written down.
Phase 1 checklist
Phase 2: Data cleanup
Data migration only works if the data is clean before it moves. Cleanup belongs in the old system or spreadsheet, not in the new ERP.
Phase 2 checklist
Phase 3: Master data
Master data is the reference data every transaction uses: customers, suppliers, items, the chart of accounts, warehouses and tax codes. Load and check it before any opening balance.
Phase 3 checklist
Phase 4: Opening balances and the cutover date
The cutover date is the date your new ERP becomes the book of record. Opening balances are the account balances, stock quantities and stock values carried over on that date.
Phase 4 checklist
Phase 5: Configuration
Configuration turns your agreed processes into system settings. Change the process to fit standard features before you customise the system.
Phase 5 checklist
Phase 6: Roles and permissions
Roles decide who can see and do what. Design them around jobs, not around people, and keep the people who prepare a transaction separate from those who approve or post it.
Phase 6 checklist
Read more about role-based access control and how roles and permissions work in 1flux.
Phase 7: Testing scenarios
Testing proves the configured system runs your real flows end to end, with real data and the people who will use it. Test complete flows, not single screens. Write down the expected result before each test.
Quote-to-cash test scenarios
| # | Scenario | Expected result |
|---|---|---|
| QC1 | Quotation with a document discount and tax, above the approval limit | Can’t be sent until approved; tax calculated correctly after the discount |
| QC2 | Revise an approved quotation | New revision number; the earlier version is kept |
| QC3 | Accepted quotation plus customer PO becomes a sales order | Lines, prices, discounts and tax carry over without retyping |
| QC4 | Order for more stock than is available | Shortage is flagged before the promise is made |
| QC5 | Partial delivery (8 of 10 units) | Delivery note for 8; 2 remain open; stock and cost of sales update |
| QC6 | Invoice only what was delivered | Invoice for 8 units; receivable, revenue and output tax post |
| QC7 | One payment settles two invoices, one in a foreign currency | Both invoices cleared; exchange difference posted |
| QC8 | Customer exceeds agreed credit days | Blocked, or allowed only with override permission |
Procure-to-pay test scenarios
| # | Scenario | Expected result |
|---|---|---|
| PP1 | Requisition above a buyer’s authority | Waits for approval |
| PP2 | Three supplier quotes compared and one awarded | Award reason recorded; purchase order created for the winner |
| PP3 | Purchase order issued and printed as an LPO | Correct letterhead, supplier tax number and tax |
| PP4 | Receive 40 of 50 units, 2 damaged | Reason recorded for the short and rejected quantities; order stays open for the rest |
| PP5 | Goods received before the price is agreed | Stock carries a provisional cost; the value is corrected, or flagged for finance, when the price is agreed |
| PP6 | Supplier invoice price differs from the order | Difference needs a reason and posts to its own account |
| PP7 | One delivery note covers two purchase orders | One receipt linked to both orders |
Also test month-end controls: posting into a closed month must fail, and a posted journal must be corrected by reversal, not edited. Use our quote-to-cash guide and procure-to-pay guide to adapt these scenarios to your business.
Phase 7 checklist
Phase 8: Training
Training should mirror jobs, not menus. A storekeeper needs to receive goods and dispatch orders well, not tour every module.
Phase 8 checklist
Phase 9: Go-live
Go-live is the controlled switch from the old system to the new one. Plan it hour by hour, and agree in advance what would make you postpone.
Phase 9 checklist
Phase 10: The first month-end
The first month-end close is the real test of an implementation. It shows whether stock, receivables and the ledger agree after a month of live transactions.
Phase 10 checklist
Where do 1flux tools help?
1flux includes tools for the phases where implementations most often stall. This table summarises them. Apps are switched on for you by the 1flux team; see implementation and onboarding for how the 1flux team works with you.
| Phase | 1flux tool | What it does |
|---|---|---|
| Data cleanup, master data | Import workbench | Add data from CSV, Excel or a paste; map columns; validate on the server before saving; download an error file. Companies and contacts up to 5,000 rows per file; items up to 10,000 rows |
| Master data | Trading chart template | One-click 25-account starting chart, including VAT, goods received not invoiced, price variances and exchange gains and losses |
| Opening balances | Opening trial balance | CSV, Excel or paste; must balance exactly; posted once per company on the cutover date |
| Opening balances | Opening stock | By form (up to 500 lines) or import (up to 10,000 rows), all or nothing, posted against opening balance equity |
| Configuration | Country packs | Tax codes, legal forms, regions and registration fields for the UAE, Saudi Arabia and India, seeded when each company is created |
| Roles and permissions | Roles, hierarchy and entity access | Custom roles built from more than 100 permissions, own-records visibility and access limited by legal entity |
| First month-end | Close checklist and periods | A six-step close checklist; closed periods refuse every posting |
What are the most common ERP implementation mistakes?
- Moving dirty data. Duplicates and missing fields multiply once transactions reference them.
- No cutover date. Without one, the old and new systems run in parallel indefinitely.
- Testing screens, not flows. Each screen works; the hand-off between them doesn’t.
- Customising before standardising. Every customisation adds cost at every upgrade.
- Training too early. People forget what they learned a month before go-live.
- Leaving finance out of testing. The accounting result of every flow needs checking.
- Declaring victory at go-live. The first month-end is where problems surface.
