Skip to content
ERP ⇄ Database

Brightpearl to DuckDB integration — real-time, two-way sync

Keep Brightpearl and DuckDB 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 DuckDB

Give your engineers Brightpearl's data in DuckDB: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Purchase orders, Contacts, Inventory and warehouses, Goods-out notes from Brightpearl into DuckDB and keeps both sides consistent in real time. Whatever Brightpearl is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in DuckDB sync back into Brightpearl with its validations respected.

Common use cases

  • Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
  • Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
  • Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
  • Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.

Read ERP records with a query

Records from Brightpearl live in DuckDB as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Brightpearl interface, limits, and retries.

React to ERP changes

Updates in Brightpearl arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.

What you can sync between Brightpearl and DuckDB

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 DuckDB objects
Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format.
Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. Attached databases Additional database files or external systems attached into one session for cross-source queries.
Invoices and payments Financial documents synced to accounting platforms for reconciliation. Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage.
Custom fields Per-object custom attributes included in field mappings. Schemas Namespaces within a database used to organize tables in sync outputs.
Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. Tables Columnar tables created via SQL; the destination for materialized sync data.
Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. Views SQL views used to shape or filter data for downstream consumers.
What ships with Brightpearl ⇄ DuckDB

Connect Brightpearl and DuckDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–DuckDB connection.

Real-time

Two-way sync

Changes in Brightpearl or DuckDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Brightpearl or DuckDB 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 DuckDB record.

Observability

Monitoring

Track your Brightpearl ⇄ DuckDB 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 DuckDB.

How the Brightpearl and DuckDB 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

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O
How it works

How to connect Brightpearl to DuckDB — 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.

  1. 01

    Connect your apps

    Authenticate Brightpearl and DuckDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Brightpearl connected
    DuckDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Brightpearl and DuckDB 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Brightpearl ⇄ DuckDB
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Brightpearl DuckDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Brightpearl and DuckDB integration FAQ

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 DuckDB.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.