Migrate from Brightpearl to Epicor Prophet 21

Brightpearl stores both customers and vendors as Contact records, differentiated by a role flag. We split these at migration time: Contact records with customer role map to Epicor AR Customer (CustCnt and CustBank records with address and contact detail), and Contact records with vendor role map to Epicor AP Supplier (VendorPP and VendBank records). The Brightpearl contact email and phone fields map to CustCnt conEmail and conPhone. We preserve any PCF_* custom field values on Contact as UDF fields on the destination Customer or Supplier record. Owner assignment from Brightpearl maps to Epicor SalesRep records resolved by email match.

Brightpearl's Chart of Accounts with structured account codes maps directly to Epicor GL Account (GLAccount table). Account code, account name, and account type (asset, liability, equity, revenue, expense) migrate as GLAccount and GLAccountType records. We extract the full account code list from Brightpearl and map each to the destination system's account codes established during Epicor implementation, preserving account balances where the migration includes open GL periods. The account hierarchy (parent/segment structure) maps to Epicor's Natural Account and Statistical Account segments.

Brightpearl Products map to Epicor Part records. The Brightpearl SKU becomes Part.PartNum, product name becomes Part.PartDescription, and product type maps to Part.TypeCode (stocked, non-stock, service). We preserve all PCF_* custom fields as Epicor PartUDF records with matching field labels and data types. Brightpearl's multiple price lists per product map to Epicor PricePer and PriceLbr records linked to the Part, resolved by currency and price break quantity. Product type (Item vs Service) in Brightpearl maps to Part.TypeCode in Epicor.

Brightpearl's four-level Aisle/Bay/Shelf/Bin location hierarchy grouped into Zones requires flattening to Epicor's Site/Warehouse/Bin structure. We represent each Brightpearl location path as a concatenated Bin string (Aisle-Bay-Shelf-Bin format) and map the Zone to the Epicor Warehouse code. Zone-to-Warehouse association is preserved as a configuration note in the migration manifest. Epicor Warehouse codes are created during schema setup and referenced by PartBin records during inventory migration. Multi-warehouse customers require multiple Site/PartWhse/PartBin entries per product.

Brightpearl Sales Orders map to Epicor OrderHed (header) and OrderRel (release) records. The order number, order date, and customer reference map to OrderHed.OrderNum, OrderHed.OrderDate, and OrderHed.Cust_PO. Line items with SKU, quantity, and price map to OrderRel with PartNum, SellingQuantity, and UnitPrice. We resolve Brightpearl customer contact IDs to Epicor AR Customer and CustCnt records at migration time. Order status in Brightpearl (pending, confirmed, shipped, invoiced) maps to Epicor OrderRel.ProdStatus and OrderRel.LineStatus. We flag any Brightpearl orders in a locked accounting period that would conflict with Epicor's fiscal period restrictions.

Brightpearl Purchase Orders map to Epicor POHeader and POLine. PO number, PO date, and vendor reference map to POHeader.PONum, POHeader.PODate, and POHeader.BuyerID. We resolve Brightpearl vendor Contact IDs to Epicor AP Supplier records during migration. POLine records carry PartNum, Quantity, DueDate, and JobNum (if the PO is linked to a production job). Lead time and expected delivery dates from Brightpearl become POLine.PromiseDate. Received quantities in Brightpearl map to POLine_received values in Epicor, and POLine status reflects the current receipt lifecycle.

Brightpearl Invoices map to Epicor InvcHead (accounts receivable invoice header). Invoice number, invoice date, and total map to InvcHead.InvoiceNum, InvcHead.InvoiceDate, and InvcHead.TotalAmt. Brightpearl's embedded accounting data (tax, discount, payment terms) map to InvcHead.TaxAmt, InvcHead.Discount, and InvcHead.TermsCode. Credit notes from Brightpearl map to Epicor InvcHead with CreditMemo = true. Line items migrate as InvcDtl records linked to the InvcHead. We note that Epicor's invoice numbering and fiscal period assignment require the GL and AR periods to be open for the invoice date at migration time.

Brightpearl Price Lists associate a price value with a product and a price list identifier. We map each Brightpearl PriceList to an Epicor PricePer record linked to the corresponding Part, with the price value mapping to PricePer.UnitPrice and the currency mapping to PricePer.CurrencyCode. Multiple price lists per product (common in Brightpearl) are preserved as multiple PricePer records with distinct price codes. Price break quantities and effective dates from Brightpearl map to PricePer BreakQty and PricePer.QualifyByDate fields where present.

Brightpearl inventory summary (total cost value per SKU) and inventory detail (per-warehouse, per-location stock levels) map to Epicor PartWhse (warehouse-level summary) and PartBin (per-bin detail) records. We reconstruct the stock position from Brightpearl's four-level location hierarchy into PartBin.BinNum using the concatenated location path, and aggregate to PartWhse.OnHandQty per Site/Part combination. Total cost value from Brightpearl maps to PartWhse.DemandUOM and PartWhse.OnHandQty with a unit cost calculation. Stock status (available, allocated, in quarantine) from Brightpearl maps to PartBin.LotNo or a PartBin UDF field depending on the customer's configuration.

Brightpearl assigns a staff member as the Owner of a Contact and can auto-assign orders to the contact owner. We export the full user roster and map each Brightpearl owner by email to an Epicor User account (UserFile) and a SalesRep record (SalesRep table) with the matching Repcode. Owners without a matching Epicor User are placed in a reconciliation queue for the customer's Epicor administrator to provision before record import proceeds. Owner assignment on orders maps to OrderHed.RepID after SalesRep resolution.

Brightpearl Automation rules (conditional triggers and actions against incoming orders, status updates, and post-purchase workflows) do not migrate. The Brightpearl rules engine and Epicor Kinetic Workflow/Process Management are architecturally distinct, and Epicor's automation context (production jobs, MES, shop-floor routing) differs fundamentally from Brightpearl's retail order-processing model. We deliver a written inventory of every active Brightpearl Automation rule with its trigger condition, action sequence, and scope (contacts, orders, inventory). The customer's Epicor administrator or implementation partner rebuilds these in Kinetic Workflow or Epicor Process Management post-migration.

Brightpearl analytics dashboards and custom reports do not migrate. Epicor's reporting architecture uses Kinetic BAQ (Business Activity Queries) and Power BI integration for advanced analytics, which is structurally different from Brightpearl's report builder. We deliver a manifest of every Brightpearl report and dashboard with its data source tables, filters, and scheduling. The customer's Epicor administrator rebuilds these as BAQ reports or connects the Epicor data to a BI tool of their choice.