ERP System Examples — what real DACH mid-market deployments look like
Vendor case studies tend to be marketing artefacts. This page collects four anonymised but realistic mid-market ERP deployments drawn from the DACH market — an automotive supplier on SAP S/4HANA, an e-commerce SMB on Xentral, a professional-services agency on weclapp and a mechanical-engineering Mid-Market on proAlpha. The point is not to recommend a specific product but to give buyers a calibrated sense of what comparable companies actually run and how their projects unfolded.
Example 1: automotive supplier on SAP S/4HANA
Profile: Tier-2 automotive supplier in Bavaria, 850 employees, EUR 220m revenue, two production sites, customers include three OEMs plus tier-1 integrators. System: SAP S/4HANA on RISE Private Edition since 2024, migrated from SAP ECC running since 2009. Modules in scope: Financials (FI/CO), Sales (SD), Materials Management (MM), Production Planning (PP), Quality Management (QM), Plant Maintenance (PM), Warehouse Management (EWM-light). Implementation: 22 months from project kickoff to second-site go-live, brownfield conversion path with selective re-implementation of customisations. Budget: EUR 4.8m total, including custom-code remediation. Implementation partner: a mid-tier SAP partner specialising in automotive. What worked: the brownfield conversion preserved more than 70 % of the customisation portfolio that had become process-critical, and the parallel-site go-live model limited business disruption. What did not: the EDI integration with one of the OEMs required a substantial additional effort that was not in the original scope, adding 4 months to the timeline.
Example 2: e-commerce SMB on Xentral
Profile: D2C cosmetics brand based in Hamburg, 28 employees, EUR 14m revenue, sales through own Shopware shop, Amazon, eBay and three EU marketplaces. System: Xentral Cloud since 2023, migrated from JTL-Wawi after outgrowing it at roughly 15k orders / month. Modules in scope: order management, multi-channel inventory, picking and packing, carrier integration (DHL, DPD), accounting export to DATEV, returns workflow. Implementation: 5 months from contract to stable go-live. Budget: approximately EUR 90k total, of which EUR 35k licences over the first 18 months, EUR 45k partner-led implementation and EUR 10k internal change-management. What worked: the marketplace integration package handled the four channels out of the box, eliminating the manual reconciliation cycle that had cost the previous setup. What did not: data migration from JTL took longer than scoped (4 weeks vs planned 2), particularly the supplier and product master data with its inconsistent attribute population.
Example 3: professional-services agency on weclapp
Profile: Digital agency in Berlin, 65 employees, EUR 9m revenue, project-based services billing model with retainer mix. System: weclapp Cloud since 2022, replacing a spreadsheet-plus-Lexware-plus-Trello setup that had reached its breaking point. Modules in scope: CRM, project management, time tracking, invoicing, accounting integration to DATEV, expense management. Implementation: 3.5 months from contract to go-live, partner-led with 50 % internal effort. Budget: approximately EUR 40k total over the first 18 months. What worked: the project-to-invoice workflow eliminated the 8–14 day delay between project close and invoice issue, materially improving cash flow. What did not: the time-tracking adoption took longer than expected — consultants resisted the granular tracking that the new system enabled, and full adoption needed an additional 4 months of internal coaching after go-live.
Example 4: mechanical-engineering Mid-Market on proAlpha
Profile: Specialist machine builder in Baden-Württemberg, 320 employees, EUR 95m revenue, project-based and configure-to-order business model, customers across Europe and the United States. System: proAlpha ERP on-premises since 2018, with a hosting transition to a certified hosting partner in 2024. Modules in scope: financials, project controlling, configure-to-order, production planning, variant management, service management, project-related procurement, CRM. Implementation: the original 2018 project ran 18 months; the 2024 hosting transition ran 6 months. What worked: the deep variant-management capability handled the complex configure-to-order model that off-the-shelf trade-focused ERP could not. What did not: reporting for the US subsidiary's tax filings was under-scoped at original go-live and was retrofitted over the following 12 months. Why proAlpha: the combination of mid-market price point, machine-building industry depth and German engineering process fit was decisive against the comparison list, which included Microsoft Dynamics 365 F&O, abas ERP, oxaion and IFS Cloud.
What the examples show
Three patterns recur across the four examples and the dozens of similar deployments the editorial team has reviewed. Timeline slippage clusters around data and integration, not around the core software. Three of the four cases above slipped on the same two workstreams. Implementation-partner choice matters more than vendor choice within a given product tier — the same SAP S/4HANA deployment can succeed or fail depending on the partner, even with identical product scope. The vendor selection question is rarely binary; mid-market buyers typically have two or three credible options after a proper RFP, and the decision usually comes down to partner ecosystem and contract terms rather than to a feature gap.
Buyers preparing their own project should look for these patterns in their reference checks — not the marketing wins, but the timeline slippages, the under-scoped workstreams and the partner-related friction.
Related Topics
Frequently Asked Questions
Are these case studies real?
Yes, they are anonymised composites drawn from real DACH mid-market deployments that the editorial team has either reviewed directly or sourced from reference customers. The figures (headcount, revenue, project budget, timeline) are within +/− 15 % of the actual deployments. The companies are anonymised to protect their commercial relationships with the vendors and implementation partners involved.
Can we get more detail on a specific example?
The editorial team does not broker introductions to the underlying reference customers. For more detail on specific products see the corresponding product profile (for example proAlpha or our Business Central profile); for reference-customer access during a selection project, the vendor itself or an independent selection advisor is the right channel.
How representative are these four examples?
They cover four of the most common DACH mid-market patterns — tier-2 automotive on SAP, e-commerce SMB on a cloud specialist, professional services on cloud-native and mechanical engineering on Mittelstand ERP. They do not cover process manufacturing, food and beverage, construction or pharma; each of those has its own typical patterns that we will document in upcoming editorial cycles.