How to Setup Notion CRM with Microsoft Dynamics 365 (2026 Guide)

Why Use Microsoft Dynamics 365 with Notion

Microsoft Dynamics 365 is a full-scale enterprise CRM handling complex sales workflows, customer service, and operations. Notion is a flexible workspace that some teams use as a lightweight CRM — tracking deals in databases, managing pipelines with Kanban boards, and storing customer notes in linked pages. Using both together makes sense when certain teams need a simpler, more collaborative way to interact with customer data without navigating the full complexity of Dynamics 365.

Product teams, customer success managers, and founders at growing companies often prefer Notion's familiar interface for deal tracking and account planning. When the organization also runs Dynamics 365 for its enterprise sales force, connecting the two ensures that lightweight tracking in Notion stays aligned with the official CRM data. Key deals, contact details, and pipeline stages can flow between both tools.

This setup is also useful during transitions. A startup that outgrows Notion as a CRM and adopts Dynamics 365 can maintain Notion for internal documentation and planning while migrating customer data to Dynamics 365. The integration bridges the gap during the transition period and can persist afterward for teams that still benefit from Notion's flexibility.

What You Can Do

• Sync key deal and contact data from Dynamics 365 to Notion databases for easy reference
• Use Notion as a collaborative workspace for account planning linked to Dynamics 365 records
• Push new deals or contacts created in Notion to Dynamics 365
• Create lightweight pipeline views in Notion using live Dynamics 365 data
• Maintain customer notes and meeting logs in Notion, linked to Dynamics 365 contacts
• Connect via Zapier, Make, or the Notion and Dynamics 365 APIs
• Build team wikis in Notion enriched with real-time CRM metrics

Prerequisites

• A Microsoft Dynamics 365 account with API access
• A Notion account (Plus plan or higher for API access and advanced database features)
• A Notion integration (internal integration) created at notion.so/my-integrations
• Admin access to Dynamics 365 and Notion workspace
• An integration platform: Zapier, Make, or Power Automate with HTTP actions
• Notion databases set up for the data you want to sync (contacts, deals, accounts)
• Azure AD app registration for Dynamics 365 API access

Step-by-Step Setup Guide

Step 1: Design Your Notion CRM Databases

Create a Notion database for each type of record you want to track. A typical setup includes a Contacts database, a Deals database, and an Accounts/Companies database. For each database, add properties that mirror the key Dynamics 365 fields: Name, Email, Company (as a relation to the Accounts database), Deal Value, Stage (as a select property), Close Date, and Owner. Add a "Dynamics 365 ID" property (text type) to store the unique record identifier from Dynamics 365 — this is essential for the sync to work. Share each database with your Notion integration by clicking the three-dot menu and selecting "Connect to" your integration.

Step 2: Create API Connections

In Notion, go to notion.so/my-integrations and create a new internal integration for your workspace. Copy the integration token. In Azure Active Directory, register an application for the Dynamics 365 integration. Add Dynamics CRM API permissions and generate a client secret. If using Zapier, you can authenticate both services directly through Zapier's connection flow — Notion uses OAuth and Dynamics 365 uses the registered app credentials. Test both connections before building workflows.

Step 3: Build the Dynamics 365 to Notion Sync

Create a workflow in your integration platform triggered by new or updated opportunities in Dynamics 365. For each triggered record, search the Notion Deals database for a page with a matching Dynamics 365 ID. If a match is found, update the existing Notion page with the latest data. If no match exists, create a new page in the Notion database and populate all mapped properties, including the Dynamics 365 ID. Repeat this pattern for Contacts and Accounts. Run the workflows and verify data appears correctly in Notion.

Step 4: Set Up Notion to Dynamics 365 Updates

If your team updates deal information in Notion (such as adding notes, changing stages, or updating close dates), you need a reverse sync. Use a Zapier trigger for "Updated Database Item" in Notion or a Make Notion module watching for changes. When a Notion page is updated, use the stored Dynamics 365 ID to find and update the corresponding Dynamics 365 record. Be selective — only sync fields that are actively managed in Notion. Add a "Last Synced" timestamp property to Notion to track when each record was last updated by the integration.

Step 5: Link Notion Pages for Rich Context

One of Notion's strengths is its ability to combine database records with rich content. For each synced deal, add a Notion template that includes sections for meeting notes, action items, competitor analysis, and account strategy. Sales reps and account managers can fill in this rich context in Notion while the hard data (deal value, stage, close date) syncs to Dynamics 365. This approach gives teams a collaborative workspace without cluttering the enterprise CRM with unstructured notes.

Step 6: Test, Validate, and Train Your Team

Test the sync by creating a deal in Dynamics 365 and verifying it appears in Notion with all fields populated. Update the deal stage in Dynamics 365 and confirm the Notion page updates. Then update a field in Notion and verify it flows back to Dynamics 365. Document the workflow for your team: which fields to update in Notion vs. Dynamics 365, how often the sync runs, and what to do if data looks out of date. Create a simple guide in your Notion workspace explaining the integration.

Practical Examples

Account Planning in Notion

Strategic accounts from Dynamics 365 sync to a Notion database. Each account page includes live data from Dynamics (revenue, deal count, contact list) plus Notion-native content: SWOT analysis, relationship maps, meeting notes, and strategic goals. Account managers collaborate on plans in Notion while deal execution stays in Dynamics 365.

Founder-Led Sales Tracking

A startup founder tracks early-stage deals in Notion using simple Kanban views. When the company adopts Dynamics 365 for its growing sales team, the founder's Notion pipeline syncs key deals to Dynamics 365. The founder continues using Notion's familiar interface while the sales team works in Dynamics 365. Both see the same pipeline data.

Customer Success Playbooks

Customer accounts sync from Dynamics 365 to a Notion database managed by the customer success team. Each account page in Notion includes onboarding checklists, health score tracking, and renewal planning — all as Notion templates. Health scores and renewal dates sync back to Dynamics 365 so sales reps see customer status alongside revenue data.

Weekly Pipeline Reviews

A Notion dashboard pulls live deal data from the synced Deals database. The sales manager runs weekly pipeline reviews using Notion's filtered views and inline discussions. Action items from the review are tracked as Notion tasks linked to the relevant deal pages. Deal updates made during the review sync back to Dynamics 365 overnight.

Tips and Troubleshooting

• Notion API rate limits: The Notion API allows 3 requests per second. For initial bulk syncs, implement rate limiting in your integration workflows to avoid hitting this limit.
• Use Dynamics 365 ID as the anchor: Every Notion page synced from Dynamics 365 must store the Dynamics record's unique ID. Without this, the integration cannot reliably match records and will create duplicates.
• Notion select property values must exist: If you sync a deal stage from Dynamics 365, the corresponding select option must already exist in the Notion database property. Pre-populate all possible stage values in Notion before enabling the sync.
• Handle relations carefully: Notion's relation properties link pages within the workspace. When syncing contacts and companies separately, you may need a two-pass approach: sync companies first, then sync contacts and set up the relation using the company's Notion page ID.
• Avoid syncing everything: Notion works best when it contains a curated, manageable dataset. Sync only active deals, key accounts, or specific segments rather than your entire Dynamics 365 database.
• Template pages for consistency: Create a Notion template for synced deal pages so that every new record arrives with the same structure for notes, action items, and planning sections.