If you've been told to add a DUNS Number field to Salesforce, there's a good chance you're trying to fix something the DUNS Number doesn't fix.
Most sales and RevOps teams who go down this path are actually trying to solve account matching — recognizing the same company across the website form, the marketing automation tool, the CRM, and the data warehouse. A DUNS Number can be one input to that problem. It's almost never the answer.
This page is for the person who just got handed that ticket. It covers:
What a DUNS Number is, and what it means for your Salesforce data
The three reasons people add one in Salesforce
The two scenarios where you need one
How modern account matching works
How to add the field, if you've decided you need it
What a DUNS Number is, and what it means for your Salesforce data
A D-U-N-S Number — Data Universal Numbering System — is a nine-digit identifier assigned by Dun & Bradstreet to a business location. Each physical business location gets its own DUNS. It's not a tax ID, it's not a credit score, and it isn't proprietary to Salesforce or to any CRM.
D&B issues DUNS Numbers for free. The number itself does nothing — it's a key. What sits behind that key in the Dun & Bradstreet Data Cloud is firmographic and credit data. The DUNS gives D&B (and anyone licensing D&B data) a consistent way to refer to a specific business location.
The three reasons people add DUNS Numbers to Salesforce — and which ones make sense
When a request to add a DUNS Number field to Salesforce lands, it almost always traces back to one of three motivations.
One is a genuine requirement, one is a misdiagnosis, and one is worth pausing on before you build anything. Knowing which you're dealing with tells you whether to create the field or push back.
1. Regulated-industry compliance (legitimate)
If you sell into financial services with KYC/AML requirements, insurance with regulated vendor onboarding, or commercial supplier portals that mandate it, the DUNS Number has to sit on the account record. This is the only scenario where you should add the field without a second thought.
One thing worth flagging: federal contracting via SAM.gov no longer uses DUNS. The US government replaced it with the UEI in April 2022. If your compliance team is asking for "the SAM number," that's the UEI now.
2. Account matching across systems (the wrong tool)
Most teams asking "how do I add a DUNS Number to Salesforce?" really mean "how do I stop the same company showing up as four accounts (Acme Inc, Acme, Acme LLC, acme-inc.com) across Marketing, Sales, the web form, and the warehouse?"
DUNS won't fix that, for two reasons. First, it identifies a business location, not a company. A firm with 40 offices has 40 DUNS Numbers, so matching on it fragments accounts rather than unifying them. Second, you don't have one: D&B's free tool works one company at a time and needs a name plus address, useless against thousands of inbound records carrying just an email. Matching at scale is what you pay for.
Modern account matching is a different problem with a different solution, covered below.
3. Your CRO mentioned it (audit before building)
Sometimes the request comes down from leadership without a clear use case.
Before you build the field, the schema migration, and the workflow, ask: what business question are we going to answer with this number that we can't answer today? If the answer is "I'm not sure," go back upstream. Building data infrastructure to answer a question nobody can articulate is the most expensive way to fail a quarter.
How modern account matching works in Salesforce
Account matching across systems is solved by an account-match engine: a service that takes a noisy input (an email domain, a partial company name, a website URL) and returns a confident match to a canonical company record.
ZoomInfo Operations is built to solve exactly this: the matching and data-quality problem the DUNS Number doesn't. It integrates with Salesforce to run continuously against your accounts, leads, and contacts, writing matched and enriched data back into the records your reps already work from.
Lead-to-account matching that resolves a noisy inbound record to the right account using company hierarchies and domain intelligence
Multi-vendor waterfall enrichment that appends missing company and contact attributes automatically, with deduplication and continuous verification keeping records accurate as they decay
Cross-system orchestration that connects data and actions across the CRM, marketing automation, sales engagement, and the data warehouse — so the same company isn't recognized three different ways across three systems
Momentive used it to cut speed-to-lead from 20 minutes to 60 seconds.
What turns identity resolution from plumbing into pipeline is the GTM Context Graph. The graph fuses your CRM records, conversation transcripts, intent signals, behavioral data, and ZoomInfo's own B2B data into one reasoning layer. The result is that a matched account isn't a static row tagged with an ID; it's an entity the system understands across the full lifecycle of the deal. The DUNS Number was designed to be a key. The Context Graph is designed to be the knowledge behind the key.
This is what most teams asking about DUNS in Salesforce actually wanted: a stable, populated identifier that survives the messy reality of inbound data — plus a reasoning layer that does something with it. The DUNS Number wasn't designed for either job.
When you need a DUNS Number in Salesforce
Two scenarios:
Compliance-driven. Financial services KYC, insurance vendor onboarding, supplier portals, anywhere DUNS is mandated by a regulator or commercial contract.
You already license D&B data. If D&B Connect or Optimizer is enriching your Salesforce, the DUNS is already being written. Keep it. It's a useful secondary key.
Outside those two cases, the DUNS Number in Salesforce is an empty column nobody updates. It will sit there for two years, then get retired in the next data clean-up.
How to add a DUNS Number field to Salesforce
Salesforce doesn't ship with a DUNS field by default, so you create it as a custom field on the Account object. Here's the five-step setup for the cases where you actually need one.
Create the field. Setup → Object Manager → Account → Fields & Relationships → New. Field type: Text (9 characters, no formatting). Label: D-U-N-S Number. Field name: DUNS_Number__c.
Add field-level security. Read for everyone, edit limited to RevOps and the integration user.
Add the field to the Account page layout in the "Compliance" or "Identifiers" section, not the top of the page.
Populate the field. Three options: (a) manual lookup via D&B's free DUNS Number Lookup tool, fine for a small enterprise book, painful at scale; (b) D&B Optimizer or Connect, automated, costs money; (c) a data-enrichment platform like ZoomInfo or one of the other D&B alternatives that returns DUNS as one firmographic field among many.
Set a refresh cadence. DUNS values are stable for the life of the business location, so refresh is rarely needed. If a company is acquired, the parent DUNS may change.
Next step
Most teams asking about DUNS in Salesforce are trying to solve account matching. Book a 30-minute walkthrough — we'll match 1,000 of your Salesforce accounts and show what changes when the foreign key is fit for purpose.
Frequently asked questions
Does Salesforce have a built-in DUNS Number field?
Not by default in Sales Cloud. Some Salesforce-native partner packages, including D&B's own AppExchange listings and several enrichment products, install a DUNS field automatically. If you're starting from a clean instance, you create it as a custom text field.
How do I find a company's DUNS Number for a Salesforce record?
D&B publishes a free DUNS Number Lookup tool that returns the number for a known company. It's accurate but manual. For bulk population, you'll need an enrichment subscription, either D&B's own product or a data vendor that licenses D&B data and writes the DUNS to your CRM as part of standard enrichment.
Can ZoomInfo write DUNS Numbers to Salesforce?
Depending on your ZoomInfo SKU, yes. DUNS is one of the firmographic fields available via the Salesforce enrichment integration. Confirm with your account team before assuming it's in your plan.
Is the DUNS Number free?
Yes, the number itself is free from D&B. What costs money is the enrichment data behind the number, and the automation of populating it across a CRM at scale.
What's the difference between a DUNS Number and a Tax ID (EIN)?
EIN is issued by the IRS for tax filing purposes. DUNS is issued by D&B for business identification, primarily in the context of credit and corporate hierarchy. They're separate identifiers and serve different jobs.
What about SAM.gov and federal contracting?
The DUNS Number used to be the federal government's primary entity identifier, but SAM.gov replaced it with the UEI (Unique Entity Identifier) in April 2022. If you're registering to do business with the US federal government, you need a UEI, not a DUNS. The UEI is issued for free directly through SAM.gov as part of entity registration.
