Migrate from e-Emphasys ERP to Epicor Prophet 21

e-Emphasys customer records carrying full contact details, billing addresses, and linkage to equipment and service history map to Epicor Customer (header-level) and CustCnt (contact-level) records. We resolve the primary billing address to Epicor ShipTo records and preserve the customer-specific pricing code as a custom field if it exceeds Epicor's standard pricing tier configuration. Branch assignment from e-Emphasys maps to Epicor Plant or Company assignment to support multi-branch deployments.

Serialized equipment records from e-Emphasys including OEM codes, VIN-equivalent identifiers, branch assignment, and current status map to Epicor Part records with Lot/Serial Number tracking. We preserve the OEM equipment number as Epicor's manufacturersParts cross-reference, the branch assignment as a Plant-level PartBin entry, and the equipment status (available, rented, sold, retired) as a custom field because Epicor tracks status through inventory transactions rather than a status field. If the equipment spans multiple bin locations, we generate a multi-bin reconciliation report.

Both serialized and non-serialized parts from e-Emphasys map to Epicor Part records with the appropriate tracking flag (Non-Network tracked, Lot tracked, or Serial tracked). Bin locations from e-Emphasys map to Epicor PartBin records per Plant. Vendor links, cost tiers, and reorder points migrate as Epicor PartPlant settings. We preserve the OEM parts cross-reference and any supplier-specific part numbers in the PartXRef table.

e-Emphasys service work orders tied to equipment records, technicians, and line items map to Epicor JobMtl (material consumption), LaborDtl (labor tracking), and ServiceCall or ServiceContract records. We preserve the equipment link as a JobHead UserChar field or ServiceCallEquip reference, the warranty claim association as a ServiceCallType or custom field, and the technician labor record with labor rates and certifications. Open work orders require Epicor Job status planning before migration to avoid triggering unwanted production scheduling.

Rental contracts in e-Emphasys store complex rate structures including daily/weekly/monthly billing tiers, equipment swaps, and early return conditions. We extract contract terms into an intermediate schema and map active contract status, equipment assignments, and base rate schedules to Epicor RentalOrder or ContractHead depending on the destination edition and configuration. Any multi-tier billing schedules that exceed Epicor's contract line item configuration are flagged in a reconciliation report for manual verification before go-live. Active rental contracts with equipment swaps require special handling to avoid duplicate serial number assignments.

Whole goods sales orders and quotes from e-Emphasys link to customer and equipment records and map to Epicor OrderHed and QuoteHed. Pricing tiers and OEM incentives migrate as OrderDtl and QuoteDtl line items with the OEM incentive code preserved as a custom field or discount break reference. Quote and order status maps to Epicor OpenLine status. We resolve the customer and equipment links to Epicor CustNum and PartNum references before import.

GL accounts, journal entries, and account balances from e-Emphasys financial module map to Epicor GLJrnGrp (journal group) and GLJrnDtl (journal detail). We preserve the chart of accounts structure with account segments mapping to Epicor's account segment configuration, and period associations map to fiscal period and fiscal year. Account balances for open periods migrate as beginning balances; historical closed periods migrate as reference entries for audit trail. Epicor requires the fiscal year template to be configured before GL data can import.

Vendor invoices and payment records from e-Emphasys AP module export with full vendor linkage and map to Epicor APTran records attached to Vendor invoices. We preserve PO-to-invoice associations where they exist as Epicor POLine references on the APTran. Vendor records map to Epicor Vendor, with the e-Emphasys vendor-specific terms and ACH routing preserved as custom fields if they exceed standard Epicor payment terms configuration.

Customer invoices, payments, and AR aging data from e-Emphasys export with customer linkage and map to Epicor ARInvc and ARCash records. Open invoice balances and payment history preserve the customer link via CustNum, with invoice number and payment reference carried through as ARTran entries. Epicor's AR module uses a separate CashBHed and CashDtl structure for payments versus e-Emphasys's combined AP/AR module.

Employee records from e-Emphasys including labor rates, certifications, and branch assignments map to Epicor EmpBasic with labor rate configuration in LaborHed. Branch assignments map to Epicor Plant assignments or ResourceGroup assignments depending on whether the employee is production labor or service labor. Custom labor rate tiers that exceed Epicor's standard rate matrix configuration are flagged for manual entry or custom LaborRate table extension.

Warranty records tied to serialized equipment and OEM claims in e-Emphasys map to Epicor WarrantyClaim records and PartXRef entries linking OEM warranty codes to Epicor Part records. We preserve claim history and coverage periods, mapping OEM warranty codes to Epicor's WarrantyCode table. Active warranty claims attached to open work orders require Epicor ServiceCall linkage before migration to avoid orphaned claim records.

e-Emphasys user-defined fields in customer, equipment, parts, and work order modules require pre-mapping to Epicor UD columns or custom fields before data load. We identify all user-defined fields during discovery, map their data types to Epicor field types (character, number, date, checkbox, combo), and pre-create the Epicor UD field schema via customization or direct database insert before migration. Epicor User Defined Tables (UD01-UD20) are available for fields that do not fit standard Epicor column definitions.