A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Veeva CRM Integration

Powered by Commercient
HubSpot and Veeva CRM integration
Integration Assessment
Integration Assessment · Life Sciences

Veeva CRM / Vault CRM × HubSpot

How a life sciences company can run HCP and HCO marketing in HubSpot (medical education events, digital engagement and consented email) while field reps keep working in Veeva CRM and its successor, Vault CRM, with one shared view of identity, consent and engagement.

Vault CRMVeeva CRMVault REST APIVeeva NetworkConsent syncHCP and HCO marketing
Platform ownerVeeva Systems
Integration typeCustom build on the Vault REST API and Network API
Primary directionTwo-way, by record type
FeasibilityBuildable, compliance-led
API accessOpen API
01 — Summary

Does Veeva integrate with HubSpot?

Veeva is where a life sciences company's field force works: HCP and HCO accounts, calls, territories, consent and events. HubSpot is where marketing reaches the same HCPs at scale through email, events, web and nurture. The two work side by side when they share who the HCP is, what they have agreed to receive, and what has already happened in the field.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The Vault REST API is documented publicly. The client's Vault admin creates an integration user with API access.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Vault CRM runs on the Vault Platform and its documented REST API, so HubSpot and the field force can work from one view of each HCP, with consent kept in step in both systems.

Campaign Creators assessment

Vault CRM is Veeva's go-forward CRM for new customers, and existing Veeva CRM customers are moving to it. Vault CRM keeps the familiar data model with new naming (a __vod suffix becomes __v), so CC builds the sync module against Vault CRM and maps the equivalent Veeva CRM objects for a client that has not moved yet. Veeva Network, Veeva's customer master, supplies the HCP and HCO identity through the Veeva Network ID, and the NPI is stored on the account. Consent records, call summaries, territory alignment and event attendance all have documented objects. The client's compliance team decides the consent rules, the content review path and how events are reported before any data moves.

Scorecard
Data richnessHigh
Public docsExtensive
Platform transitionPlan for
Build complexityMod–High

Ratings are CC judgments from Veeva's public help, developer and Network documentation. The client's Veeva configuration, custom fields and API limits are confirmed with its Veeva administrator during discovery.

Strength

A documented, stable identity

Each account carries a Veeva Network ID (veeva_network_id__v) linked to the Network record, plus npi__v. HubSpot matches HCPs on those keys, not on email alone.

Plan for

Two platforms, one consent truth

Consent lives in Vault CRM consent records and in HubSpot subscription status. The sync module makes opt-outs flow both ways quickly and only accepts opt-ins from approved capture points.

Gate

Compliance decides the rules first

The client's compliance team signs off consent rules by country and channel, the content review path for HubSpot emails, and how events and transfers of value are reported.

02 — API modules

Which Veeva APIs does the integration use?

Seven areas matter to HubSpot. Four carry the integration, two add context, and one is a scope decision about the platform transition.

Core

Accounts (HCPs & HCOs)

Vault CRM account__v

HCPs and HCOs are accounts with object types such as professional__v and organization__v or hospital__v. HCPs become HubSpot contacts; HCOs become companies.

  • npi__v, specialty_1__v, primary_parent__v
  • Veeva Network ID on every mastered account
  • Read through the Vault REST API and VQL
Core

Veeva Network

Network MDM API · customer master

Veeva's customer master for HCPs, HCOs, addresses, licenses and parent HCO affiliations. It is the tie-breaker for identity and the path for new HCPs captured in HubSpot.

  • veeva_network_id__v maps to Network vid__v
  • Search, retrieve and change request APIs
  • New HCPs from HubSpot become Network change requests
Core

Consent

multichannel_consent__v · consent_type__v

Vault CRM records opt-in and opt-out per channel and content type, with the address, capture time and source. HubSpot subscription status follows the same rules.

  • opt_type__v, channel_value__v, capture_datetime__v
  • approved_email_opt_type__v on the account
  • HubSpot unsubscribes written back as opt-outs
Core

Events Management

em_event__v · em_attendee__v

Medical education and promotional events are planned in Veeva. HubSpot promotes them, handles digital registration where approved, and follows up on attendance.

  • Events as HubSpot marketing events
  • em_attendee_status__v drives follow-up
  • Registrations written to Veeva only if in scope
Context

Call activity

call2__v · call2_detail__v

Rep calls give marketing context: when the HCP was last seen and which products were detailed. HubSpot receives summaries only, never call notes.

  • call_date__v and products detailed
  • Calls as HubSpot timeline events
  • Suppresses marketing sends after a recent call, if approved
Context

Territories & alignment

territory__v · account_territory__v · tsf__v

