For mid-size manufacturing companies in the DACH region, an ERP implementation is often the most significant IT investment of a decade. Done right, it transforms operations — from procurement to production to customer delivery. Done poorly, it disrupts the entire business for months.
At senapsa, we’ve guided more than 200 companies through ERP projects — from initial scoping to successful go-live. This article summarises the five critical phases we rely on, regardless of whether the underlying technology is abas ERP, SAP S/4HANA, or another system.
This framework is designed for IT managers, production directors, and operations leads at manufacturing companies with 50–500 employees who are evaluating or actively planning their first ERP rollout.
Step 1: Define Business Requirements — Before Touching Software
The single most common cause of ERP project failure is insufficient requirements definition. Companies rush into vendor selection before understanding what they actually need the system to do.
A proper requirements phase typically takes 4–8 weeks and involves every department that will be affected by the new system. The output is a structured requirements document that covers:
- Core business processes that must be supported (order-to-cash, procure-to-pay, production planning)
- Integration requirements with existing systems (CRM, warehouse management, e-commerce)
- Reporting and analytics needs across management levels
- Compliance and regulatory requirements specific to your industry
- Non-functional requirements: performance, availability, user count
„Companies that invest four weeks in requirements definition save an average of twelve weeks in rework later in the project.“— Based on senapsa project retrospectives, 2019–2024
Stakeholder Mapping
Requirements definition cannot happen in isolation. Identify all process owners early. In a typical manufacturing company this includes production planning, quality management, purchasing, finance, sales, and IT.
Download our ERP Requirements Checklist
A 47-point checklist used across 200+ senapsa projects. Available as PDF and Excel.
Step 2: Vendor Selection — Fit Over Features
After requirements are defined, vendor selection can begin. Most mid-size manufacturers shortlist 2–4 ERP systems and run structured evaluation processes over 6–10 weeks.
Evaluation Criteria
| Criterion | Weight | What to evaluate |
|---|---|---|
| Functional fit | 30% | Coverage of core business processes without heavy customisation |
| Industry expertise | 20% | Reference customers in your sector, industry-specific modules |
| Implementation partner quality | 20% | Experience, methodology, local presence, post-go-live support |
| TCO over 5 years | 20% | License, implementation, training, maintenance, infrastructure |
| Scalability | 10% | Ability to support international rollout, multi-site, growth |
Selecting the vendor with the most features rather than the best fit. A system with 200 modules that covers 70% of your core processes is worse than a focused system that covers 95%.
Step 3: Data Migration — The Hidden Project Within the Project
Data migration is consistently underestimated in ERP projects. In practice, data cleansing and preparation accounts for 20–30% of total project effort.
- Conduct a full data inventory — what data exists, where it lives, its quality state
- Define migration scope — not all historical data needs to migrate on day one
- Cleanse data in the source system, not in the target
- Run at least three full migration dry-runs before go-live
- Define a rollback procedure in case the cutover fails
We use Apache NiFi and Apache Kafka for high-volume data migrations, allowing real-time validation and transformation pipelines that significantly reduce migration risk.
Struggling with data quality before your ERP migration?
Our data engineers have handled migrations for over 80 manufacturing clients. Book a free 30-minute scoping call.
Step 4: Change Management — The Human Side of ERP
An ERP system is only as effective as the people using it. Change management is consistently the most underinvested area in ERP projects.
Training Architecture
Effective ERP training is role-based, scenario-driven, and delivered close to go-live. Our recommended approach:
- Super-user programme: identify 8–12 internal champions who receive deep system training
- Role-based training: every user receives training only on their relevant processes
- Scenario simulation: training uses real company data and realistic business cases
- Hypercare support: intensive first-line support in the first 4 weeks after go-live
Communication Plan
Regular, transparent communication from project leadership prevents the rumours and resistance that derail ERP projects. A monthly update to all affected employees, plus weekly updates to department heads, is the minimum cadence we recommend.
Step 5: Go-Live Strategy — Phased vs. Big Bang
The go-live approach is one of the most consequential decisions in the project. There is no universally correct answer.
| Approach | Best for | Risk profile | Typical duration |
|---|---|---|---|
| Big Bang | Smaller companies, single-site, tight budget | High short-term, lower total | 1 cutover weekend |
| Phased by module | Complex organisations, large user base | Moderate, spread over time | 3–9 months |
| Phased by site | Multi-site manufacturers | Low per site, manageable | 6–18 months |
| Parallel run | Highly risk-averse, critical operations | Lowest, highest cost | 2–4 months overlap |
At senapsa, we favour phased approaches for clients with more than 100 ERP users or multiple production sites.
Conclusion
A successful ERP implementation is not primarily a technology project — it is a business transformation project with technology as its backbone. The five steps outlined here are not a rigid methodology but a proven framework that can be adapted to your company’s specific context.
The companies that succeed with ERP implementations share three characteristics: they invest adequately in planning, they treat change management as equal in importance to technical implementation, and they choose an implementation partner with genuine industry expertise rather than the lowest bid.
[tags_share]