Migrate from Aptean Distribution ERP to Epicor Prophet 21

Aptean Customer records with hierarchical pricing tiers, customer groups, and reference customer links map directly to Epicor Customer. The Aptean Customer pricing structure (price lists, discount tiers, contract pricing) migrates as Epicor Customer Price Lists and Volume Discount records. Customer credit limits and payment terms map to Epicor Customer Credit and Terms fields. We preserve the customer hierarchy for replicating trade agreements and parent-child billing relationships.

Aptean Vendor records include multi-currency support and landed cost component fields. We preserve the cost structure hierarchy (agency fees, freight, duties by harmonization code) across Vendor records and migrate them to Epicor Supplier Master. The Aptean vendor lead time, MOQ, and country-of-origin fields map to Epicor Supplier Part and Supplier Quality fields. Vendor bank details for ACH/wire payments map to Epicor Payment Methods.

Aptean Item Master records with lot/serial tracking, warehouse-specific stocking locations, and cost layers migrate to Epicor Part Master. The Aptean item classification hierarchy (category, subcategory, product group) maps to Epicor Part Class and Related Parts. Unit of measure conversions and stocking categories migrate as Epicor UOM definitions and Part Planning fields. Lot-expiry configurations and shelf-life settings transfer to Epicor Part Lot Control settings.

Multi-warehouse configurations in Aptean with directed putaway rules, speed-bin definitions, and wave-picking criteria migrate to Epicor Warehouses. We map the Aptean putaway rule logic (location priority, replenishment triggers, overflow handling) to Epicor Warehouse Configuration including Bin Locators and Zone assignments. Staging configurations and shipping dock assignments transfer to Epicor Shipping and Receiving setup.

Aptean Sales Orders with full lifecycle from entry through fulfillment and invoicing map to Epicor Sales Order. Order status, backorder flags, promised delivery dates, and customer PO references preserve. Open order balances migrate as Epicor open Sales Orders with the original order date and promised date retained. Order holds and credit status flags transfer to Epicor order flags. Ship-to addresses and freight terms migrate with the order header.

Aptean Purchase Orders tracking vendor lead times and import shipment associations migrate to Epicor PO Header. Open PO balances transfer as Epicor open Purchase Orders with the associated Supplier and Part records resolved at migration time. The Aptean container and shipment link fields map to Epicor PO Linked Shipment records for import tracking continuity.

Aptean Chargeback records tied to customer deduction codes require a deduction-code crosswalk for Epicor. Each retailer sends deduction reason codes in different formats (numeric codes, alpha prefixes, free-text memos). We review the Aptean deduction codes against Epicor's Deduction Management schema during data audit, build a mapping table for each unique code, and flag any unmapped codes for customer review. Open chargebacks migrate as Epicor Deduction records linked to the Customer.

Aptean calculates landed costs at shipment receipt and allocates across items per shipment. The per-unit landed cost is derived, not stored as a static field. We extract the landed cost components (freight, duty, insurance, agency fees by harmonization code) from the Aptean shipment record and write the resulting allocated per-unit costs as Epicor custom Part fields or Landed Cost distribution records. The allocation methodology (by value, weight, or quantity) is documented from Aptean and recreated in Epicor Landed Cost Management.

Aptean EDI 850, 810, and 856 documents are stored in a proprietary format that may not parse cleanly through the standard integration layer. We extract the functional business data (order lines, invoices, ship notice details) from whatever export format Aptean provides, transform it into Epicor-compatible flat or JSON records, and create Epicor Sales Orders or Purchase Orders from the parsed EDI content. EDI transaction history is migrated as reference records linked to the corresponding orders, not as active EDI configuration.

Lot genealogy and serial number assignment history stored per transaction in Aptean migrate to Epicor Part Lot records. We preserve the full traceability chain including receiving dates, stock movements, and customer shipment links as Epicor Lot Attributes and Lot Trace. Serial number assignment history transfers to Epicor Serial Number records with their transaction genealogy.

Aptean GL account structure migrates cleanly to Epicor GL Account Master with account type, currency assignment, and department/cost-center rollups preserved. We maintain the full account hierarchy for financial reporting continuity. The Aptean multi-segment account structure (if used) maps to Epicor's account code segments with department and cost center as sub-account dimensions.

Outstanding Aptean invoices, credit memos, and payment applications migrate with open/closed status flags. Open AP transfers as Epicor AP Open invoices linked to the corresponding Supplier. Open AR transfers as Epicor AR Open invoices linked to the corresponding Customer. Records near payment threshold or with disputed status are flagged for pre-cutover verification with the customer's AP/AR team.

Aptean vessel, shipment, and container tracking tools with documentation attachments (demurrage, detention, additional charges) migrate to Epicor Container/Shipment records. Vessel name, voyage number, container number, and carrier details transfer. Documentation attachments move as Epicor Document Management records linked to the Container. The container tracking demurrage and detention flags map to Epicor Container Tracking attributes.