From Fragmented Subsystems to a Single Core
Marabu, the Stuttgart ink maker founded in 1859 and now selling more than 20,000 products across 80 countries, has completed a build that many mid-market manufacturers talk about and few finish: a single global platform for both ERP and customer engagement. The company replaced a sprawl of partly outdated subsystems, accumulated through decades of growth and international expansion, with a standardised stack on Microsoft Dynamics 365, implemented with Hitachi Solutions.
The problem Marabu described will be familiar to any CIO who has inherited an estate built one acquisition and one country at a time. Fragmentation drove up costs, forced manual reconciliation between systems, and left the business with inconsistent data it could not fully trust. We were able to significantly optimise and internationally harmonise our digital business processes, said Marabu chief executive York Boeder, framing the project as harmonisation rather than mere upgrade.
Why Marabu Chose a Unified Suite
The architecture Marabu settled on spans Dynamics 365 Sales and Customer Service on the front office, and Dynamics 365 Finance and Supply Chain on the back office. That pairing matters. Rather than stitching a best-of-breed CRM to a separate ERP through middleware, Marabu chose a single vendor's suite so that customer, order and financial data live in a common model from the outset.
We have long argued that the integration tax is where most transformation budgets quietly disappear. By committing to one platform, Marabu is betting that reduced integration complexity and a single data backbone will outweigh the flexibility it gives up by not picking specialist tools for each function. For a company of Marabu's size, that is usually the right trade: the value is in coherence, not in owning the theoretically best module for every task.
The Phased Rollout Playbook
Marabu did not attempt a big-bang cutover, and that discipline is worth highlighting. The Customer Engagement rollout began in Germany and the United States, while the ERP deployment started in Scandinavia. The company reports that its Customer Engagement layer reached six countries within six months, a brisk pace for a cross-border programme touching sales and service in multiple languages and jurisdictions.
Sequencing by capability and geography lets a team prove the template in one region, capture lessons, then repeat with less risk. It also keeps the business running while the transformation proceeds, which is the entire point. The alternative, flipping every country and every function at once, is how transformation programmes end up as cautionary tales rather than reference customers.
The Systems Integrator Question
No enterprise platform succeeds on licences alone, and Marabu leaned on Hitachi Solutions as its implementation partner. Doris Pauli, account director at Hitachi Solutions, characterised the engagement as one characterised by a clear focus on goals and a pragmatic approach, language that hints at scope discipline being a deliberate choice rather than an accident.
We read the SI selection as the load-bearing decision it usually is. The difference between a Dynamics 365 programme that lands and one that stalls is rarely the software, it is whether the partner keeps the client from over-customising and gold-plating early. Pragmatism, in this context, is not a soft virtue. It is the guardrail that keeps a phased rollout on its timeline and the platform close enough to standard that upgrades stay painless.
What Mid-Market Manufacturers Can Learn
Marabu is not a Fortune 500 name, and that is precisely why its programme is instructive. The mid-market carries a disproportionate share of the fragmented, aging estates that AI and automation initiatives keep colliding with, because you cannot layer intelligent workflows on top of inconsistent data. Marabu's sequence, consolidate the core first, harmonise the data, then unlock the upside, is the unglamorous prerequisite most digital ambitions skip.
The reported outcomes are the familiar ones: higher productivity, fewer errors, faster decisions on better data, and global transparency the old estate could never provide. None of that is revolutionary on its own. What makes it notable is that a 167-year-old manufacturer executed it as a single coherent programme rather than a decade of disconnected projects.
The Suite Versus Best-of-Breed Trade
Marabu's decision reopens a debate every CIO eventually confronts: buy a single vendor's integrated suite, or assemble best-of-breed tools and integrate them. The suite approach that Marabu chose sacrifices some functional depth in any given module, because Dynamics 365 Sales is not going to out-feature a dedicated CRM specialist, nor will its warehouse module match a purpose-built logistics platform. What it buys instead is a shared data model, one support relationship and a predictable upgrade path.
For a mid-market manufacturer with a lean IT function, we think that is almost always the correct call. Best-of-breed rewards organisations large enough to run the integration and vendor-management overhead it demands. For everyone else, the hidden cost of stitching specialist tools together, in middleware, in reconciliation and in the people who maintain both, quietly exceeds the functional gains. Marabu appears to have understood that the coherence of the whole matters more than the sophistication of any part.
The Data Quality Payoff
The most durable win here is the least visible. By moving to one data model, Marabu addressed the inconsistent data quality that had been quietly taxing every decision the business made. Clean, shared master data is the foundation that makes everything downstream, from demand planning to service response, more reliable.
We would frame Marabu's project as a data play wearing an ERP and CRM costume. The productivity and cost numbers are real, but the strategic asset the company actually built is a trustworthy single version of its operational truth. For any CIO weighing whether a suite consolidation is worth the disruption, that is the outcome to keep front of mind, because it is the one that compounds.
