Migrate from Genius ERP to Epicor Prophet 21

Genius ERP Work Orders are the central production record and map to Epicor Kinetic Jobs. We migrate Work Order headers (job number, description, status, start and due dates), operations (routing steps with work centers, estimated hours, and actual hours), and material allocations (material requisitions linked to the BOM). Status preservation maps Genius's open/in-progress/complete/closed states to Epicor Kinetic JobHead.JobClosed and JobOper.OprComplete flags. Work Orders with active engineering changes carry the effectivity date and revision number from the linked BOM, which we resolve during the BOM traversal phase before Job import.

Genius ERP multi-level BOMs with nested assemblies and subassemblies map to Epicor Kinetic Part.BOM records. We preserve the full hierarchy including CAD-linked component relationships, revision numbers, and effectivity dates (from and to revision dates). BOM versions in Genius ERP that are flagged as alternate or substitute configurations map to Epicor's PartMtl record with the AltMtlJobNum or RelatedOperation reference. Multi-level nesting depth above five levels requires explicit scoping because Epicor's standard BOM explorer UI throttles rendering on very deep trees; we document any depth-reduction strategy during scoping.

Genius ERP Job Costing tracks actual vs. estimated costs per Work Order across labor, materials, and overhead allocations. Epicor Kinetic separates actual cost tracking into two paths: Project Costing (if the customer licenses Epicor Project Management) and Labor and Material transactions posted directly to the Job. We export the full cost ledger per Work Order — labor clock entries, material issues, and overhead postings — and reconstruct them as JobMtl, JobOper, and LaborDtl records in Epicor. Overhead allocation rates in Genius ERP map to Epicor's Resource Group overhead rate definitions, which the customer configures during the Epicor setup phase.

Genius ERP Items, stock quantities, warehouse locations, and reorder points migrate to Epicor Kinetic Part and PartBin. We handle serial and lot number traceability where present in the source. Open purchase orders attached to inventory items are flagged separately as they represent live procurement commitments that require vendor and expected-delivery-date reconciliation before Epicor PO creation. Inventory valuation method (FIFO, average, standard) in Genius ERP maps to Epicor's costing lot method on Part.CostMethod.

Genius ERP Customer records map to Epicor Kinetic Customer, including contact information, account hierarchies, credit limits, and payment terms. Where Genius CRM fields differ from the Epicor Customer schema, we apply field-level mapping and preserve any custom fields as Epicor UD fields on Customer. Customer-specific pricing and discount schedules migrate as Part.CustXRef and CustomerPriceLxs records in Epicor.

Genius ERP Sales Orders and Quotes map to Epicor Kinetic SalesOrder and OrderDtl. Open orders migrate with order status preserved. Line items carry the link to the parent Work Order (Genius Quote-to-Work Order) as Epicor's LinkToOrder field on JobHead if production has been released. Historical quotes that were never converted are scoped separately — the customer chooses whether to import them as Inactive Quotes in Epicor or as a reference-only dataset for manual re-entry. Pricing, discounts, and multi-currency amounts map directly where both systems store currency on the order header.

Open purchase orders migrate to Epicor Kinetic POHeader and PODetail with vendor details, line items, expected delivery dates, and received-vs.-ordered quantities. Genius ERP purchase order statuses (pending, sent, partial, complete) map to Epicor's POStatus values (open, partial, complete). Closed POs are treated as historical records and scoped separately — the customer specifies how many years of closed PO history to retain as reference records versus archival-only. Purchase contracts and blanket PO headers in Genius ERP map to Epicor Kinetic POHeader as Blanket or Contract type.

Genius ERP's G/L is intentionally lightweight and lacks multi-entity posting and detailed cost center allocation. We export all posted journal entries, but the destination's chart of accounts in Epicor Kinetic must be structured before import — the customer defines the account code mask (segment structure) during Epicor implementation. Journal entries linked to Work Orders or inventory movements may reference Genius ERP-specific account codes that require manual mapping or a transitional account during cutover. We flag these cross-references and deliver a journal mapping spreadsheet.

Genius ERP user accounts, role assignments, and permission sets export as Epicor Kinetic User records. Active vs. inactive status is preserved. Permissions are mapped to Epicor's Kinetic security groups (UserSecGrp and CompanySecurity) rather than a direct role-to-role transfer because Genius ERP's opinionated role model (Estimator, Production Manager, Shop Operator, Sales) does not map 1:1 to Epicor's granular security configuration. We deliver a security mapping matrix for the customer's Epicor admin to apply during user provisioning.

Genius ERP custom field definitions and their values migrate as Epicor Kinetic UD fields (the ZDataField / ZDataTable model in Epicor 10.x, Extended User Defined Fields in Kinetic). We preserve field types (text, numeric, date, picklist) and map them to the equivalent Epicor data type. Epicor's UD field architecture requires the migration user to write a Business Processing Methodology (BPM) to populate UD fields on certain record events — we document this requirement and recommend the Epicor admin implement it during the configuration phase rather than during data load to avoid mid-import BPM conflicts.

Quality management records in Genius ERP including inspection results, non-conformance logs, and lot traceability data migrate to Epicor Kinetic's Quality Management module if the customer licenses it. Record headers and structured inspection data move as NonConf and RMA records. Unstructured inspection notes migrate as attachments to NonConf. Lot traceability links map to PartLot and PartLotCust records in Epicor. If Quality Management is not licensed, we flag the object as out-of-scope and recommend the customer evaluate the module before migration.

Documents attached to Work Orders, BOMs, or Customers export as binary blobs via the Genius ERP REST API or server-side file share. We preserve the original filename, object association, and upload date. Large CAD files are chunked to avoid API payload limits. Epicor Kinetic stores attachments as External Nesting (file share) or in the Epicor Data Library depending on the deployment model chosen during Epicor implementation. We align the attachment storage strategy during discovery.