Migrate from Blue Link ERP to Epicor Prophet 21

Blue Link Customer records map to Epicor Customer and the underlying Partytbl (party) record. We preserve contact details, multi-currency settings, and credit status fields. Blue Link's multi-currency flags map to Epicor's currency configuration on the party record. Customer is imported before Sales Orders so that the CustNum reference is satisfied at the time of order header insert. Address records map to Epicor CustomerShipTo and are linked via ShipToNum.

Blue Link Vendor records map to Epicor Supplier and the underlying Partytbl. Payment terms, currency flags, and address records transfer directly. Vendor-to-PO linkage is preserved by migrating Vendors before Purchase Orders. If Blue Link vendors use multi-currency, we map the currency configuration to Epicor's Supplier currency record and flag any vendor records where the payment terms convention differs from Epicor's standard terms table for admin reconciliation.

This is the highest-complexity mapping in the pair. Blue Link stores inventory as a single Item record with multiple UOMs embedded. Epicor separates Part master data (Part table), UOM assignments (PartUOM table), Site (Site table), and Warehouse/Bin locations (WarehouseBin table). Each Blue Link inventory item with multiple UOMs decomposes into one Epicor Part record plus one PartUOM row per UOM. Reorder points and bin assignments decompose to Site and WarehouseBin. Lot tracking flags map from Blue Link's lot number fields to Epicor's lot traceability configuration at the Site level. Customers with 2,000+ items and multiple UOMs per item see inventory record count multiply significantly; we surface this decomposition count in the scoping phase so the customer is not surprised post-migration.

Open Blue Link AR invoices map to Epicor AR Invoice records with invoice number, customer reference, invoice date, due date, and open amount. Invoice lines map to Epicor InvoiceLine with part number, quantity, unit price, and tax code. Collections history from Blue Link does not migrate as activity log entries in Epicor; we flag this gap and recommend the customer export collections history as a CSV for reference. Credit limit data migrates to the Customer record's credit limit fields.

Open Blue Link AP invoices map to Epicor AP Invoice records with vendor reference, invoice date, due date, and open amount. Invoice lines map to Epicor AP InvoiceLine with part number, quantity, and unit price. Payment terms and cash requirements migrate from Blue Link to Epicor's AP terms configuration. Any partially paid or disputed AP invoices are flagged in the reconciliation phase for the customer's AP team to review and resolve before or immediately after go-live.

Open Sales Orders migrate last, just before Go-Live, per Blue Link's own sequencing guidance. Order headers map to Epicor SalesOrder with OrderNum, Customer reference (CustNum already resolved), order date, and requested date. Order lines map to Epicor OrderDtl with part number (PartNum resolved via the Part mapping), quantity ordered, quantity fulfilled to date, and unit price. We flag partial-ship order lines for the customer's operations team to reconcile after go-live. Any order that ships between the final data extract and the cutover delta run is caught by a within-24-hours delta validation check.

Open Purchase Orders map to Epicor POHeader with vendor reference (VendorNum resolved via Vendor mapping), PO date, and required date. PO lines map to Epicor POLine with part number, quantity ordered, quantity received to date, and unit cost. PO-to-receipt linkage (partial receipts already received in Blue Link) is preserved by mapping received quantities and flagging any open POLine records where the received quantity does not equal the ordered quantity. Vendor confirmation status migrates as-is; the Epicor admin reconciles any PO with a status that requires re-confirmation in the destination.

Blue Link's full Chart of Accounts hierarchy maps to Epicor GL Account records with Account Number, Description, and active status. Blue Link's departmental or cost center segments map to Epicor's account structure; if Blue Link uses custom segments beyond the standard account number, we map each segment to a separate Epicor GL Account segment or to a custom field on the account record, depending on the customer's Epicor account code convention. Any account number that conflicts with an existing Epicor account code is flagged for renumbering or suffix adjustment before migration.

Blue Link multi-warehouse and bin-level locations map to Epicor Site, Warehouse, and WarehouseBin. Each Blue Link warehouse becomes an Epicor Site if the customer has distinct legal entities or regional reporting needs, or a Warehouse within a single Site if operational segmentation is sufficient. Bin-level assignments map to WarehouseBin. If Blue Link bin-level assignments cannot be preserved due to differences in bin naming conventions, we flag the bin assignment gap and document it for manual reconfiguration post-migration.

Lot number assignments from Blue Link map to Epicor PartLot records linked to the Part master. Lot expiration dates, lot attributes, and lot-controlled inventory quantities migrate. If Blue Link tracks lot genealogy (which lot supplied which outbound shipment), we document the genealogy structure and flag whether the customer requires PartLot tracing in Epicor, which requires site-level configuration before lot data can be loaded.

Blue Link document attachments stored at the record level use a proprietary format not accessible via a documented export endpoint. We do not migrate document attachments. During the data audit phase, we flag every record type that carries document attachments (typically Orders, Inventory Items, and Transactions), count the attachment volume, and advise the customer to use Blue Link's built-in export or engage Blue Link support for binary file extraction. The attachment inventory is documented in the migration runbook so nothing is silently skipped.

Blue Link's Amazon, eBay, and Shopify channel integrations pull orders into the system with channel metadata. Historical eCommerce orders migrate as Epicor SalesOrder records with a custom field or OrderMsc (misc charge) line carrying the channel source. Channel metadata (marketplace, channel order ID, fulfillment status) is preserved in a custom field for reporting and reconciliation. We recommend the customer's Epicor admin evaluate the native Shopify or Amazon connector for Epicor if ongoing eCommerce sync is required post-migration.