Skip to content
ERP ⇄ Business productivity

Dynamics 365 Business Central to Notion integration — real-time, two-way sync

Keep Dynamics 365 Business Central 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 Dynamics 365 Business Central and Notion

Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Notion and Dynamics 365 Business Central.

The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Notion is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.

Stacksync syncs Comments, Files and attachments, Pages, Databases / Data sources in Notion with Sales Orders, Sales Invoices, Purchase Orders, General Ledger Entries in Dynamics 365 Business Central bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.

Common use cases

  • 01 Read Notion wiki Pages and their Blocks into a database or search index for internal knowledge retrieval.
  • 02 Two-way sync a Notion projects or tasks data source with a Postgres table so engineers work in SQL while the team edits Pages in Notion, mapping status, date, and assignee properties both ways.
  • 03 Sync vendor and purchase order data with procurement or AP automation tools.
  • 04 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.

Common sync patterns

Master data corrections travel

A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.

Where Notion faces customers and Dynamics 365 Business Central carries account records

Order, invoice, or account status from Dynamics 365 Business Central appears alongside the customer in Notion, so front-line teams answer from live data.

Where Dynamics 365 Business Central is the HR or people system of record

Worker and organization data from Dynamics 365 Business Central stays current in Notion, so the tools people use daily reflect the org as it actually is.

What you can sync between Dynamics 365 Business Central 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.

Dynamics 365 Business Central objects Notion objects How this pairing syncs
Customers Core master data synced with CRMs so sales and finance share one customer list. Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. Customers is specific to Dynamics 365 Business Central and Pages to Notion — each maps to any object or custom field on the other side.
Vendors Supplier master data synced with procurement and AP automation tools. 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. Vendors is specific to Dynamics 365 Business Central and Databases / Data sources to Notion — each maps to any object or custom field on the other side.
Items Product and inventory records aligned with e-commerce and warehouse systems. Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. Items is specific to Dynamics 365 Business Central and Properties to Notion — each maps to any object or custom field on the other side.
Sales Orders Order headers and lines created from external channels and read back for fulfillment status. Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Sales Orders is specific to Dynamics 365 Business Central and Blocks to Notion — each maps to any object or custom field on the other side.
Sales Invoices Billing documents synced to CRMs and payment platforms. Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Sales Invoices is specific to Dynamics 365 Business Central and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents exchanged with supplier-facing systems. Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Purchase Orders is specific to Dynamics 365 Business Central and Users to Notion — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central 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.

Dynamics 365 Business Central Notion Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

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

Notion Dynamics 365 Business Central 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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • 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 Dynamics 365 Business Central ⇄ Notion

Connect Dynamics 365 Business Central and Notion for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 Business Central 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 Dynamics 365 Business Central or Notion record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Notion.

How the Dynamics 365 Business Central and Notion connectors work

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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
    Dynamics 365 Business Central connected
    Notion connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 Business Central 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 · Dynamics 365 Business Central ⇄ 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
    Dynamics 365 Business Central Notion
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 Business Central 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 514 integrations available for Dynamics 365 Business Central and Notion.

Popular · 8 of 514
All Dynamics 365 Business Central 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