Skip to content
CRM

Dun And Bradstreet to Seismic integration — real-time data sync

Keep Dun And Bradstreet and Seismic in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dun And Bradstreet and Seismic

Run Dun And Bradstreet and Seismic side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into Seismic, so Seismic always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.

Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.

Common use cases

  • 01 Sync the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
  • 02 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM analysis.
  • 03 Provision and deactivate Seismic Users and User Groups from an HRIS or IdP so content access mirrors joiner, mover, and leaver changes.
  • 04 Extract content-interaction and LiveSend engagement from the Reporting API v2 into a warehouse to tie asset views to CRM Opportunities.

Common sync patterns

Divisional or regional split

Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.

Where both track pipeline: deal visibility across systems

Deal stage and value on shared accounts stay visible from either CRM.

Post-acquisition consolidation

Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.

What you can sync between Dun And Bradstreet and Seismic

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Dun And Bradstreet objects Seismic objects How this pairing syncs
Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. Teamsites Tenant-scoped workspace partitions organizing Library content, permissions, and config; scoped by teamSiteId on most content calls. Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Teamsites to Seismic — each maps to any object or custom field on the other side.
Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. LiveSend Links Trackable content-share links created via the engagement API; their open and view engagement is read back through Reporting. Criteria Search is specific to Dun And Bradstreet and LiveSend Links to Seismic — each maps to any object or custom field on the other side.
Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. Digital Sales Rooms Buyer-facing microsites (DSRs); lifecycle and content-change events surface via webhooks, currently marked Early Access. Monitoring Notifications is specific to Dun And Bradstreet and Digital Sales Rooms to Seismic — each maps to any object or custom field on the other side.
Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. Reporting Activities Content-interaction, engagement, and usage analytics extracted read-only through the ETL-oriented Reporting API v2 for a warehouse. Company Information (Data Block) is specific to Dun And Bradstreet and Reporting Activities to Seismic — each maps to any object or custom field on the other side.
Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. Library Content Documents, decks, and assets stored in teamsites; created, moved, and retrieved via the Content Management API, each with a contentId. Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Library Content to Seismic — each maps to any object or custom field on the other side.
Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Content Versions Version history for a library item; new versions upload via API and old ones expire, with events firing on ContentManager webhooks. Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Content Versions to Seismic — each maps to any object or custom field on the other side.

How changes propagate between Dun And Bradstreet and Seismic

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Dun And Bradstreet Seismic Interval-based propagation

DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).

DeliveryEach detected change is written to Seismic through its API, with automatic retries and rate-limit backoff.

Seismic Dun And Bradstreet Sub-second propagation

DetectionSeismic notifies Stacksync of record changes through webhook events. Webhooks for content, version, user, group, workflow, DSR, and LiveSend events.

DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Seismic records.

Rate-limit considerations

  • Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
  • Seismic: Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers.
What ships with Dun And Bradstreet ⇄ Seismic

Connect Dun And Bradstreet and Seismic for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Seismic connection.

Real-time

Real-time sync

Changes in Dun And Bradstreet or Seismic instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dun And Bradstreet or Seismic data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dun And Bradstreet or Seismic record.

Observability

Monitoring

Track your Dun And Bradstreet ⇄ Seismic sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and Seismic.

How the Dun And Bradstreet and Seismic connectors work

Dun And Bradstreet

Integration surface
D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
Authentication
OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
Change detection
Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
Capabilities
read
Rate limits
Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.

Seismic

Integration surface
REST Integration APIs and Reporting API v2
Authentication
OAuth 2.0 / OpenID Connect; Bearer token in the Authorization header, via Authorization Code (user context) or client-credentials app-only flows
Change detection
Webhooks for content, version, user, group, workflow, DSR, and LiveSend events; the Reporting API v2 is polled for batch historical extracts (ETL-oriented, not high-frequency)
Capabilities
read · write · webhooks
Rate limits
Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers
Seismic setup guide
How it works

How to connect Dun And Bradstreet to Seismic — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Dun And Bradstreet and Seismic with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dun And Bradstreet connected
    Seismic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dun And Bradstreet and Seismic objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dun And Bradstreet ⇄ Seismic
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dun And Bradstreet Seismic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dun And Bradstreet and Seismic integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 506 integrations available for Dun And Bradstreet and Seismic.

Popular · 8 of 506
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.