Project plan for an ERP implementation
An ERP implementation changes purchasing, production, warehouse and accounting at the same time — it rarely fails because of the software, but on master data, processes and key users without time. This plan shows the implementation at a machinery manufacturer with two sites, from requirements to go-live.
No sign-up · opens instantly · 28 Weeks · 10 Phases · 67 Tasks · Budget approx. €577,600
This is how the plan looks in PathHub — click through the tabs or tick off tasks.
Manufacturing ERP Implementation and Legacy-System Replacement
This project will replace spreadsheets and a legacy production system with a new ERP platform for a machinery manufacturer with 180 employees across two sites. The scope includes production, materials management, planning, warehouse barcode operations, accounting integration, data migration, and role-based training. It is intended to standardize processes, improve data reliability, and support end-to-end operational control. The implementation must be delivered within a nine-month business target, requiring disciplined governance and coordinated execution across business and IT teams.
Phases
Phase 1: Project Mobilization and Governance
Establish the governance structure, decision rights, implementation method, and resources for the ERP replacement. This phase creates the control framework needed to deliver the nine-month go-live across both manufacturing sites.
Phase 2: Current-State Analysis and Requirements
Document how both sites currently manage production, materials, planning, warehousing, finance, reporting, and spreadsheet-based workarounds. The outcome is a validated requirements baseline that distinguishes common processes from site-specific needs.
Phase 3: Solution Design and Fit-Gap Assessment
Define the future-state ERP processes and determine which requirements can be met by standard functionality, configuration, or controlled extensions. The phase prevents uncontrolled customization while ensuring that production, planning, warehouse, and financial needs are covered.
Phase 4: Data and Integration Architecture
Establish the technical and business architecture for migrating legacy and spreadsheet data and connecting the ERP with accounting and other required systems. Clear ownership and reconciliation rules are defined before configuration and migration work begin.
Phase 5: ERP Configuration and Process Build
Configure and build the core ERP solution based on the approved future-state design. The work covers production, materials, purchasing, planning, inventory, finance-related processes, workflow, reporting, and user security.
Phase 6: Barcode Warehouse Implementation
Implement the barcode-enabled warehouse processes at both sites, including physical locations, scanners, printers, labels, stock transactions, and user procedures. The objective is reliable real-time inventory visibility and controlled material movement.
Phase 7: Data Cleansing and Migration Rehearsals
Clean, standardize, validate, and rehearse the migration of data from the legacy production system and spreadsheets. Repeated migration cycles establish confidence in master data, open transactions, inventory, production structures, and opening financial balances.
Phase 8: End-to-End Testing and Business Readiness
Validate integrated business scenarios across both sites, from demand and purchasing through production, warehousing, accounting, and management reporting. Business users confirm that the ERP can support daily operations before training and cutover approval.
Phase 9: Training, Cutover Preparation, and Go-Live Readiness
Prepare employees for the new ERP processes and complete all operational, technical, data, and support preparations for go-live. Readiness is assessed separately for both sites and for every critical business function.
Phase 10: Go-Live and Hypercare
Execute the cutover from the legacy production system and spreadsheets to the ERP, stabilize daily operations, and transition the solution to normal support. Hypercare focuses on production continuity, inventory accuracy, accounting integrity, and rapid issue resolution.
Timeline
Budget
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Data Migration Lead | 35 Person days | €1,100 | €38,500 |
| Data Cleansing and Master Data Analyst | 45 Person days | €700 | €31,500 |
| Migration Templates and Data Conversion Tooling | 1 Flat rate | €12,000 | €12,000 |
| Test Manager and Integration Test Coordination | 25 Person days | €1,000 | €25,000 |
| Test Automation and Defect Management Support | 15 Person days | €800 | €12,000 |
| Training and Change Management Lead | 25 Person days | €900 | €22,500 |
| Training Materials, Work Instructions, and E-Learning Content | 1 Flat rate | €12,000 | €12,000 |
| Cutover and Hypercare Support Consultants | 18 Person days | €1,100 | €19,800 |
| Cross-Site Travel and Workshop Expenses | 1 Flat rate | €7,200 | €7,200 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| ERP Implementation Project Manager | 35 Person days | €1,000 | €35,000 |
| Manufacturing and Production Planning Consultant | 45 Person days | €1,200 | €54,000 |
| Materials Management and Warehouse Consultant | 30 Person days | €1,100 | €33,000 |
| Finance and Accounting Interface Consultant | 25 Person days | €1,200 | €30,000 |
| ERP Technical Configuration and Development Consultant | 25 Person days | €900 | €22,500 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Manufacturing ERP Licenses and Initial User Setup | 1 Flat rate | €90,000 | €90,000 |
| Accounting Connector and Integration Middleware | 1 Flat rate | €15,000 | €15,000 |
| Accounting Interface Developer | 25 Person days | €1,200 | €30,000 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Industrial Barcode Handheld Scanners | 12 Person days | €1,800 | €21,600 |
| Industrial Barcode Label Printers | 4 Person days | €2,500 | €10,000 |
| Warehouse Wireless Network and Site Installation | 1 Flat rate | €12,000 | €12,000 |
| Mobile Warehouse Software Licenses | 2 Person days | €4,000 | €8,000 |
| Initial Barcode Labels and Consumables | 1 Flat rate | €6,000 | €6,000 |
| Item | Qty | Unit price | Total |
|---|---|---|---|
| Internal ERP Project Coordinator | 20 Person days | €850 | €17,000 |
| Business Workstream Leads and Key Users | 40 Person days | €250 | €10,000 |
| Operational Backfill for Workshops and Testing | 20 Person days | €150 | €3,000 |
Risks
Scope Expansion and Uncontrolled Customization
If requirements are added after the signed-off catalogue in Week 6, or more than a small number of material gaps require custom development after Week 9, the configuration, testing, budget, and nine-month go-live date may become unachievable.
Inadequate Legacy and Spreadsheet Data Quality
If data owners have not profiled and cleansed inventory, bills of material, routings, suppliers, customers, locations, and open transactions by Week 14, migration errors may cause incorrect stock, purchasing, production, or customer records at go-live.
Unreliable Production Planning and Manufacturing Master Data
If bills of material, routings, work centres, capacity calendars, lead times, yield factors, or planning parameters fail agreed accuracy tests during Weeks 15-17, MRP and production schedules may generate shortages, excess inventory, unrealistic dates, or shop-floor disruption.
Accounting Interface and Financial Reconciliation Failure
If account mappings, tax treatment, inventory valuation, cost flows, or interface error handling are not approved by Week 15, or if financial totals do not reconcile during the Week 17 rehearsal, postings, month-end close, tax reporting, and audit evidence may be incorrect.
Barcode Warehouse and Network Implementation Failure
If scanner connectivity, printer configuration, label readability, location data, or warehouse transaction procedures fail under realistic operating conditions during Weeks 15-17, stock accuracy, picking, receiving, production issuing, and dispatch may be disrupted at one or both sites.
Loss of Product Traceability or Quality Records
If serial numbers, batch numbers, material certificates, inspection results, nonconformances, or links between purchased material and manufactured product are not defined and tested by Week 20, the business may be unable to demonstrate product history or respond effectively to quality issues and customer inquiries.
Insufficient Key-User Availability
If production, warehouse, planning, procurement, finance, or quality key users cannot provide the planned workshop, validation, and testing time during Weeks 3-21, decisions and defect resolution may be delayed and the solution may be accepted without adequate operational review.
Training and User Adoption Gaps
If fewer than 95% of critical users complete role-based training and practical assessment by the end of Week 25, employees may continue using spreadsheets, bypass barcode transactions, or enter incomplete ERP data after go-live.
Vendor Capacity, Budget, and Schedule Pressure
If vendor deliverables, interface development, or critical defect fixes slip beyond their baseline dates—particularly configuration beyond Week 15 or critical testing defects beyond Week 21—the remaining schedule and the EUR 650,000 budget reserve may be insufficient for recovery.
Go-Live Disruption and Inadequate Recovery Planning
If the cutover rehearsal does not prove opening balances, inventory status, open orders, user access, interfaces, and rollback steps by Week 24, production, purchasing, warehousing, dispatch, or financial close may be interrupted during Weeks 26-28.
Unresolved Differences Between the Two Sites
If site-specific differences in inventory units, warehouse locations, production procedures, approval rules, or planning calendars remain unresolved after Week 9, the ERP may require inconsistent configurations, duplicate master data, or manual workarounds.
Stakeholders
Executive Sponsor and Steering Committee
Approves scope, budget, major design decisions, and escalations
ERP Project Manager
Coordinates workstreams, schedule, risks, vendor activities, and decisions
IT and Integration Lead
Owns infrastructure, security, interfaces, technical testing, and support readiness
Site Managers for Both Locations
Resolve site-specific conflicts, provide operational resources, and approve local readiness
ERP Vendor and Implementation Partner
Provides product expertise, configuration, development, migration support, and defect resolution
Production and Operations Lead
Defines production execution requirements, shop-floor processes, and operational acceptance criteria
Production Planning Lead
Owns planning logic, scheduling parameters, capacity requirements, and planning validation
Materials Management and Procurement Lead
Defines purchasing, replenishment, inventory, supplier, and material master processes
Warehouse and Logistics Lead
Owns warehouse layout, barcode transactions, scanner usage, stock movements, and inventory accuracy
Finance and Accounting Lead
Defines financial postings, accounting controls, reporting, reconciliation, and interface acceptance
Quality and Traceability Representative
Ensures production records, material traceability, quality-related data, and audit requirements are represented
Employee Representatives or Works Council, if applicable
Reviews changes to employee workflows, monitoring, training, and working practices
Compliance
Configure statutory accounting, tax, audit-trail, record-retention, financial-approval, and segregation-of-duties controls applicable to the company’s jurisdiction
Consult employee representatives or a works council, where applicable, regarding workflow changes, user monitoring, personal data processing, training, and changes to working practices before implementation
Align process ownership, document control, master-data governance, nonconformance handling, and audit evidence with the company’s ISO 9001 or equivalent quality-management system where maintained or contractually required
Implement role-based access, privileged-account control, segregation of duties, secure interfaces, backup and restore testing, change control, incident response, and business-continuity measures in line with internal IT security policy
Milestones
- Week 2
Approved project charter, staffed workstreams, governance framework, and baseline implementation schedule
Depends on: Project mobilization and governance - Week 6
Signed-off current-state process maps, requirements catalogue, site-difference register, and master-data source inventory
Depends on: Current-state analysis and requirements - Week 9
Approved future-state design, fit-gap catalogue, customization decisions, and process acceptance criteria
Depends on: Solution design and fit-gap assessment - Week 9
Approved integration specification, migration object catalogue, data ownership matrix, and technical architecture
Depends on: Data and integration architecture - Week 15
Core ERP configuration completed, approved extensions delivered, security roles assigned, and unit-test exit criteria met
Depends on: ERP configuration and process build - Week 16
Barcode hardware installed, warehouse transactions validated at both sites, and approved warehouse operating procedures completed
Depends on: Barcode warehouse implementation - Week 17
Approved migration datasets, two completed migration rehearsals, reconciliation evidence, and signed migration runbook
Depends on: Data cleansing and migration rehearsals - Week 21
Critical end-to-end defects closed or formally accepted, business acceptance completed, and test exit approval granted
Depends on: End-to-end testing and business readiness - Week 25
Approved cutover plan, completed critical-user training, signed site readiness checklists, and formal go-live decision
Depends on: Training, cutover preparation, and go-live readiness - Week 28
ERP live at both sites, critical operations stabilized, first reconciliations completed, and ownership transferred to the support organization
Depends on: Go-live and hypercare
How this plan was created
This plan was created by PathHub AI from a single description: “Introduce a new ERP system in a machinery manufacturer with 180 employees at two sites: replace spreadsheets and a legacy production system, materials management, production planning, barcode warehouse, accounting interface, data migration and training. Go-live in nine months.” — without company context. With your departments, approval processes and compliance requirements it becomes much more precise.
Related documents
The requirements specification usually comes before the project plan — here is the matching example with Word download.
Obligations with lead time: what many think of too late
These obligations are typically triggered by an ERP implementation (example: Germany). PathHub AI schedules them with lead time, warns when the schedule is too tight and shows the rule with its criteria under “Rule & evidence”, which you tick off and back with evidence. Not legal advice.
Rule & evidence
Why: The new system processes personal data of customers or employees.
- Legal basis for every processing of personal data (consent, contract, legal obligation, legitimate interest)
- Complete record of processing activities (Art. 30) for all processes
- Data Processing Agreements (DPA) with all sub-processors
- Data Protection Impact Assessment (DPIA) for high-risk processing
- Technical and organisational measures (TOM) documented
If breached: Fines up to €20 million or 4% of global annual revenue — whichever is higher. Plus civil damages claims by affected individuals.
Rule & evidence
Why: The provider processes personal data on your behalf (cloud, maintenance, support).
Legal basis: GDPR Art. 28: the contract must be in place before processing starts, including tests with real data or data migration.
- Data Processing Agreement (DPA) with cloud provider
- SLA with availability, RPO, RTO
- Exit and portability clause
- Data localisation and transfer mechanism (SCC / adequacy)
If breached: Civil claims for data loss; recourse depends on contract. GDPR fines for non-compliance.
Rule & evidence
Why: Almost any software logs user actions and is therefore suitable for monitoring performance or behaviour.
Applies: only if a works council exists
Legal basis: Sec. 87(1) No. 6 Works Constitution Act: co-determination for technical systems suitable for monitoring behaviour or performance; suitability is enough. Without agreement the system must not be introduced.
- Enable works council election from 5 eligible employees upward
- Co-determination on working time, monitoring systems, IT rollouts (§87)
- Hearing before every dismissal (§102) — written with reasons
- Balance-of-interests and social plan on operational changes (§111)
If breached: Dismissals without works council hearing are void. Administrative fines up to €10,000 per violation. Criminal liability (§119) for obstructing the works council up to 1 year imprisonment.
Rule & evidence
Why: Tax-relevant data must be retained completely, unalterably and auditably, also after the system change.
Applies: if the system processes accounting or tax-relevant data (ERP, invoices, POS)
- Process documentation for all tax-relevant systems and procedures
- Complete and unalterable records, changes are logged
- Retention of tax-relevant documents for the statutory period (generally 8 or 10 years)
- Data access for tax audits possible (Sec. 147(6) German Fiscal Code)
- Receipt of structured e-invoices (XRechnung, ZUGFeRD) since 1 Jan 2025
- Issuing e-invoices to domestic businesses: from 2027 for prior-year turnover above EUR 800,000, from 2028 generally for all (exceptions incl. small-amount invoices, small businesses)
If breached: Formal defects can lead to the bookkeeping being rejected and the tax base being estimated (Sec. 162 German Fiscal Code); refusing data access can trigger a delay penalty (Sec. 146(2c)).
Frequently asked questions
More project plan examples
Adapt this plan to your company
Open the plan in PathHub — no sign-up. Or describe your own initiative and get a complete plan in minutes.
Open plan →