Which territory and rep cover each HCP, and whether the HCP is a target. Marketing segments and reports follow the field structure.

  • my_target__v and last_activity_date__v on tsf__v
  • yearly_call_activity__v for call counts
  • Rep alignment as HubSpot owner or a property
Scope decision

Veeva CRM to Vault CRM transition

__vod objects → __v objects

A client still on Veeva CRM, or mid-transition, needs a plan for which platform the sync module reads first and when it switches.

  • Same concepts, renamed objects and fields
  • Build once against Vault CRM, map Veeva CRM equivalents
  • Switch-over is a planned phase in the SOW
03 — Framework

How does the Veeva HubSpot integration work?

The integration layer reads changed accounts, consent, calls, territories and events from Vault CRM through the Vault REST API, checks identity against Veeva Network, and writes to HubSpot in batches. HubSpot sends back consent opt-outs, new HCP requests (as Network change requests) and, where approved, event registrations and a marketing engagement summary for reps.

Veeva
Vault CRM accountsHCPs, HCOs, NPI, specialty
Consent recordsopt-in and opt-out by channel
Calls & territoriescall summaries, alignment, targets
Events & Networkattendees, master identity
CC integration layer
Vault API clientVQL reads, burst-limit aware
Identity resolverNetwork ID · NPI · email
Consent engineopt-outs both ways, opt-ins by rule
Compliance filterno call notes, no medical content
HubSpot writerbatch upserts, error replay
HubSpot
ContactsHCPs with Network ID and NPI
CompaniesHCOs and parent affiliations
Marketing eventsmedical education and promotional events
Subscription typesconsent by channel and topic
Lists, workflows & reportssegments by specialty, territory, target
Veeva → HubSpot (accounts, consent, call summaries, territories, events)HubSpot → Veeva (opt-outs, new HCP change requests, optional registrations and engagement summary)
Principle

Each record has one owner

Veeva Network owns HCP identity, Vault CRM owns field activity and territories, HubSpot owns marketing engagement. Consent is shared under rules the compliance team signs.

Principle

Summaries, not field notes

HubSpot receives call dates, counts and products detailed. Call notes, medical inquiries and samples stay in Veeva.

Principle

An opt-out wins everywhere

An opt-out captured in either system reaches the other on the next sync cycle, and no workflow can re-subscribe an HCP outside an approved capture point.

04 — Process

What does Veeva HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Compliance and platform decisions come first, because they set what the sync module reads and writes.

1

Platform & compliance inventory

Confirm whether the client runs Veeva CRM, Vault CRM or both during transition, which countries are in scope, and the compliance team's rules for consent, content review and event reporting.

Gate to next phaseSigned platform plan and compliance rules
2

Access

Create an integration user in Vault CRM with API access and read permission on the agreed objects, and a Network API user if Network is in scope. Read the Vault's burst limit from the API response headers.

Gate to next phaseTest VQL queries and Network search succeed
3

Identity & consent rules

Agree the match order (Veeva Network ID, then NPI, then email) and the consent rules: which system captures each opt-in, and how opt-outs flow in each direction.

Gate to next phaseSigned match and consent rules
4

HubSpot data model

Create the vv_ properties, HCP and HCO associations, subscription types per channel and topic, marketing event settings and team permissions in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the Vault API client, identity resolver, consent engine, compliance filter, HubSpot writer, Network change request path and error replay.

Gate to next phaseAll agreed objects syncing in sandbox with clean reconciliation
6

Backfill

Load HCP and HCO accounts, consent records, territory alignment and an agreed window of call and event history.

Gate to next phaseCounts and consent status reconcile to Vault CRM reports
7

Workflows, parallel run & launch

Build event promotion, nurture and follow-up workflows with sends paused, have the content review team approve each email, run two weeks in parallel, then switch on.

Gate to next phaseCompliance sign-off and five days with no unresolved sync errors
05 — Data mapping

What does the Veeva HubSpot integration sync?

Object and field names follow Vault CRM's public help. For a client still on Veeva CRM, the same concepts carry a __vod suffix. Custom fields and email field names are confirmed against the client's configuration in discovery.

