Migrate from Enterox Enterprise Cloud to Dolibarr ERP

Enterox Contacts map to Dolibarr Contact records. The mapping target depends on whether the Contact is linked to a Company: if yes, we map to Dolibarr Contact attached to the ThirdParty; if standalone, we map directly to Dolibarr ThirdParty with the isIndividual flag set. Standard fields (name, email, phone, address) map directly. Any custom Contact properties discovered during schema discovery map to Dolibarr extrafields on the Contact object. We preserve the Enterox contact owner as a text field if the user cannot be matched in Dolibarr's User table.

Enterox Company records map to Dolibarr ThirdParty with the isIndividual flag unset. Company name becomes the ThirdParty name, domain becomes the website field, and address fields map to the address block. The Company-Contact linkage is preserved by linking the migrated Contact record to the migrated ThirdParty via the socid foreign key in Dolibarr's database. Dolibarr ThirdParties serve as both the Company/Account and the customer-parent for Contacts.

Enterox Leads in the Sales Automation module map to Dolibarr ThirdParty records with the client status field set to 2 (Prospect). Lead status and assignment data migrate to extrafields on the ThirdParty if needed. Dolibarr does not have a separate Lead object equivalent to Salesforce; unqualified prospects live in the ThirdParty table with a prospect status rather than a separate record type.

Enterox Opportunities with pipeline stage, amount, and owner map to Dolibarr commercial opportunities if the customer has the Commercial module enabled. Stage names from Enterox map to Dolibarr OppStatus values. Amount and probability migrate to amount and opp_percent fields. If the Commercial module is not enabled in the target Dolibarr instance, Opportunities map to Dolibarr Proposals (propal) in draft status as a holding object, and the customer enables the module before the records are converted.

Enterox Quotations with line items, pricing rules, and validity dates map to Dolibarr Proposals. The quotation status in Enterox maps to the dolibarr status field (draft, validated, closed won, closed lost). Line items map to propaldet rows with product reference, description, quantity, UnitPrice, and TotalPrice. Multiple price lists in Enterox's pricing engine map to Dolibarr's price list conditions stored on the Proposal header.

Enterox Sales Orders link Products, Customers, and Warehouse inventory and map to Dolibар Order records. Order status (pending, confirmed, fulfilled, cancelled) maps to Dolibarr commande status. Line items map to commanded rows. Order lifecycle states differ between platforms; we maintain a status mapping table during scoping and flag any multi-step fulfillment workflows that will require manual reconstruction in Dolibarr's order workflow configuration.

Enterox Purchase Orders in the SCM module map to Dolibarr Supplier Orders. Vendor references map to the linked ThirdParty (socid), line items to fourn_lignedet rows, and approval statuses to the status field. Any multi-step approval workflows configured in Enterox are documented as a workflow map in the handoff inventory; Dolibarr's approval workflow for supplier orders requires reconfiguration post-migration.

Enterox Product/Service Catalog entries with SKU, description, pricing, and category map to Dolibarr Product records. The product_type field distinguishes between goods (0) and services (1). Category assignments from Enterox map to Dolibarr categories linked via the categorie_association table. Stock levels from Enterox's inventory module map to the product_stock table if the Stock module is enabled in Dolibarr.

Enterox Support Cases with request type, priority, status, and assignee map to Dolibarr Interventions if the Interventions module is enabled. Case request types map to the intervention type field; priority and status map to the corresponding Dolibarr fields. Assignee maps to the fk_user_assign field. Case conversations and thread history are not migrated because Dolibarr's Intervention object does not store threaded communications; we export them as Notes attached to the Intervention record.

Enterox allows arbitrary custom entity definitions that do not have a direct Dolibarr equivalent. We inspect the custom entity schema during discovery, identify the parent Enterox entity it relates to, and map the custom fields to extrafields on the closest Dolibarr standard object. Custom entities that represent standalone objects rather than extensions of standard ones are documented as requiring either a custom Dolibarr module (PHP development) or restructuring as Dolibarr Projects with extrafields for the custom data points.

Enterox User records with name, email, role, and access profile map to Dolibarr User records and Permission Groups. Enterox's profile-based permission model does not map 1:1 to Dolibarr's permission system; we export the full role assignment matrix and map each Enterox permission to the nearest Dolibarr permission flag. Manual role review is required post-migration because Enterox entity-level access rules (which Dolibarr does not natively support) may need to be replaced with Dolibarr's module-level permission toggles.

Enterox entity attachments are not accessible via the published Developer API. Binary files stored within Enterox entities cannot be extracted programmatically. We do not migrate attachments; we export text content from entity fields as a fallback. Customers requiring attachment migration must use Enterox's native export UI manually or engage Enterox professional services for a bespoke data extract.