Loading tutorials…
Loading tutorials…
Sales Navigator CRM Sync is the difference between a lead-list silo and a real prospecting engine. Done right, every Sales Nav action (view, save, InMail, Smart Link share) lands in your CRM as activity. Done wrong, you pollute your CRM with thousands of stub records.
Who this is forRevenue ops, SDR leaders, and B2B sales teams on Sales Navigator Advanced Plus (the only tier with native CRM Sync). For Core/Advanced users, this tutorial covers the Zapier/integration workaround.
What you'll need
Step 1
Native CRM Sync is Advanced Plus only (~$1,600/user/yr). For Core/Advanced, use Zapier, Outreach, or Salesloft to bridge.
Native CRM Sync: included in Sales Navigator Advanced Plus only. Supports HubSpot, Salesforce, Microsoft Dynamics, and Oracle SalesCloud. Bidirectional sync — Sales Nav activity flows to CRM, CRM data flows back to Sales Nav (account ownership, account status).
Native sync is REAL-TIME (within 5-15 minutes). Workarounds are typically 5-60 minute lag.
For Core ($99/mo) or Advanced ($149/mo): no native sync. Workarounds: (1) Zapier — connects "New Saved Lead" trigger to CRM "Create Contact" action; (2) Outreach / Salesloft / Apollo — orchestrate Sales Nav workflows with native CRM sync built in.
Cost calculation: Advanced Plus = ~$133/user/mo. Advanced + Outreach = $149 + $130/seat/mo = $279/user/mo (more expensive but more orchestration). Advanced + Zapier = $149 + $20/mo (cheapest but most fragile).
For 5+ SDR teams: native CRM Sync (Advanced Plus) is almost always worth it. For solo founders or 1-2 person teams: Zapier workaround usually fine.
Step 2
Map Sales Nav fields to CRM fields explicitly. Decide: which Sales Nav actions create records vs update existing.
Sales Nav fields to map: Lead (person), Account (company), InMail Sent, InMail Reply, Smart Link Share, Smart Link View, Profile View, Note.
CRM destinations: Contact, Lead (in Salesforce), Account, Activity, Engagement, Note, Task.
Critical decision: do Sales Nav "Saved Leads" auto-create CRM Contacts? If YES, every saved lead becomes a CRM record — pollution risk. If NO, only manually-promoted leads enter CRM — controlled but more manual work.
Recommended pattern: Sales Nav Saved Leads do NOT auto-create. SDR manually promotes a lead to Contact when intent signal is real (InMail reply, demo request, deck open). This keeps CRM clean.
Field-level mapping: Sales Nav "Job Title" → CRM "Job Title." Sales Nav "Company" → CRM "Account Name." Sales Nav "LinkedIn URL" → custom CRM field "LinkedIn URL." Map fields one-to-one; do not auto-merge.
Document the mapping in a shared doc. Every CRM admin should be able to look up what syncs from where.
Step 3
Sales Navigator Admin Center → Settings → CRM Settings → connect your CRM via OAuth. Map fields. Enable activity writeback.
Open Sales Navigator → Admin Center (only visible to Admin Plus admins) → Settings → "CRM Settings."
Click "Connect CRM" → select your CRM (HubSpot / Salesforce / Microsoft Dynamics / Oracle SalesCloud) → OAuth-authorize.
Field mapping: LinkedIn shows default mappings (Lead → Contact, Account → Account). Override based on your plan from step 2.
Enable "Activity Writeback": Sales Nav actions (InMail sent/replied, Smart Link share, profile view) write back to CRM as Activities/Engagements. CRITICAL for sales/marketing alignment.
Enable "Account/Contact import": pulls existing CRM data into Sales Nav so reps can see "this contact is already in our CRM as [stage]."
Disable "Auto-create CRM Contact from Saved Lead" unless you have a specific use case.
Run a test: save one lead in Sales Nav → confirm it appears (or does NOT appear) in CRM per your mapping. Send a test InMail → confirm the InMail Sent activity appears in CRM within 15 minutes.
Step 4
Zapier → "LinkedIn Sales Navigator" trigger → "New Saved Lead" → action: HubSpot/Salesforce "Create or Update Contact."
Open Zapier → "Make a Zap." Trigger: "LinkedIn Sales Navigator" → "New Saved Lead."
Action: HubSpot "Create or Update Contact" OR Salesforce "Create or Update Contact/Lead." Use the dedup-on-email setting to prevent duplicates.
Field mapping: Sales Nav Name → CRM First/Last Name (split). Email (if available — Sales Nav does not always return email). Company → Account. Job Title → Job Title. LinkedIn URL → custom field.
Critical limitation: Sales Nav often does NOT expose lead email via Zapier. Workaround: use a 2-step Zap — Step 1 enrich with Apollo/Hunter to find email → Step 2 push to CRM.
Test: save one new lead in Sales Nav → wait 5-15 minutes → confirm Zap fires and CRM gets the record.
Cost: Zapier Starter plan ($20/mo) supports 750 Zap runs/mo — enough for 1-2 SDRs. Higher volume = Professional plan ($50/mo).
Step 5
Decide: which CRM Account owns this Sales Nav lead? Which CRM Contact maps to which Sales Nav Lead? Set ownership rules.
In CRM Sync settings: configure Account matching rule. Default = match by Company Name. Better = match by LinkedIn Company URL (more accurate for companies with name variants).
Configure Lead/Contact matching rule: by email (best), then by LinkedIn URL, then by first/last name + company (fallback).
Set ownership defaults: when Sales Nav syncs a new lead, who is the CRM owner? Options: the Sales Nav seat that saved the lead, an account-based round-robin, the existing CRM Account Owner if account is known.
For ABM teams: ownership should follow CRM Account Owner — the rep already working the account inherits any new contacts.
For inbound/SMB teams: ownership = round-robin by territory.
Document ownership rules and review monthly. Misallocated leads create rep conflict and miss SLAs.
Step 6
Weekly: audit duplicate records, stub contacts, failed syncs. Monthly: review field mapping for drift.
Weekly hygiene: in CRM, filter Contacts created in past 7 days WHERE Source = "Sales Navigator." Audit for duplicates, missing email, missing company. Clean or merge.
Weekly: check Sales Navigator → Admin Center → CRM Sync → "Sync Errors" tab. LinkedIn shows records that failed to sync (API errors, field mismatch, missing required fields). Resolve weekly to prevent backlog.
Monthly: pull a report of Sales Nav contacts vs CRM contacts. If counts diverge significantly (e.g., 1,000 Sales Nav leads vs 200 CRM contacts), sync is broken — investigate.
Monthly: review field mapping. CRM fields can change (custom field renames, new required fields) and break sync silently. Walk through mapping monthly.
Quarterly: full data hygiene sprint. Merge duplicates, remove stub records, archive closed-lost contacts. CRM rot compounds — quarterly resets prevent it.
Common mistakes
Auto-create enabled on Saved Leads
What goes wrong: Every Saved Lead becomes a CRM Contact. A 1,000-lead Sales Nav list creates 1,000 stub CRM records overnight. Sales reps complain that CRM is "full of junk" and ignore Sales Nav contacts entirely.
How to avoid: Disable auto-create. Promote leads to CRM manually only when intent signal is real (InMail reply, demo request, Smart Link re-open).
No email enrichment in Zapier flow
What goes wrong: Sales Nav does not expose email reliably. Your Zap creates CRM Contacts without email — useless for outreach. Sales team has hundreds of stub records they cannot email.
How to avoid: Add Apollo or Hunter enrichment step between Sales Nav and CRM. Costs $50-100/mo but transforms data quality.
No matching rules for accounts
What goes wrong: Sales Nav syncs "Acme Inc" while CRM has "Acme Corporation." Two different Account records get created. Account-based attribution breaks; ABM reports become meaningless.
How to avoid: Configure Account matching by LinkedIn Company URL (more accurate than name). For unmatched: route to a "Sales Ops Review" queue, not auto-create.
No activity writeback
What goes wrong: Sales reps send InMails, share Smart Links, take notes in Sales Nav. None of it appears in CRM. CRM-based forecasting and pipeline reports miss the actual sales activity.
How to avoid: Enable Activity Writeback in CRM Sync settings. Every InMail/Smart Link/Note becomes a CRM Engagement. Pipeline visibility transforms.
No ownership defaults
What goes wrong: New synced contacts have no CRM owner. They sit in an unassigned queue. SLAs miss. Reps fight over hot leads. Cold leads rot.
How to avoid: Set ownership rule: inherit CRM Account Owner if account exists, else round-robin by territory. Document the rule. Monitor for misallocation.
No sync error monitoring
What goes wrong: Failed syncs (field mismatch, API errors, missing required fields) accumulate. After 90 days, hundreds of records never made it to CRM. You discover during quarterly audit, by which time most leads are cold.
How to avoid: Weekly check of Admin Center → CRM Sync → Sync Errors. Resolve each week. Set up a Slack alert via Zapier if sync error volume spikes (>50/day).
Recap
Done — what's next
How to set up Sales Navigator account and lead lists (with saved searches and alerts)
Read the next tutorial
Hand it off
CRM Sync is the highest-stakes Sales Nav setup decision — get it right and pipeline visibility transforms; get it wrong and you pollute your CRM for years. A LinkedIn Sales Nav specialist (with HubSpot/Salesforce admin background) will design field mappings, configure activity writeback, set ownership rules, and stand up monitoring in 4-6 hours, typically $70-120. The data quality payback is permanent.
See specialist rates
No — CRM Sync (native, real-time, bidirectional) is Advanced Plus only (~$1,600/user/yr, 10+ seat minimum). Advanced ($149/mo) does NOT include native CRM sync. For Advanced users: use Zapier ($20-50/mo) or Outreach/Salesloft/Apollo as a bridge.
Advanced Plus supports: HubSpot, Salesforce, Microsoft Dynamics 365, Oracle SalesCloud. Other CRMs (Pipedrive, Zoho, Close) require Zapier or third-party integration tools.
Not reliably. Sales Nav exposes the LinkedIn profile and inferred company info, but email is only available when the lead has chosen to share it OR when an integration (Apollo, Hunter, ZoomInfo) is layered on top. For CRM Sync, plan to use an enrichment tool to fill the email gap.
Sales Nav actions appear in CRM within 5-15 minutes typically. Bulk operations (importing a saved list) can take 30-60 minutes. CRM-to-Sales-Nav direction (e.g., updating CRM Account Owner reflecting in Sales Nav) is similar — within 15 minutes.
Yes — Sales Navigator Admin Center → CRM Settings → "Field Mapping" supports custom field mappings on Contact, Lead, Account, and Activity objects. Useful for tagging the original Sales Nav saved list, the SDR who saved it, or the campaign context.
Records already synced REMAIN in CRM. New Sales Nav activity stops flowing. Historical CRM data still appears in Sales Nav (cached for ~30 days, then expires). If you reconnect later, only NEW activity from reconnection onward syncs — historical gap is lost.
LinkedIn Sales Navigator
Lead Lists and Account Lists are where Sales Navigator turns from a search tool into a pipeline engine. But 80% of teams treat them as static buckets that go stale within 60 days. This walks through the dynamic-list architecture, saved searches, and alert wiring that keeps lists self-refreshing.
LinkedIn Sales Navigator
InMails are Sales Navigator's scarce resource — 50 credits/month on Core, 150 on Advanced Plus. Each one costs LinkedIn ~$2-4 in opportunity. Spend them on a 1-touch generic pitch and you waste the whole month. Spend them on a researched 3-touch sequence and you build pipeline.
LinkedIn Sales Navigator
Relationship Explorer is the 2026 upgrade to TeamLink — it maps every connection your team has into target accounts, surfaces second-degree intros, and highlights mutual relationships. This is the warm-intro lever that turns cold outreach into champion-introduced conversations.
LinkedIn Sales Navigator
DIY Sales Navigator is fine — until it is not. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you are on.