Biopharma companies should keep the results of KOL mapping in HubSpot and leave the underlying research in the mapping platform. The results are each KOL's tier, therapeutic area, influence type, institution and role links, internal owner, and engagement summary. Claims data, publication databases, payment records, and scientific exchange notes stay in their own systems, and HubSpot links to them.
KOL lists usually start in a spreadsheet or a mapping vendor's platform, and the trouble begins when commercial, medical, and marketing teams each keep their own copy. One governed record in HubSpot gives everyone the same tier and owner for each expert, and it keeps payment and medical data where your compliance team expects to find it.
If you're designing that structure for the first time, our HubSpot onboarding team builds data models around how life sciences companies sell.
KOL mapping is the process of finding the experts who shape practice in a therapeutic area and measuring how much influence each one has. Teams score experts on publications, clinical trial roles, congress speaking, institutional affiliations, and referral networks, then sort them into tiers.
KOL identification finds the names, and KOL identification and profiling adds detail on each expert. Mapping ties those profiles into a network that shows who influences whom. US teams usually combine publications, trial roles, claims, affiliations, conference lists, and Open Payments data to build that network.
Open Payments is the federal program where the Centers for Medicare & Medicaid Services (CMS) publishes industry payments to clinicians, and it covers a lot of ground, with 667,898 US physicians holding at least one payment record for 2025.
The mapping itself usually happens in a dedicated KOL mapping tool or with a data vendor, since it depends on claims and publication databases HubSpot doesn't hold. HubSpot comes in once the map exists, as the place your teams plan and record their work with each expert.
The KOL data that belongs in HubSpot is the data your teams act on. That covers who each KOL is, how influential they are, how they connect to institutions and peers, and who owns the relationship.
| KOL data | Where it lives in HubSpot | Example values |
|---|---|---|
| KOL tier | Dropdown property on the contact | Tier 1 national, Tier 2 regional, Tier 3 local |
| Therapeutic area and specialty | Multiple checkboxes property | Oncology, hematology |
| Influence type | Multiple checkboxes property | Researcher, clinical leader, guideline author, digital opinion leader |
| Engagement readiness | Dropdown property | Not engaged, open to advisory work, active |
| Institution and role | Contact-to-company association with labels | Department chair, principal investigator |
| Peer relationships | Contact-to-contact association labels | Mentor and mentee, co-author |
| Internal owners | Contact owner plus a user property for the medical science liaison (MSL) | Field rep, MSL |
| Mapping source and score date | Text and date properties | Vendor name, last scored October 2026 |
| Engagement summary | Meetings, notes, and marketing events | Advisory board, webinar attended |
Each property needs one owner and one source, so a tier from your mapping vendor never competes with a tier a rep typed by hand.
Structure KOL data with the contact as the core record, custom properties for scores, association labels for relationships, and a custom object only for repeating programs. Build it in this order.
A handful of objects with clear labels is easier to report on than a new object for every program idea. When we worked with our client Torigen Pharmaceuticals, a veterinary pharma company, we consolidated 14 legacy objects into 6 and set up 4 company types (clinic, distributor, corporate owner, and group purchasing organization) so every team worked from the same structure.
Apply the same test before you decide when a custom object is worth it for KOL programs.
Professional covers custom properties, association labels, lists, and custom reports. Enterprise adds custom objects, Sensitive Data, and property-level access controls.
| HubSpot feature | Minimum tier | Use for KOL data |
|---|---|---|
| Custom properties | All tiers (limits vary by subscription) | Tier, therapeutic area, influence type |
| Marketing events | All plans (custom event reports need Professional) | Congress symposia, dinner programs |
| Association labels | Professional | Institution roles, peer links |
| Lists filtered by association label | Professional | Principal investigators by site |
| Custom report builder | Professional | KOL coverage and engagement reports |
| Custom objects | Enterprise | Advisory boards, speaker programs |
| Property view and edit restrictions | Enterprise | Medical-only fields |
| Sensitive Data properties | Enterprise | Fields that hold health or financial data |
The number of custom properties you can create depends on your subscription, so count your planned KOL fields against your limit early. Teams usually start on Professional with properties and labels, then move to Enterprise when they need program records or medical-only fields.
Match KOL records on the NPI, and set it up as a unique-value property before your first import. The NPI is a 10-digit numeric identifier for US health care providers, and it carries no other information, such as the provider's state or specialty. That makes it a clean match key, but specialty and therapeutic area still need their own properties.
For our client Torigen, same-named clinics in different cities had to be told apart, so a Record ID naming scheme kept HubSpot companies and QuickBooks Online customers linked in a two-way sync. One match key per KOL keeps tier updates, event attendance, and meeting history on a single record.
Track one-off meetings, such as congress symposia and dinner programs, with HubSpot marketing events, and use a custom object for advisory boards that meet over months.
Marketing events are available on all HubSpot plans. You can create in-person events by hand or sync webinars from apps like Zoom, Microsoft Teams, GoToWebinar, and Eventbrite. Each event shows how many contacts registered, canceled, and attended, and you can build segments from those statuses.
Contacts can't be added to an event from their own record, so load attendees through an import, a workflow, or a connected app. Workflows can update participant status only on events you created by hand.
Event attendance and reportable payments often overlap. For Program Year 2026, Open Payments excludes payments under $13.82 unless a clinician's annual total passes $138.13, so a congress dinner can count. Share HubSpot attendance lists with your aggregate spend team so they can check them against the payments they report.
Build reports that show KOL coverage, engagement recency, and tier movement, so medical affairs leaders can find gaps by tier and therapeutic area.
| Report | Question it answers | Data it uses |
|---|---|---|
| Tier 1 coverage | Does every Tier 1 KOL have an MSL owner? | Tier, MSL owner property |
| Engagement recency | Which Tier 1 and Tier 2 KOLs have had no MSL meeting in 90 days? | Tier, meetings |
| Event attendance by tier | Who attended our symposia, by tier and therapeutic area? | Marketing events, tier |
| Tier movement | What KOLs moved up or down since the last score? | Current tier, previous tier, last scored date |
| Institution footprint | How many KOLs and principal investigators work at each target institution? | Association labels, companies |
The custom report builder needs a Professional or Enterprise subscription, and it can combine data from several objects in one report. If some KOL fields are restricted to medical affairs, build those reports for the people who can see the fields, since reports can fail to load for users without access.
Raw mapping inputs, payment records, scientific exchange notes, and patient information should stay out of HubSpot. Each has a system built for it, and HubSpot only needs a status or a link.
When a field is borderline, store a link or a status in HubSpot and keep the detail in the system of record. Your compliance team and reporting vendor make the final call on what gets reported.
Keep KOL data separate from sales activity with teams, object permissions, property restrictions, and separate owner fields for MSLs and reps. MSLs engage KOLs on scientific evidence, and their records shouldn't drift into promotional workflows.
These controls sit alongside your broader permissions, consent, and sensitive data settings. Field reps can still run sequences for medtech and pharma sales on commercial contacts without touching medical records.
Keep KOL maps current by refreshing scores from your mapping source on a fixed schedule and stamping each record with the date it was last scored.
A dated score also tells medical affairs how much weight to give a tier when they plan the next round of outreach.
KOL data gets messy when every team keeps its own copy of the list. We design the HubSpot data model first, with properties, association labels, permissions, and custom objects where Enterprise fits. Then we connect your mapping vendor or aggregate spend system through HubSpot integration development.
We used the same model-first approach with our client Everis, a medical device maker, to migrate 129,326 records across 22 objects before its Salesforce deadline. If your KOL lists live in spreadsheets today, our team can help you build one structure your medical and commercial teams share.
Keep the results of KOL mapping in HubSpot. Tiers, therapeutic areas, relationship labels, owners, and engagement summaries give every team the same view of each expert, while raw data, payments, and medical records stay in their own systems.
Get your HubSpot portal set up right the first time with our onboarding team. Our Custom Object or Custom Property guide helps you decide how to store each KOL field before you build.