Skip to content
CRM ⇄ Business productivity

Microsoft Dynamics 365 Sales to Notion integration — real-time, two-way sync

Keep Microsoft Dynamics 365 Sales and Notion in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Microsoft Dynamics 365 Sales and Notion

Sync what happens in Notion with the customer records in Microsoft Dynamics 365 Sales, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Notion holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Formula and Rollup properties, Users, Comments, Files and attachments in Notion to Orders, Invoices, Activities, Custom Tables in Microsoft Dynamics 365 Sales with bi-directional, real-time sync. Activity and record changes in Notion update the matching contact or account in Microsoft Dynamics 365 Sales, and CRM data flows the other way wherever Notion can store and use it.

Common use cases

  • 01 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
  • 02 Read Notion wiki Pages and their Blocks into a database or search index for internal knowledge retrieval.
  • 03 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.
  • 04 Run a two-way dual-run between Dynamics and another CRM during a migration.

Common sync patterns

Where Notion can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Microsoft Dynamics 365 Sales sync into Notion, so people working there have the context without switching tools.

Where Notion supplies contact or company data

Enriched fields land directly on records in Microsoft Dynamics 365 Sales, and refreshes keep them from going stale.

What you can sync between Microsoft Dynamics 365 Sales and Notion

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Microsoft Dynamics 365 Sales objects Notion objects How this pairing syncs
Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. Files and attachments File-property and file-block values. Notion-hosted URLs are temporary and expire, so files are re-fetched or copied at sync time. Opportunities is specific to Microsoft Dynamics 365 Sales and Files and attachments to Notion — each maps to any object or custom field on the other side.
Quotes Pricing proposals; often synced with CPQ or ERP pricing data. Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. Quotes is specific to Microsoft Dynamics 365 Sales and Pages to Notion — each maps to any object or custom field on the other side.
Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. Databases / Data sources Collections of pages with a typed property schema. Since the 2025-09-03 API a database is a container holding one or more data sources; syncs target a specific data_source_id. Orders is specific to Microsoft Dynamics 365 Sales and Databases / Data sources to Notion — each maps to any object or custom field on the other side.
Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. Invoices is specific to Microsoft Dynamics 365 Sales and Properties to Notion — each maps to any object or custom field on the other side.
Activities Emails, calls, appointments, and tasks; read out for activity analytics. Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Activities is specific to Microsoft Dynamics 365 Sales and Blocks to Notion — each maps to any object or custom field on the other side.
Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Custom Tables is specific to Microsoft Dynamics 365 Sales and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 Sales and Notion

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Microsoft Dynamics 365 Sales Notion Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.

Notion Microsoft Dynamics 365 Sales Sub-second propagation

DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.

DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
  • Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
What ships with Microsoft Dynamics 365 Sales ⇄ Notion

Connect Microsoft Dynamics 365 Sales and Notion for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365 Sales–Notion connection.

Real-time

Two-way sync

Changes in Microsoft Dynamics 365 Sales or Notion instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics 365 Sales or Notion data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Microsoft Dynamics 365 Sales or Notion record.

Observability

Monitoring

Track your Microsoft Dynamics 365 Sales ⇄ Notion sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 Sales and Notion.

How the Microsoft Dynamics 365 Sales and Notion connectors work

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.

Notion

Integration surface
REST API (api.notion.com/v1)
Authentication
OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header
Change detection
Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
Capabilities
read · write · webhooks
Rate limits
Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
How it works

How to connect Microsoft Dynamics 365 Sales to Notion — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Microsoft Dynamics 365 Sales and Notion with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Microsoft Dynamics 365 Sales connected
    Notion connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics 365 Sales and Notion objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Microsoft Dynamics 365 Sales ⇄ Notion
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Microsoft Dynamics 365 Sales Notion
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Dynamics 365 Sales and Notion integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 436 integrations available for Microsoft Dynamics 365 Sales and Notion.

Popular · 8 of 436
All Microsoft Dynamics 365 Sales integrations All Notion integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own