Salesforce and Dun & Bradstreet integration

Company details on every account, a credit check where the deal needs one, and the result reused instead of paid for twice.

Into SalesforceSalesforce and Dun & Bradstreet

What moves between them

  • Into SalesforceFirmographics on the account, and credit results on the deal and account, with the date they were pulled.
  • Out of SalesforceThe companies and deals that need a check, sent when the deal reaches the stage that requires one.

How we build it

  • A credit gate at the right stageDeals above a set size need a recent credit result before the contract goes out.
  • Results reused within a windowA check from the last few months is reused, so the same report is not bought twice.
  • Fields with ownersEnrichment fills its own fields and never overwrites what a rep entered.

What goes wrong, and the fix

Problems we have found and fixed in production.

  • Paying for the same report twiceNothing records when a check was last pulled. Store the date and reuse within the window.
  • Credit checks skipped on large dealsThe check is a request, not a gate. Make it a requirement at the stage it matters.
  • Enrichment overwrites rep-entered dataShared fields. Give enrichment its own fields and let people choose.

Questions

Do we need the AppExchange package?

Not always. It suits enrichment at scale; credit checks on deals can run through the API with the gate in Salesforce.

Other Salesforce integrations

  • Salesforce and SnowflakeWarehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
  • Salesforce and DocuSignAgreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
  • Salesforce and Adobe Commerce (Magento)Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.
  • Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
  • Salesforce and Microsoft Dynamics 365Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.
  • Salesforce and Apollo.ioProspects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.

Talk to us about Salesforce and Dun & Bradstreet.

Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.

hello@feldtgroup.com