Blank Values in Merging
Blank values in merging are the empty fields on duplicate records, and the way merge logic handles them when a duplicate set becomes one record. A blank value can be a null, an empty text string or a field that holds only spaces. In each case the field has no data, and the question is whether that emptiness can replace a filled value on another record.
It's the question behind a common search: does merging overwrite data with blank values? The answer depends on the merge logic. Logic that treats a blank as missing keeps the filled value from whichever record has one. Logic that takes one record's value without checking it can keep an empty field and drop a real phone number, address or job title. Placeholders such as "N/A," "Unknown" or "test" are a related problem: they look filled, so a check for blanks alone lets them win.
See how Dedupely keeps blank values from overwriting data in your CRM
What Are Blank Values in Merging?
Blank values in merging are the empty values a merge has to deal with when the records in a duplicate set don't hold the same information. Records fill in at different times and from different sources. A contact created by a form may have an email and nothing else, while a contact created by sales has a phone number, a title and an address. When the two merge, most fields are filled on one record and blank on the other.
A simple example: two contacts for Lena Ortiz. The older one has the phone number (555) 010-4400 and the job title "Head of Operations." The newer one has an empty phone field and "N/A" as the title. If the newer record survives and keeps all of its own values, the merged record has no phone and the title "N/A." If blanks and placeholders are treated as missing, it keeps the phone number and the real title.
There are a few ways merge logic handles empty values. Treating blanks as missing keeps a filled value from any record in the set, which protects data and suits most fields. Keeping the surviving record's value as it stands is simple and predictable, and it respects a field someone cleared on purpose, but it can carry a blank forward. Choosing values by hand gives full control over each field, which suits a few sets where the records disagree on a lot.
How Blank Values in Merging Work
A merge deals with empty values field by field, in roughly this order:
- Read each record's value. For each field, the merge collects the value from every record in the duplicate set, including the empty ones. Depending on the system, a blank may be stored as a null, an empty string or a few spaces, and some logic treats these differently.
- Decide whether a blank counts. Whether merging overwrites data with blank values comes down to this step. Logic that treats blanks as missing removes them from the candidates. Logic that keeps the surviving record's value without a fallback keeps whatever that record holds, blank or not. A "most recent" rule can also pick a blank if the newest record left the field empty.
- Check for placeholders. Values like "N/A," "Unknown," "none" or a row of zeros in a phone field are filled in technically. Unless a rule makes them lose, they compete with real values and can win.
- Pick the winner from what's left. The remaining values are compared on the field's rule, such as the newest, the longest or the one from a trusted record.
- Handle fields that are empty on every record. When no record has a value, the field stays empty on the merged record. A merge can't create data that none of the records hold.
Some tools also send sets with blank or filler values to a person for review instead of merging them, so the missing value can be checked first.
Why Blank Values in Merging Matter for CRM Teams
A blank that wins a merge removes data without any sign that it happened. The merged record looks complete, but the phone number, address or title that was on the other record is gone, and with many merges hard to reverse, it may not come back. Sales loses a way to reach the customer, support sees less context, and the gap often surfaces only when someone needs the value.
Blank fields also shape reports and automation. Segments built on country, industry or lifecycle stage leave out records with empty fields, and routing that depends on a region or owner can't assign them. A merge that keeps a blank over a real value takes a record out of the lists and workflows that relied on it, and the fill rate for that field drops even though the data existed before the cleanup.
Placeholders cause a quieter version of the same problem. A title of "Unknown" or a phone number of "000-000-0000" passes a check for empty fields, so it's counted as data in reports and fill rates. When a placeholder beats a real value in a merge, the record ends up looking filled and staying unusable. Treating blanks and placeholders as missing keeps the merged record as complete as its duplicates were together.
Getting Started With Blank Values in Merging
Start by finding out how often your key fields are empty on one record and filled on another. Phone, address, job title, industry and lifecycle stage are common gaps, especially between records from forms, imports and manual entry. Knowing which fields are often blank tells you where a merge has the most to lose.
Then check the merge logic for those fields. A rule that keeps the surviving record's value should fall back to the other records when that value is empty. A rule that keeps the most recent value should skip a newer blank. Fields where a value was cleared on purpose, such as an outdated phone number, are worth fixing on the records before merging, so the old value doesn't come back.
Look for placeholders as well. List the filler values your CRM collects, such as "N/A," "Unknown," "none" or a dummy phone number, and make them lose to real values. Preview a few merged records where the duplicates disagree before merging in bulk, and spot-check the fields after the merge.
In Dedupely, blank values never win a merge, with or without Merge Rules, and the suggested "Placeholders lose" rule drops filler such as "Unknown" or "N/A" when a real value exists. A preview of the merge result while you build a rule shows the winning values in bold before anything changes in your CRM.
Key Takeaways: Blank Values in Merging
Blank values in merging are the empty fields on duplicate records and how a merge treats them. Logic that treats blanks as missing keeps the filled value from whichever record has one; logic that takes the surviving record's value without a fallback can carry a blank forward and erase real data. Placeholders such as "N/A" or "Unknown" look filled, so they need their own rule. Checking the often-empty fields and previewing merged records before merging in bulk keeps the result complete. In Dedupely, blank values never win a merge, with or without Merge Rules. The "Placeholders lose" suggestion and Custom rules with operators such as "is blank" and "is a placeholder" give finer control, previews show the result first, and Merge History keeps each merge's original records and values.
Frequently Asked Questions About Blank Values in Merging
Does merging duplicates overwrite data with blank values in a CRM such as HubSpot or Salesforce?
It can, depending on the merge logic the CRM or tool uses for each field. Many merges keep a filled value over a blank one, but a rule that always keeps the surviving record's value, with no fallback to the other records, keeps that record's empty field and drops the real value. A "most recent" rule can do the same when the newest record left a field blank. Because native merge logic varies by CRM and by field, the safest check is to preview the merged record for a pair with known gaps, such as an empty phone field on the record you plan to keep. In Dedupely, blank values never win a merge, with or without Merge Rules, so a filled value from another record in the set takes the empty field's place. Without Merge Rules, Dedupely otherwise follows the CRM's own merge logic for which value wins, and Merge Rules let you set the Primary Record and a rule per field.
Why did a merge erase a value from a record?
A merge erases a value when another value wins the field, and that winner can be a blank, a placeholder or an older entry. The most common causes are a rule that keeps the surviving record's value without checking it, a "most recent" rule that picked a newer blank, and a placeholder such as "N/A" that counted as filled. A single-value field can also hold only one value, so a second email address or phone number is dropped unless it moves to a field built for several values. To find the cause, compare the original records with the merged one and check the rule on that field. In Dedupely, blank values never win, so an erased value points to another value winning, such as a placeholder or the CRM's own logic when no Merge Rule was set. Merge History shows each merge's original records and values, with a CSV download. Merges can't be undone, so use it to restore the value by hand.
How do you stop placeholder values like "N/A" or "Unknown" from winning a merge?
Set a rule that makes placeholders lose to real values, so filler only survives when no record has anything better. A check for blanks alone doesn't catch them, because "N/A," "Unknown," "none," "test" or a dummy phone number are filled in technically. Start by listing the placeholders your forms, imports and team enter, then apply the rule to the fields where they appear most, such as job title, phone and industry. Preview a few merged records that hold a placeholder on one side and a real value on the other. In Dedupely, the suggested "Placeholders lose" rule drops filler such as "Unknown" or "N/A" when a real value exists, and it can be applied or dismissed field by field in Merge Rules. Custom rules can also use an "is a placeholder" operator in a Lose Rule, and Lose Rules run before Win Rules. Operators vary by field type, so the options on a phone field differ from those on a text field.
What happens when every record in a duplicate set is blank in a field?
The field stays empty on the merged record, because a merge can only keep values the records already hold. That's expected, and it doesn't lose any data, but it does mean the merged record carries the same gap as each of its duplicates. If the field matters for reporting or routing, such as country, industry or owner, fill it on one of the records before merging, or add it to the merged record afterward. The same applies when every record holds only a placeholder: a rule that makes placeholders lose has no real value to pick, so the filler stays. In Dedupely, the "Placeholders lose" rule applies when a real value exists. To catch these sets before merging, a field in a Duplicate Search can have "Send incorrect formats to manual review" checked. It's off by default, and when it's on, sets with invalid or filler values in that field, such as blank or N/A, go to Manual Review instead of being merged with the rest.
How do you check for blank values before merging duplicates?
Filter the duplicate sets on the fields that matter and preview the merged record before merging. A filter for empty values shows which records are missing a phone number, address or stage, and comparing them with their duplicates shows where a merge depends on the other record's value. Then preview a few merged records from those sets and confirm that each filled value survives. Check placeholders the same way, since they don't show up in a filter for blanks. After merging, spot-check a sample of records in the CRM. In Dedupely, Filters include "is blank" and "is not blank" operators for narrowing a Duplicate Search, and they only change what's displayed, never CRM data. The in-line preview shows the winning values in bold, and the Preview Merge panel shows the final merged record before anything changes.
