triggers-for-ERP-projects1The age of the ERP software used is still by far the most dominating trigger for the implementation of a new ERP. However, this aspect has lost some of its relevance in the course of the last 10 years or so (since 2000 -20.7 %, finishing at 31.2% in 2012). Instead, the implementation of a new ERP Software is increasingly triggered by the companies‘ dissatisfaction with their ERP software or the ERP vendor (2010: 17.3%, increase: 8.1%). This aspect is especially relevant for smaller companies and for service providers and comes in second in the top 10 triggers for ERP projects. Another frequently mentioned trigger is the fact that the used ERP infra tructure cannot fulfill all of the new requirements originating from changed business processes or a changed business orientation. Other aspects are less important or only relevant for selected market segments: Larger companies (>500 employees), for example, exchange their own developed systems for standard ERP software. This trend shows that standard ERP software has matured so far so as to make the expenses for the maintenance of individual solutions unnecessary. Production companies often stated that the system they had been using respectively their former ERP supplier are no longer on the market. Migration, caused by a changed maintenance contract, has increased significantly over the last 10 years.