Migrate from EBMS to Epicor Prophet 21

EBMS Customer records map to Epicor Customer with the CustomerID as the dedupe key. Standard EBMS fields (name, address, terms, ship-to locations) map to Epicor Customer base fields. EBMS customer price levels map to Epicor Customer Price Group assignments on the Customer record or to individual CustomerPart Xref records if the customer has negotiated per-part pricing. We resolve the CustomerID from EBMS using the customer code field and validate uniqueness before insert. EBMS Customer Portal accounts map to Epicor Customer with the portal price level stored in a custom field or as a Customer Price Group assignment.

EBMS inventory items map to Epicor Part records. EBMS product fields (description, unit of measure, standard cost, stocking quantity) map to Epicor Part (PartNum, PartDescription,IUM) and PartPlant (OnHandQty, LeadTime, ABCCode). Serial number tracking in EBMS maps to Part.SalesUM and PartStock.SerialNumber if the Epicor environment is configured for serial tracking. EBMS product pricing tiers (price levels 1-99) map to Epicor PriceLbr records or to Part.SalesUM pricing if simplified. EBMS product categories map to Epicor Product Group codes. We request PartPlant configuration (site-specific stocking and planning data) to be exported separately from the base Part master.

EBMS Sales Order headers map to Epicor OrderHed with OrderNum as the parent key. EBMS order line items map to OrderDtl with Line, PartNum, OrderQty, UnitPrice, and Discount fields preserved. EBMS payment terms on the order header map to OrderHed.TermsCode. EBMS order status (open, shipped, invoiced, closed) maps to Epicor OrderHed.OpenLine and OrderHed shipped/released flags. We extract OrderHed and OrderDtl via separate EBMS reports and merge them during transform so that the parent-child relationship is resolved at import time. Historical closed orders require careful date-range scoping; we confirm whether the customer wants full history or only open and recent orders.

EBMS does not have an explicit pipeline or deal-stage model; orders progress through document statuses (Quote, Order, Shipped, Invoiced, Closed). Epicor OrderHed has a Status field that maps to these document states. We configure Epicor OrderHed.Status values to match the EBMS order lifecycle during migration. EBMS quote extensions (quotes not yet converted to orders) map to Epicor QuoteHed if the customer uses Epicor CPQ, or to OrderHed with a Quote-held status if CPQ is not licensed.

EBMS Purchase Order headers map to Epicor POHeader with PONum as the parent key. EBMS PO line items map to PODetail with POLine, PartNum, POLine.UnitCost, OrderQty, and DueDate preserved. EBMS vendor references on PO map to POHeader.SupplierID via the Vendor mapping. EBMS PO approval status maps to POHeader.Status. We extract POHeader and PODetail via separate EBMS reports and merge them before Epicor DMT import. EBMS custom fields on PO headers or lines require explicit mapping to Epicor UD fields on POHeader or PODetail.

EBMS invoices map to Epicor InvoiceHed and InvoiceDtl. EBMS invoice header fields (invoice number, date, customer, terms, total) map to Epicor InvoiceHed fields. EBMS invoice line items map to InvoiceDtl with PartNum, InvoiceQty, UnitPrice, and ExtendedPrice. EBMS open AR aging data maps to Epicor CashReceipt if partial payments have been recorded. Historical invoice PDFs are exported as files and attached to Epicor InvoiceHed via DocumentRev records. We scope historical invoices by date range to avoid mid-period splits and confirm with the customer whether the new Epicor environment will carry the full AR history or only open items.

EBMS Vendor records map to Epicor Supplier with SupplierID as the dedupe key. EBMS vendor fields (name, address, payment terms, contacts) map to Epicor Supplier base fields. EBMS vendor part numbers for purchased items map to Epicor SupplierPart Xref records for cross-referencing. EBMS vendor-specific pricing tiers map to Epicor SupplierPrice effective-date records. We extract vendors via EBMS vendor reports and map them to Supplier before PO import to satisfy the SupplierID lookup on POHeader.

EBMS custom fields created in the Customization Designer may exist on any entity (Customer, Product, Order, PO, Vendor). These are not always visible in standard EBMS reports without first adding them to the report layout. We request read-only SQL access during data profiling to enumerate all custom field columns in the EBMS database, then work with the customer to confirm which custom fields require migration. Each EBMS custom field maps to a corresponding Epicor UD field (e.g., PartUOM.Character01 for string UD fields, Customer.UDFld1 for customer custom fields). We pre-create Epicor UD fields in the destination environment before data import begins. Fields without an Epicor destination are flagged in the mapping document for the admin to resolve.

EBMS eCommerce product data (product name, description, images, availability, pricing, categories) maps to Epicor Part and PartWebConf (web configuration) records if the customer licenses Epicor Commerce or integrates with a third-party commerce platform. EBMS product catalog exports via inventory reports include web-specific fields (web description, image URLs, category assignments) that map to PartWebConf and CategoryPart records in Epicor. EBMS eCommerce tier caps do not affect the migration scope directly, but we confirm whether the customer has been capping or manually handling orders at the tier boundary, which could result in incomplete order history.

EBMS Customer Portal accounts store B2B customer login credentials, price levels, and payment terms. These map to Epicor Customer records with the portal price level stored in CustomerPriceLbr or a custom field on Customer. EBMS portal-specific fields (price level visibility, credit limit override) map to Epicor CustomerCreditLimit and Customer.PriceCode. We extract portal accounts from EBMS customer reports and map them as a supplement to the standard Customer migration, with the portal-specific fields stored in designated Epicor custom fields.

EBMS general ledger account codes and descriptions map to Epicor GLAccount with AccountDesc preserved. EBMS account segments (if using segmented chart of accounts) map to Epicor GLAccount with COACode and segments parsed from the EBMS account code. We extract GL accounts via EBMS financial reports and map them before invoice and PO import so that distribution accounts are resolved at load time. Cross-reference mapping from EBMS account codes to Epicor GLAccount numbers is delivered as a written mapping table for the customer's GL team to validate.

EBMS salesperson records map to Epicor SalesRep with SalesRepCode as the dedupe key. EBMS salesperson names, commission rates, and territories map to Epicor SalesRep fields. Salesperson assignments on EBMS orders map to OrderHed.SalesRepCode via the SalesRep mapping during order import. We extract salespersons via EBMS user and sales reports and validate against Epicor SalesRep records before importing orders.