Migrate from Epicor BisTrack to Microsoft Dynamics 365 Business Central

BisTrack Customer records map to Dynamics 365 Customer (Account) with a primary Contact record derived from the Customer's main contact fields. The BisTrack Customer Number becomes the Dynamics Account Number, which is the dedupe key during import. We extract the primary contact name, email, phone, and address from the BisTrack Customer record and create a linked Contact record. If the BisTrack customer has multiple contacts, we create additional Contact records linked to the Account.

BisTrack Vendor records map directly to Dynamics 365 Vendor. The Vendor Number becomes the Vendor Account Number. We preserve PO terms, lead times, EDI settings, and vendor-specific pricing tiers. When a default customer is not set in BisTrack for vendor-specific pricing, we coordinate with the customer to assign the default in Dynamics 365 before import.

BisTrack Item master records map to Dynamics 365 Items (Product2 in Business Central, released products in Finance and Supply Chain). SKU, description, bin location, and pricing migrate directly. Kit assembly rules require special handling: if the BisTrack item is a kit with component relationships, we map the kit structure to a Bill of Materials in Dynamics 365. The Max Description Length setting (default 254 characters) may truncate in Dynamics if the destination enforces shorter field lengths; we flag this during pre-migration audit.

BisTrack Sales Order headers and lines are exportable via Smart View SQL. Special order SKUs generated using the DefaultSKU prefix convention (e.g., zz_SOWINDOWS_0001) require pre-seeded number sequences in Dynamics 365 or suppression of auto-generation during import to avoid SKU conflicts. We map order header status, customer reference, and line-level pricing, then back-reference the customer and item records using the lookup resolution sequence. We load Vendors and Items before Sales Orders to maintain referential integrity.

BisTrack Purchase Order records extract via Smart View SQL with line items referencing Vendor and Item records. We sequence the import to load Vendors and Items before Purchase Orders to maintain referential integrity. PO status, terms, and expected receipt dates migrate. If the BisTrack PO references special-order SKUs, we resolve those against the number sequence configuration before import.

BisTrack Quotes accessible via API and the outside sales module map to Microsoft Dynamics 365 Sales Quote. We preserve quote status, expiration dates, and quoted line items referencing current item pricing. Conversion history (Quote to Order) migrates as a linked relationship rather than a state transition, since Dynamics 365 handles quote-to-order conversion natively.

Inventory levels, bin locations, and on-hand quantities are stored per warehouse in BisTrack. We extract via Smart View SQL and map to Dynamics 365 warehouse and location entries. The bin-location structure in BisTrack maps to Location codes in Business Central or Warehouse Management locations in Finance and Supply Chain. Stock history is available but may require separate extraction with a date-range filter to limit scope.

BisTrack AR invoices and payment records export via Smart View SQL. The lookup interface for invoice-to-payment reconciliation is reportedly cumbersome in BisTrack; we handle the matching during the transform phase using invoice number and payment date. Open invoices migrate as open entries; closed invoices migrate as closed entries with payment date. Dynamics 365 uses the general ledger posting profile to determine how AR entries are posted.

BisTrack AP data including vendor invoices and payment records exports via Smart View SQL. Duplicate invoice controls are a native BisTrack feature we flag during import scoping to avoid re-triggering duplicate detection logic during import. Open AP invoices migrate as open entries; closed invoices migrate with payment date. We map to Dynamics 365 vendor posting groups and payment terms.

BisTrack GL accounts extract via Smart View. We map account numbers and hierarchies to the Dynamics 365 chart of accounts. Segment structures in BisTrack (e.g., department cost centers) may require mapping to separate Dimensions in Dynamics 365 (Business Unit, Department, Division, Project) depending on the customer's account structure. We document the segment mapping during scoping before any data moves.

BisTrack counter-sale transactions (POS transactions) are complex records with header, payment, and line components. We extract the transaction header (customer, date, tender type) and line details (item, quantity, price) via Smart View SQL, then map to Dynamics 365 posted sales invoices or shipment records depending on whether the transaction has been invoiced in BisTrack. We flag whether the counter-sale should be posted as an invoice or as a shipment-and-later-invoice in Dynamics.

BisTrack user-defined fields (UD codes) with per-field user-level security settings via Field Security Maintenance map to Dynamics 365 custom fields or extensions. We extract UDF definitions and data, applying the same access restrictions in Dynamics where possible via field-level security groups. The destination field type must be determined during scoping (text, number, date, picklist) to ensure proper data type mapping.

BisTrack outside sales module records (quotes, orders, customer info accessed by field sales) map to Dynamics 365 Opportunities or Sales Quotes depending on whether the record represents an early-stage quote or a confirmed order. The outside sales territory assignment maps to a Microsoft Dynamics 365 Sales Territory if configured.

BisTrack kit assembly rules embedded in the Item master map to Dynamics 365 Bills of Materials. The kit header item becomes the parent BOM item; the components become BOM lines with quantity-per. Kit pricing rules migrate as sales prices on the parent item or as separate pricing sheets linked to the kit.