Real-time
Two-way sync
Changes in Brightpearl or Close instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
Brightpearl to Close integration — real-time, two-way sync
Keep Brightpearl and Close 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 Close
Close the gap between front office and back office: Close and Brightpearl share customers and status in real time, in both directions.
Close holds the customer relationship; Brightpearl runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Smart Views, Leads, Contacts, Opportunities in Close with Custom fields, Products, Sales orders, Purchase orders in Brightpearl field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
- 02 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
- 03 Land order and margin data in a warehouse for retail performance reporting.
- 04 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
Common sync patterns
Where Brightpearl manages people and org data: keep Close aligned
Owners, territories, and org structure informed by Brightpearl stay current in Close.
Where Brightpearl handles order-to-cash: closed-won flows through
A deal won in Close creates or updates the customer in Brightpearl with clean data, so fulfillment and invoicing start without re-entry.
Where Brightpearl is the finance system of record: money status on the account
Invoice and payment state from Brightpearl shows on the account in Close, so reps see balances before promising the next order.
What you can sync between Brightpearl and Close
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 | Close objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Custom fields Per-object custom attributes included in field mappings. | Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Invoices and payments is specific to Brightpearl and Activities to Close — each maps to any object or custom field on the other side. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Tasks Follow-up items assigned to users; synced for workload and SLA reporting. | Products is specific to Brightpearl and Tasks to Close — each maps to any object or custom field on the other side. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Sales orders is specific to Brightpearl and Custom Activities to Close — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Users Sales reps referenced as owners on leads, opportunities, and activities. | Purchase orders is specific to Brightpearl and Users to Close — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Close
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Brightpearl Close Sub-second propagation
DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.
DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.
Close Brightpearl Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
- Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Brightpearl ⇄ Close
Connect Brightpearl and Close for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Close connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Close 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 Close record.
Observability
Monitoring
Track your Brightpearl ⇄ Close 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 Close.
How the Brightpearl and Close 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
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
How it works
How to connect Brightpearl to Close — 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 Close 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
Close
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Close 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 ⇄ CloseCustomers 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 CloseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Close integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Close: authenticate both systems, choose the objects to sync (such as Brightpearl's Contacts and Custom fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Close side: Smart Views, Leads, Contacts, Opportunities, plus custom fields where Close 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 Close: Where Brightpearl manages people and org data: keep Close aligned; Where Brightpearl handles order-to-cash: closed-won flows through; Where Brightpearl is the finance system of record: money status on the account. Owners, territories, and org structure informed by Brightpearl stay current in Close.
-
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. Close: REST API. Authentication: API key (sent via HTTP Basic auth). Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams trust 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
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 530 integrations available for Brightpearl and Close.
Popular · 7 of 530
-
Brightpearl ⇄ Kommo -
Brightpearl ⇄ Kustomer -
Brightpearl ⇄ Nimble -
Brightpearl ⇄ Nutshell -
Close ⇄ Infor CloudSuite - Close ⇄ Infor LN
- Close ⇄ Infor M3
No integrations match .
