Less disruption to sales
Most of the work happens in the integration layer, so your team can stay focused on customers as much as possible.
Acquisition or merger
Two ERPs, two webshops, two teams, one organisation. We help you bring the systems together while keeping disruption to sales to a minimum.
Sound familiar?
Often a parent company drives the acquisition. In a merger, both parties set the course together. Either way, the expectation is clear: lower costs from shared systems, more revenue from combined channels. On paper, it adds up.
Then the real work begins. Two ERPs, each with its own item codes, customers and pricing agreements. Webshops and EDI links wired into the old system. And a team that has to rebuild it all on top of the day job.
Where it goes wrong
The instinct is to standardise straight away: one system, one way of working, new people in charge. That puts pressure on a team that still has customers to serve. Knowledge walks out of the door, attention goes to the rebuild, and sales pay the price.
A real example
After an acquisition in the two-wheeler industry, a great deal was rebuilt at once, by new people, while the existing team had to keep up with it on top of the day job. Revenue fell instead of rising, and the IT got worse rather than better. In the end, the business was sold back to its original owners.
We connect both landscapes to the integration platform, with PLGGR | HUB from our partner PLGGR as the central integration layer. The two businesses can work together, and you only merge what clearly works better.
Which systems, integrations and data flows are there, and which of them carry the revenue? That tells you what must keep running.
Both ERPs and the main channels connect to the platform, so orders, stock and customer data can move between the two businesses without rebuilding everything first.
System by system, when the team is ready. Because the channels are connected to the platform rather than to the system being retired, you can replace systems one at a time.
Because the data from both businesses runs through one integration layer, you can put the figures side by side and see whether the business case holds up, in revenue rather than project hours.
Most of the work happens in the integration layer, so your team can stay focused on customers as much as possible.
No big-bang switchover under time pressure. The knowledge of the people behind the systems stays in the business while the landscape comes together step by step.
Reliable data from both businesses, as the basis for the figures for the board and the parent company.
No. Through the integration platform, two ERPs can work side by side. You then decide whether and when to merge, based on what it delivers.
That depends on the landscape. With more than 150 integrations in the integration layer, you rarely start from scratch. In our first conversation, we estimate how long it will take in your situation.
They connect to the integration platform instead of the old ERP. If that ERP is retired later, the channels stay connected to the platform; the work is mainly in connecting the new system.
That is where it pays off most. Each new business connects to the same platform, so a second or third acquisition builds on what is already in place.