# When duplicates disagree on lead status, which one wins? > When two duplicates have different lead statuses, the merge has to pick one. How to rank statuses so the right one wins every time. - URL: https://dedupe.ly/blog/duplicates/duplicates-lead-status-which-wins - Section: blog - Published: 2026-11-09 - 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) [Duplicates](https://dedupe.ly/blog/duplicates) ## When duplicates disagree on lead status, which one wins? By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated November 9, 2026 # min read TL;DR - Duplicates often disagree on status: one says Customer, the other says New Lead. - Keeping the oldest or newest record's value can pick the wrong one. - Rank your statuses so the furthest-along or most important one wins. - Write the ranking down and check it against a few real pairs before merging in bulk. - In Dedupely, Win Rules run from top to bottom, so their order sets which status wins. Two records for the same person, and they disagree. One says the person is a customer. The other, created last week by a form, says they're a new lead. When you merge them, the record can only keep one status. If the merge keeps whatever the oldest record says, or the newest, you'll sometimes get it wrong. A customer marked as a new lead gets prospecting emails. A disqualified lead marked as open goes back into a rep's queue. This post covers how to decide which status wins and how to make that decision the same for every merge. ### Why "oldest" or "newest" isn't enough Most merges pick one record as the primary and keep its values. That works for many fields, but status isn't about age. - **The oldest record** may hold the most history, but its status may be out of date. - **The newest record** is often the one a form or import just created, so it has the default status, like "New." - **The last updated record** may have been touched by an integration that didn't change the status at all. Status is a stage. What matters is how far along the person is, or which status your team acts on. ### Rank your statuses The fix is a ranking: an ordered list where the higher status always wins. A typical ranking for a lead status field: | Rank | Status | Why it wins over the ones below | | --- | --- | --- | | 1 | Customer | They've bought. Everything else is out of date | | 2 | Opportunity / In negotiation | A deal is open | | 3 | Qualified | A rep confirmed interest | | 4 | Contacted | Someone reached out | | 5 | New | The default value most tools set | | 6 | Unqualified / Disqualified | Only wins if nothing else applies | Your ranking depends on how your team works. Some teams put "Do not contact" at the top, because a request to stop contact should never be lost in a merge. Others rank "Disqualified" above "New," so a lead that was ruled out doesn't reappear as fresh. Pro tip Put any status that protects someone, like "Do not contact" or "Unsubscribed," at the very top. Losing it in a merge is worse than losing a sales stage. ### Check the ranking against real pairs Before merging in bulk, pull ten or twenty real duplicate pairs with different statuses. For each one, say which status should win, then check the ranking picks the same one. Where it doesn't, adjust the order. Common surprises: - A status your team stopped using that still sits on old records. - Statuses written slightly differently by different tools ("Customer" and "customer"). - A status that means different things to sales and marketing. [Getting sales, marketing and support to agree on duplicates](https://dedupe.ly/blog/team-collaboration/agree-on-what-counts-as-duplicate) covers how to settle those differences before a cleanup. ### Other fields that need the same treatment Status isn't the only field where a ranking beats "oldest" or "newest." The same approach works for: - **Lifecycle stage**, where some CRMs already keep the furthest stage on merge. - **Lead source**, where you may want the first source to win, not the last. - **Owner**, where the active rep should win over a former employee. - **Priority or tier**, where the highest should win. ### How to rank statuses in Dedupely In Dedupely, Merge Rules let you set field-level rules for any synced field. Custom Win Rules use operators like "is equal to" with the status values you choose, and Win Rules are checked from top to bottom, so their order is your ranking. Lose Rules are checked first, so you can stop a value like "New" from winning unless no other status exists. You can preview the merged result before merging, so you can test the ranking on real pairs first. [Set which status wins in your merges](https://v2.app.dedupe.ly/signup) ### Decide once, merge consistently When duplicates disagree on status, age is a poor tie-breaker. A ranked list of statuses, with the most important one on top, makes the right status win every time. Write the ranking down, test it on real pairs and put protective statuses like "Do not contact" first. Then every merge keeps the status your team would have picked by hand. ### Frequently asked questions #### Which lead status should win when I merge duplicates? The one furthest along or most important to your team, usually Customer, then open opportunity, then qualified. Rank your statuses and let the highest win. #### Why not just keep the newest record's status? The newest record is often created by a form or import with a default status like "New." Keeping it can turn a customer back into a lead. #### What about "Do not contact" or unsubscribed statuses? Put them at the top of your ranking. A request to stop contact should survive every merge. #### Does the same approach work for lifecycle stage? Yes. Rank the stages so the furthest one wins. Some CRMs already do this on their own merge, but check before relying on it. #### How do I test a status ranking? Take ten or twenty real duplicate pairs with different statuses, decide which should win and check the ranking agrees. Adjust the order where it doesn't. 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. - [Duplicates How do I know which duplicate record is the real one? When a contact exists several times, each record holds part of the history. How to pick the right one today, and how merging puts calls and notes on one. Gaby Salinas October 30, 2026](https://dedupe.ly/blog/duplicates/which-duplicate-record-is-the-real-one) - [CRM Organization How duplicate records distort lead scoring Duplicates split one buyer's engagement across records, create false MQLs and delay routing. Merge the obvious ones before you tune lead scoring. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-organization/lead-scoring-duplicates) - [Duplicates Merge CRM records without losing data Field-level merge rules let you control how each value is kept or replaced during a CRM merge. More accurate merges, fewer reviews, and logic you can scale. Gaby Salinas February 12, 2026](https://dedupe.ly/blog/duplicates/merge-crm-records-without-losing-data) ### 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)