Real-time
Two-way sync
Changes in Brightpearl or Exasol instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Data warehouse
Brightpearl to Exasol integration — real-time, two-way sync
Keep Brightpearl and Exasol 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 Exasol
Put Brightpearl's records in Exasol 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 Exasol next to everything else the company measures.
Stacksync syncs Invoices and payments, Custom fields, Products, Sales orders from Brightpearl into tables in Exasol continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Exasol can be written back to fields in Brightpearl where that is useful.
Common use cases
- Sync computed metrics or customer segments from Exasol back into a CRM for sales and marketing use (reverse ETL).
- Consolidate data from multiple operational databases into Exasol as the central analytics layer.
- Push invoices and payments into an accounting platform for reconciliation.
- Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
Group reporting across systems
Combine Brightpearl's records with data synced from other systems in Exasol for consolidated views no single system can produce.
Write-back where Brightpearl exposes writable fields
Classifications or reference values computed in Exasol sync back onto the corresponding records in Brightpearl.
Where Brightpearl holds the books: finance reporting from live data
Financial records land in Exasol as they change, so period-end reporting queries current numbers rather than last night's extract.
What you can sync between Brightpearl and Exasol
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 | Exasol objects | |
|---|---|---|
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Tables Primary sync target; columnar relational tables written with standard SQL. | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Views Read-only query surfaces often used as curated sources for reverse ETL. | |
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | UDF scripts In-database functions that can transform synced data after load. | |
| Custom fields Per-object custom attributes included in field mappings. | Users and roles Grant read/write access for the dedicated integration account. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Schemas Namespaces that group the tables a sync reads from or writes into. |
What ships with Brightpearl ⇄ Exasol
Connect Brightpearl and Exasol for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Exasol connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Exasol 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 Exasol record.
Observability
Monitoring
Track your Brightpearl ⇄ Exasol 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 Exasol.
How the Brightpearl and Exasol 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
Exasol
- Integration surface
- SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
- Authentication
- Database credentials (username and password)
- Change detection
- Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
- Capabilities
- read · write
- Rate limits
- No API quota; concurrency is bounded by cluster resources and session limits
How it works
How to connect Brightpearl to Exasol — 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 Exasol 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
Exasol
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Exasol 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 ⇄ ExasolCustomers 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 ExasolCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Exasol integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Exasol: authenticate both systems, choose the objects to sync (such as Brightpearl's Contacts and Inventory and warehouses), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Exasol connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Exasol integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Exasol. 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 Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Exasol side: Schemas, Tables, Views, Virtual schemas, plus custom fields where Exasol exposes them. On the Brightpearl side: Invoices and payments, Custom fields, Products, Sales orders. 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.
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 Exasol.
Popular · 8 of 386
-
Brightpearl ⇄ StarRocks -
Brightpearl ⇄ Teradata Vantage -
Brightpearl ⇄ Tinybird -
Brightpearl ⇄ Vertica -
Exasol ⇄ SAP S/4HANA -
Exasol ⇄ Odoo -
Exasol ⇄ Blue Yonder WMS -
Exasol ⇄ Cetec ERP
No integrations match .
