Migrate from Omni ERP to Epicor Prophet 21

Omni ERP's Chart of Accounts maps directly to Epicor ERP's GL Account master. We preserve account numbering schemes and COA segment structures (if Omni uses a segmented chart) and remap account references in journal entries, AP, and AR during import. Epicor GL Account accepts segment-delimited codes (e.g., 1000-000-00) which we configure before the first import run. Account types (Asset, Liability, Equity, Revenue, Expense) map to Epicor's AcctType field.

Omni ERP Customer records map to Epicor ERP Customer with contact hierarchies, addresses, payment terms, and credit limits preserved. The Omni customer code becomes Epicor's CustID (the primary key). We preserve the parent-child relationship if Omni uses a customer hierarchy. Payment terms map to Epicor's Terms master. The primary Owner/User reference in Omni remaps to an Epicor Sales Rep record resolved by email match.

Omni ERP Vendor records map to Epicor ERP Vendor with contact hierarchies, addresses, and payment terms preserved. The Omni vendor code becomes Epicor's VendorID. We resolve the default GL Account assignments for AP liability and maintain 1099 flag settings if applicable to the US tax context.

Omni ERP Items with serial/batch tracking and multi-warehouse costing map to Epicor ERP Part records. The Omni Item Code becomes Epicor's PartNum; the Part Description, UOM, and cost layers migrate directly. Serial and lot tracking configuration maps to Epicor's LotMfgManaged and SerialMfg flags. We flag items with lot-level tracking for Epicor NumberSeq rule setup during the configuration phase. Omni's default warehouse assignment maps to an Epicor Site.

Omni ERP's multi-warehouse costing generates one PartWhse record per warehouse-site combination in Epicor. Each PartWhse carries the cost layer (average, standard, or lot-specific) and on-hand quantity from the corresponding Omni warehouse. We resolve Omni warehouse IDs to Epicor Site codes during the PartWhse import phase and flag any warehouse with inter-warehouse transfer pricing rules for manual review.

Omni ERP BOMs reference finished Items by code string. We export the Item-to-internal-ID mapping alongside the BOM export and apply it at import time so that all component references resolve against the Epicor Part master before the BOM structure is committed. Epicor BOMs operate within a Part Revision context; we create a Revision record in Epicor for each BOM version and populate JobMtl (materials) and JobOper (operations) accordingly. We preserve BOM versioning as a custom field if the customer's revision workflow requires it.

Omni ERP does not have native Routing or Work Center records, so no direct routing data exists to migrate. However, if Omni BOMs store operation sequences or estimated labor hours as custom properties, we map those to Epicor JobOper records with Work Center references that we provision as standard Work Centers in Epicor during configuration. The customer specifies the default Work Center for each operation type during scoping.

Open AP invoices in Omni ERP reference Vendor and GL Account records. We sequence AP import after Vendors and GL Accounts are live in Epicor and validate that all referenced VendorIDs and account codes exist in the destination before posting. Open AP invoice header and line data migrate to Epicor InvcHead and InvcDtl. Outstanding payment records migrate to APMemo with matching Vendor references.

Open AR invoices in Omni ERP reference Customer and GL Account records. We sequence AR import after Customers and GL Accounts are live. AR invoice header and line data migrate to Epicor ARInvcHead and ARInvcDtl. Outstanding AR payment memos migrate with matching Customer references. Credit memos and pre-payments map to Epicor credit memo types.

Historical journal entries in Omni ERP reference Chart of Accounts by code and include multi-currency amounts. We remap account codes, convert currency amounts using the exchange rate stored on the Omni transaction date, and flag any entries where the Omni rate differs from the Epicor rate table by more than a defined threshold (default 0.5%) for manual review. Epicor GLJrnEnt requires an open fiscal period; we validate that all historical entry dates fall within a configured Epicor fiscal year before posting.

Fixed Asset records in Omni ERP include acquisition cost, depreciation schedule, depreciation method, and asset category. We migrate FaAsset records to Epicor with the depreciation method preserved as a custom field if the Epicor FaDepMethod does not natively replicate the source method. Asset category maps to Epicor FaCategory. Accumulated depreciation posts as a GL journal entry after FaAsset import is validated.

Omni ERP Departments and Cost Centers referenced in journal entries and user assignments map to Epicor ERP Department records. We preserve the department hierarchy and remap department codes against the destination org structure, flagging any circular or orphaned references for the customer's Epicor admin to resolve before final reconciliation.

Omni ERP User records with role assignments and department affiliations map to Epicor ERP User accounts. We map Omni roles to Epicor Security Role IDs and flag any role assignments that exceed the Epicor edition's permission scope. Users without a matching Epicor User are held in a reconciliation queue for the customer's admin to provision before record import proceeds.

Omni ERP custom fields applied to Item or Customer objects map to Epicor ERP User-Defined (UD) fields on Part and Customer. We pre-create the UD field schema in Epicor during the configuration phase, including data type, length, and validation rules. The customer's Epicor admin reviews and approves the UD field mapping before the Part and Customer import phases run.