Veeva fieldHubSpot propertyObjectDirectionNotes
Accounts & identity · account__v, Veeva Network
veeva_network_id__vvv_network_idContactVV → HSMatch key #1. Links to Network vid__v. Unique.
npi__vvv_npiContactVV → HSMatch key #2 for US HCPs.
Namefirstname, lastnameContactVV → HSFill blanks only; Network is the master.
Primary emailemailContactVV → HSMatch key #3. Field name confirmed in discovery.
specialty_1__vvv_specialtyContactVV → HSDrives specialty segments.
Object type (professional__v, kol__v)vv_account_typeContactVV → HSHCP type for segmentation.
HCO account (organization__v, hospital__v)name, vv_hco_network_idCompanyVV → HSHCOs as companies.
primary_parent__vContact to Company associationContactVV → HSHCP's primary HCO affiliation.
New HCP from HubSpot formNetwork change requestContactHS → VVSubmitted to Network for validation; not created directly in Vault CRM.
Consent · multichannel_consent__v
opt_type__v (opt_in__v)Subscription status (opted in)ContactVV → HSAccepted only from approved capture sources.
opt_type__v (opt_out__v)Subscription status (opted out)Contact↔ BothOpt-outs flow both ways on the next cycle.
channel_value__vemailContactVV → HSThe address the consent applies to.
capture_datetime__vvv_consent_captured_atContactVV → HSEvidence of when consent was given.
consent_type__v, content_type__vSubscription typeContactVV → HSMapped to HubSpot subscription types by topic.
approved_email_opt_type__vvv_approved_email_opt_typeContactVV → HSAccount-level Approved Email status.
Calls & territories · call2__v, tsf__v
call2__v call_date__vvv_last_call_dateContactVV → HSMost recent submitted call.
call2__vCustom event: Rep callContactVV → HSDate, channel and products only. No call notes.
call2_detail__v product__vvv_products_detailedContactVV → HSMulti-select of products detailed.
tsf__v yearly_call_activity__vvv_calls_ytdContactVV → HSYear-to-date calls in the aligned territory.
tsf__v my_target__vvv_is_targetContactVV → HSTarget flag for the aligned territory.
territory__v via account_territory__vvv_territoryContactVV → HSTerritory name for segments and reports.
user_territory__v (rep)hubspot_owner_id or vv_rep_nameContactVV → HSOwner only if reps hold HubSpot seats.
Events & marketing engagement · em_event__v, em_attendee__v
em_event__vMarketing eventMarketing eventVV → HSEvent name, type, date and format.
em_attendee__v em_attendee_status__vMarketing event participationContactVV → HSInvited, registered, attended; drives follow-up.
HubSpot event registrationem_attendee__vContactHS → VVOptional. Only where the event rules allow digital registration.
attendance_type__vvv_attendance_typeContactVV → HSIn-person or virtual, for follow-up content.
HubSpot email and web engagementMarketing engagement summary in Vault CRMContactHS → VVOptional. Target object or field agreed with the Vault administrator.
06 — Auth & API

How are authentication and API limits handled?

Veeva grants API access through user permissions in each Vault and in Network. Values Veeva does not publish are marked for confirmation.

