What's included
ERP programmes fail on data and testing far more often than on software. The template gives both their own tracks rather than hiding them inside a build phase:
- Discovery & fit-gap — Current-state process mapping, requirements, fit-gap analysis against standard functionality and the scope baseline. Milestone: scope agreed.
- Solution design — To-be process design, configuration workbooks, integration and reporting specifications, and the design sign-off gate.
- Build & configuration — System configuration, extensions, integrations, reports and the security and role model.
- Data migration — Data profiling, cleansing, mapping and successive mock loads — the workstream that most often forces a go-live to slip.
- Testing — System integration testing, user acceptance testing, performance testing and defect resolution. Milestone: UAT signed off.
- Training, cutover & hypercare — End-user training, cutover rehearsal, go/no-go decision, the cutover window itself and post-go-live support. Milestone: go-live.
How to customize it
- Fix the go-live date and work backwards — most ERP dates are set by a fiscal or contractual boundary, not by the plan.
- Add a row per module or per legal entity if you are rolling out in waves rather than big bang.
- Expand the data migration rows to one per data object (customers, vendors, materials, open orders) once mapping starts.
- Insert a formal go/no-go milestone a week before cutover, with testing and data sign-off as its predecessors.
- Keep hypercare on the chart as real work — it needs named people who are not simultaneously starting the next phase.
Scheduling tips
- Protect UAT. It is the first phase squeezed when the build runs late, and it is the only one that finds the defects your users care about.
- Sequence the cutover hour by hour. The weekend itself deserves its own detailed schedule; a single "cutover" bar hides the fact that the final data load has a hard finish time.
- Start data cleansing before design finishes. It has no dependency on configuration and always takes longer than expected, so run it in parallel from early on.
- Book training close to go-live. Train too early and it is forgotten; too late and there is no room to fix what the sessions reveal.
- Baseline at design sign-off. Everything before that is estimation; after it, track variance so scope creep is visible to the steering committee.
Related templates
- Software Development Gantt Chart Template
- Project Management Gantt Chart Template
- Free Employee Onboarding Gantt Chart Template
- Browse all Gantt chart templates
Frequently asked questions
How long does an ERP implementation take?
Typically 9–18 months for a mid-market single-instance rollout, and considerably longer for multi-entity or global programmes. The template uses a twelve-month schedule you can compress or extend from the go-live date.
What phases should an ERP project plan have?
Discovery and fit-gap, solution design, build and configuration, data migration, testing, and training with cutover and hypercare. Data migration and testing are separate tracks here because they are the two that most often drive delay.
Does this work for a phased rollout rather than big bang?
Yes — duplicate the build, testing and cutover phases per wave and keep discovery and design shared. The template gives you the pattern for the first wave.
Is the ERP implementation template free?
Yes. Free Excel, PowerPoint and CSV downloads, and free online editing with no sign-up.