The fix for a fragmented tool landscape is rarely “replace everything” — it is one platform that owns the core workflow and either integrates or retires the satellites, step by step. That is the approach behind two of our projects at UP2DATE: an auto-service ERP that consolidated quotes, work orders, vehicle files, parts stock, invoicing and reporting — previously spread across separate tools and paper — into 12+ integrated modules, and an internal travel-management platform for PPC, where approvals that used to crawl through email for 3 days now complete in 30 minutes. Here is what actually works, and the two classic ways consolidation projects die.
Why does fragmentation hurt more every year?
Every extra system adds three taxes: a data tax (the same customer exists in four databases, none authoritative), a swivel-chair tax (staff re-typing between tools — the hours nobody budgets), and a licence tax that scales with headcount. The compounding cost, though, is decision latency: when the numbers live in five places, every management question starts with a week of spreadsheet archaeology. If your monthly reporting is a copy-paste ritual, you are already paying for the platform you have not built yet.
The playbook: own the workflow, integrate the edges
1. Map the core workflow first. Not the systems — the flow of work: what enters, who touches it, what leaves. The platform must own that spine end to end.
2. Decide integrate vs. replace per system, coldly. Your accounting package talks to ANAF and works? Integrate it. The scheduling tool that exists because nothing else did? Replace it inside the platform. We routinely keep 2–3 systems of record and absorb the rest.
3. One system becomes the source of truth per entity. Customers live in one place, stock in one place — everything else subscribes. This single rule kills most of the data chaos.
4. Migrate in slices, run in parallel briefly, then cut over. Big-bang cutovers are how consolidation projects make the news for the wrong reasons. One department, one workflow, real data, then expand.
5. Design the integration layer as a product. APIs, queues and error handling that survive a vendor's API change — this is engineering, and it is where senior experience shows.
What kills consolidation projects?
Two things, reliably. Scope theology — trying to model every exception of every department before shipping anything; eighteen months later there is a specification and no platform. And the missing owner — consolidation crosses departments, so without one accountable owner on your side and one on the vendor's (ours: a specialist consultant as single point of contact), every integration becomes a negotiation. The remedy for both is the same: a first production slice within months, expansion by proof.
What does it cost?
Consolidation platforms are custom software with real integration load, so they price at the upper custom range: €80,000–250,000+ depending on the number of systems touched, user roles, and how much historical data has to move. The offsetting math is licence retirement plus recovered hours — in most cases we have seen, the platform pays for itself well before the roadmap ends. Security is non-negotiable at this concentration of data: our delivery process is ISO 27001-certified.
If your operations run on a patchwork of vendors and spreadsheets, this is precisely the work our custom software team does — built by senior engineers, 8+ years of production experience each. Talk to us; bring the list of tools you dream of cancelling.
