Migrate from Brightpearl to Acumatica

Brightpearl Contact records map to Acumatica Customers with direct field translation. Names, emails, phone numbers, job titles, and addresses transfer directly without transformation. The Brightpearl contact ID is stored as an ExtRef custom field for cross-reference during reconciliation and delta-run traceability. Owner assignment resolves by matching the Brightpearl owner email to existing Acumatica users in the target tenant.

Brightpearl Company records map to Acumatica Customers of type Organization. Primary shipping and billing addresses consolidate into Acumatica address branches using the address location schema. Parent-company hierarchies in Brightpearl map to Acumatica CustomerClass assignments or a parent-customer link where the target schema supports hierarchical account structures.

Brightpearl product rows carry an inventory flag distinguishing stock vs. non-stock items. We map stock items to Acumatica Stock Items with warehouse allocation enabled, while non-stock items become Non-Stock Items used only on sales documents. The product type flag determines the Acumatica item class assigned during migration.

Brightpearl sales orders map to Acumatica SOOrder records with complete line-item detail preserved. Order status values (pending, confirmed, shipped, invoiced, cancelled) map directly to Acumatica SOStatus enumerations. Warehouse assignments on order lines carry over to the shipment warehouse location on the Acumatica document header and lines.

Brightpearl purchase orders map to Acumatica POOrder records preserving vendor references, line items, quantities ordered, and expected delivery dates. PO status values (draft, confirmed, received, closed) align with corresponding Acumatica POStatus enumerations to maintain order lifecycle tracking through the procurement workflow.

Brightpearl invoices map to Acumatica ARInvoice records preserving original invoice numbers, dates, amounts, tax totals, and customer references as ExtRef values for audit continuity. Partial payments attached to Brightpearl invoices generate corresponding Acumatica payment applications automatically applied against the ARInvoice upon migration completion.

Brightpearl bills map to Acumatica APInvoice records preserving vendor references, line items, and amounts for accounts payable tracking. APInvoice IDs are stored alongside Brightpearl bill IDs for audit continuity and cross-reference during reconciliation. Retainage amounts where present map to Acumatica's retainage hold fields for proper accounting treatment.

Brightpearl manual journal entries map to Acumatica JournalTransaction records with account codes and debit/credit amounts preserved exactly as recorded. Account codes must be reconciled against Acumatica's chart of accounts before posting to avoid referential integrity errors. Batch IDs from Brightpearl map to Acumatica Batch module entries to preserve grouping.

Brightpearl warehouse records with aisle-bay-shelf-bin location hierarchy map to Acumatica Warehouse definitions and associated location codes. Zone assignments on Brightpearl locations become Acumatica location codes within each warehouse. Multi-warehouse setups generate one Acumatica Warehouse record per Brightpearl warehouse with corresponding location structures.

Brightpearl inventory adjustment and transfer records map to Acumatica INReleaseDoc (issue) and INReceiptDoc (receipt) entries for inventory movements. Transfer transactions between Brightpearl warehouses generate matched receipt-and-issue pairs in Acumatica's inventory module. Lot and serial numbers tracked in Brightpearl carry forward into Acumatica's lot/serial attributes for traceability.

Brightpearl automation rules govern order routing, status transitions, and accounting period locking based on configurable conditions. Acumatica has no direct equivalent — rules must be rebuilt using Acumatica screen-level workflows, generic inquiries, or PowerShell automation scripts. We export Brightpearl rule definitions as JSON for your consultant's functional specification during the rebuild phase.

Brightpearl reports are platform-specific definitions that do not export to external systems. The underlying financial and transactional data migrates normally to Acumatica. Acumatica reports and Generic Inquiries must be recreated from scratch. We document the complete Brightpearl report list with row counts and data sources for your team to reference during the rebuild process.