HubSpot's native Sales Navigator integration does not turn Navigator into a HubSpot sync. On eligible plans (Sales Hub Professional or Enterprise plus a paid Sales Navigator Advanced license) you get a viewing panel on Contact and Company records: icebreakers, related leads, InMail composed from the record. It does not create HubSpot contacts from the Navigator profiles you browse, it does not write LinkedIn profile fields into HubSpot properties, and it does not sync everyday DMs to the timeline.
If you prospect in Sales Navigator and report in HubSpot, the working workflow is: research in Navigator, capture the profile into HubSpot from that page, enrich on save, message in LinkedIn, let conversation sync log the thread, then run lists and follow-up in HubSpot.
SurroundR is the capture layer in that loop. One click from a LinkedIn or Sales Navigator profile. HubSpot stays the system of record.
Native panel vs capture workflow
Keep these jobs separate so you do not buy the wrong thing.
The native panel is useful when the HubSpot record already exists and you want Navigator context without leaving CRM. That is a viewing integration. It is a poor fit for "I just found this lead in Navigator and I need them in HubSpot now."
Capture is the opposite direction: you are on the Navigator profile, you click, HubSpot gets a Contact (or an update to the existing one). Enrichment and optional DM sync ride on that same motion.
The LinkedIn to HubSpot methods guide owns the full method comparison (manual, native, CSV, automation, extensions). If you are still choosing a category, start there. This post assumes you already live in Navigator and need the hands-on path into HubSpot.
Saved Navigator leads and InMail logging on compatible plans can still help. They do not replace everyday feed or inbox work outside that panel. Do not treat "we connected Sales Navigator" as "DMs and new profiles now land in HubSpot."
Sales Navigator to HubSpot, step by step
- Open the prospect in Sales Navigator. Stay on the lead or profile you are researching. Export is for batch sprints, not for the person in front of you.
- Capture the profile into HubSpot. One click from the Navigator profile creates or updates the contact: name, title, company, owner, lifecycle stage. Dedup matches on email, phone, or LinkedIn URL.
- Enrich on save. Verified email and mobile run through a waterfall of 20+ premium data vendors and write to standard Contact properties. No separate enrichment tab, no paste from another database.
- Message on LinkedIn and keep auto-sync on. Connection notes, follow-ups, and video DMs stay in the thread you already use. Auto-sync posts that conversation to the HubSpot timeline. See how to sync LinkedIn messages to HubSpot if logging is the only gap you still have.
- Work the record in HubSpot. Sequences, lists, owner, and reporting live in CRM once the person exists. Navigator remains research. HubSpot remains the system of record.
That is the daily loop. It is the same capture click the contact capture page describes, used on a Navigator profile instead of a feed profile. If OAuth screens or the first capture still look unfamiliar, the getting started guide is the install walkthrough. This post stays on the Navigator-shaped loop after you are connected.
What capture actually writes
The contact capture product page is the feature deep-dive: one click from LinkedIn, standard HubSpot Contact and Company objects, enrichment on save. Do not re-learn HubSpot objects here. The workflow fact you need is simple: capture from the page you are on, including Sales Navigator, and HubSpot is updated in about two seconds per contact.
Dedup matters more in Navigator than people expect. Teams pull the same buying committee from Account IQ, then from a lead list, then from a colleague's saved leads. Matching on LinkedIn URL (and email or phone once enrichment lands) is what stops three records for one human.
If a record already exists, you update it. You do not create a shadow contact because Navigator showed you a slightly different title.
After capture: the SDR job in HubSpot
Capture without a next step is just a cleaner pile of records. SurroundR for SDRs and BDRs is the persona page for prospecting that has to survive the evening: the list is already in HubSpot, DMs can sync, enrichment is on the record so you are not tabbing out for an email.
Use HubSpot for:
- Owner and lifecycle stage (set on capture, adjustable in CRM)
- Lists and views your manager actually inspects
- Follow-up tasks next to the rest of the pipeline
- Sequences you already run in HubSpot, not a second engagement platform unless you chose that stack on purpose
Use LinkedIn / Navigator for:
- Research, icebreakers, and the conversation
- InMail when your Navigator plan is the right channel
- The thread that auto-sync should be logging
If your team is still building the first HubSpot list from LinkedIn rather than working one profile at a time, use list building from LinkedIn to HubSpot. Batch CSV is a sprint tool. It is not the Navigator daily driver.
CSV and automation, used on purpose
A quarterly Navigator export into HubSpot can still be right: event-style sprints, a purchased list that originated on LinkedIn, RevOps batching. Data is stale the moment the file leaves LinkedIn. Dedup against missing emails is painful. Messages never come along.
Zapier, Make, or n8n can create HubSpot contacts when a row appears in a sheet. That is plumbing for a stable source, not a substitute for clicking a live Navigator profile. Fragile mappings and task limits belong in the methods guide, not in your Monday standup.
When those paths are the actual job, link out and use them. When the job is "this lead, this account, this afternoon," capture from Navigator.
Native InMail is not DM sync
On compatible HubSpot and Navigator plans, some InMail activity can show up as HubSpot activities. Everyday LinkedIn DMs outside that path do not. If coaching and forecast hygiene depend on "what did we actually say," you still want conversation sync on the contacts you captured.
Database tools answer a different question. Kaspr is built around reveal-and-export. Cognism is a curated B2B contact-data platform for cold outbound. Useful when prospecting starts from purchased data. They are not a Sales Navigator capture click into HubSpot with the thread attached. Keep Cognism as the database, SurroundR as the in-feed HubSpot layer, if you run both. Do not expect one to replace the other.
Put the workflow on the profile, not in a weekly import
Stay on the native panel only when the HubSpot record already exists and you want Navigator context inside CRM. The moment you are researching a new lead in Navigator, capture. If your team already runs a clean import every quarter, keep it. Do not make that import the way Monday's new leads enter HubSpot.
Open Navigator. Capture. Enrich on save. Talk on LinkedIn. Let the timeline update. Work the record in HubSpot.
That is how you connect Sales Navigator to HubSpot as a seller's loop, without pretending the native panel is a sync.
