ERP Implementation Timeline for Manufacturers (2026)
A mid-size manufacturer should plan for roughly 6 to 12 months, but the range depends on sites, modules, data and your own team. We lay out who published each figure, how SAP and Microsoft name the phases, and the five questions to put to any vendor's timeline.
One vendor tells you go-live in eight weeks. Another quotes eighteen months. Both can be telling the truth, because they are quoting different projects. The ERP implementation timeline for a manufacturer depends less on the software than on how many plants you run, how many modules go live first, how clean your data is and how much time your own people can give.
This guide gives you the ranges that vendors and surveys publish, with who said each one and why it might lean short. It lines the phases up with the frameworks SAP and Microsoft use, shows three common project shapes, and lists what stretches a schedule. At the end you will know how to read a quote.
How long does an ERP implementation take?
Published ranges for a mid-size manufacturer cluster around 6 to 12 months. The sources differ in who they are, and that decides how much weight each deserves.
| Source | Who it is | What it says |
|---|---|---|
| Panorama Consulting, 2026 ERP Report | Independent ERP consultancy. Survey of 170 organisations, data collected January 2025 to January 2026 | Median project timeline of 9 months. Respondents' median annual revenue was $200.5 million, and 56.5% were multinational |
| ERP Research | ERP comparison site that sells advertising and runs sponsored content | Mid-market (50 to 500 staff): 6 to 12 months. Small business: 3 to 6. Large enterprise: 12 to 24. A median of 6 months across 299 vendor and partner case studies, which the page itself calls best cases |
| BusinessHub (July 2026) | Australian ERP partner that implements Acumatica | Cloud ERP for mid-sized manufacturers typically takes 4 to 9 months from kick-off to go-live |
| Navigator Business Solutions (2023) | ERP services firm, in a blog post | Small business: 3 to 6 months. Mid-sized: 6 to 12 months. Large enterprise: 1 to 3 years |
Read these with two cautions. Vendor and partner figures describe projects they sold and delivered, so they lean short. And Panorama's respondents have a median revenue of $200.5 million and more than half are multinational, so they are likely bigger and more complex than your plant. Treat 9 months as a reference point, not a promise.
The phases of an ERP implementation
Every vendor draws the phases a little differently. Underneath, the work is the same eight activities. SAP and Microsoft publish their own frameworks, so here is how they line up.
| Activity | What happens | SAP Activate | Microsoft Success by Design |
|---|---|---|---|
| Discovery and scoping | Agree goals, scope, owners and the project team | Discover, Prepare | Discover, Initiate |
| Fit-gap and design | Test your processes against the standard product and log what does not fit | Explore (fit-to-standard workshops) | Discover, Initiate (solution blueprint) |
| Configuration and build | Set up the system and add only the changes you need | Realize | Implement |
| Data migration | Clean and load masters, opening stock and open transactions | Not a phase of its own | Not a phase of its own |
| Testing | Unit, integration and user acceptance testing | Realize (testing in sprints) | Prepare (final round of user acceptance testing) |
| Training | Role-based training before go-live | Deploy (adoption) | Prepare (user acceptance testing and training) |
| Cutover | Freeze, final load, go or no-go decision, go-live | Deploy | Prepare (cutover plan with go or no-go criteria, mock go-lives) |
| Hypercare and stabilisation | Extra support while your team learns the live system | Deploy (hypercare), Run | Operate (stabilisation) |
The names come from SAP's course material on SAP Activate (Discover, Prepare, Explore, Realize, Deploy, Run) and Microsoft Learn (Discover, Initiate, Implement, Prepare, Operate).
Neither framework makes data migration a phase of its own. That is one reason it is the part of a plan that slips. Our guide to ERP data migration for manufacturers covers it in detail.
How long each activity takes
Two vendor guides break the work into phases with durations. Use them as planning ranges, not benchmarks.
- ERP Research: discovery and planning 2 to 4 weeks, design and configuration 6 to 10 weeks, data migration 4 to 8 weeks (running in parallel), user acceptance testing 4 to 8 weeks, training and cutover 3 to 6 weeks, hypercare 4 to 12 weeks. The page notes that phases overlap, so they add up to more than the calendar timeline.
- BusinessHub, for a mid-complexity manufacturing project: about 6 to 8 weeks for discovery and design, 8 to 12 weeks for configuration and data migration, 4 to 6 weeks for testing and user acceptance, and 4 to 8 weeks for go-live preparation and hypercare. It recommends a 10 to 15% contingency buffer in each phase.
BusinessHub's four stages add up to 22 to 34 weeks, roughly five to eight months, before the buffer. That fits its own 4 to 9 month headline and sits at the short end of the 6 to 12 months the other sources give for mid-market plants.
What stretches an ERP implementation
Panorama's 2026 report found almost a quarter of organisations over schedule and more than a quarter over budget. The reasons are more about people than software.
- Sign-offs and design disputes. Of the projects that ran late, the most common cause Panorama found was organisational: governance, resistance to change and process redesign. It shows up as delayed sign-offs, long design workshops and a longer stabilisation period. Its example is a process owner resisting a common chart of accounts, which sends the team back to redo the design.
- Too little change management. Fewer than a quarter of Panorama's respondents reported an intense focus on it.
- A system that does not fit. Over-budget projects most often needed unexpected extra technology. Panorama links that to poor system selection: misfits found late, then patched with added tools, wider scope and custom builds.
- Data. Both ERP Research and BusinessHub name data quality and migration as drivers of duration.
- Your team's time. BusinessHub points to team members being pulled back to operational work during critical phases. In a plant, that is the stores manager who cannot leave the dispatch bay.
- Scope creep. New requirements added mid-project push the date out, as BusinessHub notes. Customisation, integrations and the number of users and sites do the same, according to ERP Research and Navigator.
Three project shapes and the range to plan for
Most plants fit one of three shapes. The ranges below are our reading of the sources above, not a measurement.
| Shape | What it looks like | Planning range | Why |
|---|---|---|---|
| Single plant, standard modules | One site and one company entity. Inventory, purchase, sales and accounts. Little customisation. Cloud | 4 to 9 months | BusinessHub's cloud range for mid-sized manufacturers. The 3 to 6 month small-business band is the best case |
| Two sites with production planning | Two locations. BOMs, work orders and scheduling. Some customisation and one or two integrations, for example Tally or a bank | 6 to 12 months | The mid-market band that ERP Research and Navigator both give |
| Multi-site or regulated | Three or more locations, several legal entities, or a plant that must validate its systems, such as a pharma unit | 12 months or more | The large-enterprise bands start at 12 months. More sites and validation add testing and rollout work (our judgement) |
Panorama's median of 9 months sits at the top of the first range and inside the second.
Many projects also split the go-live. Panorama found that more than a quarter used a hybrid approach: core modules or a pilot site first, with the remaining sites and functions later. If a vendor quotes a short timeline, ask whether it covers the core modules only.
How to read a vendor's timeline
Put these five questions to every quote:
- Which project shape are you quoting, and what is in the first go-live?
- Who cleans the data, and how many weeks does the plan give it?
- How many hours a week do you need from our stores, purchase, production and accounts people?
- Where is the contingency, and what happens to the date when we change scope?
- What does live mean: core modules in use, or everything on the original list?
Ask for the answers by phase and in writing. A plan that cannot show where your own team's time goes has not counted it.
Conclusion
Most sources put a mid-size manufacturer at 6 to 12 months, and a much shorter quote usually means a narrower scope. Most delays come from sign-offs, data and your team's availability, not from the software. Before you sign, ask for the timeline by phase and check what live means.
If you are coming off Excel or Tally, start with our guides on moving from spreadsheets to ERP and moving from Tally to ERP, or read how to choose a manufacturing ERP. To scope a rollout for your own plant, talk to our team about our manufacturing ERP software.