Skip to content
ERP ⇄ Human resources

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

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

Sync the workers, org structure, and cost centers that Dynamics 365 Business Central and Namely share in real time, so the people Namely manages stay current in the system that runs finance and operations.

Namely is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Dynamics 365 Business Central runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Sales Orders, Sales Invoices, Purchase Orders, General Ledger Entries in Dynamics 365 Business Central with Job Titles, Job Tiers, Groups, Teams in Namely field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Dynamics 365 Business Central keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
  • 02 Sync vendor and purchase order data with procurement or AP automation tools.
  • 03 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.
  • 04 Provision or deprovision accounts in an IdP or directory when a Profile's user_status or start_date changes, and write the resulting user ID and email back onto the Profile.

Common sync patterns

Where Namely is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Namely, the matching employee record in Dynamics 365 Business Central is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in Dynamics 365 Business Central

A new person set up in Namely becomes an employee record in Dynamics 365 Business Central in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Dynamics 365 Business Central roll up to the same structure Namely maintains.

What you can sync between Dynamics 365 Business Central and Namely

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 Namely objects How this pairing syncs
Customers Core master data synced with CRMs so sales and finance share one customer list. Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. Customers is specific to Dynamics 365 Business Central and Teams to Namely — each maps to any object or custom field on the other side.
Vendors Supplier master data synced with procurement and AP automation tools. Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. Vendors is specific to Dynamics 365 Business Central and Reports to Namely — each maps to any object or custom field on the other side.
Items Product and inventory records aligned with e-commerce and warehouse systems. Profile Fields Metadata describing standard and company-defined custom field sections; read to discover schema and generate mappings. Items is specific to Dynamics 365 Business Central and Profile Fields to Namely — 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. Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. Sales Orders is specific to Dynamics 365 Business Central and Events to Namely — each maps to any object or custom field on the other side.
Sales Invoices Billing documents synced to CRMs and payment platforms. Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. Sales Invoices is specific to Dynamics 365 Business Central and Profiles to Namely — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents exchanged with supplier-facing systems. Job Titles Job title definitions; read and written so titles stay aligned with an HRIS, directory, or reporting dimension. Purchase Orders is specific to Dynamics 365 Business Central and Job Titles to Namely — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central and Namely

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 Namely 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 Namely through its API, with automatic retries and rate-limit backoff.

Namely Dynamics 365 Business Central Interval-based propagation

DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.

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

Rate-limit considerations

  • Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
What ships with Dynamics 365 Business Central ⇄ Namely

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

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

Real-time

Two-way sync

Changes in Dynamics 365 Business Central or Namely 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 Namely 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 Namely record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ Namely 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 Namely.

How the Dynamics 365 Business Central and Namely 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

Namely

Integration surface
REST API (JSON over HTTPS)
Authentication
OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
Change detection
No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
Capabilities
read · write
Rate limits
Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
How it works

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

    Choose tables

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

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

Popular · 6 of 406
All Dynamics 365 Business Central integrations All Namely 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