TopicVeevaHubSpot
Access modelAn integration user in the client's Vault with API access and permission on the agreed objects. A separate Network user with API access if Network is in scope.Self-serve in the client portal. Custom objects need an Enterprise hub; marketing events and subscription types are standard.
InterfacesVault REST API with VQL queries for Vault CRM; Network MDM API (REST, JSON) for search, retrieve and change requests. Veeva CRM, for clients not yet moved, through its platform's APIs; confirm with the client's admin.REST APIs: CRM objects, associations, marketing events, subscription preferences, custom events.
AuthenticationVault: session ID from a username and password, OAuth 2.0 / OpenID Connect profiles, or API access tokens scoped to a single Vault. Network: session ID from the auth endpoint.Private app access token or OAuth 2.0 public app, scoped per object.
Rate limitsVault: a burst limit per 5-minute window that varies by Vault (Veeva's example is 2,000 calls), reported in X-VaultAPI-BurstLimitRemaining; no daily limit enforced. Network: not published. Confirm with Veeva.Per-10-second burst and daily limits by subscription tier.
Change detectionIncremental VQL queries on last-modified time for each object. Field names confirmed in discovery.Writes are immediate; batch endpoints handle volume.
Bulk dataVault Platform's Direct Data API supports large extracts for the initial backfill. Confirm availability for the client's Vault.Imports API for the initial load.
Personal dataHCP personal data is stamped onto related records across Vault CRM. Deletion requests are handled in both systems under the client's privacy process.GDPR tools for deletion and legal basis; field-level permissions by team.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Platform transition during the projectHigh

If the client moves from Veeva CRM to Vault CRM during the engagement, the sync module's source changes. Agree in the SOW which platform comes first and make the switch a planned phase.

Consent must agree in both systemsHigh

Consent rules differ by country and channel. The compliance team signs the rules; the sync module applies them and logs every change for audit.

Promotional review and industry codesHigh

HubSpot emails to HCPs follow the client's medical, legal and regulatory review. PhRMA Code rules for events, and sunshine (transfer of value) reporting for meals or payments, are planning items for the compliance team.

Medical content and adverse eventsMedium

Call notes and medical inquiries stay in Veeva. If an HCP reply in HubSpot mentions an adverse event, the client's pharmacovigilance process applies; the routing rule is agreed before launch.

Duplicate HCPsMedium

An HCP who fills in a HubSpot form may already exist in Network. New HCPs go to Network as change requests, and HubSpot merges once the Network ID returns.

Burst limits and volumeLow

Vault applies a burst limit per Vault. The sync module reads the limit headers, throttles itself and uses bulk extracts for the backfill.

Opportunities in HubSpot

Coordinated field and digital journeysHigh value

Marketing sees which HCPs a rep has just called, and reps see which HCPs engaged with email or attended an event, so outreach complements rather than repeats.

Event promotion that fills seatsHigh value

Medical education events planned in Veeva are promoted from HubSpot to consented, targeted HCPs, with attendance flowing back for follow-up.

Consent captured once, honored everywhereHigh value

An opt-in or opt-out in either system reaches the other, so HCPs only receive what they agreed to.

Clean HCP data through NetworkMedium value

HubSpot contacts carry the Network ID and NPI, so lists and reports count each HCP once.

Segments that match the field structureMedium value

Specialty, territory and target flags let marketing build lists that mirror how the field force is organized.

Marketing reported by territoryMedium value

Engagement, event attendance and content reach by territory and target status, in HubSpot dashboards leaders can share with sales.

Coexistence plan

Field in Veeva, marketing in HubSpot.

Reps keep working in Veeva CRM and its successor, Vault CRM. Marketing runs HCP programs in HubSpot. The sync module keeps identity, consent and engagement aligned between them.

  1. Veeva Network sets who each HCP and HCO is; HubSpot matches on the Network ID and NPI.
  2. Consent is captured in either system and applied in both, under the compliance team's rules.
  3. Calls, territories and targets inform HubSpot segments; HubSpot engagement informs the rep.
  4. Events planned in Veeva are promoted and followed up in HubSpot, with attendance shared.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the vv_ prefix in a Veeva property group. Calls per year come from Vault CRM's territory field records, so HubSpot and Veeva reports agree.

Internal nameLabelObjectTypeSource / logic
vv_network_idVeeva Network IDContactSingle-line textveeva_network_id__v; unique
vv_npiNPIContactSingle-line textnpi__v; unique
vv_hco_network_idHCO Network IDCompanySingle-line textHCO veeva_network_id__v; unique
vv_account_typeHCP TypeContactDropdownAccount object type
vv_specialtySpecialtyContactDropdownspecialty_1__v
vv_territoryTerritoryContactDropdownterritory__v via account_territory__v
vv_is_targetTarget HCPContactSingle checkboxtsf__v my_target__v
vv_last_call_dateLast Rep CallContactDate pickerLatest call_date__v
vv_calls_ytdCalls YTDContactNumbertsf__v yearly_call_activity__v
vv_products_detailedProducts DetailedContactMultiple checkboxescall2_detail__v product__v
vv_approved_email_opt_typeApproved Email ConsentContactDropdownapproved_email_opt_type__v
vv_consent_captured_atConsent CapturedContactDate pickercapture_datetime__v of latest consent
09 — Scope builder

Interactive scope builder

Choose the data and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Every field is subject to the client's compliance rules. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Veeva × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Veeva HubSpot integration FAQ

Does Veeva CRM integrate with HubSpot?

Yes. Campaign Creators builds a custom integration on the Vault REST API and the Veeva Network API. It is built against Vault CRM, Veeva's go-forward CRM, and maps the equivalent Veeva CRM objects for a client that has not moved yet.

What data syncs between Veeva CRM and HubSpot?

HCP accounts sync to HubSpot contacts with their Veeva Network ID and NPI, and HCOs to companies. Consent records map to HubSpot subscription types, and call summaries, territory alignment and events reach HubSpot. HubSpot sends back opt-outs, new HCPs as Network change requests and, where approved, event registrations.

Which system owns which data?

Veeva Network owns HCP identity, Vault CRM owns field activity and territories, and HubSpot owns marketing engagement. Consent is shared under rules the compliance team signs, and an opt-out in either system reaches the other on the next sync cycle. Call notes, medical inquiries and samples stay in Veeva.

What does setting up the Veeva CRM HubSpot integration involve?

Seven phases, each closed by a client sign-off: platform and compliance inventory, access, identity and consent rules, the HubSpot data model, the build, backfill, and a two-week parallel run with content review approval of each email before workflows are switched on.

How long does the integration take and what does it cost?

Timeline and cost depend on the platform (Veeva CRM, Vault CRM or both during transition), the countries and objects in scope, and the compliance rules. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.