Veeva OpenData vs IQVIA OneKey: How to Choose Your HCP Reference Data in 2026

Veeva OpenData vs IQVIA OneKey: the short answer

Veeva OpenData vs IQVIA OneKey is a choice between two HCP and HCO reference data services that now cover the US at a similar scale, so the decision rests on fit rather than raw size. OpenData is the natural default if you run Vault CRM or Veeva Network and want fast, built-in change requests. OneKey is the stronger pick if your analytics already run on IQVIA prescription and sales data such as Xponent and DDD, or you need its depth on organisations, purchasing relationships and integrated delivery networks.

Until August 2025 that choice was also a choice of ecosystem. On 18 August 2025 IQVIA and Veeva settled every pending dispute and signed third-party access agreements, so IQVIA data can now be used in Veeva Network, Veeva Nitro and Veeva AI, and Veeva data with IQVIA software. You can pick the data on its merits and keep the CRM you have.

This guide puts the vendors' own published figures side by side, explains what the agreement changed in practice, gives a scorecard and a test you can run on sample files before signing, and covers the switching work most comparisons skip. It is written for commercial operations, data and IT leads at pharma and biotech companies, and for anyone approving the contract.

What HCP reference data is, and why the choice matters

HCP reference data is the master list of healthcare professionals and organisations your commercial systems hang off: names, addresses, specialties, NPI and licence details, sample eligibility, and the affiliations that say which doctor works at which hospital and which hospital belongs to which health system. Your CRM, your targeting, your incentive compensation, your sampling compliance and every prescriber-level report all key off these records.

That is why switching or choosing badly is expensive. A reference data provider issues its own identifier for every HCP and HCO, and those identifiers end up stitched into call history, territory alignments, segmentation and warehouse tables. Change provider and every one of those joins has to be remapped. Pick a provider with weak affiliations and your account-based reporting will be wrong in ways nobody notices until a brand review.

Reference data is not the same as a master data management platform. OpenData and OneKey supply the records. A platform such as Veeva Network, Informatica or Reltio matches them against your own sources and decides which value wins. Most mid-sized companies need both, which we cover in our guide to enterprise MDM implementation.

OneKey vs OpenData by the numbers: published US figures

Both vendors publish US coverage figures. The table uses each vendor's own material: IQVIA's OneKey Reference Data fact sheet dated March 2025, and Veeva's OpenData US product page, read in October 2026.

Do not read the HCO row as a win for either side. Two million against 746,211 looks decisive, but the vendors count organisations differently: what one treats as a single hospital with departments, another may hold as several records. The same applies to affiliations. The only fair comparison is your own: send both vendors a sample of your target accounts and count matches, as described below.

Outside the US, Veeva lists OpenData coverage in 52 countries across Europe and Canada, 24 in Latin America, 11 in Asia Pacific, 22 across the Middle East, Turkey and Africa, plus China, Hong Kong and Macao. If you sell in several regions, check each market you need, not the global total, because quality varies by country for every provider.

What the 2025 IQVIA and Veeva agreement changed for buyers

For most of the last decade the two companies were in litigation over third-party access, the permission a pharma company needs before one vendor's data can sit inside another vendor's software. In practice that pushed buyers toward matching pairs: OpenData with Veeva, OneKey with IQVIA tools. Back in 2018, Pharmaceutical Commerce reported Indivior moving to OpenData to replace systems holding what it called 17 versions of the same data source, a good picture of the duplication those walls created.

The 18 August 2025 announcement ended that. According to IQVIA's press release, the companies signed master data and software third-party access agreements that allow IQVIA or Veeva data to be used with each other's software in customer instances, including IQVIA data in Veeva Network for MDM, Veeva Nitro for analytics and Veeva AI. IQVIA also joined Veeva's technology, AI and services partner programmes to support integrations with IQVIA analytics, MDM and commercial orchestration offerings.

Three practical consequences follow:

• Moving to Vault CRM no longer forces a data switch. Veeva has set 31 December 2029 as end of support for legacy Veeva CRM, so many companies are migrating now. A OneKey customer can keep OneKey through that move. Our Vault CRM vs Salesforce Life Sciences Cloud comparison covers the CRM side.
• Running both is now workable. Some companies use one provider as the primary source and license the other for specific markets or attributes, with Network or another MDM tool deciding which value wins.
• The negotiation has changed. With lock-in weaker, the vendor you do not currently use is a credible alternative, which is worth using in renewal talks.

What the agreement does not do is make the data interchangeable. Identifiers, hierarchies, specialty codes and change request workflows still differ, and those differences are where the real switching cost sits.

Which HCP reference data provider fits your situation?

Veeva-centric

OpenData is delivered through a productised integration with Vault CRM, Veeva CRM and Network, and reps can raise change requests from inside CRM. If your stack is mostly Veeva and your analytics do not depend on IQVIA prescription data, OpenData usually means the least integration work.

IQVIA-centric

If Xponent, DDD or LAAD already drive targeting, sizing and incentive compensation, OneKey is designed to connect directly to them, so prescriber and account joins take less building. Since 2025 you can still load OneKey into Network or Vault CRM.

Account-based

Specialty and hospital products live or die on affiliations. OneKey publishes IDN and corporate parent counts; Veeva publishes a larger affiliation total across HCP to HCO and HCO to HCO links. Test both against your own top accounts rather than trusting either headline.

Emerging biopharma

You have no legacy identifiers to protect, which is the cheapest moment to choose. Decide on CRM and syndicated data at the same time, because the reference data should match whichever prescription and claims data you license.

The evaluation scorecard: eight things to test

