Plan your ERP implementation with a Gantt chart. Map all phases from vendor selection through hypercare, including data migration dry runs, UAT, training, and cutover.
ERP implementations are the most complex IT projects most companies ever undertake. They touch every department, replace multiple existing systems, require months of data migration and configuration work, and demand parallel organizational change management. According to industry research, more than half of ERP implementations run over budget or over schedule — and the primary reason is inadequate project planning and timeline visibility.
A Gantt chart for ERP implementation is the foundational planning tool that keeps a 12–18 month, cross-functional program on track. It maps every workstream — configuration, data migration, integration development, testing, training, and cutover — on a single timeline with explicit dependencies. When a configuration milestone slips 2 weeks in month 4, the Gantt immediately shows how that affects UAT scheduling in month 9, and the program manager can adjust before the delay cascades.
At gantt-chart.io, you can build a comprehensive ERP implementation Gantt chart without expensive project portfolio management software. Free, browser-based, and capable of handling the complexity of a multi-stream ERP program.
Before implementation begins, the organization must select its ERP vendor. This phase appears in the Gantt because it consumes real time and has a specific deliverable: a signed contract.
RFP preparation and distribution (2–4 weeks)
Vendor responses and evaluation (4–6 weeks)
Demonstrations and reference checks (3–4 weeks)
Vendor selection decision (milestone)
Contract negotiation (2–4 weeks — often underestimated; legal review of an ERP contract is substantial)
Contract signed (milestone — this is the start gate for implementation)
The contract signed milestone is a hard dependency. No system access is granted, no implementation resources are assigned by the vendor, and no internal resources should be fully committed until the contract is executed.
Project team mobilization: Internal team members — project manager, functional leads by module (Finance, HR, Supply Chain, Manufacturing), IT lead, data migration lead, change management lead — are formally assigned. External consulting team is onboarded.
Project kickoff meeting (milestone): All stakeholders aligned on scope, timeline, governance, and escalation paths.
Project infrastructure setup: Project management tools, collaboration platforms, document repositories, ERP sandbox environment provisioned.
Communication plan published (milestone): How status will be reported, to whom, and on what frequency.
Business process mapping is the foundation of ERP configuration. You cannot configure a system to run your business until you've documented how your business actually runs — including the gaps between documented process and actual practice.
Current-state process documentation: Each functional workstream documents its current processes. This is time-consuming work that often uncovers process inconsistencies that have accumulated over years.
Future-state process design: The team designs how processes will work in the new ERP. Some processes will conform to ERP standards (the system does it this way, so you adapt). Others require configuration or customization to match the business. The "to-customize or to-adapt" decision for each process is a critical design choice.
Process gap analysis: Identifies where the ERP's native capability doesn't meet business requirements. Each gap requires a decision: configure, customize, use a workaround, or change the business process. Gap analysis: 4–6 weeks.
Design document approval (milestone by module): Functional specifications documenting configuration decisions. These approved specs are what the configuration team builds from.
Configuration is the core build phase. The ERP system is set up to reflect your business processes: organizational structures, chart of accounts, cost centers, product catalog, workflow rules, approval hierarchies, tax configuration, and hundreds of other parameters.
Configuration is organized by module:
Each module's configuration runs as its own swim lane in the ERP Gantt chart. Modules are not fully independent — financial configuration affects almost every other module, so Finance typically configures first. Show cross-module dependencies as linked bars.
Unit testing by module follows configuration of each module. Individual configuration decisions are validated before integration testing begins. Unit testing: 2–4 weeks per module.
System integration testing (SIT): Tests how modules work together — does an approved purchase order correctly update inventory, AP liability, and financial commitments? SIT requires all configured modules to be substantially complete. SIT: 4–6 weeks.
Data migration is the most technically complex and most commonly underestimated workstream in any ERP implementation. It runs in parallel with configuration from early in the project through go-live.
Data migration has four sub-phases, which repeat:
Extract: Pull data from source systems (current ERP, spreadsheets, legacy systems). Source systems often have inconsistent formats, duplicate records, and missing fields. Extraction scripts are custom-built per source system.
Cleanse: Data quality remediation. Vendor master deduplication, customer address normalization, open purchase order reconciliation, historical financial balance validation. Data cleansing is labor-intensive business process work, not just an IT task. Plan for significant business user involvement.
Load: Transform cleansed data into ERP-compatible format and load into the target system. Loading scripts are tested and refined over multiple iterations.
Validate: Reconcile loaded data against source system records. Verify record counts, financial totals, open transaction balances. Validation is a milestone: loaded and validated data is the go/no-go condition for each migration dry run.
Data migration dry runs: Dry runs are full practice migrations performed in the ERP test environment before production cutover. Most ERP implementations run 2–3 migration dry runs.
Each dry run is a milestone in the Gantt chart. Dry runs that fail validation gate delay the project — if Dry Run 2 doesn't reach 90% pass rate, Dry Run 3 is delayed. Show this as a go/no-go decision milestone.
An ERP rarely operates in isolation. It integrates with ecommerce platforms, CRM systems, payroll providers, EDI trading partners, banking systems, and third-party logistics providers. Each integration requires custom development.
Each integration appears as its own bar in the Gantt, with:
Integrations are frequently on the critical path because they depend on both internal configuration completion and external vendor cooperation. A payroll integration that requires your payroll provider to build a custom API may slip by 4–6 weeks due to the vendor's own development queue.
UAT is the final validation that the configured system meets business requirements before go-live. Unlike SIT (performed by the implementation team), UAT is performed by the business users who will operate the system every day.
UAT planning: Test scenario development, user selection and scheduling, test environment preparation. 2–3 weeks.
UAT execution: Business users execute predefined test scenarios covering their key workflows. Issues are logged, triaged, and resolved. UAT rounds: typically 2 rounds over 4–6 weeks.
UAT sign-off (milestone by module): Business leads formally sign off that their module is production-ready. UAT sign-off is a go/no-go gate for scheduling the go-live date.
Training runs parallel with UAT. Business users need training before they can execute UAT effectively; it also reduces the support load at go-live.
Training material development: Role-based training guides, recorded walkthroughs, quick reference cards. Allow 4–6 weeks for comprehensive training material creation.
Superuser training: Superusers (power users who will support their department peers) train first and most deeply. Superuser training: 3–5 days per role.
End-user training: Broader training for all staff who will use the system. End-user training: 1–3 days per role, delivered in waves.
Training completion milestone: All required users trained before go-live.
Cutover is the most operationally sensitive phase: shutting down legacy systems, completing final data migration, and going live on the new ERP.
Cutover plan development: Documents every task, every dependency, every rollback decision point, and every responsible person for the cutover weekend. A good cutover plan is a Gantt chart of its own — tasks at 15-minute granularity, spanning 48–96 hours.
Cutover timing: Most ERP go-lives happen at a quarter boundary or fiscal year boundary. Going live at the start of a new period minimizes the complexity of balancing accounts across two systems.
Parallel run period: Some organizations run legacy and new systems simultaneously for 1–4 weeks before fully decommissioning the legacy system. This is an insurance policy. Show the parallel run as a bar overlapping the start of the post-go-live period.
Go-live (milestone): Production system is live. The bar that spans the entire Gantt ends here.
Hypercare is the intensive support period immediately after go-live: 2–4 weeks when the full implementation team is on standby to resolve issues rapidly.
Hypercare exit is a formal milestone. After hypercare ends, the implementation team transitions to steady-state support and the project closes.
Change management — organizational readiness, stakeholder communication, resistance management — runs throughout the entire ERP implementation as its own swim lane. It never starts and ends; it's continuous.
Key change management milestones to show in the Gantt:
Open gantt-chart.io. Create swim lanes for each major workstream: Vendor/Contract, Project Management, Business Process Design, Configuration (by module), Data Migration, Integration Development, Testing, Training, Change Management, Cutover, and Hypercare.
Anchor the chart to your go-live target date and work backward. Show the migration dry runs as explicit milestones. Link UAT to configuration completion and data migration dry run 2. Link go-live to UAT sign-off, training completion, and dry run 3 validation.
The result is a comprehensive ERP implementation roadmap that surfaces risks before they become delays — and gives every workstream lead a clear picture of where their work fits in the broader program.
Build your ERP implementation timeline at gantt-chart.io — free, no account required.