Merge Duplicate Carriers
Duplicate carriers can occur when data moves or merges between systems, or when users mistakenly add custom Carriers which are already in your Carriers/MGAs list under a different name. Follow the steps below to consolidate duplicate carriers using the Merge Carrier function and keep your setup streamlined. A well-organized carrier setup keeps your policies consistent and makes reporting more accurate.
In order to complete this task, user permissions must be set to include:
Agency Setup > Carrier Setup
Agency Setup > Agency/Office Setup
See User Permissions for more information.
What the Merge Carrier tool does
The Merge Carriers tool allows you to combine two duplicate carrier records into a single, consolidated entry in Carrier/MGA Setup. When you merge carriers, the tool will:
-
Combine carrier details from both carriers (such as LOBs, coverages, programs, states, etc.) into the final merged carrier
-
Give you the option to choose which data and/or settings to keep when there is a conflict between the two carriers and only one carrier's information can be kept (such as the carrier's Display Name, Policy Snapshot Override settings, and Custom Policy Title settings)
-
Reassign all policies from the carrier you are archiving to the carrier you are keeping.
To merge carriers
Merging a carrier cannot be undone. The archived duplicate carrier can be viewed if needed, by selecting "Show Inactive" on the carrier list.
-
Open the
Setup menu, and then select Carrier/MGA Setup.The Carrier/MGA Setup dialog opens in an Agency Setup window.
-
Click the Merge Carriers/MGAs button in the upper right.
The Carrier Merge dialog launches.
-
Select a Primary Carrier/MGA from the drop-down.
The Primary Carrier is the copy of the carrier that will be active at the end of the merge process.
-
Select a Secondary Carrier/MGA from the drop-down.
The Secondary Carrier's information will be merged into the Primary Carrier, and the Secondary Carrier will be archived at the end of the merge process.
A HawkSoft Managed carrier cannot be merged into a custom primary carrier.
-
Click Next.
The dialog proceeds to the next step: Resolve Conflicts. This step enables you to select whether to keep the Primary or the Secondary carrier's settings for certain fields which only accept a single value.
-
Select whether to use all the conflicting information from either the Primary or the Secondary carrier, using the Select All radio buttons at the top.
OR
Select which carrier's unique value to use for each piece of conflicting data individually, using the radio buttons on each row.
Carrier Merge Conflicts
These fields may appear in the list of merge conflicts, and either the value from the Primary or the Secondary carrier must be selected to merge to the final merged carrier. Fields not included on this list will have the information from both the primary and secondary carriers.
Value Merge notes Contact Info > Primary Contact Info > Merge Field HawkSoft adds the contacts from both selected carriers to the final merged carrier.
Conflict: Only one primary contact record per contact type can be designated as the "merge field" for use in correspondence templates.
Contact Info > Addresses > Merge Field HawkSoft adds the addresses from both selected carriers to the final merged carrier.
Conflict: Only one address can be designated as the "merge field" for use in correspondence templates.
Policy Info > Receipt Reference Only one Receipt Reference Number setting can be merged
Conflict: If the two carriers do not have the same value for this setting, select which value to use for the merged carrier.
Policy Info > Receipt Payee Only one Receipt Payee setting can be merged.
Conflict: If the two carriers do not have the same value for this setting, select which value to use for the merged carrier.
Lines of Business > Policy Snapshot Override Only one Policy Snapshot Override setting for a given application type can be merged.
Conflict: If the two carriers do not have the same value for this setting, select which value to use for the merged carrier.
Lines of Business > Custom Policy Titles Only one Custom Policy Title setting, for a given application type, can be merged.
If the carriers are both configured to use custom policy titles, the merged carrier's custom policy title list will contain all the distinct values from both.
Conflict: If the two carriers do not have the same value for this setting, select which carrier's value to use. If the selected value is Use Custom Titles, the primary carrier will contain the custom policy titles from the secondary carrier.
Lines of Business > Automatically Add Default Coverages To Only one setting for default coverages can be applied to each line of business.
Conflict: If the two carriers do not have the same value for this setting for any of the lines of business, select which value to use for the merged carrier.
Lines of Business > Coverage Defaults Only one default Limit or Deductible can be set for a specific coverage.
Conflict: If the two carriers have different carrier-specific default values set for a given coverage's Limits or Deductibles, choose which default to use for the merged carrier.
See Carrier Coverages and Lines of Business for more details on carrier-specific default values for LOB coverages.
-
Click Next.
The dialog proceeds to the next step: Confirmation.
-
Review the information displayed. The selected values from any conflicts are displayed, giving you a preview of what information the merged carrier will contain. If you need to make changes, click Back and re-select your preferred values on any conflicts.
-
Click Confirm Merge if the information looks correct.
The Carrier Merge dialog closes, and a pop-up message confirms that the merge was successful.
Now that the carrier merge is complete, the information selected has been consolidated onto the Primary Carrier, and the Secondary Carrier is inactive. In addition, all policies that were previously associated with the Secondary Carrier are now associated with the Primary Carrier. The secondary carrier will no longer be found on any clients or policies.