Migrate your Brightpearl data
Cloud ERP for omnichannel retailers combining inventory, orders, warehouse management, CRM and accounting into one platform, built by Sage and targeted at mid-to-large merchants.
In its favor
Why people choose Brightpearl
The signal that keeps Brightpearl on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Brightpearl's unified retail OS consolidates inventory, orders, CRM and accounting in a single real-time system, eliminating the need to maintain separate tools and reconciliation spreadsheets across multiple channels.
The platform natively supports omnichannel operations with built-in automation for sales orders, purchase orders and drop-ship workflows, reducing manual re-keying for merchants selling across Shopify, Amazon and physical retail simultaneously.
Automation rules allow merchants to define conditional triggers and actions against incoming orders, enabling custom routing, status updates and post-purchase workflows without additional scripting.
Multi-warehouse inventory management with zone-based location hierarchies and real-time stock visibility supports businesses scaling from single-location to distributed fulfilment operations.
As part of Sage, Brightpearl benefits from a mature accounting engine with real-time ledger updates, giving retail operators a natively integrated financials layer rather than a third-party accounting sync.
Sales teams report that core features such as bulk pricing updates, payment gateway integration and product syncing to connected storefronts did not work as described during implementation, leading to disputes over prepaid contracts.
System errors and performance degradation — with some warehouse and sales teams experiencing delays of up to five minutes — disrupt fulfilment throughput during peak order periods.
Discovery and demo practices have been criticised: customers report being asked to commit full payment upfront before receiving a live trial, which limits recourse when promised capabilities are absent or misrepresented.
Brightpearl's development pace has been flagged by long-term users, who note that maintaining competitive feature parity requires increasing investment in third-party connectors and integrations.
Reasons to switch
Why people leave Brightpearl
The recurring reasons buyers give for replacing Brightpearl. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Brightpearl fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Brightpearl pricing overview
Brightpearl prices on a monthly tier model from $63 for Starter up to $665 for Platinum, with Platinum+ offered under a custom enterprise agreement. All tiers include unlimited users, with pricing scaling by feature depth — WMS, advanced reporting, demand planning and premium support are tier-gated. A 14-day free trial is available and full payment is required upfront.
Starter
Tier 1 of 6
$63/month
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Brightpearl's schedule — see our quote-based pricing →
What gets migrated
Brightpearl object support
Object-by-object support for Brightpearl migrations. Per-pair details surface during scoping.
Contacts (Customers and Suppliers)
Fully supportedBrightpearl stores both customers and vendors as Contact records, differentiated by a contact role flag. Each Contact supports addresses, owner assignment and PCF_* custom fields. We map the contact role and preserve owner assignments during migration, resolving duplicate contacts by email deduplication.
Products (Items and Services)
Fully supportedProducts are the core inventory and catalogue object. Brightpearl tracks SKU, product type, multiple price lists and product custom fields (PCF_*). We export all standard fields plus PCF_* custom fields via the product export endpoint and re-import using Brightpearl's data map format.
Warehouse Locations
Fully supportedBrightpearl supports a four-level location hierarchy: Aisle / Bay / Shelf / Bin. Locations are grouped into Zones. We represent each location as a nested path string and reconstruct the zone association at the destination using Brightpearl's location import format.
Sales Orders
Fully supportedSales orders are the primary order object in Brightpearl, holding line items, pricing, discounts and fulfillment status. We map order headers and line items preserving order numbers, dates and owner assignments. Pending orders require a placeholder contact to be configured with valid address fields to avoid download failures.
Purchase Orders
Fully supportedPurchase orders represent incoming stock requests to vendors and include vendor assignment, lead time and expected delivery dates. We preserve the full PO lifecycle including received quantities and link POs to corresponding vendor Contacts.
Invoices and Credit Notes
Mapping requiredBrightpearl generates invoices from sales orders and supports standalone invoices and credit notes. Accounting data is embedded in the invoice record. We map invoice headers and line items but note that post-payment ledger entries require Chart of Accounts alignment at the destination.
Price Lists
Fully supportedPrice lists in Brightpearl associate a price value with a product and a price list identifier. Multiple price lists per product are common. We export all price list assignments and map them to the destination's pricing tier or customer-segment structure.
Chart of Accounts
Fully supportedBrightpearl's accounting module uses a structured Chart of Accounts with account codes. We export the full account code list and map each to the destination system's account codes, preserving account types and categories.
Inventory Summary and Detail
Fully supportedBrightpearl provides inventory summary (total cost value per SKU) and inventory detail (per-warehouse, per-location stock levels). We export both reports and reconstruct the stock position at the destination, including warehouse-to-warehouse transfer history.
Users and Owner Assignments
Mapping requiredBrightpearl assigns a staff member as the Owner of a Contact, and auto-assigns orders to the contact owner when configured. We export the user roster and map owner references to corresponding user identities in the destination system. Custom role permissions do not export and must be reconfigured.
| Object | Support | Notes |
|---|---|---|
| Contacts (Customers and Suppliers) | Fully supported | Brightpearl stores both customers and vendors as Contact records, differentiated by a contact role flag. Each Contact supports addresses, owner assignment and PCF_* custom fields. We map the contact role and preserve owner assignments during migration, resolving duplicate contacts by email deduplication. |
| Products (Items and Services) | Fully supported | Products are the core inventory and catalogue object. Brightpearl tracks SKU, product type, multiple price lists and product custom fields (PCF_*). We export all standard fields plus PCF_* custom fields via the product export endpoint and re-import using Brightpearl's data map format. |
| Warehouse Locations | Fully supported | Brightpearl supports a four-level location hierarchy: Aisle / Bay / Shelf / Bin. Locations are grouped into Zones. We represent each location as a nested path string and reconstruct the zone association at the destination using Brightpearl's location import format. |
| Sales Orders | Fully supported | Sales orders are the primary order object in Brightpearl, holding line items, pricing, discounts and fulfillment status. We map order headers and line items preserving order numbers, dates and owner assignments. Pending orders require a placeholder contact to be configured with valid address fields to avoid download failures. |
| Purchase Orders | Fully supported | Purchase orders represent incoming stock requests to vendors and include vendor assignment, lead time and expected delivery dates. We preserve the full PO lifecycle including received quantities and link POs to corresponding vendor Contacts. |
| Invoices and Credit Notes | Mapping required | Brightpearl generates invoices from sales orders and supports standalone invoices and credit notes. Accounting data is embedded in the invoice record. We map invoice headers and line items but note that post-payment ledger entries require Chart of Accounts alignment at the destination. |
| Price Lists | Fully supported | Price lists in Brightpearl associate a price value with a product and a price list identifier. Multiple price lists per product are common. We export all price list assignments and map them to the destination's pricing tier or customer-segment structure. |
| Chart of Accounts | Fully supported | Brightpearl's accounting module uses a structured Chart of Accounts with account codes. We export the full account code list and map each to the destination system's account codes, preserving account types and categories. |
| Inventory Summary and Detail | Fully supported | Brightpearl provides inventory summary (total cost value per SKU) and inventory detail (per-warehouse, per-location stock levels). We export both reports and reconstruct the stock position at the destination, including warehouse-to-warehouse transfer history. |
| Users and Owner Assignments | Mapping required | Brightpearl assigns a staff member as the Owner of a Contact, and auto-assigns orders to the contact owner when configured. We export the user roster and map owner references to corresponding user identities in the destination system. Custom role permissions do not export and must be reconfigured. |
Gotchas
What to watch for in Brightpearl migrations
Issues we've hit on past Brightpearl migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Brightpearl API rate limits are undocumented
Pending order download has a 36-hour recovery window
Country names must match exact localisation strings
Automation rules can execute in locked accounting periods
Placeholder contacts require valid formatted data
| Severity | Issue |
|---|---|
| High | Brightpearl API rate limits are undocumented |
| High | Pending order download has a 36-hour recovery window |
| Medium | Country names must match exact localisation strings |
| Medium | Automation rules can execute in locked accounting periods |
| Low | Placeholder contacts require valid formatted data |
Leaving Brightpearl?
Where Brightpearl customers move next
6 destinations Brightpearl can migrate to.
How a Brightpearl migration works
Four steps, Brightpearl-specific
Connect
OAuth 2.0 (Authorization Code Grant flow) into Brightpearl. Scopes limited to read-only on the data we move.
Map
We translate Brightpearl-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Brightpearl quirks before production.
Migrate
Full migration with Brightpearl rate-limit handling. Rollback available throughout.
FAQ
Brightpearl migration FAQ
Answers to the questions buyers ask most during Brightpearl migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Brightpearl migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Brightpearl.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Brightpearl setup and destination — written quote back within a business day.