Real-time
Two-way sync
Changes in Brightpearl or MariaDB instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Brightpearl to MariaDB integration — real-time, two-way sync
Keep Brightpearl and MariaDB 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 MariaDB
Give your engineers Brightpearl's data in MariaDB: 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 MariaDB 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 MariaDB sync back into Brightpearl with its validations respected.
Common use cases
- Keep several MariaDB instances aligned with one system of record across environments
- Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
- 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.
Read ERP records with a query
Records from Brightpearl live in MariaDB 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 MariaDB, so jobs and triggers can respond as the business record changes.
What you can sync between Brightpearl and MariaDB
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 | MariaDB objects | |
|---|---|---|
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Columns Field-level mapping targets with engine-typed values. | |
| Custom fields Per-object custom attributes included in field mappings. | Primary and Unique Keys Match keys for idempotent upserts. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | JSON Columns Semi-structured payloads validated with JSON functions. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Stored Procedures Server-side logic that can post-process synced rows. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. |
What ships with Brightpearl ⇄ MariaDB
Connect Brightpearl and MariaDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–MariaDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or MariaDB 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 MariaDB record.
Observability
Monitoring
Track your Brightpearl ⇄ MariaDB 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 MariaDB.
How the Brightpearl and MariaDB 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
MariaDB
- Integration surface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect Brightpearl to MariaDB — 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 MariaDB 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
MariaDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and MariaDB 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 ⇄ MariaDBCustomers 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 MariaDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and MariaDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and MariaDB: authenticate both systems, choose the objects to sync (such as Brightpearl's Invoices and payments and Custom fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
MariaDB: Tables without an auto-generated single primary key cannot be synced. Brightpearl: The API is split into functional services (order-service, product-service, contact-service, warehouse-service, accounting-service), each with its own resource paths. Stacksync's field mapping accounts for these differences between Brightpearl and MariaDB without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Brightpearl and MariaDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and MariaDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–MariaDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and MariaDB. 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 MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 MariaDB.
Popular · 8 of 386
-
Brightpearl ⇄ InterSystems IRIS -
Brightpearl ⇄ MarkLogic -
Brightpearl ⇄ Neo4j -
Brightpearl ⇄ OCI Database (Oracle Cloud) -
MariaDB ⇄ JobBOSS² -
MariaDB ⇄ Körber WMS -
MariaDB ⇄ Linnworks -
MariaDB ⇄ Logiwa WMS
No integrations match .
