Brightpearl to Freshsales integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Freshsales: 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.

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 Freshsales: Where Brightpearl is the finance system of record: money status on the account; One customer master; Where Brightpearl manages people and org data: keep Freshsales aligned. Invoice and payment state from Brightpearl shows on the account in Freshsales, so reps see balances before promising the next order.

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. Freshsales: REST API. Authentication: API key sent as a Token authorization header. Stacksync manages authentication, retries, and rate limits on both sides.

Freshsales: Each module supports custom fields, which the API returns alongside standard fields for mapping. Brightpearl: Order and fulfillment state is modeled through linked documents (sales order, goods-out note, invoice) rather than a single status field, so syncs track several objects to represent one order lifecycle. Stacksync's field mapping accounts for these differences between Brightpearl and Freshsales 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 Freshsales records are not retained after a sync operation.