Migrate from Sales ERP to Epicor Prophet 21

Sales ERP Accounts map to Epicor Customers. The Account Name, Billing Address, Shipping Address, Phone, and Website fields translate directly. Parent Account relationships (hierarchy) in Salesforce map to Epicor Customer Territory or Customer Group assignments. We resolve CustomerID at ingestion time by matching Account Name against Epicor's Customer table, and we flag any duplicate Customer names for the customer's Epicor admin to resolve before the Orders phase begins.

Sales ERP Contacts map to Epicor Contacts. The Contact Name, Email, Phone, and Title fields migrate directly. Salesforce Account.Contact relationships map to Epicor Customer.PhoneNum linked to Customer via CustomerID. We preserve the Contact's original Salesforce ID in a reference field for audit trail purposes.

Sales ERP Opportunities map to Epicor Quotes and Sales Orders depending on pipeline stage. Open pipeline Opportunities (Stage not Closed-Won or Closed-Lost) map to Epicor Quotes. Closed-Won Opportunities with fulfillment intent map to Epicor Sales Orders with OrderHed and OrderDtl records. We preserve the original Opportunity StageName as a custom field for post-migration reconciliation.

Sales ERP Orders map to Epicor OrderHed (header) and OrderDtl (line) records. The Account-Order-Contract lineage in Salesforce translates to Customer-SalesOrder-ShipTo relationships in Epicor. Order status transitions (draft, submitted, fulfilled, invoiced) map to Epicor OrderRel records and their ReleaseStatus values. We validate that all Order line items have a matching Epicor Part or Miscellaneous charge.

Sales ERP Contracts map to Epicor Customer Contracts (Service Contracts) if the customer's Epicor license includes Epicor Service. Contract start and end dates, status, and renewal terms migrate as ContractHed records. Contracts without an active service entitlement migrate as reference records with a flag for manual review.

Sales ERP Products map to Epicor Parts (Part table). The Product2 Name, ProductCode, Description, and IsActive flag map to Part.PartNum, PartDescription, and InActive flag. We validate that each Product has at least one active Price Book Entry before migration; those entries map to Epicor Part Plant pricing records or Price Lists.

Salesforce Price Book Entries map to Epicor Part Plant records (site-specific pricing) and Price List entries (standard pricing). Custom Price Books require explicit mapping to Epicor Price Codes. UnitPrice migrates as the base price; we flag any Price Book Entry linked to an inactive Product.

Sales ERP Opportunity Line Items map to Epicor OrderDtl records at the same time as their parent Sales Order. We resolve the Product2 reference to an Epicor Part.PartNum at migration time and validate that the Quantity and UnitPrice translate correctly to Epicor's pricing conventions (rounded to the destination currency decimal places).

Sales ERP Users map to Epicor Customer records if the User represents a company (account-type logic), or to Employee records if the User represents an Epicor employee who will log into the system. Owner assignments on Salesforce records (AccountId, OwnerId) translate to Epicor's RequestByID (Employee) or ShipToNum references. We match by email.

Sales ERP Cases map to Epicor Service Call (FieldService) records if the customer licenses Epicor's Service module. Case Status, Priority, and Description map to ServiceCallHed fields. Account-Contact relationships on Cases translate to Epicor Customer.Contact references. Cases without FieldService licensing migrate as reference records.

Sales ERP Campaigns map to Epicor Customer Groups or Marketing Segments depending on the Epicor modules licensed. Campaign Member statuses do not have a direct Epicor equivalent; we map CampaignMember Status to a custom field on the related Customer record for segmentation purposes.

Sales ERP Leads that have not converted to Contacts map to Epicor Prospect records if Epicor Prospect management is licensed. Lead Source and Lead Status migrate as custom fields on the Prospect record. Converted Leads that already exist as Contacts in Salesforce map to Epicor Contacts as described above.

Sales ERP Custom Objects (ending in __c) map to Epicor User-Defined (UD) Tables or standard Epicor tables based on their data function during discovery. Custom object records migrate as rows in the corresponding Epicor UD table, with foreign key relationships resolved to the appropriate Epicor primary table. We cannot replicate Salesforce formula fields, validation rules, or roll-up summaries in Epicor; these require rebuild as Epicor calculated fields or UD method code.

Sales ERP Attachments and Notes export as Base64-encoded binary records and migrate to Epicor's Document Management system (EDMS) or as file references linked to the parent Epicor record (Customer, Order, Part, Job). We preserve the original Salesforce ID in a reference field for audit. Multi-attachment-per-record scenarios are resolved by creating a folder structure in Epicor EDMS that mirrors the Salesforce parent-child hierarchy.