Migrate from Kentro ERP & 3PL to Epicor Prophet 21

Kentro Products with variants, SKU-level tracking, and pricing tiers map to Epicor Part Master records. Each Kentro product variant becomes a separate Part record with the Kentro SKU preserved in Part Number, and the parent product structure mapped to Part Class or a grouping Part for BOM-style variants. Pricing tiers migrate to Part Price records with effective dates. We extract the Kentro product attribute sets and map them to Epicor Part UOM, Part Class, or custom UD fields.

Kentro's variant hierarchy (parent product with child variant SKUs) maps to Epicor Part Master with a grouping structure. We create a parent Part record for the base product and child Part records for each variant, with the parent-child relationship preserved via Part Lot or a custom UD reference field. The Kentro variant attributes (size, color, material) map to Part Attr records or Part Characteristic records in Epicor Kinetic.

Kentro real-time inventory positions across warehouse locations map to Epicor Part Site records (one per Part-Warehouse combination) with Quantity On Hand. Bin-level detail from Kentro maps to Part Bin records under the Part Site. FIFO/FEFO tracking logic is preserved as a custom field or note since Epicor natively supports FEFO picking logic through warehouse configuration. Open reservations migrate as Part AllocQty on Part Site.

Kentro's multi-warehouse setup maps to Epicor Plant and Warehouse records. Each Kentro warehouse becomes a Plant (or a Warehouse within a Plant) in Epicor, with the Kentro warehouse code preserved in the Warehouse ID for reference. We configure Plant planning parameters (MRP, scheduling) per Epicor requirement during migration.

Kentro Orders across their full lifecycle (channel receipt through fulfillment and returns) map to Epicor Sales Order records. Order status from Kentro (pending, processing, shipped, returned) maps to Epicor Order Rel and Order Dtl status fields. The Kentro order number becomes the Customer PO; the Kentro internal order ID becomes a custom field. Open orders and historical orders migrate with their line items, quantities, and pricing.

Kentro Order line items map to Epicor OrderDtl (order detail) records with PartNum, OrderedQty, UnitPrice, and discount information. Fulfilled quantities map to OrderRel (release) records. If Kentro tracks partial shipments, we create multiple OrderRel records per line item to preserve the shipment history.

Kentro B2C customers map to Epicor Customer records with the customer name, email, and phone preserved. Addresses migrate as ShipTo records linked to the Customer. Account-level pricing terms from Kentro map to Customer Price Group codes. We use the Kentro customer ID as a reference field for reconciliation.

Kentro B2B company accounts map to Epicor Customer records with company-level details. The Kentro company account becomes the Epicor Customer; each address (shipping, billing) becomes a separate ShipTo or BillTo record under that Customer. Account-level pricing terms and credit limits migrate to Customer Credit Hold and Customer Price Group fields.

Kentro supplier-facing Purchase Orders map to Epicor PO Header and PODetail records. Kentro PO number, supplier reference, and line items (PartNum, OrderedQty, UnitCost, DueDate) migrate directly. Custom approval workflows in Kentro do not migrate; we flag them in the handoff document for Epicor Kinetic BPM or Prophet 21 approval chain configuration.

Kentro Supplier and Vendor records map to Epicor Vendor records with contact details, lead times, and default payment terms. The Kentro vendor code becomes the Epicor Vendor ID; the vendor name becomes VendorName. Default terms from Kentro migrate to VendorPP terms.

Kentro inter-warehouse Transfer Orders and their completion records map to Epicor Transfer Orders (Move Inventory) with PartTran records for the inventory movement. In-transit items at migration time are flagged and resolved based on the Kentro transfer status. Completed transfers migrate with their full movement history.

Kentro fulfillment events and carrier tracking data link to migrated Order records in Epicor. We map shipping method names, tracking numbers, and shipment dates to ShipHead and ShipDtl records. Carrier-specific metadata beyond standard tracking fields may require supplementary export since Epicor's shipping module is carrier-specific.

Kentro multi-client 3PL setups require explicit partitioning in Epicor. We isolate each client's inventory, orders, and billing records and migrate them into their own Epicor site (Kinetic) or company (Prophet 21) partition. Client-level billing data from Kentro migrates as Customer records with a custom 3PL client reference field. Mismatched scoping can blend client inventories; we extract tenant-level client lists first and build per-client export batches.

Kentro Marketplace connections and channel-specific settings migrate as order source codes in Epicor. The channel-to-order linkage preserves the originating source on historical orders. We map channel names to Epicor Order Source codes or custom UD fields, with the customer's approval on naming convention during scoping.

Kentro EDI transaction sets for B2B wholesale (orders, ASNs, invoices) are preserved as document snapshots in the migration package. Epicor's EDI Framework requires document mapping rebuild per retailer. We do not automatically regenerate EDI feeds; we deliver the EDI document snapshots with a mapping guide for the customer's EDI specialist or Epicor partner to configure the Epicor EDI translator post-migration.

Kentro file attachments on orders, products, or customers are migratable via the platform's file storage references. We preserve attachment URLs and re-link them post-migration where the destination supports document attachment. Epicor Kinetic uses Document Mgmt records; we map the attachment type and link to the parent record (Part, Order, Customer) during migration.

Kentro IQ reporting definitions and underlying datasets migrate as export files and written reconfiguration plans for Epicor Insight or Epicor Kinetic native dashboards. Kentro IQ-specific visualizations do not have direct Epicor equivalents; we document the report metrics, filters, and data sources so the customer's Epicor admin rebuilds them in Epicor reporting tools post-migration.