Real-time sync
Changes in Brightpearl or Microsoft Power Bi instantly reflect in both systems. No stale data, no manual imports.
Keep Brightpearl and Microsoft Power Bi in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into Brightpearl, so Brightpearl always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.
ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Brightpearl carries financials, operations, workforce data, or all three, those numbers belong in Microsoft Power Bi, next to the product, behavioral, and web data the team already measures.
Worker and organization data from Brightpearl syncs into Microsoft Power Bi for headcount, cost, and utilization reporting alongside other company data.
Segments, scores, or metrics computed in Microsoft Power Bi sync onto the matching records in Brightpearl, so operations act on what the analysis found.
Financial records from Brightpearl land in Microsoft Power Bi as they change, so revenue, margin, and spend dashboards read current figures rather than last night's export.
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 Power Bi objects | How this pairing syncs | |
|---|---|---|---|
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. | Inventory and warehouses is specific to Brightpearl and Dataflows to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. | Goods-out notes is specific to Brightpearl and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. | Invoices and payments is specific to Brightpearl and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Workspaces (Groups) Containers for content read via GET /groups (tenant-wide via GET /admin/groups); mirrored to reproduce the tenant's content hierarchy in a catalog. | Custom fields is specific to Brightpearl and Workspaces (Groups) to Microsoft Power Bi — 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. | Activity Events (Audit Log) Admin audit log of user and content actions read via GET /admin/activityevents; loaded for security, access, and usage reporting across the tenant. | Products is specific to Brightpearl and Activity Events (Audit Log) to Microsoft Power Bi — 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. | Users and Access Workspace users and roles read via GET /groups/{id}/users or the admin scanner APIs; read for access reviews and identity reconciliation against an IdP. | Sales orders is specific to Brightpearl and Users and Access to Microsoft Power Bi — each maps to any object or custom field on the other side. |
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.
DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.
DeliveryMicrosoft Power Bi does not accept inbound record writes, so this direction carries requests rather than records: Microsoft Power Bi's output flows back as field updates on the originating Brightpearl records.
DetectionStacksync polls Microsoft Power Bi for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: no webhooks or change-data-capture.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Microsoft Power Bi connection.
Changes in Brightpearl or Microsoft Power Bi instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Brightpearl or Microsoft Power Bi data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Brightpearl or Microsoft Power Bi record.
Track your Brightpearl ⇄ Microsoft Power Bi sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Brightpearl and Microsoft Power Bi.
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.
Authenticate Brightpearl and Microsoft Power Bi with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Brightpearl and Microsoft Power Bi 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between Brightpearl and Microsoft Power Bi — Microsoft Power Bi is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
On the Microsoft Power Bi side: Users and Access, Datasets (Semantic Models), Reports, Dashboards and Tiles, plus custom fields where Microsoft Power Bi exposes them. On the Brightpearl side: Sales orders, Purchase orders, Contacts, Inventory and warehouses. Stacksync auto-detects both schemas and converts types between the two systems.
Microsoft Power Bi is a read-only source, so this integration runs one-way: Stacksync reads from Microsoft Power Bi in real time and delivers into Brightpearl. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for Brightpearl and Microsoft Power Bi: Where Brightpearl is the HR system of record: workforce and cost analysis; Write-back where Brightpearl exposes writable fields: segments and scores return; Where Brightpearl holds the books: revenue and finance dashboards from live data. Worker and organization data from Brightpearl syncs into Microsoft Power Bi for headcount, cost, and utilization reporting alongside other company data.
Brightpearl: 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. Microsoft Power Bi: Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity. Authentication: Microsoft Entra ID (Azure AD) OAuth 2.0 bearer tokens. Supports delegated user tokens and app-only service principals; service principals must be enabled under the tenant's Developer settings and granted workspace access. Tenant-wide admin reads require the Tenant.Read.All scope. Stacksync manages authentication, retries, and rate limits on both sides.
Microsoft Power Bi: App-only service principal authentication must be enabled under the tenant's Developer settings ('Allow service principals to use Power BI APIs') and the principal added to each workspace; service principals cannot use Execute Queries against datasets with row-level security or SSO. Brightpearl: Resource search endpoints return column-oriented result sets with filter parameters, which is the efficient way to poll for changed records. Stacksync's field mapping accounts for these differences between Brightpearl and Microsoft Power Bi without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 439 integrations available for Brightpearl and Microsoft Power Bi.