# Dates in a merge: earliest, latest or the primary's? | Dedupely > When two duplicates have different dates, which one should the merged record keep? A field-by-field guide to created, first-touch and last-activity dates. - URL: https://dedupe.ly/blog/duplicates/dates-in-a-merge-earliest-latest - Section: blog - Published: 2026-11-13 - 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) ## Dates in a merge: earliest, latest or the primary's? By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated November 13, 2026 # min read TL;DR - Duplicates often disagree on dates, and each date field needs its own answer. - Dates that mark a beginning, like first contact or customer since, should keep the earliest value. - Dates that mark the latest state, like last activity or last purchase, should keep the newest. - System dates, like created date, usually can't be changed, so the surviving record's value stays. - In Dedupely, you pick the surviving record and set rules per field, like "Newest wins" on a date. Two duplicates almost never agree on their dates. One was created in 2021, the other last month. One shows a last activity yesterday, the other a year ago. One says the customer has been a customer since 2019, the other since 2023. A merge keeps one value per field. Which one is right depends on what the date means. This post covers how to decide, field by field. ### Two kinds of dates **Beginning dates** mark when something started: first contact, first purchase, customer since, original lead date. The earliest value is usually right, because the duplicate was created later and doesn't know the history. **Latest-state dates** mark the most recent event: last activity, last purchase, last email opened. The newest value is usually right, because it reflects what happened most recently. ### Field by field | Date field | Usually keep | Why | | --- | --- | --- | | Created date | The surviving record's | Set by the CRM; often can't be edited | | First contact or original source date | Earliest | The first record knows when it really started | | Customer since | Earliest | A duplicate created later resets the history | | Last activity | Newest | Shows the most recent touch | | Last purchase or order | Newest | Shows the latest buying date | | Next renewal or follow-up | Check by hand | Two different future dates may both be wrong | | Birthday or anniversary | Check by hand | Only one can be right | ### Created date and other system dates Most CRMs set the created date themselves and don't let you edit it. After a merge, the merged record shows the created date of the record that survived. If the earliest created date matters to you, make the oldest record the one that survives. Other system fields, like last modified, change on their own and don't need a rule. Example Say a customer exists twice. Record A was created in 2021 with "Customer since: 2021-03" and a last activity in January. Record B was created by a form last month with "Customer since: 2025-10" and a last activity yesterday. The merged record should keep "Customer since: 2021-03" from A, and "Last activity: yesterday" from B. Keeping record A as the survivor also keeps its 2021 created date. ### When dates need a person Future dates are the risky ones. Two different renewal dates or follow-up dates might mean two contracts, or a mistake on one record. Before a bulk merge, check sets where a renewal or contract date differs, or leave that field to the owner to fix. Pro tip If your reports count new customers by "customer since", a merge that keeps the newer date can move a long-time customer into this month's new-customer number. Check that field on a sample before merging in bulk. ### How Dedupely handles dates In Dedupely, the Primary Record setting decides which record survives, with options like Oldest Record, which keeps the original record and its created date. Field-level Merge Rules then decide each field separately: the suggested rule "Newest wins" keeps the latest date in fields like last activity, and "From the most recently worked record" takes values from the record someone worked on last. Blank values never win, so a date on one record isn't replaced by an empty field on the other. A preview shows the merge result while you build the rules. [Set the right date for each field](https://v2.app.dedupe.ly/signup) ### Each date has its own answer Beginning dates keep the earliest value, latest-state dates keep the newest, system dates follow the surviving record, and future dates that disagree need a person. Set a rule for each date field that matters before you merge in bulk. ### Frequently asked questions #### Which date should win when merging duplicate records? It depends on the field. Keep the earliest value for beginning dates like customer since, and the newest for latest-state dates like last activity. #### What happens to the created date when records merge? Usually the merged record shows the created date of the record that survives. Keep the oldest record as the survivor if the original created date matters. #### Should I keep the newest renewal date? Not automatically. Two different renewal dates may mean two contracts or one mistake. Check those sets by hand. #### What if one record has a date and the other is blank? Keep the date. A blank value shouldn't replace a real one, and in Dedupely blank values never win. #### Why did our new-customer report change after a merge? A merge may have kept a newer "customer since" date. Set that field to keep the earliest value. 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. - [Team Collaboration Who keeps ownership when you merge duplicates? Who keeps ownership when you merge duplicates? Usually the primary record's owner. What each CRM does with it, and how to pick the owner. Gaby Salinas October 30, 2026](https://dedupe.ly/blog/team-collaboration/who-keeps-ownership-when-merging-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) - [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) ### 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)