There will be no proALPHA version 9.6. The announcement was made on 11 June 2026 at the Sommertagung of the Anwenderkreis proALPHA (AWK) in Frankenthal, by Otmar Zewald representing the vendor (AWK Sommertagung 2026 programme). The German ERP vendor is pivoting to a cadenced release model, abandoning the major version cycle that has historically structured upgrade projects for its mid-market manufacturing customers.
Context: The AWK, Voice of 500 Mittelstand Members
The Anwenderkreis proALPHA is the proALPHA user association. With more than 500 member companies drawn primarily from German industrial Mittelstand, it is the main dialogue channel between the vendor and its installed base. The session titled “ERP-Roadmap: Warum es keine Version 9.6 geben wird” (“Why there will be no version 9.6”) appeared on the agenda of the 11 June general assembly, in the “AWK and proALPHA News” block.
The event coincides with a leadership transition within the AWK itself. Thomas Schmidt, who had led the association for 8 years and helped grow it from a few dozen to 500+ members, handed over on 1 June 2026 to two co-directors: Christoph Schott (MBA ESC Grenoble, 10+ years in business development) and Uwe Siegwart (master’s in IT management, former IT director of the Schlote Group). Schmidt remains an advisor until 30 September 2026 (presse-control.de, 1 June 2026).
What This Means in Practice for Mid-Market Manufacturers
The end of major versioning is the end of the “version upgrade project.” Until now, proALPHA customers planned a major upgrade project every two to three years: impact analysis, regression testing, user training, scope freeze during critical phases. This cycle generates recurring service costs and ties up internal IT teams for months at a time.
The shift to continuous releases changes the logic entirely: features and fixes arrive in small increments on a regular cadence. The model mirrors what SAP has progressively introduced with S/4HANA Cloud and the Business Technology Platform (BTP) — no fixed version, but a continuous stream of weekly or monthly updates without major breaks.
For an IT director at an industrial mid-market company, three adjustments need to be anticipated. First, current maintenance contracts are negotiated around a known versioning cycle — the new delivery model must be checked against existing contract terms. Second, IT teams must shift from episodic project management (the V9.5 to V9.6 project) to continuous update management, embedding regression testing into day-to-day operations. Third, customisations — bespoke developments and third-party integrations — represent the real risk factor: in a continuous delivery model, each release can break an unmaintained customisation.
What to Watch
proALPHA has not yet published technical documentation detailing the timeline of the new model or its contractual implications. The next expected step is the publication of an official roadmap for customers, likely in the weeks following the Sommertagung. Certified proALPHA resellers and implementation partners (primarily in the DACH region) should receive a briefing ahead of customer communications.
The trend extends well beyond proALPHA. Infor CloudSuite, Microsoft Dynamics 365 Business Central, and Sage X3 have all, at varying paces, migrated to continuous deployment models. For mid-market companies maintaining heavily customised configurations on on-premise ERP platforms, the pressure toward cloud delivery will intensify over the next 24 to 36 months.
To dig deeper, read our complete guide to choosing between cloud and on-premise ERP and our 7-step methodology for a painless ERP migration.
