Migrate from metasfresh to Epicor Prophet 21

metasfresh Business Partners with BPartner_Composite.C_BPartner_ID resolve to Epicor Customer (if isCustomer=true) or Supplier (if isVendor=true). Many metasfresh records are both customer and vendor simultaneously; we create both a Customer and a Supplier record in Epicor linked to the same Party record. Address data (C_BP_Location) maps to Epicor CustomerShpTo records with the default ship-to flagged per the metasfresh IsActiveToDefault flag. Contact data (C_BP_Contact) maps to Epicor Contact records linked to the Party.

metasfresh Products map to Epicor Part records. The M_Product.Value field becomes Part Number; the name becomes Part Description. Product type (Item vs Service vs Resource) maps to Part Type (Stocked, Non-Stock, Service, Charge). The metasfresh Product Category (M_Product_Category) maps to Epicor Product Group. We query the AD_Column table during discovery to capture all custom fields on M_Product and map them to UD fields on Part before migration.

metasfresh Sales Orders map to Epicor OrderHed (order header) and OrderDtl (order lines). The C_Order.C_DocType_ID mapping to Epicor OrderRel quoting the correct Doc Types. Document status (C_DocType targets for SO, PO, RMAS) maps to Epicor's Open status fields. Order date, promised date, and discount percentages transfer directly. Header-level charges (C_Order_Header_Acct) map to OrderMsc records in Epicor.

metasfresh Purchase Orders follow the same C_Order structure with a different DocType. We filter by DocTypeTarget during extraction and map to Epicor POHeader and PODetail. Vendor part numbers from C_BPartner_Product map to PartPlant VendorPartNum for reference.

metasfresh AR Invoices (C_Invoice with DocBaseType=ARI) map to Epicor AR Invoice records; AP Invoices map to Epicor AP Invoice records. The C_InvoiceLine lines map to InvoiceDtl with tax codes resolved from metasfresh C_Tax. We handle InvoiceGSTR to the extent metasfresh tax configuration uses standard tax categories, but VAT and GST jurisdictions outside the DACH default require manual tax code mapping review before final load.

metasfresh BOMs stored in pp_product_bom and pp_product_bomline require careful mapping to Epicor's multi-level BOM and Job structure. We inspect the PP_Product_BOM table during discovery and include BOM lines only when the MRP module is enabled and pp_product_bomline records are populated. Each metasfresh BOM becomes an Epicor Part BOM revision linked to the finished Part, and an Epicor Job or Estimate is created for any in-process manufacturing orders referenced in pp_order_bomrecord. Orphaned BOM component references that cannot resolve to a Part in the destination are flagged in the reconciliation report.

metasfresh organizes pricing into M_PricingSystem containing M_PriceList records with M_PriceList_Version versions and M_ProductPrice entries. We export the full pricing hierarchy and map to Epicor's PriceLst (price list header), PriceLstRev (price list revision with effective dates), and PriceLstParts entries. Versioned pricing with effective date ranges becomes separate PriceLstRev records in Epicor. Quantity breaks stored in M_ProductPrice (if present) map to Epicor PriceBreaks.

metasfresh Projects map to Epicor Project records. Project phases and milestones in C_ProjectLine map to Epicor WBS Phases. Project type (standard vs phase-based) maps to Epicor Project Type. We flag that Epicor Project DMT imports require specific table ordering: Project must load before WBS Phases, and CS Project must link back to Sales Order before WBS Phase creation, per Epicor DMT community guidance.

Bank accounts stored per Business Partner and per organization map to Epicor BankAcct records. Bank account numbers, routing codes, and IBAN data transfer to BankAcct fields. We map per-organization bank accounts by reading C_BP_BankAccount with its AD_Org_ID and linking to the corresponding Epicor Company-level bank account.

metasfresh payment terms (net 30, 2/10 net 30, etc.) stored in C_PaymentTerm map directly to Epicor PaymentTerms. Discount percentages and net due days transfer to the DiscountPercent, DueDays, and MaxDate fields in Epicor.

metasfresh tax categories and rates map to Epicor TaxRpt codes linked to TaxZone-based rate tables. We preserve the full tax configuration including effective date ranges where metasfresh stores them. Multi-jurisdiction setups (DACH vs other regions) may require the customer's Epicor admin to map the metasfresh tax category IDs to the correct Epicor TaxRpt codes during final validation.

metasfresh custom fields added via the Table and Column system are stored as rows in AD_Column with a custom flag. They are not surfaced in the standard metasfresh export format. We query AD_Column during the discovery phase to identify all custom fields per table, determine their data types, and create corresponding UD (User-Defined) fields in Epicor before migration. Custom field values are then included as additional columns in the export and loaded via DMT or REST API into the corresponding UD field.