Data Platform & Integration
Consolidating overlapping integration stacks
A North American insurer
Years of acquisitions had left the insurer running several integration stacks side by side. The same policy data moved between the same two systems by three different routes, each built by a different team, none of them documented in a way the others trusted.
Why it mattered
The cost was not the licences. It was that no one could say with confidence which pipeline was authoritative, so every downstream question about a number turned into an archaeology exercise. Change requests were priced for the risk of breaking something invisible.
The Pawa approach
Mapped what actually ran before proposing what should replace it, including the jobs everyone assumed were dead. Consolidation was sequenced by business risk rather than by technical convenience, so the flows feeding regulatory and financial reporting moved last, once the pattern had been proven on lower-stakes data.
What was built
- Full inventory of running integration jobs, with the consumers of each output identified
- A single ingestion pattern defined once and applied per source, rather than per project
- Parallel run for each migrated flow, with output compared against the pipeline it replaced
- Decommissioning treated as a delivery step with its own sign-off, not as cleanup
Delivered capability
One documented way to bring a new source in, and one answer to which pipeline owns a given feed.
Outcome
The duplicate routes were retired rather than left running alongside their replacements, which is the usual failure mode of a consolidation. Onboarding a new source became a known pattern instead of a project.
This engagement was delivered by our principal during fifteen years at Informatica, before PaWa Data Solutions. It is professional background, not this firm's client work. The client is not identified, and no quantitative outcome is claimed.
Related solutions
Not sure which one you need?
That is what the Data Health Check is for. Two to three weeks, and you leave knowing what to fix and in what order — whether or not you work with us.
Book a Data Health Check