Most ERP projects succeed or fail in the first few months. This checklist gives you a sensible order of work. Adjust the timing to your scope.
Days 1 to 30: decide and prepare
- Name a project owner inside your company.
- Write down the problems you want to fix and how you will measure them.
- Agree the scope of phase one. Keep it small.
- Agree the budget, the timeline and who approves changes.
- Set up a weekly meeting with your partner.
- Start cleaning your master data: customers, vendors, items, ledgers.
Days 31 to 60: build and test
- Configure the system for your core processes.
- Load a sample of your data and review it together.
- Test real scenarios, such as an order from quote to invoice.
- Test the compliance parts, including GST and e-invoicing.
- List the reports each team needs and check them against real numbers.
- Write simple user guides in your own words.
Days 61 to 90: train and go live
- Train each team on its own tasks, not on every screen.
- Run a trial where staff use the system with real data.
- Fix issues found and agree a go-live date.
- Plan support for the first weeks: who people call, how fast they get answers.
- Decide what happens to the old system and when.
Risks to watch
| Risk | What to do | |---|---| | Scope keeps growing | Hold a change list and review it weekly | | Poor data quality | Clean data before import, not after | | Staff do not use it | Train in small groups, and involve team leads early | | Key person leaves | Share knowledge and keep notes |
Questions to ask your partner
- What do you need from us each week?
- What are the top three risks you see in our project?
- How will we know we are ready to go live?
Get help
Find a partner with experience in your industry through SARVO, and read 10 questions to ask before hiring a technology partner.
FAQ
Is 90 days enough? For a focused first phase, often yes. Larger projects run in phases.
Who should own the project? Someone in your business who understands the work, not only the IT team.