Migrate from Epicor BisTrack to Infor CloudSuite Corporate

BisTrack Customer records map directly to Infor CloudSuite Customer. We extract via Smart View SQL or REST API, preserving Customer Number (the critical dedupe key), address fields, contact data, and pricing tier assignments. If the destination CloudSuite uses a different customer numbering scheme, we suppress the source number during import and generate a new CloudSuite customer number per the target configuration. Customer-specific pricing tiers and discount schedules map to CloudSuite Customer Price Group or Contract Price structures.

BisTrack Vendor records map to Infor CloudSuite Supplier. We preserve PO terms, lead times, EDI settings, and vendor-specific contact data. When a default vendor is not set on an Item record in BisTrack, we flag these for resolution during the Vendor import phase and coordinate with the customer to assign defaults before Items load. Supplier-specific pricing tiers map to CloudSuite Supplier Price agreements if the destination edition supports them.

BisTrack Item master records map to Infor CloudSuite Item with SKU, description, bin location reference, pricing, and kit assembly rules. The Max Description Length setting in BisTrack (default 254 chars) may truncate longer descriptions during import if CloudSuite enforces shorter field lengths; we flag and pad or truncate accordingly. Kit assembly structures (BOM headers and components) map to CloudSuite BOM and routing structures with a separate import phase sequenced after the parent Item load.

BisTrack generates special order SKUs using a configurable DefaultSKU prefix pattern (e.g., zz_SOWINDOWS_0001). We capture the customer's SKU generation settings during pre-migration audit and replicate the logic in our import adapter. If CloudSuite uses a different SKU generation rule, we suppress BisTrack's auto-generation during import to avoid conflicts. Special order Items are flagged with a user-defined attribute in CloudSuite to preserve the distinction for counter sales and special order reporting.

BisTrack kit structures (kit header with component Items and quantities) map to Infor CloudSuite Bill of Materials (BOM) with a BOM type of Kit. Component quantity and scrap factors preserve from BisTrack. If the kit has a bill of materials routing with work centers and operation sequences, these map to CloudSuite Routing records attached to the BOM. BOM and Routing are sequenced for import after all component Items have loaded successfully.

BisTrack Sales Order headers and lines map to Infor CloudSuite Sales Order. Order header fields (order number, order date, customer reference, terms) map directly. Order lines reference Item, quantity, unit of measure, pricing, and special order flag. Special order SKUs on lines are resolved by matching to the Item records imported in the Items phase. Back-reference to Customer is resolved via the Customer Number dedupe key established during the Customer import phase.

BisTrack PO records map to Infor CloudSuite Purchase Order. Line items reference Supplier and Item records, so we sequence the import to load Suppliers and Items before POs to maintain referential integrity. Open PO status flags (released, pending, closed) map to CloudSuite PO status. If the destination uses multi-company PO processing, we coordinate with the customer to set the correct company assignment during PO header creation.

BisTrack Quotes accessible via API and the outside sales module map to Infor CloudSuite Quote. We preserve quote status, expiration dates, and conversion history. Quoted line items reference current item prices. If a Quote references an Item that has changed pricing or been discontinued, we flag these records during import scoping so the customer can decide whether to migrate the quote as historical or exclude it from the active migration scope.

BisTrack inventory levels, bin locations, and on-hand quantities per warehouse map to Infor CloudSuite's multi-level warehouse structure. Each BisTrack warehouse maps to a CloudSuite Warehouse; each bin location maps to a Bin within that Warehouse; on-hand quantities map to Item-warehouse on-hand records. Stock history is available via Smart View SQL but may require a separate import phase or archival strategy depending on the volume and the customer's CloudSuite storage planning.

BisTrack AR invoices and payment records are exportable via Smart View SQL. The invoice-to-payment reconciliation lookup interface in BisTrack is reportedly cumbersome; we extract open invoices and payment history via Smart View and flag any records with missing payment linkage for manual reconciliation before AR loads into CloudSuite. Open invoice balances map to CloudSuite AR with customer and invoice number references preserved.

BisTrack AP data including vendor invoices and payment records export via Smart View SQL. Duplicate invoice controls are a native BisTrack feature we flag during import scoping to avoid re-triggering duplicate detection logic in CloudSuite AP that may use different threshold rules. Open AP balances map to CloudSuite AP with vendor and invoice number references preserved.

BisTrack GL accounts accessible via Smart View map to Infor CloudSuite GL Account. We map account numbers and hierarchies to CloudSuite's chart of accounts, noting that segment structures (e.g., department cost centers) may require a different account code format. If BisTrack uses a flat account structure and CloudSuite requires segmented accounts, we decompose the BisTrack account number into the appropriate segment fields during the transform phase.