One of the first questions every executive asks when considering a new ERP system is: “How long will this take?” The honest answer is that it depends — but that does not mean the timeline has to be a mystery. With the right expectations and planning, you can forecast your ERP implementation timeline with surprising accuracy.
This article breaks down realistic durations by company size, walks through each project phase, identifies the most common causes of delay, and offers actionable strategies to keep your project on track. It is part of our complete ERP implementation guide, which covers every aspect of deploying an ERP system in 2026.
Realistic Timelines by Company Size
Not every ERP project is created equal. The duration depends on the number of users, the complexity of business processes, the number of modules, and the degree of customization required. Here are realistic ranges based on company size and typical project scope.
Small and Medium Businesses (SMB): 3 to 6 Months
For companies with fewer than 200 employees and relatively straightforward operations, a cloud-based ERP such as Odoo, SAP Business One, or Microsoft Dynamics 365 Business Central can go live in three to six months. These projects usually involve:
- A limited number of modules (finance, inventory, purchasing)
- Minimal custom development
- Data migration from spreadsheets or a single legacy system
- A core project team of three to five people
The key advantage for SMBs is simplicity. Fewer stakeholders, fewer integrations, and less legacy baggage mean the project can move quickly — provided leadership stays engaged and decisions are made promptly.
Mid-Market Companies: 6 to 12 Months
Organizations with 200 to 2,000 employees typically face more complexity: multiple departments, cross-functional workflows, regulatory requirements, and integrations with CRM, e-commerce, or manufacturing execution systems. Mid-market implementations often involve:
- Five to ten modules deployed in phases
- Moderate customization and workflow automation
- Data migration from multiple source systems
- A project team of eight to fifteen people, plus external consultants
Six months is achievable for a focused first phase (often called an MVP or Minimum Viable Product rollout), but reaching full operational maturity across all departments usually takes closer to twelve months.
Enterprise: 12 to 36 Months
Large enterprises with thousands of users, global operations, and deeply embedded legacy systems should plan for twelve to thirty-six months. These projects are defined by:
- Multi-country, multi-currency, multi-language requirements
- Extensive custom development and third-party integrations
- Complex data migration involving data cleansing, deduplication, and transformation
- Organizational change management across dozens of business units
- Project teams of thirty or more people, often with a dedicated program management office (PMO)
For enterprise-scale deployments of SAP S/4HANA, Oracle Cloud ERP, or Microsoft Dynamics 365 Finance and Supply Chain, a phased rollout — going live country by country or business unit by business unit — is the norm rather than the exception.
Phase-by-Phase Breakdown
Regardless of company size, every ERP implementation follows a series of distinct phases. Understanding what happens in each phase and how long it typically takes allows you to build a realistic project plan.
Phase 1: Discovery and Planning (2 to 8 Weeks)
This is the foundation of the entire project. During discovery, the project team documents current business processes, identifies pain points, defines requirements, and establishes success criteria. Key activities include:
- Stakeholder interviews and workshops
- As-is process mapping
- Requirements gathering and prioritization
- Vendor selection finalization (if not already completed)
- Project charter, scope definition, and governance structure
Why it matters: Cutting this phase short is one of the most common mistakes. Teams eager to start building skip thorough requirements analysis, only to discover gaps months later that force costly rework. Invest the time here — it pays dividends throughout the project.
Phase 2: Design (3 to 8 Weeks)
In the design phase, the team translates business requirements into a detailed system blueprint. This includes:
- To-be process design (how the business will operate in the new system)
- Gap-fit analysis (what the ERP handles out of the box versus what requires configuration or customization)
- Integration architecture design
- Data migration strategy
- Security and role-based access design
- Report and dashboard specifications
The output is a detailed design document that serves as the contract between the business and the technical team. Every subsequent decision references this document.
Phase 3: Build and Configuration (6 to 20 Weeks)
This is where the system takes shape. The technical team configures modules, builds custom workflows, develops integrations, and creates reports. In parallel, the data team begins extracting, cleaning, and transforming data from legacy systems.
- Core module configuration
- Custom development (forms, workflows, automation rules)
- Integration development (APIs, middleware, EDI)
- Data extraction, transformation, and loading (ETL) scripts
- Development of training materials
The build phase is where scope creep most often surfaces. A disciplined change request process is essential to prevent timelines from ballooning.
Phase 4: Testing (3 to 8 Weeks)
Testing is not optional, and it should never be compressed to make up for delays in earlier phases. A robust testing strategy includes multiple layers:
- Unit testing: Individual configurations and customizations work as designed
- Integration testing: Data flows correctly between modules and external systems
- User acceptance testing (UAT): Business users validate that the system supports their real-world workflows
- Performance testing: The system handles expected transaction volumes without degradation
- Migration testing: A full rehearsal of the data migration process
Plan for at least two full cycles of UAT. The first cycle will uncover issues; the second cycle verifies that fixes were applied correctly.
Phase 5: Go-Live (1 to 4 Weeks)
Go-live is the moment the organization switches from the old system to the new one. The go-live phase includes:
- Final data migration (cutover)
- End-user training (classroom, e-learning, or shadowed sessions)
- Communication to the broader organization
- Hypercare support (an intensive support period immediately after launch)
- Parallel run (optional: running old and new systems simultaneously for a short period)
The choice of go-live strategy — big bang, phased rollout, or parallel run — has a significant impact on risk and duration. A big bang approach is faster but riskier. A phased rollout reduces risk but extends the overall timeline. For guidance on choosing the right strategy, see our article on ERP implementation strategies.
Phase 6: Stabilization and Optimization (4 to 12 Weeks)
Many organizations underestimate this phase. After go-live, users are still learning the system, edge cases surface, and performance tuning is often needed. Stabilization activities include:
- Bug fixes and configuration adjustments
- Additional training for struggling users
- Process optimization based on real-world usage data
- Dashboard refinement and report adjustments
- Formal project closure and lessons learned
Do not disband the project team too early. The stabilization phase is when the system transitions from “technically live” to “genuinely adopted.”
The Six Most Common Causes of Delay
Understanding why ERP projects run late is the first step toward preventing it. Based on industry data and our own project experience, these are the most frequent culprits.
1. Scope Creep
Additional requirements that emerge after the design phase is locked are the single biggest driver of timeline overruns. Every “small change” adds up. Establish a formal change request process with clear impact assessments for cost and schedule.
2. Poor Data Quality
Data migration consistently takes longer than planned because source data is messier than anyone expected. Duplicate records, inconsistent formats, missing fields, and undocumented business rules all slow the process. Start data cleansing early — ideally during the discovery phase.
3. Change Resistance
Technology is rarely the bottleneck. People are. If end users do not understand why the change is happening or how the new system will benefit them, they will resist. Invest in organizational change management from day one, not as an afterthought.
4. Insufficient Testing
When earlier phases run over schedule, testing is the phase that gets squeezed. This is a dangerous trade-off. Bugs that reach production are far more expensive to fix than bugs caught in UAT. Protect your testing window.
5. Vendor and Consultant Availability
External consultants and vendor support teams have their own schedules. If your project timeline does not account for their availability, you will experience idle periods. Lock in consultant commitments early and build buffer into handoff points.
6. Decision-Making Bottlenecks
ERP projects require hundreds of decisions, from chart of accounts structure to approval workflow logic. When decision-makers are unavailable or unable to commit, the project stalls. Establish a governance model with clear escalation paths and decision deadlines.
Waterfall vs. Agile: Which Approach Is Faster?
The traditional waterfall approach follows the phases outlined above in a strictly sequential manner: complete one phase before starting the next. It offers predictability and clear milestones, which appeals to finance teams and executive sponsors who want a fixed timeline and budget.
The agile approach, increasingly popular in ERP implementations, delivers the system in iterative sprints. Each sprint produces a working increment of the system that users can test and provide feedback on. Key differences include:
| Factor | Waterfall | Agile |
|---|---|---|
| Timeline predictability | High (but often optimistic) | Lower upfront, more accurate over time |
| Flexibility to change | Low after design freeze | High throughout the project |
| User involvement | Concentrated in UAT | Continuous throughout |
| Risk of late surprises | Higher | Lower |
| Best suited for | Stable, well-understood requirements | Evolving requirements, complex environments |
In practice, most successful ERP implementations in 2026 use a hybrid approach: waterfall governance (fixed phases, stage gates, executive steering) with agile execution within each phase (sprints, demos, iterative refinement). This combines the structure that stakeholders need with the flexibility that project teams need.
Neither approach is inherently faster. Agile can reduce overall duration by catching issues earlier, but it requires more sustained engagement from business users. Waterfall can be efficient when requirements are truly stable, but it carries the risk of late-stage rework.
Seven Tips to Stay on Schedule
-
Invest in discovery. Thorough upfront planning prevents expensive rework later. Do not rush this phase.
-
Freeze scope early and manage changes formally. Every change request should include a timeline and cost impact assessment before approval.
-
Start data cleansing before the build phase. Data migration is almost always on the critical path. Getting a head start reduces risk significantly.
-
Protect the testing window. Never compress testing to compensate for delays in earlier phases. Shift the go-live date instead.
-
Assign dedicated resources. Part-time project team members are a recipe for delays. Key team members should be at least 80% allocated to the project.
-
Communicate relentlessly. Regular status updates to stakeholders prevent surprises and maintain executive support through the inevitable rough patches.
-
Plan for stabilization. Budget time and resources for the post-go-live period. The project is not done when the system goes live — it is done when the organization has genuinely adopted it.
The Bottom Line
An ERP implementation is a significant undertaking, but it does not have to be an unpredictable one. By understanding realistic timelines for your company size, respecting each project phase, and proactively managing the most common delay factors, you can deliver your ERP project on time and on budget.
The timeline ranges in this article — three to six months for SMBs, six to twelve months for mid-market, and twelve to thirty-six months for enterprise — are based on industry benchmarks and real-world project data. Your specific timeline will depend on your unique circumstances, but these ranges provide a solid foundation for planning.
For a complete overview of every aspect of ERP deployment, return to our complete ERP implementation guide. If you are evaluating costs alongside your timeline, our article on ERP implementation costs will help you build a realistic budget.
Stéphane ZÉ-OGIER is the founder of DigitsLane and writes about ERP implementation strategy for mid-market and enterprise organizations.
