Driver Management – Merging Duplicate Drivers in Momentum AMS

Driver Management – Merging Duplicate Drivers in Momentum AMS
 Momentum AMS allows users to merge duplicate driver records under the same Insured or Prospect. This tool ensures cleaner data, reduces duplication, and keeps policy, underwriting, and ACORD form information accurate.

Driver merges commonly occur when information is imported from downloads, entered manually by multiple users, or created during quoting. The Merge Driver tool provides a simple, controlled way to consolidate these records.

Why You May Need to Merge Drivers

Duplicate drivers often appear due to:

  • Carrier downloads

  • Data imports or migrations

  • Multi-user entry workflows

  • Quote submissions and renewals

Merging ensures that:

  • Each insured has a clean list of valid drivers

  • Policy rating and forms reflect the correct information

  • Duplicate entries don’t cause errors or confusion


How to Access the Merge Drivers Option

  1. Open the Insured or Prospect record.

  2. Go to Insured Items → Drivers.

  3. Locate the driver entry you want to merge.

  4. Click the Actions dropdown.

  5. Select Merge.


The Merge Drivers Window

After clicking Merge, Momentum AMS displays a comparison window to help you choose which records to combine:

This screen displays:

From Entity (Duplicate Driver to Remove)

→ The record that will be merged into the primary driver.

Into Entity (Primary Driver to Keep)

→ The driver record that will remain after the merge.

Both sides show:

  • First/Last Name

  • Date of Birth

  • SSN

  • Excluded Status

  • Create Contact flag

This allows you to compare details before confirming which record is correct.


Override Information Option

At the bottom of the merge window, you will see:

☑ Override Information

Checking this box allows the system to:

  • Replace the data in the primary driver (“Into Entity”)

  • With the data from the driver being merged (“From Entity”)

Use this if:

  • The duplicate record actually has the correct or more complete information

  • You want to replace missing or outdated details on the primary driver

If you leave this unchecked, the system will:

  • Preserve the primary driver’s existing information

  • Only merge the linked policies and associations


Previewing the Merge

Click Preview Merge to see the final outcome before confirming.

This preview allows you to verify:

  • Which record will remain

  • What information will be carried over

  • Whether any conflicts need manual correction afterward

Once confirmed, Momentum AMS will combine the records and remove the duplicate.


What Happens After the Merge

Momentum AMS automatically:

  • Consolidates all policy links

  • Maintains history and associations

  • Updates driver lists on all policies

  • Removes the duplicate driver entry

Any updated information will flow into:

  • ACORD forms

  • Rating details

  • Quotes and submissions


Limitations & Notes

  • Drivers must belong to the same insured or prospect.

  • Merging cannot be undone — review carefully before confirming.

  • If conflicting information exists (example: different DOB values), choose the correct one before or after the merge.

  • Overrides do not apply to fields that are intentionally blank or system-restricted.


Summary

The Driver Merge tool enables agencies to:

  • Clean up duplicate driver data quickly

  • Maintain accurate underwriting information

  • Reduce errors in rating, policies, and forms

  • Improve overall data quality within Momentum AMS

This enhancement improves speed, accuracy, and data integrity across all workflows involving driver records.


If you'd like, I can now create:
✅ A companion article: “Common Causes of Duplicate Drivers & How to Prevent Them”
✅ A short tutorial script for Momentum University
✅ A version with HTML anchors for your Freshdesk table of contents



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article