Migrate from MERCI to Epicor Prophet 21

MERCI Customer records map to Epicor ERP Customer (CustCnt or Customer table depending on Epicor version). We flatten MERCI's address and contact columns into Epicor Customer address fields (Address1, Address2, City, State, Zip, Country). Where MERCI uses custom customer classification codes, we map them to Epicor Customer Type or a User-Defined field and document the translation table during schema discovery. Billing and shipping addresses require separate address records in Epicor; MERCI's combined address fields are split accordingly.

MERCI stores a single address per Customer record. Epicor separates bill-to and ship-to addresses into distinct address objects. We create a primary ShipTo address record from MERCI's address and flag it as the default ship-to. If MERCI carries separate billing and shipping addresses, we map them to separate ShipTo and BillTo records in Epicor. Any custom address fields in MERCI ( freight codes, route numbers, FOB terms) migrate to Epicor ShipTo UD fields.

MERCI contact records (name, phone, email, role) map to Epicor Customer Contact. We use the contact's email address as the dedupe key. Primary contact designation migrates to the IsPrimaryContact flag. Secondary contacts are created as additional Customer Contact records linked to the same CustomerNum.

MERCI Sales Orders map to Epicor ERP SalesOrder. Order header fields (order number, order date, customer PO, terms, warehouse) migrate directly. Order dates and expiration logic transfer to Epicor OrderHed fields. Status translation requires mapping MERCI order status codes (open, partial, complete, cancelled) to Epicor OrderRel.OpenLine and OrderHed.OpenOrder flags. MERCI order totals and discount amounts are verified against Epicor's calculated totals post-import.

MERCI line items migrate to Epicor OrderDtl records linked to the parent SalesOrder. Line-level fields (part number, quantity ordered, quantity shipped, unit of measure, unit price, discount) map to OrderDtl columns. Back-order logic from MERCI migrates to Epicor OrderRel records representing each ship-from warehouse and promised date. We handle partial line failures by inserting individual OrderDtl rows rather than blocking the entire order on a single line error.

MERCI Invoices map to Epicor InvoiceHed records with invoice line items as InvoiceDtl. The MERCI-to-order linkage is preserved in Epicor by embedding the source order number in a UD field on the InvoiceHed. Open versus closed invoice status maps to Epicor's InvoiceHed.OpenInvoice flag. Payment terms from MERCI migrate to Epicor's Terms master and are linked by TermsCode. Fiscal period assignment is verified against Epicor's accounting calendar during import.

MERCI Items (products and service variants) map to Epicor Part records. Fields including part number, description, unit of measure, and cost structure migrate to Epicor Part (PartNum, PartDescription,IUM, UnitCost). Pricing tiers from MERCI's item master migrate to Epicor PartPlant and PriceLBrk records. Bundle and kit compositions in MERCI must be expanded: the kit's component lines map to Epicor PartMtl (for manufactured kits) or to separate QuoteQty records, and we document the expansion logic for the customer's admin to validate.

MERCI pricing schedules attached to items map to Epicor PriceLBrk (price break) and PriceGrp records. We extract each pricing tier from MERCI's pricing schedule and create corresponding Epicor price break records. If MERCI uses customer-specific pricing overrides, these migrate to Epicor OrderDtl.UnitPrice overrides rather than as separate price list entries.

MERCI Chart of Accounts codes and names migrate to Epicor GL Account records. Account type mapping requires verification: MERCI uses a simplified five-type classification, while Epicor uses a more granular account type taxonomy (Asset, Liability, Equity, Revenue, Expense, and sub-types). We map MERCI account types to the closest Epicor equivalent during schema discovery and flag any ambiguous mappings for the customer's finance admin to confirm before final import.

MERCI Vendor records map to Epicor ERP Vendor. The vendor contact structure mirrors the customer contact structure: we flatten MERCI vendor address columns, create a primary VendorPP address record, and map bank account and payment terms to Epicor VendorPP (Vendor Payment) fields. Any MERCI vendor classification codes map to Epicor VendorType or a UD field.

MERCI Employee records (department, job title, hire date) map to Epicor Employee. Compensation fields require effective-date handling in Epicor: MERCI's current compensation amount maps to the most recent Epicor EmpBasic row, and if historical compensation data is present in MERCI, we create additional effective-dated rows in Epicor's LaborHistory or EmpBasic history tables. Department and job title migrate to Epicor EmpBasic.DcdnfldID or UD fields.

MERCI warehouse records (if present as a standalone entity) map to Epicor Plant and Warehse. If MERCI uses a single-site model, we create one Plant and one Warehse record in Epicor. Multi-site MERCI deployments create multiple Plant records with corresponding Warehse records per site, and inventory quantities are allocated to the correct site during item import.

MERCI binary attachments (order documents, PDFs, images) cannot be retrieved via any documented API endpoint or standard CSV export. We flag attachment objects as unsupported during scoping and direct customers to the MERCI UI for manual download or to request a full blob export from their account manager. If the blob export exceeds a practical browser-download threshold, we recommend a direct database dump of the attachment store coordinated with MERCI's hosting team as a separate workstream.