Real-time
Two-way sync
Changes in Brightpearl or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Data warehouse
Brightpearl to MotherDuck integration — real-time, two-way sync
Keep Brightpearl and MotherDuck 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 MotherDuck
Put Brightpearl's records in MotherDuck as live tables for reporting and analysis, without extract jobs, and write results back where Brightpearl can use them.
ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Brightpearl carries financials, operations, workforce data, or all three, the analysis belongs in MotherDuck next to everything else the company measures.
Stacksync syncs Contacts, Inventory and warehouses, Goods-out notes, Invoices and payments from Brightpearl into tables in MotherDuck continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in MotherDuck can be written back to fields in Brightpearl where that is useful.
Common use cases
- Share curated, synced datasets with other teams through read-only database shares
- Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
- Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
- Push invoices and payments into an accounting platform for reconciliation.
Where Brightpearl runs operations: order and supply analysis
Operational records become queryable tables in MotherDuck, joinable with sales and finance data.
Group reporting across systems
Combine Brightpearl's records with data synced from other systems in MotherDuck for consolidated views no single system can produce.
Write-back where Brightpearl exposes writable fields
Classifications or reference values computed in MotherDuck sync back onto the corresponding records in Brightpearl.
What you can sync between Brightpearl and MotherDuck
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 | MotherDuck objects | |
|---|---|---|
| Purchase orders Supplier orders synced with procurement or accounting systems. | Views Modeled projections used as outbound sync sources. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Schemas Namespaces within a database used to organize synced tables. | |
| Custom fields Per-object custom attributes included in field mappings. | Tables The main landing target for synced records and source for analysis. |
What ships with Brightpearl ⇄ MotherDuck
Connect Brightpearl and MotherDuck for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–MotherDuck connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or MotherDuck 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 MotherDuck record.
Observability
Monitoring
Track your Brightpearl ⇄ MotherDuck 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 MotherDuck.
How the Brightpearl and MotherDuck 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
MotherDuck
- Integration surface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- Change detection
- Polling; no log-based CDC or webhook surface is exposed
- Capabilities
- read · write
- Rate limits
- Subject to the platform's compute and concurrency limits rather than per-request API rate limits
How it works
How to connect Brightpearl to MotherDuck — 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 MotherDuck 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
MotherDuck
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and MotherDuck 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 ⇄ MotherDuckCustomers 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 MotherDuckCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and MotherDuck integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and MotherDuck: authenticate both systems, choose the objects to sync (such as Brightpearl's Purchase orders and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On MotherDuck: Polling; no log-based CDC or webhook surface is exposed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MotherDuck side: Database Shares, Attached Local DuckDB Databases, Databases, Schemas, plus custom fields where MotherDuck exposes them. On the Brightpearl side: Contacts, Inventory and warehouses, Goods-out notes, Invoices and payments. 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 MotherDuck: Where Brightpearl runs operations: order and supply analysis; Group reporting across systems; Write-back where Brightpearl exposes writable fields. Operational records become queryable tables in MotherDuck, joinable with sales and finance 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. MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams love 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
CSA STAR
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 386 integrations available for Brightpearl and MotherDuck.
Popular · 8 of 386
-
Brightpearl ⇄ Apache Doris -
Brightpearl ⇄ Apache Druid -
Brightpearl ⇄ Apache Hive -
Brightpearl ⇄ Apache Impala -
MotherDuck ⇄ Infor WMS -
MotherDuck ⇄ IQMS (DELMIAworks) -
MotherDuck ⇄ JobBOSS² -
MotherDuck ⇄ Körber WMS
No integrations match .
