A realistic ERP implementation timeline manufacturing UK project should plan for 6 to 12 months from kick-off to go-live for a single-site SME, and 12 to 18 months for a multi-site or heavily customised programme. The biggest risk is not the software — it is the planning, the data and the time your subject-matter experts can give the project while still running the factory. This guide sets out the phase-by-phase shape of a sensible plan, the milestones that matter, and the manufacturing-specific pitfalls that quietly add months to a project.
Last updated: 25 April 2026
What a realistic ERP implementation timeline looks like
Industry benchmarks paint a clear picture. Panorama Consulting Group’s 2024 ERP report puts the global median implementation at 15.5 months, with around 58% of projects on time and 42% running late. UK SME data ranges from 3 to 6 months for small projects, 6 to 9 for mid-sized, and 9 to 12+ for complex or customised systems.
For a typical mid-sized UK manufacturer (50 to 250 employees, single site, integrated CRM and shop floor), a 9 to 12-month plan is the most realistic baseline. It includes parallel testing, two end-user training cycles and a controlled cutover. Compressing the schedule normally costs you in change management, testing depth or post-go-live stabilisation. The Manufacturer consistently warns that aggressive timelines are the leading predictor of post-go-live disruption.
Phase-by-phase ERP implementation timeline manufacturing UK plan
A defensible 9 to 12-month plan for a UK manufacturer breaks down across seven phases. Treat each duration as an early-stage planning estimate — your specific scope and data quality will move them.
- Phase 1 — Discovery and planning (4 to 8 weeks). Confirm scope, business case, governance, project team, super users, KPIs and budget. Document current-state processes from quote-to-cash, plan-to-make and procure-to-pay.
- Phase 2 — Design and process redesign (6 to 10 weeks). Map future-state workflows in the new ERP, agree on configuration vs customisation decisions, sign off the solution design document, and define integrations with MES, CAD, e-commerce and EDI.
- Phase 3 — System configuration and build (8 to 16 weeks). Configure modules, build customisations, develop integrations, and create role-based access. Manufacturers usually run sprints by module: finance, procurement, inventory, production, sales, then advanced planning.
- Phase 4 — Data migration (6 to 12 weeks, runs in parallel). Extract, cleanse, map and load master data: customers, suppliers, items, BOMs, routings, work centres, open orders. Plan a minimum of two trial migrations before the live cutover.
- Phase 5 — Testing (4 to 8 weeks). Unit testing, integration testing, user acceptance testing and a full end-to-end business cycle test using migrated data. Stress-test month-end close, MRP run and shop-floor reporting.
- Phase 6 — Training (3 to 6 weeks, overlaps with testing). Train super users first, then run role-based end-user training. Assume 8 to 16 hours per shop-floor user, 16 to 24 hours per office user.
- Phase 7 — Go-live and stabilisation (1 week cutover, 8 to 12 weeks hypercare). Final dress rehearsal, cutover weekend, hypercare with daily stand-ups, then transition to business-as-usual.
Add 4 to 6 weeks of contingency. Few manufacturing ERP projects run completely to plan, and the projects that go best are the ones that build float into the schedule rather than discover slippage at week 30.
Why the manufacturing context changes the timeline
Manufacturers carry baggage that pure office-based businesses do not. Several factors push the ERP implementation timeline manufacturing UK projects need beyond what generic SaaS guidance suggests:
- BOMs and routings are usually messy, with engineering changes that have never been tidied up.
- Shop-floor data capture often runs on legacy MES, label printers or paper, all of which need integration or replacement.
- Production cannot stop. Subject-matter experts can only commit a fraction of their time, which lengthens every phase.
- Inventory accuracy at go-live is a make-or-break issue. Stock counts, cycle counts and bin reconciliations need to be planned weeks ahead.
- Year-end financial cutover and FRS 102/IFRS reporting requirements add VAT and Making Tax Digital complexity.
- Quality, traceability and customer-specific compliance (BRCGS, AS9100, IATF 16949) need extra configuration and testing.
- Multi-currency, multi-site and intercompany scenarios extend design and testing time.
- Shop-floor hardware refresh (handhelds, label printers, Wi-Fi) often runs in parallel and lands on the IT director’s desk.
According to Made Smarter, the UK manufacturers that succeed with ERP treat it as a business change programme led by operations, not an IT project run from a corner office. The implications are more workshops, more sign-off gates and more change-management investment — but a much higher chance of hitting go-live cleanly.
Sensible milestones and gate criteria for a UK manufacturer
Every phase should end with a written gate that the steering committee signs off before the project can move on. A typical milestone set for a UK manufacturer:
- Month 1: Business case, project charter and governance approved by board.
- Month 3: Solution design signed off, configuration vs customisation list locked.
- Month 5: First trial data migration complete, key reports producing recognisable numbers.
- Month 7: User acceptance testing pass, super users trained and certified.
- Month 8: End-to-end business cycle test passed using migrated data.
- Month 9: Cutover dress rehearsal complete, go/no-go decision made by exec team.
- Month 10: Go-live, hypercare opens, daily stand-ups for four weeks.
- Month 12: Hypercare exits, project closure paper to board, benefits-tracking handover to operations.
Each milestone should have a measurable gate criterion. “Solution design signed off” is not a gate; “the design document is signed by the COO, FD and project sponsor with no open red items” is.
Common reasons UK manufacturing ERP projects slip
The same patterns appear in nearly every late ERP project on a UK shop floor:
- Resource constraints. Now the leading cause of delay according to Panorama. Operations cannot release the right people for long enough.
- Data quality. Dirty BOMs, missing routings, and inventory variances surface late and absorb weeks of unplanned cleansing.
- Scope creep. “While we are doing this, can we also do X?” added monthly until the original plan is unrecognisable.
- Weak sponsorship. The MD attends the kick-off, then drifts away. The first politically difficult decision then derails the project.
- Under-tested integrations. CAD/PLM, MES, EDI, e-commerce and CRM connections work in isolation but not in combination.
- Training squeeze. Cut from the budget or compressed into the last two weeks before go-live.
- Aggressive go-live date set by the vendor or finance team. Without operational input, the date almost always misses peak season or audit constraints.
An experienced fractional IT director or independent programme lead spots these patterns early. Vendors and integrators have a commercial interest in a green status; an independent voice keeps the project honest.
How to choose a go-live date
For a UK manufacturer, the go-live calendar shapes the project. The best windows are usually quiet periods after a year-end close and well clear of customer audit cycles. January, June and August tend to work best; December, March and September are usually the worst. Lock the date 6 to 9 months ahead, freeze configuration two weeks before, and book a four-day cutover (typically Thursday evening to Tuesday morning) with two contingency days inside it. Run a full dress-rehearsal cutover four weeks before, on a copy of production data.
Frequently Asked Questions
How long does ERP implementation take for a UK manufacturer?
Most UK SME manufacturers should plan 6 to 12 months from kick-off to go-live for a single-site implementation. Smaller, less complex projects can finish in 3 to 6 months, while multi-site or heavily customised projects routinely run 12 to 18 months. Industry benchmarks from Panorama Consulting show the global median is around 15.5 months, so build contingency into your project plan from the start.
What are the phases of an ERP implementation timeline?
The standard manufacturing ERP implementation has seven phases: discovery and planning, design, configuration, data migration, testing, training, and go-live with post-go-live stabilisation. Each phase has clear deliverables and gating criteria. Skipping or compressing any of these phases is the most reliable way to push a go-live date back by months.
Why do ERP implementations run late?
Industry data shows that around 42% of ERP projects miss their original timeline, and the leading cause has shifted from technical issues to resource and staffing constraints. Other common causes include poor data quality, scope creep, weak executive sponsorship, under-resourced testing and a manufacturer’s reluctance to commit subject-matter experts away from production duties.
When should a UK manufacturer start planning ERP go-live?
Pick a go-live date that avoids your peak production season, the financial year-end and any major customer audit windows. Most UK manufacturers favour January, June or August. Lock the date 6 to 9 months in advance, run a full dress-rehearsal cutover four weeks beforehand, and freeze configuration changes two weeks before go-live.
Take the Next Step
If you are planning or rescuing an ERP project and need an independent voice across the steering committee, Bailey & Associates can help. We support UK manufacturers through every stage of an ERP implementation timeline manufacturing UK programme — from selection and design to data migration, testing and go-live. Fixed monthly retainer from £2,000 per month, no tie-in, cancel-anytime, fifteen-plus years of UK manufacturing IT experience. Learn more about our ERP and digital transformation services or book a free discovery call today.
Related Service: ERP & Digital Transformation Strategy — Learn how Bailey Associates can help your manufacturing business.
