Quick Answer (TL;DR)
A manufacturing ERP implementation usually takes 3 to 9 months for a single-plant mid-market company and 9 to 18 months for multi-site operations. Expect discovery in month 1, design and build in months 2 to 4, data migration and testing in months 3 to 5, go-live around month 6, then 30 to 60 days of hypercare.
Key Takeaways
- Scope, not software, sets your timeline. Plant count, BOM complexity and integrations add the most weeks.
- Business Central manufacturing projects typically run 12 to 16 weeks. Dynamics 365 Finance and Supply Chain Management runs 24 to 52 weeks.
- Start data cleanup in month 1. Late BOM and routing cleanup is the most common reason go-live slips.
- Run at least two data migration trials and one mock cutover before go-live.
- Go live at the start of a fiscal period, right after a physical inventory count.
- The project ends at the first clean month-end close, not on go-live day.
Every manufacturer that evaluates asks the same question early: how long until we are actually running on it? The honest answer is "it depends," but that is not useful when you are planning around production schedules, peak season and a fiscal year end.
This guide gives you something better. It breaks a typical manufacturing ERP implementation into months, shows what your team and your partner should be doing in each one, and flags the points where projects usually slip. The month-by-month plan below reflects a single-plant, mid-market manufacturer moving from a legacy system or spreadsheets to Microsoft Dynamics 365. Multi-site and highly regulated projects follow the same sequence, just stretched out.
If you are still comparing platforms, start with our breakdown of the and come back here once you have a shortlist.
How Long Does a Manufacturing ERP Implementation Take?
Most manufacturing ERP implementations take between 3 and 18 months from kickoff to go-live. Independent benchmarks from Ultra Consultants put small businesses at 3 to 4 months, mid-sized businesses at 6 to 9 months and large businesses at 9 to 18 months. Multinational rollouts can run 12 to 36 months.
Manufacturing sits at the longer end of each range for a simple reason. A distributor buys and sells finished items. A manufacturer also has to model how those items are made: multi-level bills of materials (BOMs), routings, work centers, capacity, scrap, costing and quality checks. Every one of those needs clean data, configuration and testing.
| Manufacturer profile | Typical platform | Kickoff to go-live | Hypercare after go-live |
|---|---|---|---|
| Small, 1 plant, make-to-stock, under 50 users | Business Central Premium | 3 to 4 months | 30 days |
| Mid-market, 1 plant, mixed make-to-stock and make-to-order | Business Central Premium | 4 to 6 months | 30 to 60 days |
| Mid-market, 2 to 3 plants or multiple legal entities | Business Central or D365 F&SCM | 6 to 9 months | 60 days |
| Enterprise, multi-site, process or regulated manufacturing | D365 Finance and Supply Chain Management | 9 to 18 months | 60 to 90 days |
Want a number for your own operation? Our estimates budget and duration from your users, modules and integrations.
Month-by-Month Manufacturing ERP Implementation Timeline
The plan below assumes a six-month project for a single-plant manufacturer, followed by two months of hypercare. Phases overlap on purpose. Data work starts long before go-live, and testing begins while the last integrations are still being built.
Data migration runs from month 3 to month 5 alongside build and testing, which is why late data cleanup is the most common cause of a slipped go-live.
Month 0: Readiness, Partner Selection and Team Setup
The weeks before kickoff decide more about your timeline than any later month. This is where you confirm scope, budget and who on your side will own each process.
- Name an executive sponsor and a full-time internal project lead.
- Pick process owners for planning, production, purchasing, inventory, quality and finance.
- Freeze the scope for phase one and park everything else on a phase two list.
- Agree on success metrics, such as inventory accuracy, on-time delivery or days to close.
A structured surfaces data gaps, process conflicts and resourcing risks before they turn into change orders. If you are still evaluating implementers, use this guide on to compare manufacturing experience, methodology and support terms.
Month 1: Discovery and Fit-Gap Analysis
Month 1 is about understanding how your plant really works, not how the old system says it works. Your partner runs workshops across the core manufacturing flows: plan to produce, procure to pay, order to cash and record to report.
What happens this month:
- Current-state process mapping, including the spreadsheets and workarounds people rely on.
- Fit-gap analysis against standard Dynamics 365 manufacturing features.
- A first audit of BOMs, routings, item cards and work centers.
- Decisions on manufacturing strategy: make-to-stock, make-to-order, assemble-to-order or a mix.
The deliverable is a signed scope and a fit-gap document that separates configuration from true custom work. A dedicated phase is the cheapest place to find problems, because changing a document costs far less than changing a configured system.
Month 2: Solution Design and Configuration Starts
In month 2, the fit-gap turns into a solution design your team signs off on. This is where the biggest manufacturing decisions get locked in.
- Costing method: standard, average or FIFO, and how variances post to the ledger.
- Planning setup: MRP parameters, reorder policies, lead times and safety stock.
- Production flow: production order types, output and consumption posting, and scrap.
- Chart of accounts, dimensions and inventory posting groups.
- Warehouse setup: bins, put-away and pick logic.
Configuration of the base environment starts in parallel. The rule that saves the most time is simple: configure first and customize only when a gap blocks a critical process. When a gap does need code, keep it in well-scoped built as extensions, so future Microsoft updates do not break it.
Month 3: Build, Integrations and the First Data Migration Trial
Month 3 is the heaviest build month. Your partner configures the agreed design, builds approved extensions and starts connecting the ERP to the rest of your stack.
Common manufacturing integrations include MES or shop floor systems, warehouse management, EDI with key customers, CAD or PLM for engineering BOMs, and payroll. Planning these early through a structured approach avoids last-minute surprises in testing. If you run a separate warehouse system, our guide to covers the sync points that matter most.
The first data migration trial also happens now. It usually covers master data only: items, BOMs, routings, work centers, vendors, customers and the chart of accounts. Expect it to fail in places. That is the point of a trial. Here are , including how we handle duplicate items and broken BOM structures.
For teams setting up make-to-order production, this walkthrough of Business Central production orders and BOM setup shows how the configuration should look before testing begins.
Month 4: Conference Room Pilots and System Integration Testing
In month 4, your team stops reviewing documents and starts running real scenarios in the system. A conference room pilot walks key users through full end-to-end flows, such as a sales order that triggers MRP, a production order, material consumption, output, shipment and invoice.
- System integration testing confirms data flows correctly between ERP, MES, WMS and EDI.
- Data migration trial 2 adds open transactions: open sales and purchase orders, open production orders, inventory balances and open AR and AP.
- Reports and dashboards get built and validated against known numbers.
This is the right time to design operational reporting, because the data model is now stable. Teams that want plant-level KPIs, such as OEE, scrap rate and schedule adherence, often pair the ERP with from day one.
Month 5: User Acceptance Testing, Training and Mock Cutover
Month 5 is where the business, not the partner, decides whether the system is ready. Key users run user acceptance testing (UAT) with real scripts and sign off on each process.
- Role-based training for planners, buyers, shop floor supervisors, warehouse staff and finance.
- A train-the-trainer model so your super users can support colleagues after go-live.
- A cost parallel: compare standard costs and a sample of production order costs against the old system.
- A full mock cutover, timed, so you know exactly how long the real one will take.
- A go or no-go meeting with clear criteria agreed in advance.
Use a structured to make sure nothing on the readiness list is based on assumptions.
Month 6: Cutover and Go-Live
Most manufacturers go live at the start of a fiscal month, right after a physical inventory count. That gives you clean opening balances and a natural cutoff for open transactions.
A typical cutover window looks like this:
- Freeze transactions in the legacy system.
- Count inventory and load final balances.
- Migrate open orders, open production orders and open AR and AP.
- Reconcile the trial balance and inventory valuation.
- Release the first production orders and ship the first orders in the new system.
If you cannot afford to stop the line, plan the cutover around a weekend or a planned shutdown, or phase it by plant or product line. This guide to zero-downtime manufacturing go-lives explains how phased Dynamics 365 deployments keep production running.
Months 7 and 8: Hypercare, Stabilization and Optimization
Go-live is not the finish line. The first 30 to 60 days after go-live are hypercare, when your partner provides priority support while users settle in. A practical way to define the end of the project is the first clean month-end close, which usually lands 4 to 6 weeks after go-live.
During hypercare you should expect to:
- Fix data issues and small configuration gaps that only show up at full volume.
- Tune MRP parameters once you see real planning suggestions.
- Review production order variances and correct standard costs.
- Close the first month and compare results against your legacy reports.
After hypercare, move into ongoing and start the phase two list you parked in month 0. Common next steps are advanced quality management, Copilot features and Dynamics 365 predictive maintenance for critical equipment.
Business Central vs Dynamics 365 F&SCM: How the Timeline Changes
The Dynamics 365 product you choose changes the length of every phase. Business Central is built for small and mid-sized manufacturers and is usually implemented in weeks. Dynamics 365 Finance and Supply Chain Management (F&SCM) is built for complex, multi-site operations and is measured in quarters.
| Factor | Business Central (Premium) | Dynamics 365 F&SCM |
|---|---|---|
| Typical manufacturing timeline | 12 to 16 weeks, up to 22 weeks with multiple entities | 24 to 52 weeks |
| Best fit | 1 to 3 plants, discrete manufacturing | Multi-site, process, mixed-mode or regulated manufacturing |
| Manufacturing license | Premium, $110 per user per month (US list) | Supply Chain Management licensing |
| Implementation budget | From about $50K for manufacturing scope | From about $110K to $500K+ |
| Design workload | Mostly configuration of standard features | Heavier design, more integrations, more testing cycles |
Note that Business Central manufacturing features (production BOMs, routings, production orders and capacity planning) require the Premium license. They cannot be added to Essentials. For a full side-by-side comparison, read .
If Business Central fits your operation, our follow fixed-scope tiers with published timelines. For multi-site or complex supply chains, see our approach to .
What Stretches a Manufacturing ERP Timeline
Most delays are predictable. They come from the same handful of causes, and almost all of them show up in months 3 to 5, when data migration and testing collide.
- Dirty BOM and routing data. Obsolete components, missing scrap factors and routings that do not match the floor. Cleanup started in month 4 instead of month 1 is the single most common reason go-live moves.
- Scope creep after design sign-off. Every "small" request added in month 3 pushes testing back.
- Over-customization. Rebuilding old workflows in code instead of adopting standard processes adds build and testing time, and it makes every future update harder.
- Key users who are not available. If your best planner is still running the schedule full time, design decisions and UAT stall.
- Integration surprises. An MES or EDI partner that cannot deliver test data on time blocks system testing.
- Legacy system complexity. Moving from old Dynamics GP or NAV versions, or from several disconnected tools, adds mapping and reconciliation work. A planned path keeps that work inside the plan instead of on top of it.
We break down these patterns in detail in . And if your project is already off track, this story of shows what a reset looks like in practice.
How to Shorten Your Timeline Without Raising Risk
You cannot skip phases, but you can remove waiting time between them. These are the moves that consistently save weeks:
- Start data cleanup on day one. Assign an owner for items, BOMs and routings before kickoff.
- Fit to standard. Adopt Dynamics 365 processes wherever they are good enough, and keep a short, justified list of gaps.
- Phase the scope. Go live with core manufacturing, inventory and finance first. Add advanced planning, quality or service in phase two.
- Free up your key users. Plan for process owners to spend one to two days a week on the project during design and testing.
- Make decisions in days, not weeks. Give the project lead authority to close open design questions quickly.
- Time go-live around your calendar. Avoid peak season, the last month of your fiscal year and the same week as a major Business Central update.
Frequently Asked Questions
How long does a Business Central implementation take for a manufacturer?
A Business Central implementation with manufacturing usually takes 12 to 16 weeks for a single company with standard production processes. Projects with multiple legal entities, several integrations or heavy data cleanup can take up to 22 weeks. Add 30 days of hypercare after go-live.
Can a manufacturing ERP go live in 30 days?
Core financials can go live in 4 to 6 weeks, but full manufacturing rarely can. BOMs, routings, MRP and costing need clean data and real testing. A 30-day manufacturing go-live usually means skipping data trials or UAT, which moves the risk into your first month of production.
What is the longest phase of a manufacturing ERP implementation?
Build, data migration and testing together take the most time, usually months 3 to 5. Data migration is the phase most likely to overrun because BOM, routing and item data in legacy systems is rarely as clean as teams expect.
Should manufacturers use a phased or big-bang go-live?
A big-bang go-live works for a single plant with a clear cutover window. Multi-plant manufacturers, or those who cannot stop production, usually do better with a phased rollout by plant, product line or module. Phasing takes longer overall but lowers the risk at each cutover.
When is the best time to go live with a new ERP?
The best time is the first day of a fiscal month, right after a physical inventory count and outside your peak season. Avoid your fiscal year-end month, since closing the year in two systems adds work and audit risk.
How much does a manufacturing ERP implementation cost?
Cost tracks timeline. Business Central manufacturing projects typically start around $50K, plus Premium licenses at $110 per user per month. Dynamics 365 F&SCM projects usually start above $100K. See our full guide on for line-item detail.
Plan Your Timeline Before You Commit
A manufacturing ERP implementation is a six-month project for most single-plant manufacturers and a year or more for complex, multi-site operations. The schedule rarely slips because of the software. It slips because data cleanup starts late, scope keeps growing or key users are not available when decisions are needed.
If you map your plant against the month-by-month plan above, you will see where your risks sit before you sign a contract. When you are ready to turn that into a real plan, talk to our certified team for a timeline built around your BOMs, routings, plants and integrations.