Real-time
Two-way sync
Changes in Bigcommerce or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ CRM
Bigcommerce to Microsoft Dynamics 365 Sales integration — real-time, two-way sync
Keep Bigcommerce 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
Live sync
stacksync.com - <1s
- latency
- 2-way
- sync
- 100M+
- records
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 Bigcommerce and Microsoft Dynamics 365 Sales
Keep the customers and orders that Microsoft Dynamics 365 Sales and Bigcommerce share aligned in real time, so sales works from live purchase history and the store works from current account details.
Microsoft Dynamics 365 Sales holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Bigcommerce runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.
Stacksync links Accounts, Contacts, Leads, Opportunities in Microsoft Dynamics 365 Sales to Orders, Customers, Categories, Brands in Bigcommerce with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.
The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.
Common use cases
- 01 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.
- 02 Run a two-way dual-run between Dynamics and another CRM during a migration.
- 03 Sync Customers and customer groups two-way with a CRM so marketing and support see the same accounts and addresses as the storefront.
- 04 Push Price Lists from an ERP into BigCommerce to drive customer-group and B2B pricing without manual catalog edits.
Common sync patterns
Where both keep product records: catalog and CRM products aligned
Where Microsoft Dynamics 365 Sales tracks products or line items and Bigcommerce holds the catalog, shared items are matched on SKU so quotes, deals, and orders reference the same products.
One customer identity across sales and store
A person who exists as a contact in Microsoft Dynamics 365 Sales and a buyer in Bigcommerce is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.
Where Bigcommerce records orders: purchase history on the account
Orders and their status from Bigcommerce appear on the matching contact or account in Microsoft Dynamics 365 Sales, so reps see what a customer has bought and what is in flight before the next conversation.
What you can sync between Bigcommerce 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.
| Bigcommerce objects | Microsoft Dynamics 365 Sales objects | How this pairing syncs | |
|---|---|---|---|
| Orders V2 Orders API header, line items, and shipping/billing addresses; read into an ERP or accounting system, with status written back. | Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Products Catalog V3 records with custom fields and images; mastered in a PIM or ERP and written to BigCommerce, or read out to a warehouse. | Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. | Products is specific to Bigcommerce and Accounts to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Variants and SKUs Per-variant pricing and inventory; synced to keep stock and SKU data aligned with an ERP or WMS at the option level. | Contacts Person records linked to accounts; synced with marketing and support systems. | Variants and SKUs is specific to Bigcommerce and Contacts to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Customers V3 customer accounts, customer groups, and addresses; synced two-way with a CRM so storefront and GTM records match. | Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Customers is specific to Bigcommerce and Leads to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Categories Catalog V3 category tree; mapped for merchandising and kept aligned with a product master or PIM. | Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | Categories is specific to Bigcommerce and Opportunities to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Brands Catalog V3 brand records linked to products; kept aligned with a product master or PIM so brand names and pages stay consistent. | Quotes Pricing proposals; often synced with CPQ or ERP pricing data. | Brands is specific to Bigcommerce and Quotes to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. |
How changes propagate between Bigcommerce 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.
Bigcommerce Microsoft Dynamics 365 Sales Sub-second propagation
DetectionBigcommerce notifies Stacksync of record changes through webhook events. Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more).
DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Sales Bigcommerce 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 Bigcommerce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bigcommerce: OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
- Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Bigcommerce ⇄ Microsoft Dynamics 365 Sales
Connect Bigcommerce and Microsoft Dynamics 365 Sales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bigcommerce–Microsoft Dynamics 365 Sales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bigcommerce 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 Bigcommerce or Microsoft Dynamics 365 Sales record.
Observability
Monitoring
Track your Bigcommerce ⇄ 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 Bigcommerce and Microsoft Dynamics 365 Sales.
How the Bigcommerce and Microsoft Dynamics 365 Sales connectors work
Bigcommerce
- Integration surface
- REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs
- Authentication
- OAuth API account credentials — a store-generated client ID and permanent access token sent in the X-Auth-Token header, limited to the OAuth scopes granted when the account is created (e.g. store_v2_orders, store_v2_products)
- Change detection
- Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers
- Capabilities
- read · write · webhooks
- Rate limits
- OAuth quota refreshes every 30 seconds and varies by plan (about 20,000 requests/hour on Standard and Plus, 60,000 on Pro, higher on Enterprise); the X-Rate-Limit-Requests-Left header reports remaining calls.
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 Bigcommerce 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 Bigcommerce 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.
Bigcommerce
connected
Microsoft Dynamics 365 Sales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bigcommerce 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 · Bigcommerce ⇄ 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.
Bigcommerce Microsoft Dynamics 365 SalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bigcommerce and Microsoft Dynamics 365 Sales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bigcommerce and Microsoft Dynamics 365 Sales: authenticate both systems, choose the objects to sync (such as Bigcommerce's Orders and Products), 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 Bigcommerce and Microsoft Dynamics 365 Sales records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Bigcommerce and Microsoft Dynamics 365 Sales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Bigcommerce–Microsoft Dynamics 365 Sales integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Bigcommerce 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 Bigcommerce: Webhooks push near-real-time events (store/order/*, store/product/*, store/customer/* and more); polling uses date_modified:min/max filters on Products, Orders, and Customers. 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: Accounts, Contacts, Leads, Opportunities, plus custom fields where Microsoft Dynamics 365 Sales exposes them. On the Bigcommerce side: Orders, Customers, Categories, Brands. 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 389 integrations available for Bigcommerce and Microsoft Dynamics 365 Sales.
Popular · 7 of 389
-
Bigcommerce ⇄ 6sense -
Bigcommerce ⇄ Apollo.io -
Bigcommerce ⇄ Clearbit -
Bigcommerce ⇄ Close -
Microsoft Dynamics 365 Sales ⇄ Shipwire -
Microsoft Dynamics 365 Sales ⇄ Shopware -
Microsoft Dynamics 365 Sales ⇄ Akeneo
No integrations match .
