

The customer's challenge
The customer's challenge
The company, which had about 10,000 employees when the project was to begin, acquired a competitor with 6,000 employees. Suddenly, the strategic decision to change the old ERP system to a common one became a much bigger and more complex issue. Two different groups were to be merged, but obviously had different governance, processes and business rules.
System before/after
System before/after
The acquiring company had largely Visma PX in the Nordic region and a little mixed in its other European operations. The acquired company had chosen a few years earlier to integrate all its 30 countries into Maconomy. The decision that was now on the table was to move everyone to the ERP system Maconomy or IFS, to the HR system SuccessFactors and to the CRM system Salesforce or Lime.
Solution
Solution
The client's management chose to follow our recommendation to develop a common operational model for the management team to decide on. This was not without challenges because the operational model goes to the heart of how the business should work. But must be done to create stability for a future system change. The operational model becomes a base plate for a system configuration.
Result
Result
After a number of iterations, and some power play between divisional managers and functional managers, we came out the other side in one piece with an agreed operational model that the future business system project could use as a starting point.
Conclusions
Conclusions
Change management starts at the top, and getting the management team to agree on how a company should operate is crucial to getting a major project like changing the ERP system for 16,000 employees off to a good start. Part of the success is that the company's CFO was very well informed and committed to pushing the decisions through the management team. When you change most administrative processes in a company, it is not an "IT project".