Migrate from Epicor BisTrack to Dolibarr ERP

BisTrack Customer records map to Dolibarr ThirdParty with category set to Customer. Address, contact, pricing tier, and Customer Number fields migrate directly. The Customer Number field is the dedupe key during import; we suppress auto-increment on Dolibarr to preserve BisTrack's numbering sequence where it is meaningful for downstream integrations. Default customer settings that are unset in BisTrack require coordination with the customer during scoping to assign sensible defaults in Dolibarr.

BisTrack Vendor records map to Dolibarr ThirdParty with category set to Supplier. PO terms, lead times, EDI settings, and vendor-specific pricing tiers preserve. Contact data migrates to Dolibarr contacts attached to the ThirdParty. If a default customer is not set in BisTrack, we coordinate with the customer to define one before vendor import so that cross-reference lookups remain consistent.

BisTrack Item master records map to Dolibarr Product with SKU preserved as ref. Description, pricing tiers, and bin location fields migrate to Dolibarr's product fields and custom location fields. Kit assembly rules (BOM structures) migrate to Dolibarr's BOM module if activated; if the BOM module is not active, we document the kit structures in a separate output and the customer activates it post-migration. The Max Description Length setting (default 254 characters) may truncate longer item descriptions; we flag and preserve full text in a custom field during import.

BisTrack Sales Order headers and lines map to Dolibarr Commande records. Line-level pricing, quantities, and back-referenced Customer and Item lookups migrate directly. Special order SKUs generated using the DefaultSKU prefix (e.g., zz_SOWINDOWS_0001) are captured during extraction and re-imported as product references in Dolibarr; we suppress Dolibarr's auto-SKU generation during this phase to avoid conflicts with the preserved BisTrack SKU pattern.

BisTrack Purchase Order records export via Smart View SQL and map to Dolibarr CommandeFournisseur. Line items reference Vendor and Item records, so we sequence Vendors and Items before POs to maintain referential integrity. PO status (Draft, Sent, Received, Closed) maps to Dolibarr statuts. Receipt line quantities and partial receipt tracking requires a post-migration reconciliation step if the customer's receiving workflow differs from BisTrack's receiving module.

BisTrack Quotes accessible via API and the outside sales module map to Dolibarr Propal. Quote status, expiration dates, and conversion history preserve. Quoted line items reference current item pricing; we migrate line items as frozen pricing at the time of quote rather than linking to live product prices. Expiration dates that have passed are flagged for the customer's admin to close or regenerate in Dolibarr.

BisTrack inventory levels, bin locations, and on-hand quantities per warehouse export via Smart View SQL and map to Dolibarr Stock. Bin-location sub-structures that BisTrack supports natively require either Dolibarr's multi-warehouse setup with location notes or a third-party stock-location add-on; we configure a standard warehouse structure during migration and document any bin-level data for post-migration configuration.

BisTrack AR invoices and payment records export via Smart View SQL and map to Dolibarr Facture records. Invoice-to-payment reconciliation is preserved through invoice reference matching. Open invoices migrate with status Open; paid invoices migrate with status Paid and payment records attached. The Dolibarr payment module is activated during schema setup to support the reconciliation workflow.

BisTrack AP data including vendor invoices and payment records export via SQL and map to Dolibarr FactureFournisseur records. Duplicate invoice controls native to BisTrack are flagged during import scoping to prevent re-triggering; we document any active duplicate-invoice rules as Dolibarr validation rule equivalents for the admin to configure post-migration.

BisTrack GL accounts accessible via Smart View map to Dolibarr's accounting module accounts. Account numbers and hierarchies migrate 1:1. Segment structures such as department cost centers that exist in BisTrack as multi-dimensional accounts may require mapping to Dolibarr's auxiliary account dimensions or a custom accounting configuration; we document the source segment structure during scoping and design the destination chart before import.

BisTrack user-defined fields (UD codes) with per-field security settings via Field Security Maintenance extract and map to Dolibarr ExtraFields. We preserve the same access restrictions using Dolibarr's field-level visibility settings per user or group. UDFs referencing dropdown lists map to Dolibarr select or checkbox field types with the same option lists.

BisTrack role-based dashboards and Smart View grid configurations are user-built and stored in a non-API-exportable format. We document every active dashboard and Smart View during the pre-migration audit with a description of its purpose, data sources, and filters. The customer rebuilds these in Dolibarr using the exported data dictionary and our field mapping reference. This is standard scope exclusion: dashboards and reports are written to a deliverable document, not migrated as code.