ERP research · Updated October 2026
ERP implementation timeline by company size: the 2026 data
How long does ERP really take? The latest independent survey puts the median at 9 months, published small-business case studies at about 3, and partner data shows timelines rising steadily with user count. Here is what the evidence says, where it is weak, and how to plan your own go-live.
- Sources cited
- Updated October 2026
- Zoho and Odoo partner
- Honest about data limits
Odoo go-live time by number of users
Typical range in weeks, SOW to go-live. Dark marker shows the median. Partner-reported
Source: Octura Solutions, State of Odoo Implementation 2026 (Odoo partner, 100+ projects, North America). Cross-vendor median for mid-market ERP: 9 months (Panorama 2026).
Key takeaways
Key findings
- The median ERP project now takes about 9 months, according to Panorama Consulting's 2026 ERP Report (170 respondents, median revenue $200.5M). Its 2024 report put the median at 15.5 months.
- Smaller firms go live faster. A corpus of 1,948 published ERP case studies shows a median of 3.2 months for SMBs against 6 months for mid-market and enterprise (ERP Research, 2026). Published case studies skew towards successes, so treat these as best-case.
- User count is a strong predictor. One Odoo partner's 2026 data shows medians rising from 8 weeks at 10 users to 24 weeks at 100+ users.
- Overruns are smaller than the old headlines. In 2017 Panorama found 59% of projects over schedule; in 2026 it was almost a quarter.
- Shorter, phased plans stay on budget more often. Mint Jutras (2018) found 54% of projects planned to go live within 6 months were on budget, while 63% of those taking over a year ran more than 10% over.
- People, not software, cause most delays. Panorama's top schedule-overrun cause in 2026 was organisational: governance, resistance to change and process redesign.
The headline numbers
How long ERP implementation takes in 2026
Panorama Consulting Group's annual ERP Report is the most widely cited independent benchmark. Its latest figures are much shorter than the numbers many websites still quote.
Panorama's 2026 ERP Report puts the median implementation at 9 months, based on 170 respondents surveyed between January 2025 and January 2026, with a median annual revenue of $200.5M [1]. Its 2024 report, based on 131 respondents, found a median of 15.5 months [2]. Back in 2017, Panorama reported an average of 16.9 months from 342 respondents [3].
Two cautions before comparing them. First, the 2017 figure is an average and the later ones are medians, and averages are pulled up by a few very long projects. Second, each year surveys different organisations. The direction is still clear: typical projects are getting shorter, helped by cloud deployment and more standardised scope.
ERP implementation duration over time
Panorama Consulting Group ERP Reports, months
Sources: Panorama 2017, Panorama 2024, Panorama 2026. Samples skew to mid-market and larger organisations.
Overruns then and now
Share of ERP projects running over budget or schedule
| Study | Over budget | Over schedule |
|---|---|---|
| Panorama 2017 (n=342) | 74% | 59% |
| Panorama 2024 (n=131) | Fewer than half | Fewer than half |
| Panorama 2026 (n=170) | More than a quarter | Almost a quarter |
Sources: Panorama ERP Reports 2017, 2024 (more than half finished within budget and timeline) and 2026.
By company size
ERP timelines by company size
No single survey reports duration by size with a large, unbiased sample. Three sources together give a consistent picture: the bigger the organisation, the longer the project.
Published case studies: 3 to 6 months
ERP Research analysed 1,948 vendor and partner case studies and reports a median duration of 3.2 months for SMBs (61 cases), 6 months for mid-market (94) and 6 months for enterprise (101) [4]. Case studies are written about projects that went well, and overrun or abandoned projects are rarely published, so these medians very likely understate real durations.
Survey evidence: time rises above $100M revenue
Mint Jutras surveyed 315 manufacturers and distributors with revenue above $25M in 2018. It found time to go-live rose with company size above $100M, and only very large companies missed their schedule expectations in aggregate [5].
Partner data for Odoo: weeks, not months, for small teams
Octura Solutions, an Odoo partner with 100+ projects, reports a median of 8 weeks at 10 users, 11 at 25, 14 at 50 and 24 weeks at 100+ users, with about 15% of projects overrunning their range, mostly for client-side reasons [6]. This is practitioner data from North America, not peer-reviewed research.
Our own published Odoo ranges sit in the same band: typically 6 to 8 weeks for small finance and sales projects and 3 to 5 months for manufacturing or multi-company projects [7]. For Zoho CRM we typically see 3 to 8 weeks for a focused rollout and 2 to 4 months across several teams.
Median ERP duration by company size
ERP Research analysis of 1,948 published case studies, months
Source: ERP Research, ERP implementation statistics (Oct 2026). Published case studies exclude most failed or late projects.
Benchmarks side by side
Each source measures something different, so compare with care
| Source | Who it covers | Typical duration | Type |
|---|---|---|---|
| Panorama 2026 | 170 organisations, median revenue $200.5M | 9 months (median) | Independent survey |
| ERP Research 2026 | 1,948 published case studies | 3.2 to 6 months (median) | Case-study analysis |
| Octura 2026 | Odoo projects, 10 to 100+ users | 8 to 24 weeks (median) | Partner-reported |
| Thoughtlogik | Odoo projects, UK | 6 to 8 weeks to 3 to 5 months | Partner-reported |
Sources listed below. Partner figures, including ours, are marketing data and labelled as such.
Plan design
Why shorter, phased go-lives work better
The longer a project runs, the more it costs and the more the business changes underneath it. The data supports going live in phases.
In Mint Jutras' 2018 survey, 41% of projects finished on or under budget overall. Among projects with an aggressive plan, going live within six months, 54% were on budget. Where go-live took more than a year, 63% ran more than 10% over budget [5]. The same study put average time to return on investment at about 2.5 years.
Older data points the same way. A 2010 Panorama study, as reported by Computerworld, found schedule overruns of 30% for Tier I vendors, 18% for Tier II and 5% for Tier III [8]. Simpler, more standard systems tend to finish closer to plan.
Odoo's documented implementation methodology is phased: deploy a group of apps, and run each phase through onboarding, data import, training and production before starting the next [9]. In practice that means finance and sales first, then inventory, then manufacturing, each with its own go-live.
Plan length and budget outcomes
Mint Jutras survey of 315 manufacturers and distributors, 2018
Source: Mint Jutras 2018, as published by Ultra Consultants. Dated, so use as directional evidence.
Risks
What drives ERP overruns
Across every study, the causes of delay are mostly organisational. That is good news, because they are within your control.
Panorama's 2026 report names organisational issues as the top cause of schedule overruns: governance, resistance to change and process redesign. The top cause of budget overruns was an unexpected need for additional technology [1]. In 2024 the top schedule cause was resource constraints [2].
Even projects that go live on time can disappoint. Gartner forecasts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business objectives [10]. A 2012 McKinsey and University of Oxford study of more than 5,400 IT projects found large projects ran 45% over budget and 7% over time while delivering 56% less value than predicted [11]. Time is not the only measure: value is.
Overrun drivers and how to prevent them
Evidence from the studies above, with Thoughtlogik practice
| Driver | Evidence | Prevention |
|---|---|---|
| Weak governance and decisions | Panorama 2026, top schedule cause | Named sponsor, weekly decisions log |
| Resistance to change | Panorama 2026 | Involve key users from design onwards |
| Process redesign mid-project | Panorama 2026 | Agree target processes in the design phase |
| Unplanned extra technology | Panorama 2026, top budget cause | Map integrations and reporting early |
| Too few internal people | Panorama 2024, top schedule cause | Backfill key users during build and testing |
| Big-bang scope | Mint Jutras 2018 | Phase go-lives by app or site |
Sources: Panorama 2026, Panorama 2024, Mint Jutras 2018. Prevention column is practitioner guidance.
How we plan it: our SCALE method (Scope, Craft, Assemble, Launch, Evolve) fixes scope and target processes before configuration starts, runs test migrations before go-live, and phases launches so each part of the business sees value early.
Timeline estimator
How long will your ERP project take?
Answer five questions for an indicative range. It is calibrated for Odoo and Zoho projects of the size we typically deliver.
Indicative ranges only, based on our project experience and the partner and survey benchmarks on this page. Real timelines are set after discovery.
FAQs
ERP implementation timeline FAQs
Cannot see your question? Our UK consultants are happy to talk it through.
How long does an ERP implementation take?
Panorama Consulting's 2026 ERP Report puts the median at 9 months for organisations with a median revenue of about $200M. Small businesses with simpler scope often go live in 2 to 4 months; published SMB case studies show a median of 3.2 months. Large, multi-site programmes can take a year or more.
How long does ERP take for a small business?
For 10 to 25 users and a focused scope such as finance, sales and stock, partner data for Odoo shows medians of 8 to 11 weeks. We typically deliver small Odoo finance and sales projects in 6 to 8 weeks. Data migration and decision speed are the biggest variables.
How long does ERP take for a mid-sized company?
Expect roughly 3 to 9 months. Published mid-market case studies show a 6-month median, partner data for 50 to 100+ users shows 14 to 24 weeks, and Panorama's mid-market-heavy survey shows 9 months. Manufacturing, multi-company and integrations push towards the top of the range.
What percentage of ERP projects run late?
In Panorama's 2026 report, almost a quarter of projects ran over schedule and more than a quarter over budget. That is a big improvement on 2017, when Panorama found 59% over schedule and 74% over budget, but each survey used a different sample.
Is it true that most ERP projects fail?
The widely quoted claim that 55% to 75% of ERP projects fail has no traceable original report. Gartner's published forecast is that by 2027 more than 70% of recently implemented ERP initiatives will not fully meet their original business objectives. That is a value problem more than a go-live problem.
What causes ERP projects to overrun?
Panorama's 2026 report names organisational issues, such as governance, resistance to change and process redesign, as the top cause of schedule overruns, and unexpected extra technology as the top budget cause. Resource constraints topped the list in 2024.
Should we go live all at once or in phases?
For most SMEs, phases. Mint Jutras found projects planned to go live within six months were more likely to stay on budget, and Odoo's methodology deploys apps in phases. A phased plan delivers value early and reduces the risk of one large cut-over.
How can we shorten our ERP timeline?
Name a sponsor who can make decisions, free up key users, clean data before migration, adopt standard processes where possible and phase the go-live. Our delivery approach builds these in from the first workshop.
Sources
- Panorama Consulting Group, 2026 ERP Report (PDF) 4439340.fs1.hubspotusercontent-na1.net/hubfs/4439340/Reports/ERP%20Rep
- Panorama Consulting Group, 2024 ERP Report (PDF) 4439340.fs1.hubspotusercontent-na1.net/hubfs/4439340/Reports/ERP%20Rep
- Panorama Consulting Group, 2017 ERP Report (PDF) panorama-consulting.com/wp-content/uploads/2017/07/2017-ERP-Report.pdf
- ERP Research, ERP implementation statistics (Oct 2026) erpresearch.com/erp-implementation-statistics
- Mint Jutras 2018 ERP survey, published by Ultra Consultants ultraconsultants.com/insights/white-papers/erp-implementation-survey/r
- Octura Solutions, State of Odoo Implementation North America 2026 (partner-reported) octurasolutions.com/resources/state-of-odoo-implementation-north-ameri
- Thoughtlogik, Odoo UK questions answered (our published timelines) thoughtlogik.com/odoo-uk-questions-answered
- Computerworld, Widespread discontent persists with ERP projects (Panorama 2010) computerworld.com/article/1516480/widespread-discontent-persists-with-
- Odoo, implementation methodology (9.0 documentation) odoo.com/documentation/user/9.0/getting_started/documentation.html
- Gartner, What IT leaders must do to avoid disappointing ERP initiatives gartner.com/en/information-technology/insights/what-it-leaders-must-do
- McKinsey and University of Oxford, Delivering large-scale IT projects on time, on budget and on value (2012) mckinsey.com/capabilities/tech-and-ai/our-insights/delivering-large-sc
Sources checked 18 October 2026. Panorama's samples skew to mid-market and larger organisations. Case-study and partner figures, including Thoughtlogik's own, are not independent research. We do not use the untraceable 55% to 75% ERP failure figure.
Keep exploring
Related services and research
Start your project
Want a realistic plan for your ERP go-live?
Tell us about your team, systems and deadlines. A consultant will come back within one working day with a phased plan and the decisions that will keep it on track.
- Free, no-obligation consultation
- Phased plan with clear milestones
- Honest view of risks and dependencies
Planning an ERP project?Get a realistic timeline from a UK partner.
Book a free call