Real-time
Two-way sync
Changes in Brightpearl or MySQL instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Brightpearl to MySQL integration — real-time, two-way sync
Keep Brightpearl and MySQL 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 MySQL
Give your engineers Brightpearl's data in MySQL: 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 Custom fields, Products, Sales orders, Purchase orders from Brightpearl into MySQL 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 MySQL sync back into Brightpearl with its validations respected.
Common use cases
- Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
- Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts
- 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.
React to ERP changes
Updates in Brightpearl arrive as row changes in MySQL, so jobs and triggers can respond as the business record changes.
Where Brightpearl is the HR system of record: people data for internal systems
Worker and org records stay current in MySQL for provisioning, access, and reporting systems that read from the database.
Controlled write-back
Choose exactly which tables and fields may flow from MySQL back into Brightpearl, keeping the ERP authoritative.
What you can sync between Brightpearl and MySQL
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 | MySQL objects | |
|---|---|---|
| Custom fields Per-object custom attributes included in field mappings. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Tables The primary sync target; rows map to records in connected systems. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Views Read-side projections used as outbound sync sources. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Columns Field-level mapping targets with engine-typed values. | |
| Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. |
What ships with Brightpearl ⇄ MySQL
Connect Brightpearl and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or MySQL 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 MySQL record.
Observability
Monitoring
Track your Brightpearl ⇄ MySQL 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 MySQL.
How the Brightpearl and MySQL 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
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- 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 MySQL — 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 MySQL 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
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and MySQL 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 ⇄ MySQLCustomers 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 MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and MySQL: authenticate both systems, choose the objects to sync (such as Brightpearl's Custom fields and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and MySQL. 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 MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MySQL side: Primary and Unique Keys, JSON Columns, Stored Procedures, Triggers, plus custom fields where MySQL exposes them. On the Brightpearl side: Custom fields, Products, Sales orders, Purchase 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.
-
Common patterns for Brightpearl and MySQL: React to ERP changes; Where Brightpearl is the HR system of record: people data for internal systems; Controlled write-back. Updates in Brightpearl arrive as row changes in MySQL, so jobs and triggers can respond as the business record changes.
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 MySQL.
Popular · 8 of 386
-
Brightpearl ⇄ AWS Aurora PostgreSQL -
Brightpearl ⇄ MongoDB -
Brightpearl ⇄ CockroachDB -
Brightpearl ⇄ Google AlloyDB -
MySQL ⇄ Dynamics 365 F&O -
MySQL ⇄ SuiteAnalytics -
MySQL ⇄ Dynamics 365 Business Central -
MySQL ⇄ SAP Business ByDesign
No integrations match .
