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.
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.
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.
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.
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.
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.
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.
Seven areas matter to HubSpot. Four carry the integration, two add context, and one is a scope decision about the platform transition.
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.
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.
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.
Medical education and promotional events are planned in Veeva. HubSpot promotes them, handles digital registration where approved, and follows up on attendance.
Rep calls give marketing context: when the HCP was last seen and which products were detailed. HubSpot receives summaries only, never call notes.
Which territory and rep cover each HCP, and whether the HCP is a target. Marketing segments and reports follow the field structure.
A client still on Veeva CRM, or mid-transition, needs a plan for which platform the sync module reads first and when it switches.
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 Network owns HCP identity, Vault CRM owns field activity and territories, HubSpot owns marketing engagement. Consent is shared under rules the compliance team signs.
HubSpot receives call dates, counts and products detailed. Call notes, medical inquiries and samples stay in Veeva.
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.
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.
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.
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.
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.
Create the vv_ properties, HCP and HCO associations, subscription types per channel and topic, marketing event settings and team permissions in a HubSpot sandbox.
Build the Vault API client, identity resolver, consent engine, compliance filter, HubSpot writer, Network change request path and error replay.
Load HCP and HCO accounts, consent records, territory alignment and an agreed window of call and event history.
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.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Accounts & identity · account__v, Veeva Network | ||||
| veeva_network_id__v | vv_network_id | Contact | VV → HS | Match key #1. Links to Network vid__v. Unique. |
| npi__v | vv_npi | Contact | VV → HS | Match key #2 for US HCPs. |
| Name | firstname, lastname | Contact | VV → HS | Fill blanks only; Network is the master. |
| Primary email | Contact | VV → HS | Match key #3. Field name confirmed in discovery. | |
| specialty_1__v | vv_specialty | Contact | VV → HS | Drives specialty segments. |
| Object type (professional__v, kol__v) | vv_account_type | Contact | VV → HS | HCP type for segmentation. |
| HCO account (organization__v, hospital__v) | name, vv_hco_network_id | Company | VV → HS | HCOs as companies. |
| primary_parent__v | Contact to Company association | Contact | VV → HS | HCP's primary HCO affiliation. |
| New HCP from HubSpot form | Network change request | Contact | HS → VV | Submitted to Network for validation; not created directly in Vault CRM. |
| Consent · multichannel_consent__v | ||||
| opt_type__v (opt_in__v) | Subscription status (opted in) | Contact | VV → HS | Accepted only from approved capture sources. |
| opt_type__v (opt_out__v) | Subscription status (opted out) | Contact | ↔ Both | Opt-outs flow both ways on the next cycle. |
| channel_value__v | Contact | VV → HS | The address the consent applies to. | |
| capture_datetime__v | vv_consent_captured_at | Contact | VV → HS | Evidence of when consent was given. |
| consent_type__v, content_type__v | Subscription type | Contact | VV → HS | Mapped to HubSpot subscription types by topic. |
| approved_email_opt_type__v | vv_approved_email_opt_type | Contact | VV → HS | Account-level Approved Email status. |
| Calls & territories · call2__v, tsf__v | ||||
| call2__v call_date__v | vv_last_call_date | Contact | VV → HS | Most recent submitted call. |
| call2__v | Custom event: Rep call | Contact | VV → HS | Date, channel and products only. No call notes. |
| call2_detail__v product__v | vv_products_detailed | Contact | VV → HS | Multi-select of products detailed. |
| tsf__v yearly_call_activity__v | vv_calls_ytd | Contact | VV → HS | Year-to-date calls in the aligned territory. |
| tsf__v my_target__v | vv_is_target | Contact | VV → HS | Target flag for the aligned territory. |
| territory__v via account_territory__v | vv_territory | Contact | VV → HS | Territory name for segments and reports. |
| user_territory__v (rep) | hubspot_owner_id or vv_rep_name | Contact | VV → HS | Owner only if reps hold HubSpot seats. |
| Events & marketing engagement · em_event__v, em_attendee__v | ||||
| em_event__v | Marketing event | Marketing event | VV → HS | Event name, type, date and format. |
| em_attendee__v em_attendee_status__v | Marketing event participation | Contact | VV → HS | Invited, registered, attended; drives follow-up. |
| HubSpot event registration | em_attendee__v | Contact | HS → VV | Optional. Only where the event rules allow digital registration. |
| attendance_type__v | vv_attendance_type | Contact | VV → HS | In-person or virtual, for follow-up content. |
| HubSpot email and web engagement | Marketing engagement summary in Vault CRM | Contact | HS → VV | Optional. Target object or field agreed with the Vault administrator. |
Veeva grants API access through user permissions in each Vault and in Network. Values Veeva does not publish are marked for confirmation.
| Topic | Veeva | HubSpot |
|---|---|---|
| Access model | An 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. |
| Interfaces | Vault 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. |
| Authentication | Vault: 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 limits | Vault: 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 detection | Incremental VQL queries on last-modified time for each object. Field names confirmed in discovery. | Writes are immediate; batch endpoints handle volume. |
| Bulk data | Vault 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 data | HCP 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. |
Severity reflects impact on the SOW, not technical difficulty alone.
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 rules differ by country and channel. The compliance team signs the rules; the sync module applies them and logs every change for audit.
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.
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.
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.
Vault applies a burst limit per Vault. The sync module reads the limit headers, throttles itself and uses bulk extracts for the backfill.
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.
Medical education events planned in Veeva are promoted from HubSpot to consented, targeted HCPs, with attendance flowing back for follow-up.
An opt-in or opt-out in either system reaches the other, so HCPs only receive what they agreed to.
HubSpot contacts carry the Network ID and NPI, so lists and reports count each HCP once.
Specialty, territory and target flags let marketing build lists that mirror how the field force is organized.
Engagement, event attendance and content reach by territory and target status, in HubSpot dashboards leaders can share with sales.
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.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| vv_network_id | Veeva Network ID | Contact | Single-line text | veeva_network_id__v; unique |
| vv_npi | NPI | Contact | Single-line text | npi__v; unique |
| vv_hco_network_id | HCO Network ID | Company | Single-line text | HCO veeva_network_id__v; unique |
| vv_account_type | HCP Type | Contact | Dropdown | Account object type |
| vv_specialty | Specialty | Contact | Dropdown | specialty_1__v |
| vv_territory | Territory | Contact | Dropdown | territory__v via account_territory__v |
| vv_is_target | Target HCP | Contact | Single checkbox | tsf__v my_target__v |
| vv_last_call_date | Last Rep Call | Contact | Date picker | Latest call_date__v |
| vv_calls_ytd | Calls YTD | Contact | Number | tsf__v yearly_call_activity__v |
| vv_products_detailed | Products Detailed | Contact | Multiple checkboxes | call2_detail__v product__v |
| vv_approved_email_opt_type | Approved Email Consent | Contact | Dropdown | approved_email_opt_type__v |
| vv_consent_captured_at | Consent Captured | Contact | Date picker | capture_datetime__v of latest consent |
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.
Based on public documentation. Object and field names, API access and limits are confirmed with the client's Veeva administrator and compliance team during discovery.
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.
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.
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.
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.
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.