# Merger Workflow Integration Kit — forwardable business brief

For: Integration delivery owners and receiving service teams.

## Work to recognize

A merger or acquired-book transition has a customer workflow or receiving consumer still to connect.

## First useful operating result

Connect or migrate one agreed cohort to its first receiving consumer, preserving the identity, required history and ownership that the workflow depends on.

## What the free reference shows

The insurance-style reference detects a missing historical policy period, two changed cells and one invalid insurer-scoped policyholder relationship. The four investigation groups include overlapping checks. A repaired control clears the supplied scope. A separate shared-defect control catches an invalid relationship even when mapped rows agree.

## Implementation to consider

One policyholder, member or account workflow, one cohort and its first receiving consumer, including the required adapter, mapped data/API path, acceptance, cutover and operating handover.

## Evidence status

Relevant team experience includes application migration and published data-access and observability contributions. The acquired-policy example is synthetic; it is not a completed merger engagement or installed-core certification.

- The local reference uses synthetic insurance policy history; member or account systems need their own semantics and cases.
- It does not connect installed cores, migrate a customer book or certify a vendor platform.
- The reference claims-intake workflow is separate from the historical-record audit; it does not prove a receiving system works.
- Historical completeness, live behavior, authority and customer release approval require separate evidence.