Migrate from Runple to Epicor Prophet 21

Runple Customer records (name, address, tax ID, payment terms) map to Epicor Customer. The Runple customer code becomes Epicor's CustID as the primary key. Tax identification numbers from Runple map to Epicor's Tax Region ID and are validated against Epicor's tax configuration during import. We preserve any Runple custom properties (e.g., credit limit flags, commission structures) as UD fields on Customer since Epicor supports user-defined columns on the Customer table.

Runple Product catalog entries (SKU, name, description, unit price, cost) map to Epicor Part. Runple's item-level cost and margin data map to Part.UnitPrice and Part.StandardCost. We extract all item-level fields including any custom properties for product classification, then map them to Epicor's Part table with UD columns for any Runple-specific attributes that do not map to standard Epicor Part fields.

Runple Invoices (header, line items, tax codes, totals, payment status) map to Epicor ARInvoice and InvoiceLine. The Runple invoice number sequence maps to Epicor's InvoiceNum. Tax calculations from Runple must be validated against Epicor's TaxConnect engine since Runple EU VAT rates may differ from Epicor's configured rates. We preserve invoice date, due date, and currency on the header, and line-level quantities and prices on the detail rows.

Runple Payment records (linked to invoices, amounts, dates, methods) map to Epicor CashHead with a CashDtl detail line. We resolve the ARInvoice reference during import so payments apply to the correct open AR item. Cash method (check, bank transfer, credit) maps to Epicor's PaymentMethod field. Historical payments migrate as posted records; open payments attach to the corresponding ARInvoice open item.

Outstanding payables and receivables require Epicor's aging bucket configuration. We extract current open items from Runple with aging buckets (current, 30, 60, 90+) and map them to Epicor's ARHead/APHead open records. Due dates and aging analysis migrate into Epicor's credit management module. Any pre-payments or unapplied cash on the Runple ledger map to Epicor Payment records with no invoice reference for the customer's AP/AR team to apply.

Runple Stock movement records (quantity changes, dates, warehouse locations) map to Epicor PartBin. Current stock levels migrate as PartBin OnHandQty. Movement history (adjustments, receipts, shipments) migrates as Epicor PartTran records with the appropriate TranType (ADJ-CST, STK-MTL, etc.). Runple warehouse location codes map to Epicor Warehse and Bin fields. For high-volume PartBin migrations, we use Epicor DMT with chunked batches to avoid timeouts.

Runple user accounts with roles and permissions do not map directly to Epicor's UserAccount model. We extract role assignments from Runple, then map them to Epicor's UD Codes (for department and job classification) and document the nearest Epicor security group for each Runple role. Epicor User provisioning is done manually by the customer's admin because Epicor requires active directory or LDAP integration for user authentication; we provide the role mapping document for the admin to assign during setup.

Runple time tracking data (hours, dates, employee assignments) maps to Epicor LaborDtl if the destination Epicor environment includes the Labor module. For manufacturing environments without Labor, we map time records to UD fields on the Part or JobOper tables, or export as a CSV reference table. Not all Epicor deployments include time-tracking, so we confirm module availability during scoping.

Runple stores commission and salary data as HR-adjacent records that have no native Epicor ERP equivalent (Epicor is a manufacturing and distribution ERP, not an HRMS). We map commission rates and salary records to Epicor UD codes on the Customer or SalesRep table, or export them as a reference CSV for the customer's finance team to maintain outside the ERP. These records require a manual compliance review for payroll data handling before go-live.

Runple EU VAT codes (Austrian and German VAT rates, reverse-charge rules) must be manually reviewed and remapped in Epicor's Tax Connect engine. We extract the full Runple tax code table and deliver a tax mapping document that maps each Runple tax code to the corresponding Epicor TaxCode and TaxRate combination. Reverse-charge handling for B2B intra-EU transactions requires explicit Epicor configuration and is flagged as a manual compliance step before go-live.

Runple Chart of Accounts entries map to Epicor GLAccount. Account codes, descriptions, and account types migrate to Epicor's COA structure. We preserve account balances as of the migration cutover date as opening balances in Epicor's GLAccount table. Any Runple custom account classifications (e.g., cost center segments) map to Epicor COA segments if the customer's Epicor deployment uses a segmented chart of accounts.

Runple custom properties for tax codes, commission structures, and item classification that do not map to standard Epicor fields are preserved as UD (user-defined) columns on the relevant Epicor tables (Part, Customer, InvoiceLine) or as UD Codes for categorical data. We document each Runple custom property, its data type, and the recommended Epicor UD column or Code value during the scoping phase.