Code release vs. policy release — what actually moves.

Transferring a book from one agency to another happens through one of two mechanisms, and the choice shapes everything downstream. Code release transfers the entire producer code — the carrier's unique identifier for the agency — along with every policy written under it. Policy release moves specific policies off one producer code and onto another, policy-by-policy or in batches. The distinction is operational, but getting it wrong can fracture a book, strand renewals, or leave commission routed to entities no longer affiliated with the business — which is why the mechanism belongs in the transaction plan, not the integration afterthought.

§ 01 · Code releaseThe full transfer.

Code release is the mechanism for moving an entire agency code from one entity to another, and it's what happens in most full-agency acquisitions — the existing code is typically terminated and all associated policies move to the acquiring agency's code in a single transaction per carrier. It's administratively efficient: one transaction moves thousands of policies, preserves the commission routing structure, and maintains the existing appointment relationship. But it has constraints. It requires carrier consent, usually formalized in the change-of-control approval, and it's sometimes conditional on the acquiring entity meeting the carrier's appointment requirements. It also moves the entire book uniformly — a buyer who wants to leave specific policies behind can't use code release to do it.

§ 02 · Policy releaseThe selective transfer.

Policy release moves specific policies off one producer code and onto another, typically through a release letter signed by the current producer of record and, where applicable, the client. It's the right tool in three scenarios: when a buyer acquires part of an agency — a carve-out, a producer's personal book, a specific segment — rather than the whole entity; when specific policies need to move to a different appointment after a code release, often because they were originally written elsewhere and never properly transferred; and when a target's policies are being rewritten onto the buyer's existing appointments as post-close consolidation. The administrative cost is materially higher than code release — each policy carries its own paperwork, carriers process releases on their own timelines (typically weeks per batch), and a large book released policy-by-policy can take months. One important corollary: when a producer leaves with their book, the policies move by policy release, because the producer doesn't own a code — the agency does.

§ 03 · The documentationWhat each carrier requires.

The documentation volume isn't trivial. A mid-sized commercial book moved by policy release can require several hundred individual release documents, so the workflow — owners assigned, completion tracked, stale releases escalated — should be built from the day the deal closes rather than discovered policy-by-policy. For commercial accounts, client consent is usually essential; for personal lines, the carrier-specific rules vary.

§ 04 · The deal-structure implicationMap it at the LOI.

Most agency acquisitions of any size are mixed: code release for the main book, policy release for a producer's personal book that's part of the acquisition, and planned post-close policy releases for consolidation. Getting the allocation right is part of the transaction-planning work, not a detail to settle after closing. The purchase agreement should specify which mechanism applies to which segment, and the integration plan should build the workflow to execute each — because the two mechanisms carry opposite risk profiles, and a deal that treats them as interchangeable inherits the worst of both: the consent risk of code release and the integration drag of policy release, with neither planned for.

◆