The biggest cause of CAFM project disappointment isn't bad software or bad vendors. It's unrealistic timelines, set by people who haven't done implementations before. This guide sets honest expectations for how long each phase actually takes.
The five implementation phases
- Discovery & Design, requirements, process mapping, architecture
- Configuration & Build, system setup, workflows, reports
- Data Migration, cleanup, validation, load
- Testing & Training: UAT, user training, change management
- Go-Live & Hyper-care, cutover, stabilisation, optimisation
Timeline by project size
Small SME deployment (3-4 months)
1 site, <500 assets, <15 users, SaaS, minimal integration
- Discovery: 2-3 weeks
- Configuration: 3-4 weeks
- Data migration: 2-3 weeks
- Testing & training: 2-3 weeks
- Go-live & hyper-care: 2-4 weeks
Mid-market deployment (6-9 months)
2-5 sites, 5K-20K assets, 30-100 users, ERP integration
- Discovery & design: 6-8 weeks
- Configuration & build: 8-12 weeks
- Data migration: 6-8 weeks (parallel)
- Testing & training: 4-6 weeks
- Go-live & hyper-care: 4-8 weeks
Enterprise deployment (12-24 months)
10+ sites, 50K+ assets, 200+ users, multiple integrations, regulated
- Discovery & design: 3-4 months
- Configuration & build: 4-6 months
- Data migration: 3-6 months (parallel)
- Testing & training: 2-3 months
- Phased go-live: 3-6 months (site by site)
Data is (almost) always the critical path
Plan the data work first
Software configuration is predictable. Data cleanup is not. Legacy data quality usually requires 2-4 weeks more than anyone estimated. Start the data discovery early and run it in parallel with configuration. See CAFM Data Migration Strategy.
What extends timelines
- Scope creep. "Can we also add...", every addition pushes dates.
- Legacy data worse than expected. The biggest single timeline-killer.
- Integration delays. Depending on another team's schedule is risky.
- Change of internal sponsor. New person wants to re-scope.
- Over-customisation. Every custom workflow adds testing burden.
- Inadequate user training. Go-live delayed because users aren't ready.
What compresses timelines
- Clean legacy data available at project kickoff
- Dedicated internal project team (not just borrowed)
- Firm scope with formal change control
- Standard SaaS deployment (no customisation)
- Experienced implementation partner
Phased go-live for enterprise
For enterprise rollouts, don't attempt big-bang across all sites. Pilot at one site, stabilise, then roll wave-by-wave to remaining sites. This spreads risk, lets you learn from each wave, and keeps the overall programme manageable.
Conclusion
Ignore vendor marketing timelines. Plan for realistic ones: 3-4 months for SMEs, 6-9 for mid-market, 12-24 for enterprise. Start data work early. Build a 15-20% schedule buffer. Most successful CAFM programmes are the ones that planned honest timelines from day one.
Written by Muhammad Abbas
Enterprise integration specialist. Honest planning support for CAFM/EAM implementations.