• Match rate on your accounts

  Send each vendor a de-identified list of your top HCPs and accounts with NPI where you have it. Count exact matches, probable matches and misses.

  • Use the same list for both
  • Split results by specialty and region

• Affiliation and hierarchy accuracy

  Pick 50 accounts your field team knows well and check whether the parent, child and HCP affiliations match reality.

  • Ask reps to verify a sample
  • Look for missing outpatient sites

• Change request speed

  Veeva publishes 99% of change requests resolved within 3 days. Ask IQVIA for its figure in writing, and test both with real requests during the trial.

  • Measure, do not take the brochure
  • Check who can raise a request

• Compliance fields

  Licence status, sample eligibility and state licence data drive sampling compliance. Confirm which fields are included in the base licence.

  • Map to your sampling rules
  • Check refresh frequency

• Delivery and integration

  API, flat files or CRM connector: confirm which you get, how often, and whether incremental changes are flagged so your pipeline is not reloading everything.

  • Ask for a sample delta file
  • Confirm the schema documentation

• Permitted use and exportability

  Read what the licence lets you do with the data: which vendors may host it, whether it can go into your warehouse, and what happens to derived data if you leave.

  • Name your agencies and vendors
  • Ask about termination rights

• Joins to your other data

  Score how easily the identifiers link to the prescription, claims, specialty pharmacy and CRM data you already license.

  • Count crosswalks you would need
  • Ask who maintains them

• Total cost over the term

  Licence fees, email add-ons, extra markets, integration build and the one-off cost of remapping identifiers if you switch.

  • Neither vendor publishes list prices
  • Price switching as a separate line

How to test both providers before you sign

A worked example: what switching actually involves

Consider a mid-sized specialty pharma company with 40 reps on legacy Veeva CRM, OneKey as its reference data, and a commercial warehouse fed by Xponent and specialty pharmacy data. It is moving to Vault CRM and wants to know whether to switch to OpenData at the same time.

Licence fees are only one part. Here is the work list for a switch, counted in objects rather than hours, because the hours depend on how clean the current data is:

• Identifier crosswalk. Every HCP and HCO in CRM, the warehouse and territory files carries a OneKey ID. Each needs a mapped OpenData ID, and the records that do not match one to one need a person to resolve them.
• Historical data. Years of calls, samples and events reference the old IDs. They either get remapped or reporting has to read through the crosswalk forever.
• Prescription joins. Xponent links most directly to OneKey, so the warehouse would need a maintained crosswalk between OpenData and the IQVIA prescriber records.
• Alignments and rosters. Territory alignments, call plans and incentive compensation files are rebuilt on the new IDs, and the quarter the switch lands in needs a reconciliation.
• Hierarchies. Account roll-ups change because the parent and child structures differ, so account-level targets and dashboards shift even when nothing changed in the market.

For this company, the honest conclusion is often to keep OneKey through the CRM migration, since the 2025 agreement allows it, and reassess at the next renewal once Vault CRM is stable. Doing both changes in one quarter doubles the reconciliation burden. The reverse also holds: an OpenData customer with no IQVIA prescription data has little reason to move. Switching pays when the current provider is visibly failing on coverage or change requests in your test, not because the other brand is bigger.

The crosswalk, matching and reconciliation work is where we spend most of our time on these projects. Our guide to matching in MDM explains the rules behind it.

Common mistakes when choosing HCP reference data

• Comparing headline counts

  More records can mean more duplicates or a different definition of an organisation. Only a match test on your accounts tells you anything useful.

• Deciding without the field

  Reps and operations staff know which addresses and affiliations are wrong. Leave them out of the test and you miss the most useful signal.

• Ignoring licence terms

  Restrictions on agencies, warehouses or derived data surface later as blocked projects. Read permitted use before price.

• Switching mid-migration

  Changing CRM and reference data in the same quarter stacks two reconciliations on one team. Sequence them.

• Treating reference data as MDM

  A vendor file does not resolve conflicts with your own CRM, specialty pharmacy and claims records. That needs match and survivorship rules.

• No owner after go-live

  Change requests, crosswalk exceptions and new markets need a named owner, or quality drifts within a year.

When you need neither, or both

You may need neither yet if you are pre-commercial with no field force, or you call on a small, stable universe of specialists that your team can maintain from NPI registry data and its own research. A full reference data licence is built for field teams and national targeting. Revisit it when you hire reps or plan a launch.

You may need both if you sell in many countries and one provider is clearly stronger in some of them, or if you need OneKey hierarchies for account-based selling while your CRM runs on OpenData. Since 2025 that is contractually workable, but it needs an MDM layer with clear survivorship rules so the two sources do not overwrite each other. Our article on survivorship and the golden record explains how those rules work.

Whichever you choose, the reference data is only as useful as its joins to the rest of your commercial data: CRM activity, prescriptions, claims and specialty pharmacy feeds. That joined layer is what our specialty pharmacy analytics work is built on.

How Greenwolf helps

We do not resell either vendor's data and we are not paid by either, so our only interest is that the choice fits your systems. Our founder came up through pharma commercial operations consulting at ZS, and we work on Veeva Network, Informatica and Reltio as well as warehouse-based masters.

On a reference data decision we typically run the match test, score the results, map the integration into your CRM, MDM and warehouse, and price the switching work honestly. If you go ahead, we build the crosswalks, the feeds and the reconciliation, and support the team that owns it afterwards.For a specialty therapy provider whose identifiers did not line up across sources, building clean identifiers and an MDM structure with automated pipelines cut manual reporting work by 60 to 80 percent. See our Veeva CRM data integration service for how this connects to a Vault CRM move, and MDM implementation services for the platform work.

Questions about Veeva OpenData and IQVIA OneKey