Migrate from Elvis Business ERP to Epicor Prophet 21

Elvis Customer records migrate to Epicor PartCust with address, contact details, and payment terms preserved. We map Elvis payment terms codes to Epicor Terms records already configured in the destination. If Elvis uses custom customer classification fields, we resolve these to Epicor UDC codes (UD04-UD08) or create new UDC values during the schema preparation phase. Parent-company hierarchies in Elvis map to Epicor's Customer Group and Territory assignments.

Elvis Vendor records migrate to Epicor PartVend with contact information, banking details, and payment terms. Elvis vendor classification schemes that do not map directly to Epicor UDC codes are flattened or expanded into new UDC values during pre-migration configuration. We create PurPoint records for each vendor to support Epicor's purchase point inventory model if the customer uses multi-location purchasing.

Elvis Item records migrate to Epicor Part with SKU, description, unit cost, and pricing tiers preserved across the Part, PartPlant, and PartCost records. Elvis category structures that do not map to Epicor's PartClass or UDC-based classification are either collapsed into a single category or mapped to a custom UDC table configured before migration. If Elvis carries lot-tracked or serial-tracked items, we pre-configure Epicor PartTran tracking parameters before item import begins.

Elvis account numbers and names transfer to Epicor GLAccount with account type (Asset, Liability, Equity, Revenue, Expense) validated against the destination chart structure. If Elvis uses a flat account list without type metadata, we derive account types from the account number prefix or from cross-referencing with the customer's trial-balance export during discovery. Epicor's segment-based chart supports natural account plus sub-account structures; we configure these segments before the GL migration phase.

Elvis open AP records (outstanding invoices and credit memos) migrate to Epicor APTran with open amounts, due dates, and source document reference numbers preserved. We extract the aged AP aging report from Elvis, map each line to APTran with the corresponding vendor invoice number and GL account, and validate that total AP open balance reconciles before cutover. APHeader is created with the original invoice date and due date; APTran carries the distribution amounts.

Elvis open AR records migrate to Epicor ARTran with open amounts, due dates, and customer invoice references preserved. We extract the aged AR aging report from Elvis, map each line to ARTran with the customer number resolved to the Epicor PartCust Customer ID. Invoice status (open, closed, voided) from Elvis is carried forward as ARTran open amounts; fully paid invoices are excluded from the live AR migration but tracked in historical reporting.

Historical invoice headers and line items from Elvis transfer to Epicor as ARInvoice (sales invoices) and APInvoice (purchase invoices) records. We extract historical invoices in batches by fiscal period, map each line to the correct GLAcct, and preserve invoice status (paid, open, voided) throughout the migration. PDF attachments associated with invoices in Elvis are exported separately and re-uploaded to Epicor as DocumentRev records linked to the corresponding Invoice number.

Elvis User records migrate to Epicor User accounts with name, email, and role assignments. We map Elvis role names to Epicor Company, Plant, and Warehouse security group assignments. If Elvis has custom role definitions not present in the Epicor security model, we create new Epicor UserCodes and assign them during migration. Active and inactive status from Elvis carries forward as User InActive flag in Epicor.

Uploaded files attached to Elvis records (invoices, items, customers, vendors) export as binary files with their parent-record association tracked in a manifest CSV. We re-upload each file to Epicor's EDMS (Electronic Document Management) as DocumentRev records with the correct Link table (PartCust, Part, Vendor, etc.) populated using the manifest. File type, original creation date, and any Elvis document description fields migrate as Epicor DocumentRev metadata.

Elvis custom fields on Customers, Vendors, and Items that have no direct Epicor equivalent are resolved to Epicor UDC codes (User Defined Codes table) or to custom UD fields (UD05-UD99) configured before migration. We capture every Elvis custom field during discovery, map its data type to an equivalent Epicor field type, and add the field to the destination schema via Epicor customization tools before the corresponding object migration runs.

If Elvis Business ERP contains manufacturing data (BOMs, routings, work orders, job records), these migrate to Epicor JobHead, JobMtl, JobOper, PartBillOfMASS, and PartRoute records. Elvis BOM levels map to Epicor's multi-level BOM structure. We validate bill of materials for circular references before loading into Epicor, as Epicor's BOM validation rules are stricter than those found in general-purpose small-business ERPs.

Elvis integrations with external systems (e-commerce, payment gateways, EDI feeds) are documented during discovery. We provide a written inventory of each integration endpoint, data flow, and the recommended Epicor Kinetic replacement (typically Epicor Service Connect, REST API calls, or EDI via 1 EDI Source). Integration rebuilds are outside the standard migration scope and are handed off to the customer's implementation partner.