Lead-to-account matching: send the new lead to the rep who knows the customer
The short answer: Lead-to-account matching means comparing a new lead to your existing accounts, usually by email domain, website or company name, and acting on a match. Native Salesforce warns about duplicates during conversion but doesn’t match new leads to accounts and route them. You build that yourself, buy it, or run a report-based check, and then route, convert or flag each match.
Your largest customer fills in the demo form. Their email address is on a company domain you’ve invoiced for six years. The lead lands in the round robin and goes to a rep who has never heard of them, who opens with “So, what does your company do?”
The account owner finds out when the customer mentions it on the next call. By then the customer has noticed too. This isn’t a data problem in the usual sense. Every record is valid. It’s a missing link between two records that nobody drew.
Why should a new lead from a customer reach the account owner?
Because the account owner holds the context: the open deals, the renewal date, the support history and the relationship. A stranger reading a form can’t see any of that. Routing the lead to the owner avoids two reps working the same company, and it keeps a customer from being cold-pitched on something they already own.
It also protects your numbers. A lead that’s really an existing account inflates new-business pipeline when it’s counted as net new. That’s an argument the RevOps lead can bring to the VP, and it’s easier to make with a log than from memory.
Does Salesforce match leads to accounts natively?
Salesforce checks for matches when you convert a lead, but it doesn’t match a new lead to an account and route it. Salesforce Help says that if a duplicate account exists, conversion prompts you to create a new account or attach to the existing one, and that attaching creates a new contact on that account.
Three limits come straight from Salesforce’s own pages:
- The prompt may not show everything. Salesforce warns that with more than three to five similarly named accounts, the conversion prompt may not list them all, and an Accounts report is the way to see every match.
- Cross-object duplicate rules don’t run during conversion. Salesforce Help says that if your admin has created any, they aren’t triggered when a lead is converted. (We could read this only in a search excerpt of the Help article, so check the current wording in your org’s Help.)
- The standard account matching rule is picky. Salesforce’s article on duplicate rules that don’t fire says it needs an account name plus a billing city or zip, so a thin record can slip past it.
None of that routes anything. Duplicate management is about catching the second copy of a record, not sending work to a person. If the lead isn’t a duplicate (it’s a new person at a known company), it passes straight through.
How do you match leads to accounts: domain, website or name?
Use email domain first, website second and company name last, because that’s the order of reliability. A domain is exact and quick to compare. A name needs cleaning before it matches anything.
Email domain. Take everything after the “@” on the lead and compare it with the domain of the account’s website. A formula field on Lead keeps it simple:
IF(CONTAINS(Email, "@"), LOWER(RIGHT(Email, LEN(Email) - FIND("@", Email))), NULL)
Website. Strip the “https://”, the “www.” and any path from the account’s website, and lowercase what’s left. Sites entered by hand are untidy, so expect to clean the field.
Normalized company name. Lowercase it, drop punctuation, and remove endings like “Inc”, “LLC” and “Ltd”. “Acme, Inc.” and “ACME Inc” then compare equal. Names are the weakest signal. Use them only when there’s no usable domain, and prefer a flag over an automatic action.
Where does matching go wrong?
It goes wrong in four places, and you should plan for all of them before you trust a match.
- Personal-email domains. Personal addresses from the big mail providers share one domain with millions of other people. Keep a list of personal-email domains and skip them, or one account will “match” every lead who uses a personal address.
- Subsidiaries and brands. A lead at a subsidiary may use the parent’s domain, or its own. Matching to the wrong level sends the lead to the wrong owner. Decide whether parent or child wins, and write it down.
- Shared and agency domains. A consultant working for you may have an address at their own firm. Domains that look like customers can belong to a partner.
- Dirty account data. An account with no website, or a typo in one, never matches. Matching tells you about your data as much as about your leads. If duplicates are part of it, merging duplicate accounts comes first, and a Data Health Check can count how many accounts lack a usable website.
Measure these before you switch anything on. A pass over last month’s leads, with matches listed and read by a person, tells you your false-positive rate. Nobody can guess it.
Can you check matches by hand with a report?
Yes, and it’s worth doing once before you automate. Salesforce reports can’t join a lead to an account on a shared domain, so the comparison happens in a spreadsheet.
- Add the email domain formula above to Lead.
- Run a leads report for the last 30 days with Lead Owner, Company and the new domain column. Export it.
- Run an accounts report with Account Name, Website and Account Owner. Export it.
- In the spreadsheet, clean the website column down to a bare domain, then look up each lead’s domain in it.
- Read every match. Mark each one right, wrong or unsure.
The count of “wrong” tells you whether domain-only matching is safe in your org. It also gives you your personal-email list as a by-product, because that’s where the wrongs will be.
What should you do with a match: route, convert or flag?
Route it to the account owner, and flag it for a person to confirm. Convert only when you’re sure, because conversion creates records and isn’t casual to undo.
- Route. Assign the lead to the account’s owner and record the account on the lead. This is the safe default. Check the owner is active first. A match to a departed rep’s account just moves the problem, as we describe in who owns the records of people who left.
- Convert. Attaching the lead to the existing account, per Salesforce Help, adds a contact to that account and doesn’t create a duplicate account. It’s right for an obvious new contact at a customer, and wrong if the lead might be unqualified.
- Flag. For a name-only or subsidiary match, set a field or create a task: “Possible match: Acme”. A person decides.
If the lead isn’t a match, it goes through your normal rotation, and our post on round-robin lead assignment covers the ways to build that.
What to do Monday:
1. Add the email domain formula field to Lead and run the 30-day leads report.
2. Export your accounts with websites and compare them with the leads in a spreadsheet. Mark each match right or wrong.
3. Write the personal-email domain list you’d exclude, and the rule for subsidiaries, in two lines.
4. Check how many of your accounts have a usable website. Under half means fix that first.
Where we come in
Bosun, by GTM Cloud, is pre-release: built, install-tested and in pilot, and not publicly listed yet. It matches a new lead to an existing account by email domain, website and normalized name, links it, and routes it to that account’s owner, with a logged reason. Version 1 doesn’t follow account hierarchies, so the subsidiary question stays yours. See Bosun.
Questions people ask
Does Salesforce automatically link a new lead to an existing account?
No. Salesforce checks for a matching account when you convert a lead and asks whether to create a new account or attach to the existing one. It doesn’t link a new, unconverted lead to an account or route it to the account owner. That needs Flow, code or an app.
What’s the best field to match leads to accounts?
Email domain, with website as the second check. A domain is exact, so comparisons are quick and rarely ambiguous. Company name is the weakest, because of spelling, punctuation and endings. Skip personal-email domains, and expect to handle subsidiaries as a separate rule.
Should matched leads be converted automatically?
Rarely. Conversion creates a contact and may create an opportunity, and it’s harder to take back than a routing change. Route the lead to the account owner, flag it, and let a person convert it once they know who they are talking to.
Sources
- Creation of duplicate account or contact on Lead conversion (Salesforce Help): the create-or-attach prompt, attaching adds a contact, and the three-to-five similar-accounts caution. Published July 8, 2026.
- Considerations for Converting Leads (Salesforce Help): cross-object duplicate rules and conversion. The page text did not load for us, so this rests on the excerpt a search returned.
- Standard duplicate rule does not fire (Salesforce Help): the standard account matching rule needs an account name and a billing city or zip.
- Things to Know About Duplicate Rules (Salesforce Help): background on when duplicate rules run, including the Apex Lead Convert setting. Page text did not load for us.