Two-way sync
Changes in Azure SQL Database or Brightpearl instantly reflect in both systems. No stale data, no manual imports.
Keep Azure SQL Database and Brightpearl in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Sales orders, Purchase orders, Contacts, Inventory and warehouses from Brightpearl into Azure SQL Database 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 Azure SQL Database sync back into Brightpearl with its validations respected.
Updates in Brightpearl arrive as row changes in Azure SQL Database, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in Azure SQL Database for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Azure SQL Database back into Brightpearl, keeping the ERP authoritative.
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.
| Azure SQL Database objects | Brightpearl objects | |
|---|---|---|
| Tables The primary sync target; rows map one-to-one to records in the paired system. | Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | |
| Views Read-only projections used when the sync should expose a curated shape rather than raw tables. | Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | |
| Schemas Namespaces that organize tables and control which objects a sync user can reach. | Purchase orders Supplier orders synced with procurement or accounting systems. | |
| Rows and columns Standard relational records with typed columns; primary keys anchor upserts. | Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | |
| Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. | Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | |
| Change tracking / CDC tables System-maintained change records used to drive incremental sync. | Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure SQL Database–Brightpearl connection.
Changes in Azure SQL Database or Brightpearl instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure SQL Database or Brightpearl data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure SQL Database or Brightpearl record.
Track your Azure SQL Database ⇄ Brightpearl sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure SQL Database and Brightpearl.
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.
Authenticate Azure SQL Database and Brightpearl with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Azure SQL Database and Brightpearl 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure SQL Database and Brightpearl: authenticate both systems, choose the objects to sync (such as Azure SQL Database's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Azure SQL Database side: Tables, Views, Schemas, Rows and columns, plus custom fields where Azure SQL Database exposes them. On the Brightpearl side: Sales orders, Purchase orders, Contacts, Inventory and warehouses. 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 Azure SQL Database and Brightpearl: 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 Azure SQL Database, so jobs and triggers can respond as the business record changes.
Azure SQL Database: SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers. Authentication: SQL authentication (database credentials) or Microsoft Entra ID authentication. 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. Stacksync manages authentication, retries, and rate limits on both sides.
Azure SQL Database: It speaks the same TDS protocol as on-premises SQL Server, so existing SQL Server drivers and tools connect without modification. 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 Azure SQL Database and Brightpearl without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Azure SQL Database and Brightpearl.