The most dangerous moment in any integration project is the one right after the connection succeeds. The status turns green, everyone exhales, and the meeting ends — and nobody asks the question the green checkmark was hiding: what exactly did we just agree to move between these two systems? When I connected Sales Navigator to my Dynamics 365 trial (the wiring is covered in Two Systems, One Conversation), the connection was maybe a third of the work. The rest lives in four quiet pages of admin settings that decide what flows into Sales Navigator, what writes back into your CRM, and how the two systems agree that a record on one side is the same human as a record on the other.
This post walks through those four pages — Summary, Imported from CRM, Exported to CRM, and CRM Mapping — with the choices I made and the reasoning behind each. None of them takes more than a few minutes to configure. All of them are decisions your future self will wish you had made on purpose.
Why “leave the defaults and move on” falls short
This sync is bidirectional, and one of those directions writes into your CRM. That means these toggles are not preferences — they’re data governance. Whether Sales Navigator is allowed to create brand-new contact records, whether it can update existing ones, whether every InMail a rep sends gets logged to the timeline: each of these changes what lives in Dataverse, who created it, and what your reporting looks like six months from now. The settings deserve the same five minutes of deliberation you’d give a new user’s security role. Defaults are somebody else’s decisions.
Everything below lives in Sales Navigator at Admin Settings, under the CRM heading — you’ll see your connection listed there (mine is a Sandbox; a Production slot sits alongside it, and the two are configured independently).
Page 1 — Summary: Connection Health and the Match Data Report
The Summary page confirms the connection (Microsoft Dynamics 365 Sales with a green check), states your access level — mine reads Read and write, meaning export to CRM is possible — and hosts the report you’ll come back to more than any other: the Match Data Report. Every 24 hours, Sales Navigator compares your CRM’s accounts, contacts, and leads against LinkedIn’s graph and reports how many it confidently matched. Matching is the foundation for everything else — auto-save, CRM badges, activity write-back all depend on the two systems agreeing on who’s who.
Two things on this page are worth a habit. First, Sample unmatched data exports up to a thousand CRM records that couldn’t be matched, based on what was present — or absent — in those records. Low match rates are almost never LinkedIn’s fault; they’re empty email and job-title columns talking. Second, the users table at the bottom has a CRM User Match column: Sales Navigator also has to match your sellers (so it knows whose activities to write back to which CRM user), and it does it by email address. Mine says Not Matched because my Sales Navigator identity and my trial admin account use different email addresses — the fix is a manual mapping on the CRM Mapping page’s User tab, not panic.
Page 2 — Imported from CRM: What Flows Into Sales Navigator
This page governs the CRM → Sales Navigator direction, and it’s essentially one big decision: Auto-save leads, contacts, and accounts. With it on, every seller’s relevant CRM records — the contacts and accounts attached to their open opportunities — are automatically saved as leads and accounts in their Sales Navigator, without anyone hand-picking them. This is the setting that makes Sales Navigator feel pre-loaded on day one instead of empty.
The dropdown underneath is easy to skip and shouldn’t be: at which stage does your sales team consider an opportunity to enter your pipeline? Auto-save imports the accounts and leads for open opportunities past that stage. Set it to your real qualification gate and the import stays focused on deals that matter; leave it at “Not sure” and Sales Navigator makes its own guess. Restricted data mode is the privacy lever on this page — turn it on and opportunity details are visible only to the opportunity’s owner rather than all seat holders. I left it off in a one-man trial; in a real org, that’s a conversation with your sales leadership, not a solo admin decision.
Page 3 — Exported to CRM: What Writes Back (the One to Read Twice)
Here’s the direction that modifies your CRM, toggle by toggle. This is the page where I slow down, because every switch is an answer to the question “what is LinkedIn allowed to do inside Dataverse?”
From the top, and how I chose:
- Validate CRM Data — on. This is the sleeper feature of the whole integration: Sales Navigator flags CRM contacts who are out of date — the champion who quietly changed companies — because LinkedIn is usually the first place that change shows up. It powers “at risk” insights in Dynamics, and it deserves (and will get) its own post in this series once my sync has had time to chew on real data.
- Create contacts / Update contacts — both on. Reps can push a Sales Navigator lead into Dynamics as a contact, and matched contacts can be enriched from LinkedIn. The Customize expanders let you constrain how creation behaves — worth opening before a wide rollout, especially if you have duplicate-detection rules with opinions.
- Create leads / Update leads — I turned these off, deliberately. My trial treats the contact table as the front door, and I’d rather not have a second machine minting lead records outside my qualification process. If your org runs lead-first, flip them on and make sure ownership defaults land with the right team.
- The logging block — Smart Links, calls, notes, messages and InMails, connection requests — all on. This is what makes LinkedIn outreach visible on the Dynamics timeline instead of trapped in a rep’s inbox: the InMail thread lands on the contact record where the whole account team can see it. Note the checkbox under messages and InMails that requires logging rather than leaving it per-rep — tempting for pipeline hygiene, but tell your sellers before you flip it. Reps deserve to know what’s being written home.
⚠️ Important: write-back means records created and edited by an integration. Loop in whoever owns your duplicate-detection rules and data-quality dashboards before you enable contact creation org-wide — they’d rather hear it from you than discover it in an audit filter.
Page 4 — CRM Mapping: How the Two Systems Agree on Fields
The last page is the dictionary. For each entity — Contact, Lead, Account, Opportunity, and User — it lists the Sales Navigator field, the CRM field it maps to, the direction data flows between them, and an example value. Certain rows are labeled Field used for matching: those are the columns the matching engine leans on, which makes this page double as a data-hygiene priority list. If a field used for matching is empty across half your contacts, you now know exactly why your Match Data Report is modest.
Out of the box the mappings are sensible — Address to Address, Department to Department — and if your Dynamics org is vanilla you may never touch Edit. The moment you’re storing job titles or emails in custom columns, though, this is where you tell Sales Navigator about it. And as promised above, the User tab is where a mismatched seller identity gets manually mapped to the right systemuser, which un-sticks their activity write-back.
Governance and Good Habits
- Configure Sandbox and Production separately, in that order. The two slots are independent — rehearse your toggle decisions against a sandbox before your production org learns them the hard way.
- Check the Match Data Report a day after connecting, then monthly. The first report tells you whether your CRM data is match-ready; the trend tells you whether your hygiene is improving or decaying.
- Write your toggle decisions down. A one-page note — “leads off because…, required InMail logging deferred because…” — turns next year’s “why is it like this?” into a thirty-second answer.
- Tell the reps what’s logged. Activity write-back is a gift to account teams and a surprise to sellers who weren’t told. Surprises erode trust in the tool; a heads-up costs one email.
Wrapping Up
A green checkmark says the pipe is connected; these four pages decide what the pipe carries. An hour here buys you a sync that imports the right book of business, writes back only what you’ve blessed, logs the outreach your account teams actually need to see, and tells you — every 24 hours — how well your two systems agree on reality. Connect deliberately, configure deliberately, and the integration stops being a checkbox on a project plan and starts being infrastructure. The gates only open when the lock-keeper says so — and now the lock-keeper is you.
