Migrate from eCommerce Pro to Epicor Prophet 21

eCommerce Pro Products with variants map to Epicor Part records where the parent product becomes the Part and each variant becomes either a Part Revision (PartRev) for BOM-driven variants or a PartUOM for unit-of-measure variants. We map the source SKU to Part Number, product name to Part Description, and variant metafields to Part Extension custom fields. Products without variants map 1:1 to Part records. The Epicor Part Plant record is created for each active warehouse in the destination Plant configuration.

eCommerce Pro product categories and tags map to Epicor PartClass records for classification, and to PartWhse records for warehouse-specific stocking. Multi-warehouse setups in eCommerce Pro require us to create one PartWhse record per source warehouse per Part, mapping the source warehouse ID to the Epicor Plant code and bin location to the PartWhse Bin Num field.

eCommerce Pro product type taxonomy and collection hierarchies map to Epicor Product Group records for reporting and inquiry purposes. Product Group assignment is set on each Part record at import time based on the source product's primary category assignment.

eCommerce Pro Customer records map directly to Epicor Customer records. We map customer name to CustID and Company, email to Primary Contact email, and address to the Epicor ShipTo record attached to the Customer. Customer pricing tier and account status from eCommerce Pro migrate to custom fields on the Epicor Customer record since standard Epicor Customer does not have a native pricing tier attribute.

eCommerce Pro Orders map to Epicor SalesOrder records with OrderNum as the key. Order line items map to OrderDtl records, with source product variants resolved to Part PartNum and UOM codes. Ship-to addresses map to OrderRel release records for multi-shipment handling. Order status (pending, processing, shipped, cancelled) maps to the Epicor OrderRel OpenStatus and Shipped flags.

eCommerce Pro order line items migrate to Epicor OrderDtl records. We resolve the source product variant to the Epicor Part PartNum, map quantity to OrderQty and SellingQuantity, map unit price to DocUnitPrice, and preserve the source line item ID as a custom field for reconciliation. Discount amounts stored on eCommerce Pro line items map to Epicor OrderMsc miscellaneous charge records with negative values.

eCommerce Pro fulfillment records with tracking numbers and carrier information map to Epicor Shipment records linked to OrderRel. Carrier name and tracking URL migrate to the Shipment's tracking info fields. For partial fulfillments, we create multiple Shipment records per OrderRel release to preserve the fulfillment timeline.

eCommerce Pro inventory quantities per warehouse map to Epicor PartWhse OnHandQty. We resolve source warehouse IDs to Epicor Plant codes during scoping and map the inventory quantity at the Part-Plant level. Negative or reserved quantities map to PartBin records for bin-level tracking if the destination Epicor environment uses bin locations.

eCommerce Pro vendor or supplier records (if present in the source platform) map to Epicor Supplier records. We map supplier name to VendorID and Company, email to Primary Contact, and address to the Epicor RemitTo or PurPoint record. Supplier-specific product pricing from the source maps to SupplierPP Part Procurement records if the customer uses Epicor's supplier pricing features.

If eCommerce Pro tracks purchase orders or supplier orders, these map to Epicor POHeader and PODetail records. We resolve source supplier IDs to Epicor Supplier VendorID, map line items to PODetail with Part PartNum resolution, and preserve PO status (open, closed, cancelled) in the POHeader Status field.

eCommerce Pro discount codes and coupons with percentage or fixed-amount values map to Epicor OrderHed Promo Codes or OrderMsc miscellaneous charge records depending on whether the discount applies to the entire order or specific line items. Percentage discounts are stored as negative OrderMsc amounts calculated against the order subtotal. The customer reconciles any tiered or stacking discount logic post-import since Epicor's native discount model differs from eCommerce Pro's coupon engine.

eCommerce Pro custom objects (custom product attributes, extended customer fields, or bespoke order metadata) migrate to Epicor UD (User Defined) tables with matching field names and data types. We pre-create the destination UD table schema including UD fields, data types, and related-entity lookups before any data import. Custom object dependencies on Products, Customers, or Orders resolve at migration time through the parent-record key mapping.