TL;DR
- CRM records without an email often come from manual entry, imports, calls and events.
- Matching on email alone can't find duplicates among records with a blank email.
- Name with company or name with phone finds many duplicates that have no email.
- A merge should never let a blank field overwrite a field that holds a value.
- Dedupely finds duplicates with or without an email, and blanks never overwrite values by default.
Email is the field many CRMs and cleanups rely on to spot duplicate contacts. It works well, as long as the email is there.
Many records don't have one. A rep logs a call with just a name and a phone number, or an import arrives without its email column. Those records slip past email matching, and their duplicates stay hidden next to the complete record for the same person.
In this post, you'll see where records without an email come from and why email matching misses them. You'll also see which fields to match them on, and how to merge them without losing the data they hold.
Where records without an email come from
Causes differ from one CRM to the next. These sources come up often.
- Manual entry: a rep creates a contact from a call, a meeting or a business card and fills in only what's at hand.
- Imports: a spreadsheet without an email column, or with the column mapped to the wrong field.
- Phone and call apps: an inbound call can create a contact with a number and little else.
- Events: badge scans and attendee lists often carry a name and company but no email. Our post on how event and purchased lists create duplicates covers this source.
- Integrations: billing, support or ecommerce tools can create contacts from an order or a ticket. The email may sit in a field the CRM doesn't map.
- Migrations: a field mapping that drops a secondary email field.
Some records have no email on purpose. A buyer who only deals by phone, or a contact who asked not to share an email, is still a real record.
Why email matching misses them
Email matching compares one value. When that value is empty, there's nothing to compare, so the record can't match anyone.
A record and its twin with an email
A frequent case is one person with two records: one complete, one with a blank email. A search on email finds the complete record and never pairs it with the blank one.
Native deduplication at entry
Some CRMs check new contacts for duplicates by email only. In some, an import row without an email or another key becomes a new record. The same person can then be imported again and again.
Blanks treated as values
The opposite problem exists too. A tool or a script that treats two empty emails as equal can group hundreds of unrelated records. Check how your tool handles blanks before you trust a match.
Which fields to match on when email is missing
What counts as a duplicate is case by case: what one team considers a duplicate, another may not. Without an email, you need two or three fields that agree, and the right combination depends on what your records hold.
| Combination | Good for | Watch out for |
|---|---|---|
| Full name + company | B2B contacts from events, imports and manual entry | Common names at large companies, and company names written differently |
| Full name + phone | Contacts from calls and phone apps | Shared office lines and family landlines |
| Full name + city or postcode | B2C records and records without a company | Common names in large cities |
| Name + another ID | Records with a social profile URL, customer number or account number | IDs copied between records by mistake |
| Last name + company + phone | Nicknames and first-name variations | Relatives at a family business |
Names need some tolerance: typos, nicknames and missing accents all hide matches. Our guide on which fields to match on covers how strict each field should be.
How to find and review them
Records without an email are easier to clean as their own group. These principles help.
Count them first
Filter your contacts by a blank email and see how many there are and where they came from. The record source or create date often points to one import or one integration. Our post on duplicate rate and other CRM accuracy metrics covers how to track missing fields over time.
Match them against complete records
Start with blank-email records that have a twin with an email, matched on name and company or name and phone. Those are the obvious duplicates, and merging them gives the complete record any details the other one held.
Review the near matches
Two people with the same name at the same company do exist. Send unclear matches to the record owner, and reject a match only when you're certain it's wrong.
How to merge them without losing data
A record without an email often holds something the complete record doesn't, like a mobile number, a meeting note or a deal. The merge should keep all of it.
- Never let a blank overwrite a value. If one record has an email and the other is blank, the email stays.
- Choose the primary record with care. The record with the email is often the better primary, since forms and integrations use it to find the contact.
- Keep the activity history. Calls, notes and meetings logged on the blank record belong to the same person.
- Check the owner. The blank record may belong to the rep who met the person, which matters for ownership rules.
How to keep new records without an email from multiplying
Once the backlog is merged, a few habits keep the group small.
- Ask reps to search by name and phone before creating a contact from a call.
- Map the email column on every import, including secondary emails.
- Check which integrations create contacts, and which field they put the email in.
- Fill in missing emails when you learn them, before a second record forms.
Enrichment tools can add missing emails, but adding data to duplicates spreads it across two records. Our post on whether to deduplicate or enrich first covers the order.
How Dedupely finds duplicates in records without an email
In Dedupely, leave email out of the search and compare name with company, phone or city to find candidates. Name and city alone are not enough to confirm identity. Review independent details, choose the surviving values and check which activities and associations your connector supports before merging.
Give every record a second way to match
Records without an email are easy to miss because email is where matching often starts. They come from calls, imports, events and integrations, and their duplicates sit next to the complete records for the same people.
Name with company, name with phone and name with city find many of them. Merged with care, so blanks never replace real values, they add the details the complete record was missing.
Frequently asked questions
How do you find duplicate contacts without an email address?
Match them on other fields that identify a person, like full name with company, full name with phone, or full name with city. Start with records that have a complete twin with an email, since those are the most likely duplicates. Review same-name matches before merging, because two people can share a name.
Why do CRM records have no email?
Often because they were created from incomplete data: manual entry after a call, imports missing an email column, phone apps, event lists or integrations. Some contacts have no email on purpose, such as buyers who only deal by phone. Those records are still valid.
Can you merge a record with no email into one that has an email?
Yes. Choose the record with the email as the primary when forms and integrations rely on it. Make sure blank fields can't overwrite filled ones. Activities, notes and phone numbers from the record without an email should carry over, so nothing logged on it is lost.
What happens to blank fields when you merge duplicates?
It depends on the merge rules. In a safe merge, a blank field never overwrites a field that holds a value, so the filled value stays. Merge rules differ between tools and CRMs. Check how blanks are handled, and test on a few records before a large merge.
Or sign up with Google
Pipedrive user 
