Migrate from Epicor BisTrack to Epicor Prophet 21

BisTrack's flat Customer record (with address, pricing tier, and default terms on one entity) maps to Epicor ERP's two-record Customer-CustCnt structure. We split the address and primary contact data into the CustCnt record linked to the Customer parent. The BisTrack Customer Number becomes Customer.CustNum; the primary contact's name and email land in CustCnt.Name and CustCntEMail. Pricing tiers and credit limits migrate as Customer-level fields. This split is the primary schema design decision for the migration and must be resolved before any record import begins.

BisTrack Vendor records map to Epicor ERP Vendor with VendCnt for vendor-specific contacts. PO terms, lead times, EDI settings, and vendor-specific pricing tiers migrate to Vendor-level fields. When BisTrack's Use Customer Number flag is set in a Vendor Module, we capture that association for cross-referencing during PO migration. The Vendor ID maps to Vendor.VendorID as the dedupe key.

BisTrack Item master records map to Epicor ERP Part with SKU in PartNum, description in Part.Description, and bin location data mapped to PartBin per warehouse per bin. Kit assembly parent items require PartMtl records created during import, with kit component lines linking to the parent PartNum. The Max Description Length setting (default 254 chars) may truncate during import if the destination field length is shorter; we flag this during scoping and apply truncation with a suffix indicator.

BisTrack Sales Order headers map to Epicor ERP OrderHed and lines to OrderDtl. The customer reference and PO number migrate to OrderHed.CustomerPoNum and OrderHed.PONum. Back-referencing to the Customer and CustCnt records resolves at import time via CustNum lookup. Special order SKUs require special handling: we capture the DefaultSKU prefix configuration during pre-migration audit and either suppress BisTrack's auto-generation during import or replicate the same pattern in our adapter to avoid SKU conflicts on the destination.

BisTrack PO records export via Smart View SQL and map to Epicor ERP POHeader and PODetail. Line items reference Vendor and Part records, so we sequence the import to load Vendors and Parts before POs to maintain referential integrity. PO release scheduling, terms, and FOB data migrate to POHeader fields. If BisTrack holds partially received POs, the received quantity maps to PODetail.PurchasedQty and open quantity to PODetail.OrderQty minus received.

BisTrack Quotes (accessible via API and the outside sales module) map to Epicor ERP QuoteHed and QuoteDtl. Quote status, expiration dates, and conversion history are preserved. Quoted line items reference current Part prices. Outside sales attachments migrate as ContentDocument records linked to the Quote.

BisTrack inventory levels, bin locations, and on-hand quantities stored per warehouse export via Smart View SQL. We map to Epicor ERP PartBin records per warehouse per bin per part. The Warehse and WhseBin tables are created or validated before PartBin import so that all warehouse-bin references resolve. Lot control settings from BisTrack migrate to Part.LotSnglIssue and Part.LotMfg皮克 flags. Stock history is available in BisTrack but may require a separate historical archive scope depending on audit requirements.

BisTrack kit structures with exploded pricing require BOM replication in Epicor ERP. The kit parent item migrates as a Part record with PartBom: true. Component lines become PartMtl records linking to the parent PartNum with quantities and unit measures. Kit pricing from BisTrack maps to the Quote or Order line with the kit's total price, while Epicor ERP's PartMtl maintains the component breakdown for manufacturing and picking logic. We preserve the kit's pricing hierarchy in a custom field for audit.

BisTrack counter-sale transactions represent a specific data pattern: cash or card payment, immediate inventory decrement, and receipt generation in a single session. We extract counter-sale order headers and lines via Smart View SQL, flagging the payment method and tender amount. These map to Epicor ERP OrderHed and OrderDtl records with OrderRel for shipments. Cash drawer data migrates as CashGrp records for register reconciliation. The customer team should verify POS module licensing in Epicor ERP before migration, as POS functionality may require an additional module beyond standard distribution.

BisTrack AR invoices and payment records export via Smart View. Open invoices map to Epicor ERP InvcHead and InvcDtl. The invoice-to-payment reconciliation uses Epicor ERP's CashRcpt and CashBcDetail tables. BisTrack's cumbersome invoice lookup interface is a known pain point; we extract a clean open-invoice report from BisTrack before migration and re-enter open balances in Epicor ERP to avoid carry-forward reconciliation issues.

BisTrack AP data including vendor invoices and payment records exports via Smart View SQL. Duplicate invoice controls native to BisTrack are flagged during import scoping to avoid re-triggering duplicate detection during AP import. Open AP balances migrate as APInvHed records with pending or open status. Vendor payment terms and due dates preserve. Historical payments link via APTran records.

BisTrack GL accounts export via Smart View. We map account numbers and hierarchies to Epicor ERP's chart of accounts with attention to segment structures. If BisTrack uses a department cost center segment, we map it to a corresponding Epicor ERP segment type (e.g., Department, Division) or a GLGpc context value. Multi-segment GL charts require the segment definition (COASegment table) to be configured in Epicor ERP before account import; we include this configuration step in the pre-migration checklist.

BisTrack user-defined fields (UD codes) with per-field user-level security settings via Field Security Maintenance extract via Smart View SQL and map to Epicor ERP UD tables (zDataField, UDColumn, UDRow). We apply the same access restriction logic post-migration so that field visibility mirrors the BisTrack configuration. Epicor ERP's UD table setup requires the UD table name and column definitions to be created before data import; we handle schema creation first.

BisTrack role-based dashboards and Smart View grid configurations are user-built and not API-exportable in structured form. We document the active dashboard and Smart View configurations during scoping, exporting the data output via Smart View SQL so that the report content migrates even if the dashboard layout does not. The customer's Epicor ERP admin rebuilds dashboards using BAQ (Business Activity Query) and Report Designer based on our documented data dictionary export.