Migrate from Enterox Enterprise Cloud to Epicor Prophet 21

Enterox Contact records map to Epicor Customer through the Erp.Customer table, where each Customer is backed by an Erp.Party record. The Contact-Company linkage in Enterox resolves to CustNum on the Customer record, and we preserve the original Enterox contact ID in a custom field ent_contact_id__c for cross-system auditing. Email, phone, and address fields map directly; Enterox custom contact properties require the per-deployment schema discovery before field-level mapping is finalized.

Enterox Company records map to Epicor Customer as the organizational entity, distinct from individual Contact records when the Company has multiple points of contact. The Company-Contact hierarchy in Enterox becomes the Epicor Customer with multiple Erp.CustShipTo addresses. The Enterox Company type or industry classification maps to a custom Erp.Customer field or UD field for segmentation in Epicor reporting.

Enterox Lead records map to Erp.Lead in Epicor ERP. The Lead status, source, and owner fields migrate directly. Epicor Lead records carry a LeadScore field if the customer's Enterox deployment used scoring; we inspect the Enterox schema during discovery to capture any lead qualification fields and map them to the equivalent Epicor UD field.

Enterox Opportunity records represent sales pipeline entries that map to Epicor SalesOrder records in a pre-quote or quote state. The pipeline stage in Enterox maps to Epicor OrderHed.OrderStatus (in process, on hold), and Opportunity amount maps to OrderHed.TotalOrderValue. We resolve the parent Customer record (CustNum) before inserting the SalesOrder, and flag any Opportunity without a linked Company or Contact for manual resolution in the Epicor admin interface.

Enterox Quotations map to Epicor Erp.QuoteHed (header) and Erp.QuoteDtl (line items). The quotation pricing rules from Enterox's pricing engine migrate as QuoteHed pricing conditions, and line item SKUs resolve to Epicor PartNum through the Product mapping. Validity dates migrate to QuoteHed. QuoteDtl quantity and unit price map directly; Enterox multi-currency quotation amounts migrate to Epicor's QuoteHed.CurrencyCode with the exchange rate preserved in a UD field.

Enterox Products map to Epicor Erp.Part records, with PartNum sourced from Enterox SKU, Description from the product name, and UnitOfMeasure from Enterox's UOM field. Product categories map to Part.ProductGroupCode or a UD field for Epicor reporting hierarchy. For manufactured items, we flag the Part as Make or Buy and reserve the BOM and routing mapping for a subsequent Phase. Discontinued products from Enterox migrate as inactive Part records with DiscontinuedDate set.

Enterox Sales Orders map to Epicor Erp.OrderHed and Erp.OrderDtl. The customer CustNum must be resolved from the Enterox Customer mapping before OrderHed insert. Order status lifecycle states differ significantly between platforms, so we build an explicit status mapping table during scoping. Ship-to address from Enterox resolves to Erp.CustShipTo linked by Customer and ShipToNum. Order total and taxes migrate to OrderHed with tax codes mapped to Epicor's Tax Region configuration.

Enterox Purchase Orders map to Epicor Erp.POHeader and Erp.PODetail. The vendor reference in Enterox resolves to Epicor Vendor.VendorNum through the vendor mapping phase. Line items map to PODetail with PartNum linked for stocked items. Approval status from Enterox migrates to a UD field on POHeader since Epicor's approval workflow is configured separately; we document the original approval chain for the Epicor admin to rebuild in the approval configuration.

Enterox Support Cases map to Epicor Erp.SupportCase. Case priority and status from Enterox map to Epicor SupportCase.Severity and SupportCase.Status respectively. The assignee resolves to the Epicor User by email match against the User mapping phase. Conversation threads and case notes from Enterox migrate as SupportCase entries with timestamps preserved. Epicor assigns a CaseNum automatically on insert.

Enterox User records map to Epicor Erp.UserFile. We match by email address to Epicor's user identity. Role-based access from Enterox maps to Epicor Security assignments, but Enterox's entity-level access rules do not map 1:1 to Epicor's security model, so we export the full permission matrix as a written document and note that the customer's Epicor admin must configure roles manually in the Epicor Security Administration console.

Enterox custom entities discovered during schema inspection map to Epicor UD tables (UD01 through UD19 or custom Erp tables created via Epicor Studio). Each custom entity's fields are inspected during the discovery phase, and field types are mapped to equivalent Epicor data types (string to Character, integer to Integer, date to Date). Epicor UD tables require a UD field prefix convention (_c) and must be registered in the Epicor MetaData system before data insert. This phase runs after all standard object migrations to avoid schema dependency issues.

Enterox binary attachments stored within entity records are not accessible via the published Developer API. We do not migrate file attachments. Text content embedded in entity fields migrates as plain text fields in the corresponding Epicor object. Customers wishing to preserve attachments must export them manually from Enterox's native export UI or engage Enterox professional services for a bespoke data extract.

GPSVT vehicle tracking data and IoT sensor logs stored in Enterox's device layer are not exposed via the standard Developer API. This data is outside the API-accessible ERP data boundary. We flag this gap during scoping and advise that GPSVT data requires a separate extraction from Enterox's device management system or manual export. FlitStack AI does not migrate IoT telemetry as it is not CRM or ERP transactional data in the standard object sense.