Migrate from Enterox Enterprise Cloud to Infor CloudSuite Corporate

Enterox Contact records with standard fields (name, email, phone, address) and any custom properties map to Infor CloudSuite Business Partner records with a Contact role designation. The HubSpot-style Company-Contact linkage in Enterox is preserved as the Business Partner relationship on the Contact record. We perform schema discovery against the customer's Enterox API instance before finalizing field-to-attribute mapping because entity field names vary per deployment.

Enterox Company records map to Infor CloudSuite Business Partner entities with Supplier or Customer classification depending on the entity's role in the Enterox deployment. We resolve the Company-Contact linkage as the Business Partner-to-Contact relationship in Infor. The domain or website field maps to the Business Partner's address or contact reference.

Enterox Lead records from the Sales Automation module map to Infor CloudSuite Prospect or Customer Prospect records, carrying pipeline stage, source attribution, and owner assignment. Lead status maps to the Infor CRM stage values. If Infor CloudSuite CRM is not in scope, Leads are mapped to Contact records without a Business Partner attachment.

Enterox Opportunity records carrying pipeline stage, amount, probability, expected close date, and owner map directly to Infor CloudSuite Opportunity. Stage sequencing is preserved by mapping each Enterox pipeline stage to the corresponding Infor Sales Process stage name. Owner assignment resolves by email against the Infor User table during migration.

Enterox Quotations with line items, pricing rules, validity dates, and multi-price list support map to Infor CloudSuite Quotation records. Pricing engine differences (Enterox multi-price list vs Infor standard price book) are resolved by selecting the primary price list as the target during scoping. Validity dates and quotation status migrate as-is; approval workflow status is flagged for manual reconstruction in Infor.

Enterox Sales Orders link Products, Customers, and Warehouse inventory with order status and fulfillment tracking. Order lifecycle states differ across platforms, so we map the Enterox status to the closest Infor Sales Order status and flag any multi-step fulfillment workflows that require reconstruction. Historical fulfilled orders migrate as closed records.

Enterox Purchase Orders in the SCM module map to Infor CloudSuite Purchase Orders with vendor references, line items, quantities, and approval statuses. Multi-step approval workflows in Enterox do not have a direct Infor equivalent, so we export the approval status as a read-only field and document the approval routing for your Infor admin to configure in Infor Workflow or ION.

Enterox Product and Service Catalog entries with SKU, description, pricing, category, and UOM map to Infor CloudSuite Item (for products) and Service (for services) records. Product categories map to Infor item groups. Multiple price lists in Enterox are consolidated to the primary price book with secondary price lists noted for manual configuration in Infor.

Enterox Support Cases with request type, priority, status, assignee, and conversation history map to Infor CloudSuite Service Management Case records. Case states map to Infor Case Status values. Conversation threads migrate as Note or EmailMessage records linked to the Case. SLA fields that cannot be mapped directly are flagged for Infor Service Management configuration post-migration.

Enterox allows custom entity definitions through its framework, and each customer deployment may have differently named custom fields and data types. We inspect the live entity schema during discovery, build a field-level mapping for each custom object, then use Infor's Data Catalog to generate equivalent custom object schemas (from connection point or sample data) in the target environment. This requires schema discovery against the customer's specific Enterox API instance before finalizing any custom object mapping.

Enterox User records with name, email, role, and access profile resolve by email match to Infor OS User records. Enterox's entity-level access rules and user profiles do not map 1:1 to Infor's role-based permission model, so we export the full permission assignment as a structured text file and note gaps for manual role review in Infor Identity Management post-migration.