Merging duplicate Keap contacts safely requires three things before you touch the merge button: a CSV backup of both records, a designated primary (golden) record, and manual transfer of any unique data sitting only in the secondary record. Skip any of these steps and Keap’s merge permanently overwrites fields you cannot recover.

Step 1: Understand the Risks Before You Touch Anything

Keap’s merge is a one-way door. Once you execute it, the secondary contact record is deleted and its data either merges into the primary or disappears – there is no native undo. The risks go beyond a missing field: notes, task associations, order history, campaign tags, and custom field values from the wrong record can all be silently overwritten if you do not control which record wins at each field.

Start with Keap’s built-in duplicate detection under Contacts. It surfaces matches based on email address and name. Use it as a starting point, not a final list. Partial matches – nicknames, maiden names, old email addresses, alternate phone numbers – require a manual review pass before you merge anything.

Step 2: Choose Your Golden Record

The golden record is the contact that survives the merge as your single source of truth, and the decision deserves more than a quick guess before you open the merge screen.

Review all associated data for each duplicate: order history, communication logs, campaign tags, custom field values, and engagement scores. The golden record should be the most complete, most active, or most historically significant entry. In most cases, that is the contact with the longer activity timeline or the most recent purchase record. Write down which record you are designating as primary before you open the merge interface – once you are inside it, the clock is running.

For a closer look at which contact fields carry the most risk if overwritten, see 11 Indispensable Keap Contact Fields to Safeguard and Swiftly Restore.

Step 3: Back Up Both Records Before Merging

Export both contacts to CSV before initiating any merge in Keap – this is your one-year undo if anything goes wrong.

Filter for the two records you intend to merge and export the full contact list including all custom fields. Store that file somewhere you can access immediately if you need to rebuild a record manually. Keap maintains internal versioning, but a local CSV export is faster to reference and does not depend on support response time.

Beyond the export, do a manual data review pass on the secondary record before the merge. Identify any unique information sitting only in that record – a note, a custom field value, a tag – that Keap will not automatically carry over. Copy those values into the golden record first. The merge screen gives you field-level choices, but loading the golden record up front is faster and safer than making judgment calls under pressure at the merge interface.

Step 4: Execute the Merge in Keap

Keap’s manual merge gives you a side-by-side field comparison before anything is written – use it deliberately, not as a formality.

Open one of the duplicate contact records. Under the Actions menu (or the contact’s detail tab, depending on your Keap version), locate “Merge Contact” and select the golden record as your target. Keap presents a field-by-field comparison where you choose which value wins for each data point. Take this screen seriously. Default to the golden record’s data, but watch for secondary-record fields that carry more recent or more complete information.

For large-scale duplicate issues across hundreds of contacts, the manual approach does not scale. A Make.com scenario that calls the Keap API can automate detection and flag records for review before queuing them for merge – without writing anything until a human approves the batch. That is the right path when you are dealing with a systematic duplicate problem rather than a one-off cleanup.

Expert Take

The merge interface feels low-stakes because it looks like a form. It is not. Every field choice you make at that screen is permanent. The teams that handle this well have a written merge protocol before they open it – which record type is always primary, which fields always defer to the most recent value, which fields always defer to the oldest. The person executing the merge follows a rule, not a judgment call under pressure.

Step 5: Verify the Merged Record Immediately

Open the merged contact the moment the merge completes and audit it field by field – do not wait until a problem surfaces downstream.

Check every critical field: name, email, phone, custom fields, tags, order history, notes, and task associations. Confirm that activities and engagement history from both records now appear under the surviving contact. Then review your active automations: any campaign, sequence, or Make.com scenario that was triggered by or linked to the now-deleted contact record needs verification that it is still running correctly. A merged contact can fall out of a sequence mid-flow if the automation was watching the secondary record’s ID rather than the tag or email address.

Log what you verified and when. If a problem surfaces a week later, that log tells you whether the issue predated or postdated the merge.

Step 6: Lock Down Your Intake Process to Stop Future Duplicates

The fastest way to eliminate duplicate cleanup work is to prevent duplicates from entering Keap in the first place.

Three changes make the biggest difference. First, standardize how names and email addresses are formatted on every intake form – inconsistent capitalization and spacing are the primary reason Keap’s duplicate detection misses records it should catch. Second, enable duplicate detection rules on every Keap form that feeds your contact database. Third, build a Make.com scenario that checks for an existing contact by email address before creating a new record from any external source – a webinar platform, a job board, an inbound form. If a match exists, update the record. If it does not, create one. That single check eliminates the majority of system-generated duplicates before they ever reach your database.

For a broader look at protecting your Keap data across the full contact lifecycle, 10 Essential Strategies for Protecting Your Keap CRM Data in HR Recruiting covers the prevention stack end to end. And if you want to cross-check your merge results against a recovery checklist, 11 Essential Checks to Restore Keap Contacts Without Headaches walks through the verification steps in detail.