Real-time
Two-way sync
Changes in Brightpearl or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Business productivity
Brightpearl to Microsoft 365 integration — real-time, two-way sync
Keep Brightpearl and Microsoft 365 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 Brightpearl and Microsoft 365
Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Microsoft 365 and Brightpearl.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Microsoft 365 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 Planner & To Do Tasks, Users, Groups, Mail Messages in Microsoft 365 with Products, Sales orders, Purchase orders, Contacts in Brightpearl 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 Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
- 02 Sync SharePoint lists with operational databases so business users edit in SharePoint while systems read SQL.
- 03 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 04 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
Common sync patterns
Where Microsoft 365 faces customers and Brightpearl carries account records
Order, invoice, or account status from Brightpearl appears alongside the customer in Microsoft 365, so front-line teams answer from live data.
Where Microsoft 365 collects payments: transactions post through
Payment events sync into Brightpearl as they occur, keeping the enterprise records current without manual entry.
Where Brightpearl is the HR or people system of record
Worker and organization data from Brightpearl stays current in Microsoft 365, so the tools people use daily reflect the org as it actually is.
What you can sync between Brightpearl and Microsoft 365
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.
| Brightpearl objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Contacts Personal and org contacts kept consistent with CRM contact records. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Invoices and payments is specific to Brightpearl and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Custom fields is specific to Brightpearl and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Products is specific to Brightpearl and OneDrive Files (driveItems) to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | SharePoint Sites & Lists List items read and written like lightweight database tables. | Sales orders is specific to Brightpearl and SharePoint Sites & Lists to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Teams Team and membership data provisioned from upstream systems. | Purchase orders is specific to Brightpearl and Teams to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Microsoft 365
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.
Brightpearl Microsoft 365 Sub-second propagation
DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Brightpearl Sub-second propagation
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
What ships with Brightpearl ⇄ Microsoft 365
Connect Brightpearl and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Microsoft 365 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 Brightpearl or Microsoft 365 record.
Observability
Monitoring
Track your Brightpearl ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Brightpearl and Microsoft 365.
How the Brightpearl and Microsoft 365 connectors work
Brightpearl
- Integration surface
- REST API, organized into services (order, product, contact, warehouse, accounting)
- Authentication
- OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token headers
- Change detection
- Webhooks for object created/updated events, with resource search polling as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints
Microsoft 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
How it works
How to connect Brightpearl to Microsoft 365 — 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 Brightpearl and Microsoft 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Brightpearl
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Microsoft 365 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 · Brightpearl ⇄ Microsoft 365Customers 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.
Brightpearl Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Microsoft 365: authenticate both systems, choose the objects to sync (such as Brightpearl's Contacts and Invoices and payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Microsoft 365. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Microsoft 365: Graph change notifications (webhooks) plus delta queries for incremental sync. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft 365 side: Planner & To Do Tasks, Users, Groups, Mail Messages, plus custom fields where Microsoft 365 exposes them. On the Brightpearl side: Products, Sales orders, Purchase orders, Contacts. 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 Brightpearl and Microsoft 365: Where Microsoft 365 faces customers and Brightpearl carries account records; Where Microsoft 365 collects payments: transactions post through; Where Brightpearl is the HR or people system of record. Order, invoice, or account status from Brightpearl appears alongside the customer in Microsoft 365, so front-line teams answer from live data.
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 458 integrations available for Brightpearl and Microsoft 365.
Popular · 5 of 458
-
Brightpearl ⇄ Slack -
Brightpearl ⇄ Agiloft -
Microsoft 365 ⇄ Infor LN - Microsoft 365 ⇄ Infor M3
- Microsoft 365 ⇄ Infor WMS
No integrations match .
