Migrate your Enterox Enterprise Cloud data

Contacts are standard entities in Enterox's CRM module. We export them with standard fields (name, email, phone, address) and any custom properties configured in the entity structure. The API returns them as structured JSON objects.

Company records are stored as separate entities linked to Contacts. We preserve the Company-Contact linkage during migration, mapping it to the destination's equivalent Account/Company object.

Leads are managed in the Sales Automation module alongside Opportunities. We export lead records with their status and assignment data, merging into Contacts on destination platforms that do not distinguish a separate Lead object.

Opportunities are part of the Sales Automation solution and carry pipeline stage, amount, and owner fields. We map these to Deals or Opportunities in the destination CRM and preserve stage sequencing.

Quotations carry line items, pricing rules, and validity dates. The platform's pricing engine supports multiple price lists; we map quotation line items to destination Quote or ProForma Invoice objects and flag any pricing logic that cannot be represented in the target.

Sales Orders in Enterox link to Products, Customers, and Warehouse inventory. Order status and fulfillment tracking data must be mapped carefully since order lifecycle states differ across platforms.

Purchase Orders are part of the SCM module. They include vendor references, line items, and approval statuses. We export these as-is but flag any multi-step approval workflows that require reconstruction in the destination.

Enterox maintains a Product/Service Catalog with pricing, SKU, description, and category fields. We export the catalog as a flat item list and map to the destination's equivalent product or item entity.

Customer Support Services stores cases with request type, priority, status, and assignee. We export case records and conversations, mapping case states to the destination ticket object and flagging any custom case fields.

Enterox allows custom entity definitions through its framework. We inspect the entity schema during the discovery phase and build field-level mappings for each custom object, as naming and data types vary by deployment.

Attachments stored within Enterox entities are not accessible via the published Developer API. We do not migrate binary attachments; we export text content from entity fields and note that customers must manually transfer file attachments or use the platform's export UI.

The GPSVT module stores vehicle telemetry and location history in a proprietary format tied to the IoT layer. This data is not exposed via the standard API and requires a separate extraction process that Enterox does not publicly document.

User records include name, email, role, and access profile. Role structures differ significantly between Enterox and standard destination platforms, so we map permissions to the closest available destination role model and flag any that require manual reassignment.

Telephony integration logs from the SMS and IVR module are not exposed via the API. These records are not migrated; they remain in Enterox's telephony system and are outside the ERP data scope.