# Protect fields when merging duplicates in Pipedrive with Dedupely > Control which fields survive a merge in Pipedrive with Merge Rules, so a bulk cleanup keeps the values your team depends on and drops only the duplicates. - URL: https://dedupe.ly/blog/pipedrive/protect-fields-in-pipedrive-with-dedupely - Section: blog - Published: 2025-10-01 - Site index: https://dedupe.ly/llms.txt - Any page: append `.md` to its URL for this plain-text form --- Skip to content [New Dedupely Intelligence Now on every paid plan, monthly or yearly.](https://dedupe.ly/ai-deduplication) [Blog](https://dedupe.ly/blog) [Pipedrive](https://dedupe.ly/blog/pipedrive) ## Protect fields when merging duplicates in Pipedrive with Dedupely Control which fields survive a merge in Pipedrive using Dedupely's merge rules. Published October 1, 2025 # min read Merging duplicates in Pipedrive can seem straightforward: You run a scan, select the match options, and complete the merge. But what happens to the data in each field is not always clear - without configuration, the wrong values can be kept, and important updates can be lost. This article explains how Pipedrive handles merge logic by default, what risks that introduces, and how to control exactly which field values are preserved using Dedupely’s field rules. ### Pipedrive merges into the oldest record by default Pipedrive’s default behavior is to keep the oldest record in a duplicate group. That means: - The system keeps the field values from the record with the earliest creation date - Fields in newer records are ignored unless the older record has that field empty - There is no automatic comparison of field quality, completeness, or recency This behavior affects every merge unless you use field rules. If two records have different owners, addresses, or names, Pipedrive keeps whatever was on the oldest one. ### What breaks when field-level data is not protected Leaving field control to defaults creates a risk of silent data loss. Teams often discover the consequences only after workflows fail or manual corrections are required. Common issues include: - An older, outdated one replaces a valid address - A placeholder owner overwrites the correct owner - An empty phone field overrides a populated one - Lead routing or reporting fails due to missing or incorrect values Because the merge completes without warning, these errors are difficult to trace. The record looks clean, but it contains the wrong information. ### Use Dedupely field rules to control what gets kept Dedupely allows you to apply specific merge rules to any field you care about; they ensure that the most relevant, accurate, or recent data survives the merge. Each rule lets you define: - Which field to control - What condition should be used to decide the winning value - Which values wins based on that condition The rest of the fields follow Pipedrive’s default logic unless you define rules for them. This makes it easy to protect what matters without overcomplicating every merge. On every paid plan, Dedupely Intelligence also lets you set Protected fields. ### Copyable Dedupely rule setups that work in Pipedrive You can apply these rule patterns directly in Dedupely: They work with any Pipedrive setup and are used by many teams managing live data: **1. Address** - Keep the address from the record with the most recent activity date - Within my PEOPLE, I want the ADDRESS to WIN IF/WHEN LAST ACTIVITY DATE is LATEST **2. Owner** - Keep the owner from the record with the most associated deals - Within my DEALS, I want the OWNER to WIN IF/WHEN OWNER is equal to [NAME] **3. Name** - Keep the name from the most recently created record - Within my LEADS, I want the CREATE DATE to LOSE IF/WHEN CREATED DATE is LATEST These rules can be tested before syncing: You can run a scan based on your match options, merge a couple of resulting duplicate records, and review the outcome. ### When the default logic is good enough You do not need field-level merge rules for every merge. In some cases, records are aligned, and the data is consistent across duplicates, if: - All fields are the same across records - You trust the oldest record to have the correct values - There is no significant difference between field data Then the default logic will produce acceptable results. But if a field has business impact, such as routing, ownership, or contact information, it is worth applying a rule. Pipedrive merges are fast, but they may not be context-aware. Without merge rules, the wrong data can be kept just because it existed earlier. Dedupely’s merge rules let you decide which field values win or lose. If you manage important data in Pipedrive, merge rules are the simplest way to keep your system accurate after every deduplication. [Book a Zoom with our team to set specific merge rules for your Pipedrive here.](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler) Behind the article ### Gaby Salinas Marketing Assistant at Dedupely Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start. As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes. [Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns) ### Contact us We’d be happy to help you get this set up. #### Write us a message We probably know the answer to your question already help@dedupe.ly Email copied to your clipboard! [Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler) ### Discover Related Blog Posts Stay updated with our latest articles and insights. - [Pipedrive How to choose which fields to match duplicates on in Pipedrive Choosing the right fields determines how duplicates are identified in Pipedrive. This guide explains how to configure field-based matching logic using search. Gaby Salinas February 24, 2026](https://dedupe.ly/blog/pipedrive/choose-fields-to-match-in-pipedrive) - [Pipedrive Protect fields when merging duplicates in Pipedrive with Dedupely Control which fields survive a merge in Pipedrive using Dedupely's merge rules. Gaby Salinas October 1, 2025](https://dedupe.ly/blog/pipedrive/protect-fields-in-pipedrive-with-dedupely) - [Pipedrive What happens when you merge in Dedupely for Pipedrive What a Dedupely merge does in Pipedrive: which values win, how emails and phones combine, what moves to the surviving record and what can't merge. Gaby Salinas October 28, 2026](https://dedupe.ly/blog/pipedrive/deduping-pipedrive-with-dedupely) [See all](https://dedupe.ly/blog) ### Get started for free 20 free trial merges and as much free support as you need to get your duplicates under control. [Try for free](https://v2.app.dedupe.ly/signup)[Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales) [Or sign up with Google](https://v2.app.dedupe.ly/signup/google) Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)