Skip to content
Database ⇄ CRM

Reltio to Veeva CRM integration — real-time, two-way sync

Keep Reltio and Veeva CRM 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 Reltio and Veeva CRM

Treat Veeva CRM like part of your database: its records live in Reltio as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Reltio, where it can be queried and joined like everything else.

Stacksync mirrors Consent Records, Key Messages and CLM Content, Territories and Alignments, Events from Veeva CRM into Entities, Relations, Crosswalks, Interactions in Reltio with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Veeva CRM with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Sync HCP and HCO accounts between Veeva CRM and a customer master or MDM system to keep the customer master aligned.
  • 02 Replicate call and activity data into a warehouse for field-force effectiveness reporting.
  • 03 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 04 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.

Common sync patterns

Query the CRM like a database

Accounts, contacts, and custom objects from Veeva CRM become tables in Reltio you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to Reltio sync onto the matching records in Veeva CRM, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Veeva CRM API, limits, and retries.

What you can sync between Reltio and Veeva CRM

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.

Reltio objects Veeva CRM objects How this pairing syncs
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Territories and Alignments Rep-to-account assignments, often fed from a roster or alignment system. Matches (Potential Matches) is specific to Reltio and Territories and Alignments to Veeva CRM — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Events Medical events and speaker programs managed through Veeva's events capabilities. Activity Log is specific to Reltio and Events to Veeva CRM — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Approved Email Activity Sent-email records from Veeva Approved Email, used in engagement reporting. Data Change Requests (DCR) is specific to Reltio and Approved Email Activity to Veeva CRM — each maps to any object or custom field on the other side.
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Accounts (HCPs and HCOs) Healthcare professionals and organizations; the central entity most syncs key on. Reference Data (RDM) is specific to Reltio and Accounts (HCPs and HCOs) to Veeva CRM — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Calls Recorded visits and interactions with HCPs, including samples dropped and key messages shown. Entities is specific to Reltio and Calls to Veeva CRM — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Medical Inquiries Information requests captured in the field and routed to medical affairs. Relations is specific to Reltio and Medical Inquiries to Veeva CRM — each maps to any object or custom field on the other side.

How changes propagate between Reltio and Veeva CRM

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.

Reltio Veeva CRM Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

Veeva CRM Reltio Interval-based propagation

DetectionStacksync polls Veeva CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification timestamps.

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

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • Veeva CRM: Subject to the underlying platform's API request allocations, which are contract-dependent.
What ships with Reltio ⇄ Veeva CRM

Connect Reltio and Veeva CRM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Veeva CRM connection.

Real-time

Two-way sync

Changes in Reltio or Veeva CRM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio or Veeva CRM 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 Reltio or Veeva CRM record.

Observability

Monitoring

Track your Reltio ⇄ Veeva CRM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Reltio and Veeva CRM.

How the Reltio and Veeva CRM connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

Veeva CRM

Integration surface
Salesforce-platform APIs (REST, SOAP, Bulk) for classic Veeva CRM; Vault REST API for Vault CRM
Authentication
OAuth 2.0
Change detection
Polling on record modification timestamps; platform event streams where the underlying org enables them
Capabilities
read · write
Rate limits
Subject to the underlying platform's API request allocations, which are contract-dependent.
How it works

How to connect Reltio to Veeva CRM — 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 Reltio and Veeva CRM 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
    Reltio connected
    Veeva CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio and Veeva CRM 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 · Reltio ⇄ Veeva CRM
    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
    Reltio Veeva CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Reltio and Veeva CRM 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 430 integrations available for Reltio and Veeva CRM.

Popular · 7 of 430
All Reltio integrations All Veeva CRM integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own