Migrate from Enterox Enterprise Cloud to Microsoft Dynamics 365 Business Central

Enterox Contact records map directly to Dynamics 365 Contact. Standard fields (name, email, phone, address) map to typed Contact fields. Custom properties configured in Enterox's entity structure map to custom fields on Contact. We resolve the parent Company (Account) reference before inserting Contacts so that the AccountId lookup is satisfied at import time. Enterox Contacts without a linked Company map as standalone Contacts with no AccountId.

Enterox Company records map to Dynamics 365 Account. The Company name becomes Account Name. We preserve the Company-Contact linkage by inserting Accounts before Contacts and resolving AccountId on each Contact at migration time. Any custom address or classification fields on the Company entity map to custom fields on Account.

Enterox Lead records from the Sales Automation module map to Dynamics 365 Lead. Lead status and owner assignment migrate as-is. Enterox does not have a separate Contact-to-Lead convert concept; Leads remain Leads at migration time and the Dynamics 365 admin manages qualification and conversion post-migration.

Enterox Opportunities map to Dynamics 365 Opportunity with pipeline stage, amount, and owner preserved. The Enterox pipeline stage name maps to a configured Opportunity Stage value in Microsoft Dynamics 365 Sales Process. We set the parent AccountId by resolving the Opportunity's linked Company at migration time. OwnerId resolves via email match to the destination Dynamics 365 User.

Enterox Quotations carry line items, pricing rules, and validity dates. They map to Dynamics 365 Quote, which is available from the Sales module. We map quotation line items to QuoteLineItem records, resolving the Product2 reference and PricebookEntry at migration time. Pricing rules from Enterox's multi-price-list engine are applied as UnitPrice values against the destination Standard Price Book.

Enterox Sales Orders link Products, Customers, and Warehouse inventory. They map to Microsoft Dynamics 365 Sales Order with order status and line items. Order lifecycle states differ between platforms; we map Enterox status values to the nearest Dynamics 365 Request Status or Inventory Status values and flag any states that do not have a direct equivalent for admin review.

Enterox Purchase Orders from the SCM module map to Dynamics 365 Purchase Order (Finance and Operations app) or to a custom Purchase Order entity (Business Central). Vendor references, line items, and approval statuses migrate, but multi-step approval workflows do not transfer as configured steps. We deliver a written document describing the approval chain structure observed in Enterox so the Dynamics 365 admin can configure matching approval workflows post-migration.

Enterox Product/Service Catalog entries (SKU, description, pricing, category) map to Dynamics 365 Product2 records. Standard Price Book entries are created during import. If the customer uses Enterox's multi-price-list feature, additional PricebookEntry records are created per price list against the same Product2.

Enterox Support Cases map to Dynamics 365 Case. Request type, priority, status, and assignee fields migrate to typed Case fields. Case conversations (internal notes and customer replies) map to Dynamics 365 Posts or EmailMessages linked to the Case. We flag any case priority or status values that do not have a direct Dynamics 365 equivalent.

Enterox's flexible entity framework means each deployment has uniquely named custom objects. We inspect the entity schema during the discovery phase with a live API call and build field-level mappings for each custom object, mapping to Dynamics 365 custom entities with __c suffixes. Lookup relationships between custom entities and standard objects (Contact, Account, Opportunity) are resolved at migration time using parent-record lookup tables. This step adds one to two days to the discovery phase but is required because there is no universal Enterox schema reference.

Enterox user records (name, email, role, access profile) map to Dynamics 365 User records by email match. Role structures differ significantly between Enterox and Dynamics 365 security roles, so we export the role assignments as a separate role-mapping document. The Dynamics 365 admin assigns security roles post-migration based on this inventory. We do not assign roles automatically because the permission models are not equivalent.

Attachments stored within Enterox entities are not accessible via the Developer API. Binary files associated with Contact, Company, Opportunity, or Quote records cannot be extracted through any documented endpoint. We export field text content where available and note that customers must use Enterox's native export UI for any binary attachments they specifically require. We do not migrate attachments as part of standard scope.

GPSVT vehicle tracking data and IoT sensor logs are stored in Enterox's proprietary device layer, which is not exposed by the standard Developer API. Historical GPS location data, route history, and telemetry events are not accessible for migration. Customers needing historical GPS data must engage Enterox support for a bespoke extract outside the scope of the Developer API. We flag this gap in the scoping document and note that FlitStack AI does not migrate IoT telemetry data.