# What to do before your first merge in a CRM | Dedupely > The first merge is the hardest one to start. Set your matching criteria, decide what the merged record keeps and preview the result before you merge. - URL: https://dedupe.ly/blog/before-your-first-crm-merge - Section: blog - Published: 2026-10-20 - Site index: https://dedupe.ly/llms.txt - Any page: append `.md` to its URL for this plain-text form --- [Blog](https://dedupe.ly/blog) CRM Organization ## What to do before your first merge in a CRM By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated October 20, 2026 # min read TL;DR - The first merge is often the hardest step of a CRM cleanup to start. - Write down what counts as a duplicate for each object before building any search. - Check a sample of matches, including the largest sets, before trusting a search. - Preview the merged record to see which values and owner survive the merge. - Dedupely lets you set matching criteria, choose which values win and preview each merge. Most teams get as far as finding their duplicates and then stop. The search is built, the matches are on the screen, and nobody wants to be the one who clicks merge. The first merge is the scary part. That pause makes sense, since a merge changes records the whole company uses. The way past it is to settle the open questions before the merge, so the click itself is the easy part. In this post, you'll see what to decide before your first merge. That covers what counts as a duplicate, your matching criteria and how to check the results. You'll also see how to decide what the merged record keeps and how to preview it. ### Why the first merge is the biggest step Finding duplicates changes nothing in your CRM. Merging does. Two or more records become one, and the values that lose are gone from the record. The first merge also sets the pattern for every merge after it. If the criteria hold up on the first sets, the next thousand follow the same logic. If they don't, you'd rather find out on ten sets than on ten thousand. So the work before the first merge comes down to two questions. Are these records really duplicates? And what should the record look like after the merge? ### Decide what counts as a duplicate What counts as a duplicate is case by case. What one team considers a duplicate, another may not. Two offices of one company can be one account for marketing and two territories for sales. Write the answer down for each object you plan to clean, like contacts, companies or deals. A short list is enough: - A few sets you know are duplicates, like two contacts with the same email. - A few sets you know aren't, like two branches that share a domain. - The cases you aren't sure about, and who on the team can decide them. Those known sets become your test. A good search finds the first group and leaves the second alone. ### Set your matching criteria Matching criteria decide which records pair up. Start with the field that identifies each record, like email for contacts or domain for companies. Then add fields that confirm the match, like name or company. #### Combine a few strong fields One field on its own rarely proves two records are the same. Two to four fields that agree make a much stronger match. Our guide on [which fields to match on](https://dedupe.ly/blog/which-fields-to-match-on-crm-duplicates) covers combinations for each object. #### Choose how strict each field is An exact match on email is safe but misses typos. A looser match on name catches "Jon" and "John" but can also pair two different people. Use looser comparisons only on fields that another field confirms. #### Leave unreliable fields out Some fields look useful but mislead. Shared inboxes like info@, placeholder values like 000-000-0000 and fields that most records leave blank can group records that have nothing in common. #### Start with the obvious duplicates Your first search should find the duplicates nobody would argue about. Exact matches on email or domain are a good start. Looser criteria can come later, once the first merges have gone well. ### Check the results before you trust them A search can look right and still pair the wrong records. Before you decide what the merged record keeps, look at what the search found. - **Count the matches and the records in them.** A search with far more matches than you expected is often too loose. - **Open the largest sets.** A set with dozens of records is usually a placeholder value or a shared inbox, rarely one customer. - **Look for your known sets.** Check that the duplicates you listed show up and the pairs you know aren't duplicates don't. - **Read a random sample.** Ten or twenty sets from the middle of the list tell you more than the first page. When you're certain a set isn't a duplicate, reject the match so it doesn't come back. When a whole type of set is wrong, change the criteria instead and run the search again. ### Decide what the merged record keeps Once you trust the matches, the next question is the outcome. Every merge keeps one record and decides which value survives in each field. Without your own rules, the CRM's default merge behavior decides, and each CRM handles it differently. That may be fine for a first set of exact matches. If you want a specific outcome, set it before the merge. | Decision | Common choices | Why it matters | | --- | --- | --- | | Which record survives | The oldest, the newest, the most recently updated or the most complete | Its record ID often stays, and integrations may point to it | | Owner | The current account owner, or the owner of the surviving record | Owner changes are what sales notices first | | Lifecycle or lead stage | The most advanced stage | A customer shouldn't drop back to lead | | Email and phone | The most recent value, with the other kept where the CRM allows | Reps need the number and address that work today | | Blank fields | Never overwrite a filled field | An empty value shouldn't erase real data | Agree on these choices with the people who use the fields. Our post on [merging CRM records without losing data](https://dedupe.ly/blog/merge-crm-records-without-losing-data) goes deeper into each one. ### Preview the outcome A rule that reads well can still produce a surprise. A preview shows the merged record before it exists, so you can compare it with what you expected. Preview a handful of sets that represent your data, including your edge cases. For each one, check: - Which record survives, and whether its ID matters to another system. - Who the owner will be. - Which email, phone and stage the record keeps. - That no filled field is replaced by a blank one. If one preview looks wrong, fix the rule itself. The same rule will decide every merge after it. Pro tip Keep your list of known duplicates and known non-duplicates. Run it against the search again every time you change the criteria, before you merge anything new. ### Make the first merge a small one With criteria tested and the outcome previewed, the first merge is a check of your preparation. Keep it small enough to look at every result. Open the merged records in your CRM the way a rep would, and look at the activity history, associated records and owner. If something is off, you've found it on a few records. Our playbook on [what to do if you merged the wrong records](https://dedupe.ly/knowledge-base/i-merged-the-wrong-records) covers the fix. When the small merge looks right, move to larger batches of the same search. Our post on [running a big cleanup without disrupting sales](https://dedupe.ly/blog/crm-cleanup-without-disrupting-sales) covers merging in stages. ### How Dedupely helps you prepare your first merge In Dedupely, you build duplicate searches and set how each field is matched, and every search shows its matches and the records in them. You can reject false matches and set rules for which value wins, or let your CRM's own merge logic decide. Before anything merges, you can preview each merge, with the winning values shown in bold. [Preview your first merge](https://v2.app.dedupe.ly/signup) ### Settle the questions before you click merge The first merge feels like the riskiest moment of a cleanup because it's the first one that changes your live CRM. Most of that risk is gone once you've decided what a duplicate is and tested the search against sets you know. Deciding what the merged record keeps and previewing it removes the rest. By the time you merge, you're confirming a result you've already seen. ### Frequently asked questions #### What should I do before merging duplicates in my CRM? Decide what counts as a duplicate for each object, then build a search on fields that identify each record, like email or domain. Check a sample of matches and decide which values win in fields like owner and stage. Preview the merged record before you merge the first set. #### Can a CRM merge be undone? A CRM's own merge usually can't, apart from a short stay in a recycle bin in some. Most Dedupely merges can be undone for 30 days from Merge History, but treat every merge as permanent. That's why the checks before the first merge matter more than any fix you could make afterward. #### How do I know if my duplicate search is accurate? Test it against sets you already know. List a few real duplicates and a few records that aren't, and check that the search finds the first group and skips the second. Open the largest sets and a random sample too, since oversized sets often come from placeholder values. #### Which record should survive a merge? It depends on your data. Many teams keep the oldest record, because integrations may point to its ID, while others keep the most complete one. Whichever you choose, decide field by field which values win, so the surviving record keeps the right owner and stage. #### How many duplicates should I merge first? Start with one set, then a single page of sets from the same search. Open the results in your CRM and check owners, activities and associated records. Once those look right, merge larger batches with the same criteria and rules, and leave looser searches for later. 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 Why matching and merging are separate decisions Matching decides which records are duplicates. Merging decides what the final record keeps. Treat them as two decisions to avoid wrong merges. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/matching-vs-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/merge-crm-records-without-losing-data) [Team Collaboration Run a big CRM cleanup without disrupting sales To clean a CRM without disrupting sales, agree on what a duplicate is, tell reps what will change, then merge in stages, starting with exact matches. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-cleanup-without-disrupting-sales) ### Get started for free 20 free trial merges and as much free support as you need to get your duplicates under control. [Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)[Try for free](https://v2.app.dedupe.ly/signup) [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) Skip to content