Real-time
Two-way sync
Changes in Box or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ CRM
Box to Microsoft Dynamics 365 Sales integration — real-time, two-way sync
Keep Box and Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales
Keep the paperwork with the relationship: Microsoft Dynamics 365 Sales and Box share every customer's records and files in real time, in both directions.
Microsoft Dynamics 365 Sales holds the customer relationship as structured records; Box holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.
Stacksync keeps Quotes, Orders, Invoices, Activities in Microsoft Dynamics 365 Sales aligned with Users, Groups, Tasks, Events in Box, in real time. A new account or deal can open its own folder in Box; a document filed in Box can surface as a link and metadata on the matching record in Microsoft Dynamics 365 Sales; and records from Microsoft Dynamics 365 Sales can be written into Box as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.
Common use cases
- 01 Feed BI models with continuously updated CRM data instead of scheduled exports.
- 02 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.
- 03 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
- 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
Common sync patterns
One place for a customer's files
Attachments that accumulate against a record in Microsoft Dynamics 365 Sales collect in that customer's folder in Box, so the full document history lives in one place and is reachable by anyone who needs it.
A folder per account or deal
When an account or deal is created in Microsoft Dynamics 365 Sales, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.
Documents linked back to the record
A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Microsoft Dynamics 365 Sales, so the customer's paperwork sits with the relationship instead of a shared drive.
What you can sync between Box and Microsoft Dynamics 365 Sales
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 | Microsoft Dynamics 365 Sales objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Events is specific to Box and Leads to Microsoft Dynamics 365 Sales — 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. | Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | Files is specific to Box and Opportunities to Microsoft Dynamics 365 Sales — 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. | Quotes Pricing proposals; often synced with CPQ or ERP pricing data. | Folders is specific to Box and Quotes to Microsoft Dynamics 365 Sales — 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. | Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. | Metadata is specific to Box and Orders to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. | Collaborations is specific to Box and Invoices to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Activities Emails, calls, appointments, and tasks; read out for activity analytics. | Users is specific to Box and Activities to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. |
How changes propagate between Box and Microsoft Dynamics 365 Sales
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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Sales Box 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 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.
- Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Box ⇄ Microsoft Dynamics 365 Sales
Connect Box and Microsoft Dynamics 365 Sales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Microsoft Dynamics 365 Sales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales record.
Observability
Monitoring
Track your Box ⇄ Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales.
How the Box and Microsoft Dynamics 365 Sales 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.
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.
How it works
How to connect Box to Microsoft Dynamics 365 Sales — 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 Microsoft Dynamics 365 Sales 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
Microsoft Dynamics 365 Sales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Microsoft Dynamics 365 Sales 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 ⇄ Microsoft Dynamics 365 SalesCustomers 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 Microsoft Dynamics 365 SalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Microsoft Dynamics 365 Sales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Microsoft Dynamics 365 Sales: authenticate both systems, choose the objects to sync (such as Box's Events and Files), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Box and Microsoft Dynamics 365 Sales. 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 Microsoft Dynamics 365 Sales: Dataverse change tracking with delta tokens, plus registered webhooks on table events. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft Dynamics 365 Sales side: Quotes, Orders, Invoices, Activities, plus custom fields where Microsoft Dynamics 365 Sales exposes them. On the Box side: Users, Groups, Tasks, Events. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Box and Microsoft Dynamics 365 Sales: One place for a customer's files; A folder per account or deal; Documents linked back to the record. Attachments that accumulate against a record in Microsoft Dynamics 365 Sales collect in that customer's folder in Box, so the full document history lives in one place and is reachable by anyone who needs it.
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 422 integrations available for Box and Microsoft Dynamics 365 Sales.
Popular · 7 of 422
-
Box ⇄ Gladly -
Box ⇄ Gorgias -
Box ⇄ Infor CRM -
Box ⇄ Insightly -
Microsoft Dynamics 365 Sales ⇄ Egnyte -
Microsoft Dynamics 365 Sales ⇄ Amazon S3 -
Microsoft Dynamics 365 Sales ⇄ Sharepoint
No integrations match .
