Migrate from Brightpearl to Microsoft Dynamics 365 Business Central

Brightpearl Contact records with the customer role flag map to Business Central Customer. The contact's primary address maps to Address fields on Customer, with additional addresses handled as Customer Address records. Email, phone, and payment terms transfer directly. The Brightpearl contact owner maps to the Salesperson/Purchaser code in Business Central if a matching salesperson exists, otherwise the field is held for reconciliation.

Brightpearl Contact records with the vendor role flag map to Business Central Vendor. Vendor-specific fields including lead time, payment terms, and the primary address transfer to the Vendor card. The contact's email and phone map to Vendor contact fields. Vendor-specific custom fields (PCF_*) on vendor contacts map to the Vendor extension table in Business Central.

Brightpearl Products of type Item map to Business Central Item records. Unit of Measure, unit cost, standard cost, and the base price transfer to the Item card. The product type (Inventory Item vs Non-Inventory Item vs Service) is set based on Brightpearl's product type field. SKU maps to the Item's No. field and serves as the dedupe key during import.

Brightpearl Products of type Service map to Business Central Item with the Type = Service flag. Service items do not carry inventory values but retain pricing and description fields. Service billing cycles from Brightpearl's subscription product fields map to Business Central's service contract or job tracking if the customer uses Jobs or Service Management modules.

Brightpearl's four-level location hierarchy (Aisle/Bay/Shelf/Bin) is represented as a nested path string per location and mapped to Business Central Warehouse records with Bin codes. We reconstruct the Zone association by parsing the Zone assignment from Brightpearl and linking the top-level Warehouse to Zone-based Bin codes in Business Central's warehouse configuration. If Brightpearl Zones correspond to separate Warehouses in Business Central, we create one Warehouse per Zone and nest Bins within.

Brightpearl Price List entries (one price per product per price list) map to Business Central Sales Price records linked to the Item and the Customer or Customer Price Group. If a Brightpearl customer has a specific price list assigned, we create a corresponding Customer Price Group in Business Central and assign prices to that group. Multiple price lists per product in Brightpearl become multiple Sales Price lines per Item in Business Central.

Brightpearl Sales Orders map directly to Business Central Sales Order. We preserve the order number as an external document number, the order date as Order Date, and the required shipment date. Line items (product, quantity, unit price, discount) map to Sales Line records. The salesperson/owner maps to the Salesperson Code field. Brightpearl's order-level custom fields (PCF_*) migrate to Sales Header extension fields.

Brightpearl Purchase Orders map to Business Central Purchase Order. The vendor assignment maps to the Buy-from Vendor No. field, and the vendor's address auto-populates. Expected receipt date migrates to Expected Receipt Date. Line items carry product, quantity, and unit cost. Received quantities in Brightpearl are used to set the quantity received on the Purchase Order if migrating partially received orders.

Brightpearl Invoices generated from sales orders map to Business Central Sales Invoice. We map the invoice number, invoice date, and due date. Line items carry to the Sales Invoice lines with pricing. If the Brightpearl invoice is posted, we create a posted Sales Invoice in Business Central with corresponding Customer Ledger Entries. Unposted invoices become Sales Invoice documents requiring posting after review.

Brightpearl Credit Notes map to Business Central Sales Credit Memo. The original invoice reference is stored in the Applies-to Doc. fields if the credit is tied to a specific invoice. Line items carry the credited product, quantity, and price. Posted credit notes create Customer Ledger Entries with the correct entry type for downstream reconciliation.

Brightpearl's Chart of Accounts with account codes maps to Business Central G/L Account records. We create G/L Accounts in dependency order (balance sheet accounts before income/expense) and assign the correct Account Category (Asset, Liability, Equity, Income, Expense) and Account Subcategory. Account numbers from Brightpearl map to the No. field; account names map to Name. The customer chooses whether to use Brightpearl account codes directly or restructure the account numbering scheme.

Brightpearl's inventory summary (total cost value per SKU) and inventory detail (per-warehouse, per-location stock levels) map to Item Ledger Entries in Business Central representing opening balances. We create a positive adjustment entry per Item per Warehouse with the quantity and unit cost from Brightpearl, referencing an Opening Inventory general ledger entry to balance the stock account. Location-level detail populates the Bin content if Business Central's Warehouse Management System is active.

Brightpearl Payments linked to customer invoices map to Customer Payment Journal lines in Business Central, applying to the corresponding posted Sales Invoice. Payments linked to vendor invoices map to Vendor Payment Journal lines. Payment method (credit card, bank transfer, cash) maps to the Payment Method Code in Business Central. Unapplied or partially applied payments are created as separate journals pending reconciliation.

Brightpearl Staff Users and Owner assignments on Contacts and Orders map to Business Central Users. We match by email address during the user provisioning phase. Owner assignments on Brightpearl records (Contact owner, Order owner) map to the Salesperson/Purchaser Code on the corresponding Business Central document. If a Brightpearl owner has no matching Business Central user, the record is held in a reconciliation queue for the customer's admin to provision the user before record migration resumes.

Brightpearl's PCF_* prefixed custom fields on Contacts, Products, and Orders require pre-migration schema setup in Business Central. We create extension fields on the corresponding Business Central tables (Customer, Vendor, Item, Sales Header, Sales Line) with matching data types before any data loads. String PCF fields become Text fields; numeric PCF fields become Decimal or Integer depending on precision; date PCF fields become Date fields. The PCF prefix is stripped from the field name to follow Business Central naming conventions.