Migrate from WP ERP to Epicor Prophet 21

WP ERP employee records (personal details, employment status, department, job title, hire date, compensation) extract from erp_hr_employees with wp_user_id cross-reference from wp_users. We map to Epicor Kinetic Employee records or PartTracker labor entries depending on the destination Epicor product (Kinetic HCM versus PartTracker). Compensation data (salary, pay type, bank details) is flagged as sensitive and handled under the payroll archive decision: migrate as record data, archive as PDF, or exclude entirely based on customer compliance requirements.

Department records in erp_hr_departments are top-down hierarchical key-value structures. We extract the full tree (parent-child relationships, department name, head of department) and rebuild it as an Epicor organizational structure. Employee-to-department assignments resolve by cross-referencing the erp_hr_employees.department_id foreign key to the migrated department ID on Epicor.

WP ERP contacts (name, email, phone, address, lifecycle stage, source attribution) extract from erp_crm_contacts with wp_user_id links. Epicor Kinetic uses a Party-based model: the contact person attaches to a Customer or Supplier Party record. We split contacts into Customer Contact (sales-related) and Employee Contact (HR-related) based on the WP ERP contact type and lifecycle stage. WooCommerce duplicate candidates (same email appearing in manually created contacts and WooCommerce order records) are flagged for merge before export.

WP ERP company records in erp_crm_companies link to CRM contacts via erp_crm_contact_relations. We map companies to Epicor Customer Party (for B2B accounts) or Supplier Party (for vendor-of-record companies) based on whether the WP ERP company record has associated sales deals or purchase transactions. Company ID remapping preserves the contact-company relationship during migration by resolving erp_crm_contact_relations.contact_id to the new Epicor CustCnt ID.

WP ERP Deals (title, value, currency, stage, owner, pipeline association) extract from the Deals extension ($9.49/mo). Epicor Kinetic does not have a standalone Deal object; deals with an active sales process map to Epicor Opportunity (if pre-quote) or to Sales Order (if in progress). Pipeline stages from WP ERP map to Epicor Opportunity Stage or Sales Order status based on deal state at migration time. Deals with a status of Closed-Won map to a closed Epicor Sales Order; Closed-Lost deals are flagged for reporting exclusion.

Activities (calls, meetings, emails, tasks) stored in erp_crm_activities with polymorphic type fields flatten into a standard activity log structure. We map WP ERP activity type to Epicor Tracker activity category (Phone Call, Meeting, Email, To-Do). Activity timestamps, owner assignment, and associated contact or company links migrate directly. Note attachments associated with activities migrate as Epicor attachments linked to the parent activity record.

WP ERP chart of accounts records (account code, name, type, subtype, parent-child hierarchy for grouped accounts) extract from erp_ac_chart_of_accounts. We map WP ERP account types to Epicor GL Account categories: Asset, Liability, Equity, Revenue, Expense. Account code prefixes and hierarchical groupings (parent_account_id) preserve the COA structure in Epicor. GL account codes that conflict with Epicor Kinetic chart of accounts conventions are remapped during the transform phase with a reconciliation report delivered to the customer.

Accounting customers in erp_ac_customers link to CRM contacts via erp_crm_contacts.id. We resolve the cross-reference at migration time so that the Epicor Customer Party record points to the correct CRM contact person (CustCnt). Billing address, payment terms, and credit limit from erp_ac_customers migrate to Epicor Customer maintenance screens. Open invoice balances and aged receivable data attach to the Customer record for AR initialization.

Vendor records in erp_ac_vendors migrate with billing address, company name, and contact email. Vendor-ledger entries (purchase transactions) link via vendor_id foreign key to the migrated VendPrt record. Epicor uses a Vendor maintenance record with Supplier contacts and payment terms. We preserve any 1099 reporting flags from WP ERP in the Epicor Vendor record for US tax compliance.

WP ERP invoices include line items, tax codes, payment status, and due dates. We flag open invoices (unpaid, partially paid) versus paid or voided invoices and map status to Epicor AR Invoice status (Open, Closed, Disputed). Open invoices migrate as Epicor AR Invoice records with aging; paid invoices migrate as historical records for financial audit trails. Invoices that reference non-existent customers or vendors are held in a reconciliation queue.

Manual journal entries stored in erp_ac_journal_entries with debit/credit line items migrate to Epicor GL Journal Entry. Each line maps the WP ERP account code (resolved via the COA migration) to the Epicor GL Account, with debit/credit amounts and descriptions preserved. Automated journal entries generated by the WP ERP Payroll module migrate as manual entries with a Payroll source reference, since Epicor handles payroll journal creation natively.

WP ERP inventory items (name, SKU, unit cost, current stock quantity, reorder level) extract from the Inventory extension if active. Epicor Kinetic uses a Part master (Part table) with PartMsc for miscellaneous costs and PartWhse for warehouse-specific stock levels. We map WP ERP stock quantity to Epicor PartWhse.OnHandQty, unit cost to PartMsc.MtlCost, and reorder level to PartWhse.MinimumQty. Stock movement history migrates as a separate transaction log for audit rather than as Epicor PartTran records.

The Document Manager extension ($2.49/mo) stores files in the WordPress media library or custom uploads directory. We export file metadata (filename, upload date, associated WP ERP entity) and re-upload the binary files to Epicor as attachments linked to the corresponding Part, Customer, Supplier, or Order record. File permissions and access controls do not migrate; Epicor's attachment security model applies post-migration.

The WP ERP Workflow extension stores automation rules as serialized PHP arrays in wp_options. These cannot be imported into Epicor Kinetic. We extract the trigger-action pairs (trigger module, condition logic, action steps) and deliver a written automation inventory with Epicor Kinetic equivalent recommendations: Business Process Automation for order-triggered workflows, MES workflow routing for shop floor automation, or Kinetic Dashboard alerts for conditional notifications. The customer's Epicor admin or implementation partner rebuilds them post-migration.