Migrate from Fulfil to Epicor Prophet 21

Fulfil Sales Orders map 1:1 to Epicor Sales Orders via REST API extraction and Epicor Sales Order entry API. We preserve order number, order date, customer reference, fulfillment state (Open, Closed, Cancelled), channel attribution (Shopify order ID, Amazon order ID), and all line items with quantity, unit price, and discount. Shipping and payment records are pulled in the same extraction pass and linked via Epicor's OrderHed and OrderRel structures. Order holds and credit check flags map to Epicor OrderHed fields.

Fulfil Items (SKU, description, cost, price, reorder point, bin location) map to Epicor Part Master records. Standard cost from Fulfil Item becomes Epicor Part.Plant Unit Cost; standard price becomes Part.SellingFactor-derived pricing. User-defined custom fields on the Fulfil Item object are mapped to Epicor Part custom fields (Part._x_ fields) which we create during schema setup. Lot and serial number control settings on the Fulfil Item determine the Part.LotShimize and Part.SerialTracking fields in Epicor.

Fulfil Purchase Orders map to Epicor POHeader records with line items mapped to POLine. Vendor assignment, expected dates, and receiving records transfer directly. We sequence PO receipts before vendor closeout to ensure no orphaned receiving commitments land in Epicor against a closed vendor. Open PO status (Open, Closed, Cancelled) maps to Epicor POHeader.OpenPor flag and PORel records.

Fulfil multi-warehouse configurations with bin-level location data map to Epicor Site records with nested Warehouse and Bin structures. Each Fulfil location and its associated stock snapshot becomes a separate Epicor PartBin entry per Site. Bin location strings from Fulfil (e.g., A-01-03) are parsed and mapped to Epicor WarehouseBin.BinNum. Multi-entity deployments with separate legal entity warehouses map to separate Epicor Sites with inter-company configuration handled post-migration.

Fulfil Customer records (contact details, billing address, shipping addresses, account-level pricing tiers) map to Epicor Customer. We use Fulfil customer number as Epicor Customer.CustID with name and contact fields mapped directly. Multiple shipping addresses from Fulfil become Epicor ShipTo records under a single Customer. Custom fields on the Fulfil Customer object require explicit per-tenant field mapping. Account-level pricing tiers map to Epicor PriceLbr and PriceMat codes or a Customer-level price group reference.

Fulfil vendor invoice records export from the financials module and map to Epicor AP Invoice records (APInvoiceHed and APInvoiceDtl). Mapping depends on the destination's chart of accounts structure which we reconcile during the manual account crosswalk phase. Open invoices transfer with full line-level detail; historical invoices transfer as posted records with invoice number preserved for audit trail continuity.

Fulfil lot tracking assignments on Items tie to inventory transactions and map to Epicor PartLot records. Lot number, lot expiration date, and lot attribute fields transfer as PartLot.LotNum and custom lot fields. Lot assignments are carried through as part of inventory ledger entries so that traceability across receiving and fulfillment is preserved in Epicor's lot tracking system.

Fulfil serial number assignments on Items map to Epicor PartSN records linked to the associated PartLot and PartBin. Serialized inventory traceability from Fulfil receiving through to sales order fulfillment is preserved as PartSN.SerNum with activity history logged to PartTran entries in Epicor.

Fulfil custom product data (engraving text, embroidery specs, made-to-order attributes) is stored as extended attributes on Sales Order Lines rather than as a standalone object. We extract these as flattened line properties and map them to Epicor OrderDtl._x_ custom fields for the Sales Order. For customers using Epicor's configure-to-order module, we also create Part Revision attributes to carry the product specification data. The customer chooses between Sales Order line custom fields or Part Revision attributes during scoping based on whether they need the customization data to live on the Part Master or on the Order.

Fulfil manufacturing work orders, BOMs, and production steps accessible via API map to Epicor Job Entry records (JobHead for the job header, JobMtl for materials, JobOper for operations). Complex multi-level BOM hierarchies may require manual sequencing in Epicor's Job Entry structure because Fulfil's BOM representation and Epicor's job/material/operation breakdown follow different data models. We deliver a written BOM mapping table for the customer's Epicor admin to finalize before production migration.

Fulfil financial accounts export from each legal entity and require a manual crosswalk against Epicor's chart of accounts before any financial record transfer begins. Multi-entity deployments need account codes reconciled across legal entities with inter-company account mapping handled as a separate configuration step in Epicor. We collect the full account tree for each entity during scoping and build the mapping table with the customer before any GL balance transfer.

Fulfil Owners referenced on Sales Orders, Purchase Orders, and Customer records map to Epicor Users by email match. We resolve OwnerId references at migration time by matching Fulfil user email against Epicor's labor table (EMailAddress field). Any Fulfil Owner without a matching Epicor User goes to a reconciliation queue for the customer's admin to provision before record import resumes.