Overview
Branch Management is where you clean up your organization when the same license number (NPN) has ended up on more than one branch. It lists every NPN that is duplicated across your branches and walks you through merging the extra branch into the one you want to keep, so all of your users, agents, contacts, documents, licenses, and appointments live on a single record.
What is Branch Management?
When two branches in your organization carry the same NPN, your compliance picture is split across duplicate records: licenses on one, appointments on the other, contacts in both. Branch Management surfaces those duplicates and lets you consolidate them into one branch in a single guided flow, so you stop maintaining the same entity twice.
Who uses it. A licensing or compliance manager (or an agency owner) who notices that the same agency appears twice in their org structure, usually after onboarding the same legal entity through two different paths. This is an organization-structure cleanup task, not a day-to-day workflow.
You use Branch Management to:
See every NPN that is shared by two or more branches in your organization, and how many branches share each one.
Choose which branch survives (the target) and which branch is absorbed into it (the source).
Move all users, agents, contacts, documents, licenses, appointments, and market relationships from the source branch onto the target branch in one step.
Resolve conflicts safely, such as two agents that share the same NPN or two copies of a W9, by picking exactly which record to keep.
Permanently retire the duplicate branch once everything has moved.
Note: Branch Management is a premium feature. If you do not see the Merge Duplicate NPN button described below, the feature is not enabled for your organization. Contact our support team to turn it on.
Accessing Branch Management
Branch Management does not have its own item in the left sidebar. You reach it from your organization settings:
In the left sidebar, click Settings (the gear icon at the bottom of the navigation).
In the Settings panel, open Org Structure.
Click the Merge Duplicate NPN button (top-right of the Org Structure page, next to Add New Agency).
This opens the Branch Management page, which lists the duplicate NPNs found in your organization.
What's visible on the page
The page shows one row per NPN that is shared by more than one branch.
Column | Description |
NPN | The National Producer Number that is duplicated across branches. |
Legal Name | The legal name on the first branch in the group. Shows |
Branch Names | The branch names of every entity that shares this NPN, shown as separate tags. |
Duplicates | A count pill showing how many branches share this NPN, for example |
If your organization has no duplicates, the page shows the message "No duplicate NPNs found" with the note that all branches have unique NPNs. In that case there is nothing to merge.
To start a merge, click any row in the table. This opens the Merge Duplicate Branches wizard for that NPN.
Merging Duplicate Branches
When you'd do this. You have found two branches that represent the same licensed entity and share one NPN, and you want to collapse them into a single branch so your compliance data is no longer split.
Clicking a row opens a five-step wizard. Your progress is saved automatically as you go, so you can leave and come back to the same NPN without losing your selections.
Warning: Merging is permanent and cannot be undone. When you complete the merge, the source branch is deleted and all of its data is moved onto the target branch. Confirm your target and source choices carefully before the final step.
Step 1: Overview (choose target and source)
Each branch that shares the NPN appears as a card. For each branch you can pick a role:
Select as Target sets the branch that will remain after the merge. All data is moved onto this branch.
Select as Source sets the branch that will be merged into the target and then deleted.
The summary banner at the top shows your current Source Branch and Target Branch selections. You cannot proceed until both are chosen.
Some branches cannot take a role, and the card explains why:
A branch that has child branches (a parent, shown with the TopCo badge) shows Cannot be Source. Only branches without children can be merged away. Merge or remove the child branches first.
A branch that has not finished identity verification shows Cannot be Target. That branch must complete its onboarding identity step before it can receive merged data.
Step 2: Users
All users from both branches are moved onto the target branch. No action is required here. The step lists the members from each branch (with the Target and Source tags and each member's email and roles) so you can review who will be carried over.
If the same person exists on both branches (matched by email), their roles are combined onto a single user. Anyone with a pending invitation is activated as part of the move.
Step 3: Contacts
All contacts from both branches are merged, and contacts with the same email are combined into one. Contacts that exist on both branches appear under a Shared Contacts heading with an In Both Branches tag; contacts unique to one branch are listed under that branch.
You must choose a Primary Contact before continuing. Click Set as Primary on the contact that should be the main point of contact for the merged branch. The chosen contact is highlighted and labeled Primary Contact. If neither branch has any contacts, you can proceed without selecting one.
Step 4: Agents
All agents from both branches are merged onto the target branch. Agents that exist on only one branch (or have no NPN conflict) move over automatically and are marked Will be merged.
When two agents share the same NPN, that is a conflict you must resolve. Each conflict is grouped under its NPN, and you click Select on the one agent to keep for that NPN. A group shows a Resolved tag once you have made a choice. You cannot complete the merge until every NPN conflict is resolved.
Step 5: Documents
All documents from both branches are merged. For most document types this happens automatically and the documents are marked to be kept.
Four document categories can only have one document per organization: W9, E&O, Cyber, and Crime & Fidelity. If both branches hold a document in one of these categories, that is a conflict. For each conflicting category, select which document to keep. You can use the view and download controls to inspect each document before choosing. A category shows a Resolved tag once you have chosen. You cannot complete the merge until every document conflict is resolved.
Completing the merge
When you reach the final step and all conflicts are resolved, click Complete Merge. Turris moves every record from the source branch to the target branch (users, agents, contacts, documents, licenses, appointments, market relationships, corporate registrations, and NIPR subscriptions), then permanently deletes the source branch. You are returned to the Branch Management list, and the activated members on the former source branch receive an email letting them know their account has moved.
Filtering and Searching
This page has no filter dropdowns or status toggles. It has a single search box above the table.
The search box matches against the NPN, Legal Name, and Branch Names columns. Typing part of a branch name or a legal name narrows the list to matching duplicate groups, and typing digits of an NPN finds that specific group.
Status and Visual Elements
The branch cards and conflict steps use tags to show the state of each item and what is expected of you.
Tag | Where it appears | Meaning | What to do about it |
TopCo | Branch card (Step 1) | This branch is a parent with child branches. | It can be a target, but it cannot be a source. To retire it, merge or remove its child branches first. |
Target (blue) | Branch card and review steps | This is the branch that will remain after the merge. | Confirm this is the branch you want to keep. All data moves here. |
Source (green) | Branch card and review steps | This is the branch that will be absorbed and then deleted. | Confirm this is the branch you want to retire. It will be permanently removed. |
Cannot be Source | Branch card (Step 1) | The branch has child branches, so it cannot be merged away. | Merge or remove its child branches first, then return to this merge. |
Cannot be Target | Branch card (Step 1) | The branch has not finished identity verification. | Complete that branch's onboarding identity step, then select it as target. |
In Both Branches | Shared Contacts (Step 3) | This contact exists on both branches and will be combined. | Review the combined roles, and decide whether this should be the primary contact. |
Resolved (green) | Agent and document conflicts (Steps 4 and 5) | You have chosen which record to keep for this conflict. | None. The conflict is settled. Groups without this tag still need a choice. |
Frequently Asked Questions
Can I undo a merge after it completes? No. The merge is permanent and the source branch is deleted. There is no automatic way to split the branches back apart, so confirm your target and source choices before clicking Complete Merge.
Why can't I select a branch as the source? The branch has child branches under it (it carries the TopCo badge). Only branches with no children can be merged away. Merge or remove the child branches first, then come back.
Why can't I select a branch as the target? The branch has not finished identity verification. Complete that branch's onboarding identity step, and it will become selectable as a target.
What happens to the users and agents on the source branch? They are moved onto the target branch. Duplicate users (same email) have their roles combined, and pending invitations are activated. For agents that share an NPN, you choose which one to keep in Step 4.
Two of my documents are in the same category. Why do I have to choose one? W9, E&O, Cyber, and Crime & Fidelity documents are limited to one per organization. When both branches hold one, you select which document to keep so the target branch ends up with a single, correct file.
Will the people on the source branch know it moved? Yes. Admin, legal, and compliance members of the source branch receive an email letting them know their account has been activated on the target branch.
Best Practices
Confirm the direction before you finish. The target survives and the source is deleted. Re-read the summary banner so you do not accidentally keep the wrong branch.
Resolve every conflict deliberately. When two agents share an NPN, or two documents share a restricted category, pick the record with the most complete and current information. The unselected records are discarded.
Merge from the bottom of the hierarchy up. A parent branch cannot be a source while it still has children. If you need to retire a parent, merge or move its child branches first.
Choose the right primary contact. The primary contact you set in Step 3 becomes the main point of contact for the merged branch, so pick the person who should own that relationship going forward.
Treat this as a one-time cleanup, not routine maintenance. Because the merge is irreversible, only run it when you are certain the two branches are genuinely the same entity.
Need Help?
If you have questions about Branch Management or encounter any issues, contact our support team at support@turris.com.