Migrate from Shipedge to Epicor Prophet 21

Shipedge Customer records (name, email, billing address, shipping address, contact info) map to Epicor Customer and one or more ShipTo records. Shipedge's per-customer carrier preferences and routing rules require Epicor Data directives to recreate as Customer ShipTo overrides or BPM-driven logic. The customer's primary billing address becomes the Customer record address; each unique shipping address becomes a separate ShipTo record with its own ShipToNum.

Shipedge Orders map to Epicor OrderHed (header: order date, customer, terms, PO number, ship via) and OrderDtl (lines: part number, quantity, unit price, warehouse, ship date). Shipedge's fulfillment status (pending, shipped, cancelled) maps to Epicor OrderRel.Status and OrderHed.OpenLine/OpenOrder flags. We preserve the original Shipedge order number as a user-defined field on OrderHed for audit traceability.

Shipedge Products (SKU, variant attributes, barcodes, supplier links) map to Epicor Part records. Shipedge variant attributes (size, color, style) map to Part character fields or user-defined columns depending on the Epicor field configuration. Barcode values migrate to Part.Large Picture or a user-defined barcode field. Shipedge's product type (kit, standard, bundle) influences the Part.TypeCode (Stocked, Make-to-Order, Configured) in Epicor.

Shipedge warehouse-specific inventory quantities map to Epicor PartWhse (per-warehouse stocking status) and PartBin (per-bin quantity). Each Shipedge warehouse maps to an Epicor Plant/Warehouse combination. Lot numbers and bin locations from Shipedge migrate to PartBin.LotNumber and PartBin.BinNum. Bin assignments not present in Shipedge default to the warehouse's standard receiving bin.

Shipedge kit configurations (bundle structure and component links) map to Epicor Part records with Part.TypeCode = Phantom or Make and a corresponding BOM. Shipedge kitting type (on-the-fly assembly vs. pre-built) determines whether the BOM is a standard BOM (pre-built stock) or a Phantom BOM (explodes at job creation). The kit parent SKU becomes the Part; each component SKU becomes a BOM line with a quantity-per relationship.

Shipedge Supplier records (name, contact, lead time, SKU associations) map to Epicor Supplier and SupplierPP (per-part supplier price breaks). Shipedge's supplier lead time per product maps to SupplierPP lead time or the Part.PurchasingFactor field. Supplier terms and payment methods migrate as Supplier records with default terms that can be overridden at the Purchase Order line level.

Shipedge shipment records (carrier, service level, tracking number, weight, dimensions) map to Epicor ShipHead and ShipDtl. Carrier and service level values from Shipedge (UPS Ground, FedEx 2Day, USPS Priority) migrate as Epicor ShipVia codes. Tracking numbers preserve in ShipHead.BOLNumber or ShipDtlTracking. We flag carrier accounts requiring reconnection in Epicor's Shipping transaction configuration.

Shipedge Return Authorizations (RA number, reason codes, disposition) map to Epicor RMA and RMADtl records. Shipedge return reasons (defective, wrong item, changed mind) map to Epicor ReasonCode values that the customer configures before migration. Disposition codes (restock, dispose, repair) map to RMADtl.ReturnChargeType. We flag any disposition mapping that requires Epicor warehouse receiving workflow reconfiguration.

Shipedge warehouse records (site name, address, operating hours, carrier accounts) map to Epicor Plant and Warehouse entities. Shipedge's carrier rate profile associations per warehouse require Epicor ShipVia configuration per Plant. Multi-warehouse Shipedge accounts (common for 3PL clients) map to multiple Epicor Plant records if separate GL books are needed, or to multiple Warehouse records within a single Plant for shared inventory pools.

Shipedge batch fulfillment records (batch number, order count, SKU count, units, ship method) do not have a direct Epicor equivalent as batch records are specific to Shipedge's v11+ fulfillment workflow. We export batch metadata as a linked CSV file attached to the relevant OrderHed records and note that Epicor's Job (work order) or MPS scheduling replaces batch-level reporting in Epicor.

Shipedge user accounts (name, email, role, warehouse assignment) map to Epicor User records. We export user name, email, and role for manual provisioning in Epicor. Authentication credentials cannot transfer; all users must be provisioned fresh in Epicor Identity with appropriate Plant and Warehouse security assignments configured by the customer's admin.

Shipedge Order Rules (automated routing logic: warehouse selection, carrier assignment, split-order conditions) are Shipedge-specific workflow configurations stored in a proprietary format with no documented export mechanism. We flag all active Order Rules during discovery and deliver a written inventory with Epicor equivalent recommendations using Epicor Data directives (record-change rules) and BPMs (method-override logic). Rule recreation is a 1-3 day manual exercise depending on complexity and is outside the standard migration scope.