Migrate from Focus ERP to Epicor Prophet 21

Account structures, parent-child hierarchies, and account types export cleanly via Focus ERP's database layer. We preserve account codes and descriptions exactly, including any segment columns used for cost-center or department breakdown. Epicor Kinetic's GL Account structure supports multi-segment charts natively; we map Focus ERP segments to Epicor dimension codes and validate the resulting natural-account rollups post-load. Account types (Asset, Liability, Equity, Revenue, Expense) map directly to Epicor GL Account types.

Customer master records including billing addresses, payment terms, and tax registration numbers migrate 1:1 to Epicor Customer. We deduplicate on customer name and address keys where multi-company Focus ERP instances created duplicate entries. Ship-to addresses map to Epicor ShipTo records linked to the parent Customer. Credit limits and payment terms migrate as custom fields if the Epicor customer's credit-hold configuration differs from Focus ERP's terms model.

Vendor master records map directly to Epicor Supplier with all address, payment-term, and tax-registration fields transferred. Focus ERP's vendor-level approval limits and multi-bank-account configurations are captured as custom fields on Supplier in Epicor since Epicor's native approval workflow is configured differently. Vendor type classifications (one-time, blanket, regular) map to Epicor Supplier Type with a custom field flag for any that cannot be expressed natively.

Outstanding receivable records carry invoice numbers, due dates, and outstanding amounts. We extract each open AR line with its payment-history reference, flag records with partial payments requiring split-line treatment, and ask the customer to confirm the intended resolution (pay down oldest first, largest first, or pro-rata) before committing the load. Focus ERP credit memos attached to open AR lines are carried as negative invoice lines in Epicor AR.

Open payable records require the same split-line treatment as AR. Focus ERP invoices with multiple partial payments need line-level resolution against the vendor's outstanding balance. We extract full payment history and flag any AP records where Focus ERP's invoice date differs from the posting date by more than 30 days, as Epicor's AP aging report will expose the discrepancy differently. Prepayments and retention withholdings are carried as separate AP adjustments in Epicor.

Item masters with SKUs, descriptions, cost prices, selling prices, and stock levels export directly to Epicor Part records. Focus ERP's min/max replenishment rules are preserved as custom numeric fields (min_reorder_qty__c, max_reorder_qty__c) because Epicor's replenishment logic uses different rulesets (Min-Max, MPS, or Kanban) that the customer's admin configures post-migration. Lot and serial number configurations migrate as Part Plant stocking attributes. Stock levels from Focus ERP's multi-warehouse structure map to Epicor Warehse/PartWhse records.

Open and historical purchase orders map to Epicor PO Header and PO Detail. Focus ERP's line-item tax codes and discount percentages vary by country configuration and require explicit value-mapping before load; we produce a tax-code cross-reference table during discovery. Closed POs migrate as historical records only (Epicor does not allow PO status to return to open). Release-based POs in Focus ERP map to Epicor PO Release lines with the release number preserved as a custom field.

Sales orders map to Epicor OrderHed (header) and OrderDtl (detail). Focus ERP's order-type classification, payment terms, and ship-via codes map to Epicor OrderHed fields; line-level pricing, discount percentages, and tax codes require the same value-mapping treatment as PO lines. We preserve Focus ERP's order acknowledgments and quote references as custom fields on OrderHed since Epicor's quote-to-order conversion is a separate process. Back-order quantities are carried forward as open OrderDtl lines in Epicor.

Focus ERP's field-service and job-tracking records carry custom status workflows, technician assignments, and job-percentage progress fields. These map to Epicor JobHead (job header with status and project reference), JobMtl (material requirements), and JobOper (operations and labor). Focus ERP status values map to Epicor JobHead.JobStatus codes with a custom field original_focus_status__c for audit. Technician assignments from Focus ERP's field-service module map to JobOper with the resource code preserved. Percentage-complete values are converted to Epicor's operations-level percent-complete tracking on JobOper.

Asset registers include acquisition dates, depreciation methods, and book values from Focus ERP. Epicor Kinetic calculates depreciation schedules based on its fiscal year settings, so we extract the original depreciation method, useful life, and accumulated depreciation as custom fields on the Epicor Asset record and recalculate the first depreciation run post-migration before closing the period. Any mid-year acquisitions in the current fiscal year require manual adjustment of the first depreciation amount in Epicor.

User accounts export from Focus ERP's user table. Role naming conventions differ between Focus ERP versions and Epicor, so we extract role assignments as user-level permissions rather than role templates and map them to Epicor's permission model during migration. Any Focus ERP role with no direct Epicor equivalent is documented in a permissions matrix for the customer's admin to configure in Epicor Security Administration post-migration.

Custom fields added via Focus ERP's form builder are stored in extended tables. We extract these as key-value pairs and attach them as Epicor UD (User-Defined) fields on the corresponding tables (Part, Customer, Supplier, OrderHed, JobHead, etc.). We flag any Focus ERP custom fields that reference other custom objects (cross-lookups) because Epicor's UD field model does not natively support cross-table references without custom Business Objects, which require a separate development engagement.