Real-time
Two-way sync
Changes in Box or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to Dynamics 365 Business Central integration — real-time, two-way sync
Keep Box and Dynamics 365 Business Central 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 Box and Dynamics 365 Business Central
Move the documents and data that Dynamics 365 Business Central produces into Box as files, and let files stored in Box update the records they belong to in Dynamics 365 Business Central, continuously and without exports or manual filing.
Dynamics 365 Business Central runs the business on structured records: Items, Sales Orders, Sales Invoices, Purchase Orders. Box holds files and the metadata that describes them: Tasks, Events, Files, Folders. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Dynamics 365 Business Central touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Box, from signed contracts to vendor bills to receipts, describe a transaction Dynamics 365 Business Central needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Items, Sales Orders, Sales Invoices, Purchase Orders in Dynamics 365 Business Central and Tasks, Events, Files, Folders in Box in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in Dynamics 365 Business Central. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Dynamics 365 Business Central and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.
- 02 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
- 03 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
- 04 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
Common sync patterns
Where Box captures inbound files: details reach the record
A contract, vendor bill, or receipt added to Box with its details can create or update the matching record in Dynamics 365 Business Central, so a document captured outside the finance system still reaches the books.
An archive that stays current
As records change in Dynamics 365 Business Central, the corresponding files and metadata in Box are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
Audit-ready retention
Every transaction's supporting file lives in Box beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Dynamics 365 Business Central.
What you can sync between Box and Dynamics 365 Business Central
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.
| Box objects | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Groups is specific to Box and General Ledger Entries to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Journals Staging records for financial postings created by integrations before posting. | Tasks is specific to Box and Journals to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Events is specific to Box and Dimensions to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Payments Customer and vendor payment records reconciled against invoices. | Files is specific to Box and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Customers Core master data synced with CRMs so sales and finance share one customer list. | Folders is specific to Box and Customers to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Vendors Supplier master data synced with procurement and AP automation tools. | Metadata is specific to Box and Vendors to Dynamics 365 Business Central — each maps to any object or custom field on the other side. |
How changes propagate between Box and Dynamics 365 Business Central
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.
Box Dynamics 365 Business Central Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Dynamics 365 Business Central Box 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 Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
What ships with Box ⇄ Dynamics 365 Business Central
Connect Box and Dynamics 365 Business Central for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Dynamics 365 Business Central connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Dynamics 365 Business Central 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 Box or Dynamics 365 Business Central record.
Observability
Monitoring
Track your Box ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and Dynamics 365 Business Central.
How the Box and Dynamics 365 Business Central connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
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
How it works
How to connect Box to Dynamics 365 Business Central — 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.
- 01
Connect your apps
Authenticate Box and Dynamics 365 Business Central with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
Dynamics 365 Business Central
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Dynamics 365 Business Central 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.
objects · Box ⇄ Dynamics 365 Business CentralCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Box Dynamics 365 Business CentralCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Dynamics 365 Business Central integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Box's Groups and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Box and Dynamics 365 Business Central records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Dynamics 365 Business Central connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Dynamics 365 Business Central integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Dynamics 365 Business Central. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed. On Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Dynamics 365 Business Central side: Items, Sales Orders, Sales Invoices, Purchase Orders, plus custom fields where Dynamics 365 Business Central exposes them. On the Box side: Tasks, Events, Files, Folders. Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 500 integrations available for Box and Dynamics 365 Business Central.
Popular · 7 of 500
-
Box ⇄ Manhattan Associates WMS -
Box ⇄ Microsoft Dynamics GP - Box ⇄ Microsoft Dynamics NAV
-
Box ⇄ Plex ERP -
Dynamics 365 Business Central ⇄ Sharepoint -
Dynamics 365 Business Central ⇄ Egnyte -
Dynamics 365 Business Central ⇄ Amazon S3
No integrations match .
