Post-merger integration

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Design integration before closing

Build a workstream register during diligence. For each change, name the current state, target state, authority, owner, dependency, evidence, client or workforce impact, release test, rollback, and stop condition.

Separate day-one necessities from later improvements. Payroll, safe service delivery, records, emergency routes, access, payer submissions, privacy, and communication need continuity on day one. Brand redesign, optional system consolidation, and broad process optimization can wait.

Keep clinical decisions with qualified roles

Ownership can change governance and resources. It does not transfer clinical judgment to finance, integration software, or deal teams. A qualified clinical leader should review treatment-policy changes, supervision, documentation, risk, and case continuity.

For covered certificants and applicants, the BACB Ethics Code addresses competence, resources, consent and assent when applicable, documentation, confidentiality, supervision, interruption, discontinuation, and transition. BACB has no separate jurisdiction over organizations or corporations, so the organization needs its own accountable controls.

Client and family communication should state what changes, what remains, when it takes effect, whom to contact, and how to raise concerns. Preserve AAC, interpreters, accessibility, and choice.

Integrate payer and billing routes cautiously

Map every entity, tax ID, NPI, provider, location, payer, product, contract, roster, authorization, claim, remittance, and bank relationship. Determine which records continue, which require notice, and which require new approval.

Avoid changing billing identity or submission route before payer evidence supports it. Maintain old and new configurations while older claims, corrections, appeals, refunds, and recoupments remain open. Reconcile cash and remittance separately.

Protect records during system migration

Inventory clinical, billing, workforce, contract, and compliance records. Define legal custodian, permitted access, migration scope, retention, audit trail, corrections, and validation.

For HIPAA covered entities and business associates, HHS risk-analysis guidance covers all ePHI. Integration adds accounts, interfaces, exports, vendors, and temporary copies. Test access, field mapping, authorship, dates, attachments, restoration, and deletion before retiring a source system.

Stabilize the workforce

Tell workers who employs them, when payroll and benefits change, how tenure and leave are treated, who supervises them, which policies apply, and where concerns go. Verify licenses, exclusions, background checks, payer rosters, training, and system access.

Track regretted attrition, vacancies, supervision capacity, payroll errors, access delays, and workload. A synergy target should never depend on staffing below safe or professionally supportable levels.

Sequence facilities and vendors

Confirm lease assignments, occupancy, insurance, accessibility, local permits, utilities, supplies, emergency equipment, and vendor continuity. Shared-services transitions need scope, performance, security, pricing, ownership, and exit terms.

A transition services agreement can keep selected functions operating temporarily. It should never become an indefinite substitute for the buyer’s own authority, staffing, or systems.

Maintain a dependency map. Moving email can affect identity access; changing tax IDs can affect payers and payroll; consolidating vendors can affect records and downtime. Sequence each cutover only after upstream approvals and downstream tests are complete.

Define exit criteria for every temporary arrangement. Track remaining users, data, open claims, tickets, credentials, retained records, and unresolved obligations before shutting it down.

Integration governance should include a decision log. Record who approved each release, what evidence they reviewed, which risks remain, and when the decision expires or returns for review. This history helps later teams explain why sites moved on different dates.

A fictional twenty-workstream plan

Willow Care closes an acquisition with 20 integration workstreams. Fourteen pass their day-30 release tests. Six remain open: two payer configurations, one payroll correction, one record-migration validation, one lease consent, and one backup-AAC inventory.

Day-30 readiness is 14 of 20, or 70%. Willow reports every open item with age and impact. The percentage does not authorize release of a failed item or imply 70% clinical quality.

Services continue only where existing or new authority, staff, records, payer path, access, and safety remain valid. The integration team pauses the affected change rather than forcing a common cutover date.

Measure outcomes without losing the cohort

Track each due workstream from planned date to verified acceptance. Report late items, failed tests, rollbacks, incidents, payroll errors, claim rejects, denials, record mismatches, and unresolved family concerns.

Compare client continuity, family experience, workforce stability, access, supervision, documentation, and financial outcomes before and after integration with explicit cohorts. Acquisition mix and changing denominators can make a simple average misleading.

The SBA growth guide and M&A page provide general transaction orientation. They do not prescribe healthcare integration.

Accept each integration change only after the current owner, future owner, dependencies, test evidence, rollback, communication, and residual risks are documented. A common deadline cannot substitute for release readiness. Keep temporary arrangements active until the successor control works and every retained obligation has an owner.