Migrate from Epicor BisTrack to Acumatica

BisTrack Part master maps directly to Acumatica InventoryItem for stocked parts and Non-StockItem for special-order items. The PartNumber becomes InventoryID, Description maps to Description, and the ProductClass becomes the Inventory灵柩 relationship. Warehouse assignment uses the PartBin table joined by PartNum and WareHouseID.

Customer records migrate as Acumatica Customer with CUSTID matching the BisTrack CustNum. Billing and ship-to addresses map to the Address table with the same structure. Customer-specific pricing rows in BisTrack require Acumatica CustomerPriceClass or price worksheet entries — FlitStack surfaces each pricing row for manual rebuild in Acumatica's price management module.

Vendor records map 1:1 to Acumatica Vendor entities, preserving the VendorID, vendor name, primary address, and payment terms configuration from BisTrack. The BuyerID field in BisTrack that assigns purchasing responsibility to specific users maps to Acumatica's BuyerID on the Vendor record, maintaining purchasing workflow accountability. Buyer assignments stored as VendorContact records in BisTrack — containing buyer name, email, and phone — translate to Acumatica Contact records with ContactClass='VENDOR' to scope them correctly under the vendor entity for accurate purchasing contact reporting and communication routing.

Open BisTrack sales orders migrate as Acumatica SalesOrder with OrderNbr preserved as an external reference. Each OrderDtl line maps with PartNum, OrderQty, UnitPrice, and the original OrderDate. Closed orders transfer as historical records with the OrderDate intact so Acumatica reporting reflects the full order history.

Open purchase orders in BisTrack translate directly to Acumatica PurchaseOrder records, preserving the original PONumber, vendor reference, and order dates. POLine items carry PartNum, PODetail.Qty, and the original PromiseDate for delivery tracking. Purchase agreements and blanket orders from BisTrack — including release schedules and quantity allocations — become Acumatica blanket PurchaseOrders with release tracking enabled, maintaining the contractual purchasing relationship for recurring supply arrangements with key lumber and building material vendors.

BisTrack stores warehouse assignments in PartBin with WareHouseID and BinNum. Acumatica separates warehouses (Warehouse table) from bin locations (Location table). FlitStack maps each BisTrack warehouse to an Acumatica Warehouse record first, then creates Location records per unique BinNum, then links inventory by InventoryID + LocationID.

BisTrack UOMs (Eaches, Packages, Linear Feet, Board Feet) are stored per-part. Acumatica requires UOM definitions in the UOM table and conversion factors in UOMConversion linked by InventoryID. We extract the BisTrack UOMCode and conversion multiplier and create the corresponding UOM and UOMConversion rows in Acumatica before inventory lands.

Lot and serial numbers from BisTrack's PartLot table migrate to Acumatica's LotSerial tracking table, preserving LotSerialNbr, linked InventoryID, and the original LotEffDate (lot effective date) for FIFO/FEFO costing accuracy. For LBM dealers handling lumber, treated wood, or specialty building materials with lot expiration requirements, the LotExpireDate field maps where populated. Active lots at migration time link to on-hand quantities in Acumatica's INSiteCount table, maintaining accurate available inventory by lot for order picking and shipping confirmation.

BisTrack contact records attached to Customer or Vendor parent entities migrate to Acumatica Contact records, preserving Email, Phone1, Fax, and full Name fields from the source system. The ContactClass attribute is set to 'CUSTOMER' for customer-attached contacts or 'VENDOR' for vendor-attached contacts, scoping each contact to its parent entity so Acumatica's contact reports, email campaigns, and purchase communication routing function accurately. Secondary contacts, backup buyers, and accounts payable contacts are all preserved with their respective roles intact.

BisTrack User Defined (UD) fields on any screen — such as DealerCode, Division, CounterSaleFlags, or region codes — are exported from Smart View and created as custom fields on the corresponding Acumatica DAC (InventoryItem, Customer, Vendor) before data loads. FlitStack names each custom field using the BisTrack UD field label for traceability.

BisTrack ShipVia codes — including common LBM carrier types like UPS Ground, FedEx Freight, LTL carriers (Old Dominion, SAIA, XPO), and regional delivery services — map to Acumatica Carrier records. For each carrier, FlitStack creates the CarrierID using the BisTrack ShipVia code and populates CarrierDescription with the BisTrack description text. If the exact carrier match does not exist in Acumatica's standard carrier list, a new carrier record is created automatically with the BisTrack data preserved, ensuring shipping method routing in Acumatica's sales orders and purchase orders reflects the dealer's established carrier relationships.

Counter sales in BisTrack that generated immediate AR invoice recognition map to Acumatica CashSale transactions for cash-and-carry customer payments and ARInvoice for credit counter sales requiring later settlement. Each counter sale line item — including part number, quantity sold, unit price, and any applicable discounts — maps to Trandoc and CashSaleDetail records with the same InventoryID and quantity for accurate revenue recognition. Tax calculations from BisTrack carry forward to Acumatica's tax engine based on the customer tax zone, and payment method (cash, check, credit card reference) is preserved in the PaymentMethod field for counter sale reconciliation reporting.