Getting It Right the First Time
ERP implementation has a reputation for being complex, expensive, and risky. And historically, that reputation was earned — industry studies have consistently shown that a significant percentage of ERP projects run over budget, behind schedule, or fail to deliver expected benefits. But much of this failure stems from avoidable mistakes in planning and execution. Here's how to get it right.
Phase 1: Assessment & Planning
Before evaluating any vendor, document your current processes thoroughly. Map out how data flows between departments, identify pain points and bottlenecks, and define clear success metrics. What does "successful implementation" look like for your organisation? Is it reducing fee collection time by 50%? Eliminating manual attendance? Getting real-time financial visibility? Be specific.
Assemble a cross-functional implementation team with representatives from every department that will use the system. Include both management stakeholders and frontline users — the people who will actually use the system daily often have insights that managers miss.
Phase 2: Vendor Selection
Evaluate vendors against your documented requirements, not their feature lists. Key criteria should include industry-specific experience (an ERP vendor who has successfully deployed in 50 schools understands school workflows in ways a generic ERP vendor doesn't), language support for your user base, implementation timeline, total cost of ownership, and the quality of their training and support.
Request references from organisations similar to yours and actually contact them. Ask about the implementation experience, not just the end result. How responsive was the vendor when issues arose? How did they handle data migration? What would they do differently?
Phase 3: Configuration & Data Migration
Resist the temptation to customise everything. The best implementations use standard configurations wherever possible and only customise where your processes genuinely require it. Every customisation adds cost, complexity, and maintenance burden.
Data migration deserves more attention than it typically receives. Clean your data before migration — remove duplicates, standardise formats, and verify accuracy. This is also an excellent opportunity to decide what historical data you actually need in the new system versus what can be archived.
Phase 4: Training & Change Management
This is where most implementations succeed or fail. Technology is the easy part; getting people to change their daily habits is hard. Train users in their preferred language, provide role-specific training rather than generic overviews, and create internal champions who can help their colleagues. Plan for at least two rounds of training — initial training before go-live and reinforcement training 2-4 weeks after.
Phase 5: Go-Live & Optimisation
Consider a phased rollout rather than a big-bang approach. Start with core modules and add functionality over time. This reduces risk and gives users time to adjust. Expect a productivity dip during the first 2-4 weeks as everyone learns the new system — this is normal and temporary.
After go-live, schedule regular check-ins to identify unused features, workflow improvements, and additional training needs. The best ERP implementations aren't events — they're ongoing processes of optimisation.
Common Mistakes to Avoid
Underestimating change management, trying to replicate every existing process (some processes should change), skipping data cleanup, not involving end users in vendor selection, choosing based on price alone, and failing to define clear success metrics upfront. Avoid these, and you'll be ahead of 80% of ERP implementations.